Lucent Technologies DMX Access Multiplexer User Operations Guide

Metropolis

®

DMX Access Multiplexer

Release 6.0

User Operations Guide

365-372-301 R6.0

CC109587105

Issue 15

January 2006

Copyright © 2006 Lucent Technologies. All Rights Reserved.

This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts or licensing, without the express written consent of Lucent Technologies and the business management owner of the material.

Trademarks

All trademarks and service marks specified herein are owned by their respective companies.

Notice

The information in this document is subject to change without notice. Although every effort has been made to make this document as accurate, complete, and clear as possible, Lucent Technologies and its predecessors assume no responsibility for any errors that may appear in this document.

Federal Communications Commission (FCC) Notification and Repair Information

This equipment is designed to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions manual, may cause interference to radio communications. Operation of this equipment in a residence is likely to cause harmful interference, in which case, the user will be required to correct the interference at his own expense.

Security

In rare instances, unauthorized individuals make connections to the telecommunications network. In such an event, applicable tariffs require that the customer pay all network charges for traffic. Lucent Technologies and its predecessors cannot be responsible for such charges and will not make any allowance or give any credit for charges that result from unauthorized access.

Limited warranty

The terms and conditions of sale will include a 1-year warranty on hardware and applicable software.

Ordering information

To order more copies of this document or other Lucent documents, please contact the Customer Information Center (CIC) at CIC Web-Site

( http://www.lucentdocs.com

).

Technical support telephone number

For technical assistance, call Lucent Technologies’ Technical Support Services (TSS) at 1-866-LUCENT8 (866-582-3688). This number is monitored 24 hours a day.

Information product support telephone number

You can also call this telephone number to provide comments on the Metropolis

®

DMX Access Multiplexer or to suggest enhancements.

Comments or suggestions for enhancements can also be emailed to the Comments Hotline ( [email protected]

) and/or entered online at the

Online Comment Form ( http://www.lucent-info.com/comments/enus/ ).

Contents

About this information product

Purpose

..........................................................................................................................................................................................................

xxxv

Reason for reissue

..................................................................................................................................................................................

xxxv

Safety information

..................................................................................................................................................................................

xxxv

Intended audience

...................................................................................................................................................................................

xxxv

How to use this information product

.........................................................................................................................................

xxxv

Conventions used

.................................................................................................................................................................................

xxxvii

User interface to system

................................................................................................................................................................

xxxviii

Using procedures

................................................................................................................................................................................

xxxviii

Related information

.............................................................................................................................................................................

xxxix

Information product support

...................................................................................................................................................................

xl

Technical support

..........................................................................................................................................................................................

xl

How to order

....................................................................................................................................................................................................

xl

How to comment

.........................................................................................................................................................................................

xli

1

Safety

Overview

.........................................................................................................................................................................................................

1-1

Structure of hazard statements

...........................................................................................................................................................

1-2

General notes on safety

..........................................................................................................................................................................

1-4

Laser safety

....................................................................................................................................................................................................

1-6

Electrostatic discharge

..........................................................................................................................................................................

1-14

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 iii

Contents

2

3

4

Save these safety instructions

..........................................................................................................................................................

1-17

Software installation and upgrades, and database backup procedures

Overview

.........................................................................................................................................................................................................

2-1

Before you begin

........................................................................................................................................................................................

2-2

Procedure 2-1: Install software generic (initial) via FTAM

............................................................................................

2-3

Procedure 2-2: Install software generic (initial) via FTP

...............................................................................................

2-21

Procedure 2-3: Upgrade software generic via FTAM

.......................................................................................................

2-40

Procedure 2-4: Upgrade software generic via FTP

............................................................................................................

2-72

Procedure 2-5: Upgrade software generic via FTTD (6.0.0 to 6.0.x)

.................................................................

2-109

Procedure 2-6: Copy software generic to a remote shelf

............................................................................................

2-115

Procedure 2-7: Apply software generic

..................................................................................................................................

2-120

Procedure 2-8: Backup and restore NE database via FTP

..........................................................................................

2-123

Procedure 2-9: Backup and restore NE database via FTTD

.....................................................................................

2-135

Procedure 2-10: Backup and restore NE database via FTAM

.................................................................................

2-150

Acceptance procedures

Overview

.........................................................................................................................................................................................................

3-1

Before you begin

........................................................................................................................................................................................

3-2

Procedure 3-1: Accept Metropolis

®

DMX shelf (looped-back)

....................................................................................

3-3

Procedure 3-2: Accept Metropolis

®

DMX network

.............................................................................................................

3-9

Install and provision circuit packs/OLIUs procedures

Overview

.........................................................................................................................................................................................................

4-1

Before you begin

........................................................................................................................................................................................

4-3

Procedure 4-1: Install SYSCTL (LNW2) in new Metropolis

®

DMX shelf

..........................................................

4-4

Procedure 4-2: Install OLIU circuit packs in Main slots

..................................................................................................

4-7

Procedure 4-3: Install OLIU circuit packs in Function slots

.......................................................................................

4-14

Procedure 4-4: Provision OLIU circuit packs/ports for service

.................................................................................

4-22

.................................................................................................................................................................................................................................

iv 365-372-301 R6.0

Issue 15, January 2006

Contents

5

6

Procedure 4-5: Provision unprotected operation on optical ports

.............................................................................

4-26

Procedure 4-6: Install DS3/EC1 circuit packs

.......................................................................................................................

4-32

Procedure 4-7: Provision DS3/EC1 circuit packs/ports for service

.........................................................................

4-37

Procedure 4-8: Install DS1/E1 circuit packs

..........................................................................................................................

4-39

Procedure 4-9: Provision DS1/E1 circuit packs/ports for service

.............................................................................

4-42

Procedure 4-10: Install TMUX circuit packs

.........................................................................................................................

4-45

Procedure 4-11: Provision TMUX ports for service

.........................................................................................................

4-48

Procedure 4-12: Install 10/100 Ethernet circuit packs

.....................................................................................................

4-50

Procedure 4-13: Install Gigabit Ethernet circuit packs

....................................................................................................

4-54

Procedure 4-14: Provision Ethernet circuit pack/LAN port/VCG for service

...................................................

4-59

Procedure 4-15: Install pluggable transmission modules

...............................................................................................

4-62

Procedure 4-16: Install LNW80 switch pack

.........................................................................................................................

4-72

Procedure 4-17: Install Fibre Channel circuit packs

.........................................................................................................

4-74

Procedure 4-18: Provision Fibre Channel circuit pack/Data port/VCG for service

.......................................

4-77

Procedure 4-19: Provision pluggable transmission module

..........................................................................................

4-80

Procedure 4-20: Provision non-volatile memory cards

....................................................................................................

4-82

Procedure 4-21: Provision STS-n/VT1.5 tributary

.............................................................................................................

4-83

Procedure 4-22: Change circuit pack mode of LNW26B, LNW28, LNW77, or LNW121B-159B OC-48

OLIU circuit packs

.............................................................................................................................................................................

4-84

Node turnup procedures

Overview

.........................................................................................................................................................................................................

5-1

Before you begin

........................................................................................................................................................................................

5-2

Procedure 5-1: Equip new Metropolis

®

DMX Access Multiplexer with OLIUs in Main slots

...............

5-3

Procedure 5-2: Equip new Metropolis

®

DMX Access Multiplexer with LNW80 switch packs in Main slots

...............................................................................................................................................................................................................

5-10

System configuration procedures

Overview

.........................................................................................................................................................................................................

6-1

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 v

Contents

Before you begin

........................................................................................................................................................................................

6-2

Procedure 6-1: Provision system configuration parameters

.............................................................................................

6-3

Procedure 6-2: Provision shelf/system parameters

................................................................................................................

6-7

Procedure 6-3: Provision miscellaneous discrete inputs and outputs

......................................................................

6-11

Procedure 6-4: Provision DCC terminations

..........................................................................................................................

6-13

Procedure 6-5: Network Element synchronization provisioning

...............................................................................

6-16

Procedure 6-6: Provision system alarm configuration

.....................................................................................................

6-33

Procedure 6-7: Provision new alarm severity assignment profile

.............................................................................

6-34

Procedure 6-8: Change existing alarm severity assignment profile

.........................................................................

6-36

Procedure 6-9: Delete alarm severity assignment profile

..............................................................................................

6-39

Procedure 6-10: Assign alarm severity assignment profile

...........................................................................................

6-41

Procedure 6-11: Evaluate bandwidth utilization

..................................................................................................................

6-44

Procedure 6-12: Optimize backplane bandwidth

.................................................................................................................

6-46

7

System administration procedures

Overview

.........................................................................................................................................................................................................

7-1

Before you begin

........................................................................................................................................................................................

7-3

Procedure 7-1: Provision system administration parameters

..........................................................................................

7-4

Procedure 7-2: Change your own password

...........................................................................................................................

7-10

Procedure 7-3: Edit, delete, or enter a user’s login

...........................................................................................................

7-12

Procedure 7-4: Enable/disable lockout security state

........................................................................................................

7-16

Procedure 7-5: Provision system SNMP management features

..................................................................................

7-17

Procedure 7-6: Edit, delete, or enter SNMP users

..............................................................................................................

7-20

Procedure 7-7: Allow/inhibit autonomous message reporting

.....................................................................................

7-24

Procedure 7-8: Create or edit login banner

.............................................................................................................................

7-26

Procedure 7-9: Set NE defaults — alarm gateway, alarm group, remote NE status, FTP/FTTD, security and history log thresholds

..............................................................................................................................................................

7-28

Procedure 7-10: Set date and time

...............................................................................................................................................

7-33

.................................................................................................................................................................................................................................

vi 365-372-301 R6.0

Issue 15, January 2006

Contents

8

9

Procedure 7-11: Set/change system TID

...................................................................................................................................

7-38

Procedure 7-12: Enable/disable OSI on an IAO LAN port

..........................................................................................

7-39

Procedure 7-13: Provision network layer 3 parameters

..................................................................................................

7-40

Procedure 7-14: Set TARP parameters

.......................................................................................................................................

7-43

Procedure 7-15: Provision TCP/IP and Proxy ARP on an IAO LAN port

.........................................................

7-46

Procedure 7-16: Provision/enable/disable the NE as a TL1 TCP/IP GNE

..........................................................

7-49

Procedure 7-17: Provision static IP routes on DCC links

.............................................................................................

7-52

Procedure 7-18: Provision RS232 CIT (CIT-1) and/or MODEM (CIT-2) serial port parameters

........

7-54

Procedure 7-19: Map TL1 message types to OS applications

....................................................................................

7-57

Procedure 7-20: Enable/disable user ID(s)

..............................................................................................................................

7-59

Procedure 7-21: Provision network element security

.......................................................................................................

7-61

Procedure 7-22: Log out user(s)

....................................................................................................................................................

7-63

System performance monitoring procedures

Overview

.........................................................................................................................................................................................................

8-1

Before you begin

........................................................................................................................................................................................

8-2

Procedure 8-1: View performance monitoring (PM) thresholds

...................................................................................

8-3

Procedure 8-2: Provision performance monitoring (PM) thresholds

.........................................................................

8-4

Procedure 8-3: Initialize performance monitoring (PM) registers

...............................................................................

8-5

Procedure 8-4: View performance monitoring (PM) settings

.........................................................................................

8-7

Procedure 8-5: Provision performance monitoring (PM) settings

...............................................................................

8-8

Procedure 8-6: View performance monitoring (PM) reports

........................................................................................

8-11

Procedure 8-7: Schedule performance monitoring (PM) reports

...............................................................................

8-14

Procedure 8-8: Clear threshold crossing alert (TCA) counts

.......................................................................................

8-17

Network configuration procedures

Overview

.........................................................................................................................................................................................................

9-1

Before you begin

........................................................................................................................................................................................

9-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 vii

Contents

10

Procedure 9-1: Establish high-speed end-to-end Metropolis

®

DMX system

.......................................................

9-3

Procedure 9-2: Add new Metropolis

®

DMX node to network

...................................................................................

9-29

Procedure 9-3: Discontinue Metropolis

®

DMX node from network

......................................................................

9-48

Procedure 9-4: Provision manual ring map

............................................................................................................................

9-63

Procedure 9-5: Establish low-speed 1+1 linear optical extension

............................................................................

9-69

Procedure 9-6: Establish single-homed network configurations

................................................................................

9-76

Procedure 9-7: Establish dual-homed network configurations

....................................................................................

9-84

Procedure 9-8: Establish OC-48 0x1 unprotected extensions

......................................................................................

9-93

Procedure 9-9: Establish subtending low-speed UPSR/BLSR

....................................................................................

9-98

Procedure 9-10: Add IP route(s) through network

...........................................................................................................

9-113

Procedure 9-11: Establish low-speed 1+1 unprotected linear optical extension

...........................................

9-132

TDM service provisioning procedures

Overview

.......................................................................................................................................................................................................

10-1

Before you begin

.....................................................................................................................................................................................

10-2

Procedure 10-1: Establish DS1 or E1 service

.......................................................................................................................

10-3

Procedure 10-2: Discontinue DS1 or E1 service

.................................................................................................................

10-7

Procedure 10-3: Establish DS3 or EC-1 service

...............................................................................................................

10-10

Procedure 10-4: Discontinue DS3 or EC-1 service

.........................................................................................................

10-13

Procedure 10-5: Make VT1.5 or STS-n cross-connections, single OC-3/OC-12 UPSR configuration

...........................................................................................................................................................................................................

Procedure 10-6: Make Function unit UPSR, hairpin, and Main to Function unit UPSR cross-connections

...............................................................................................................................................................................

10-22

Procedure 10-7: Make 1+1 (linear extension) cross-connections

...........................................................................

10-26

Procedure 10-8: Make single-homed cross-connections

..............................................................................................

10-32

Procedure 10-9: Make dual-homed cross-connections

..................................................................................................

10-39

Procedure 10-10: Bridge and roll cross-connections

......................................................................................................

10-48

Procedure 10-11: Establish dual ring interworking (DRI) connections

..............................................................

10-56

.................................................................................................................................................................................................................................

viii 365-372-301 R6.0

Issue 15, January 2006

Contents

11

Procedure 10-12: Provision DS1/DS3 locked cross-connections on a UPSR

................................................

10-64

Procedure 10-13: Provision VT1.5 cross-connections on a BLSR

........................................................................

10-71

VT cross-connections for BLSR

.................................................................................................................................................

10-76

Ethernet/Data network provisioning procedures

Overview

.......................................................................................................................................................................................................

11-1

Before you begin

.....................................................................................................................................................................................

11-4

Procedure 11-1: Establishing Ethernet services

....................................................................................................................

11-5

Procedure 11-2: Establish point-to-point UPSR protected 1GbE full rate private line service (NOTAG mode)

........................................................................................................................................................................................................

11-11

Procedure 11-3: Establish point-to-point UPSR protected GbE service (802.1q mode)

..........................

11-18

Procedure 11-4: Establish point-to-point UPSR protected GbE service (transparent mode)

.................

11-28

Procedure 11-5: Establish Ethernet packet ring on a UPSR

......................................................................................

11-37

Procedure 11-6: Establish 802.1q mode Ethernet service on established packet ring (UPSR)

............

11-46

Procedure 11-7: Establish transparent mode Ethernet service on established packet ring (UPSR)

..

11-51

Procedure 11-8: Establish Ethernet packet ring on a BLSR without NUT

......................................................

11-55

Procedure 11-9: Establish 802.1q mode Ethernet service on established packet ring (BLSR protected)

...........................................................................................................................................................................................................

Procedure 11-10: Establish transparent mode Ethernet service on established packet ring (BLSR protected)

................................................................................................................................................................................................

11-68

Procedure 11-11: Provision Ethernet LAN port parameters

......................................................................................

11-72

Procedure 11-12: Provision Ethernet VCG parameters

.................................................................................................

11-86

Procedure 11-13: Provision Ethernet circuit pack parameters

..................................................................................

11-96

Procedure 11-14: Establish point-to-point BLSR protected 1GbE full rate private line service (NOTAG mode)

........................................................................................................................................................................................................

11-99

Procedure 11-15: Establish point-to-point BLSR protected GbE service (802.1q mode)

....................

11-106

Procedure 11-16: Establish point-to-point BLSR protected GbE service (transparent mode)

...........

11-115

Procedure 11-17: Establish Ethernet packet ring on a BLSR with non-preemptible unprotected traffic

(NUT)

....................................................................................................................................................................................................

11-124

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 ix

Contents

Procedure 11-18: Add bandwidth to a point-to-point UPSR/BLSR protected GbE service (802.1q mode)

......................................................................................................................................................................................................

Procedure 11-19: Establish a dedicated multiple point private line UPSR protected GbE service

(transparent mode)

.........................................................................................................................................................................

11-140

Procedure 11-20: Add Fast Ethernet services to Ethernet packet ring – FE to GbE hairpin

.............

11-150

Procedure 11-21: Establish LNW71 10/100-PL Fast Ethernet private line service on UPSR

...........

11-160

Procedure 11-22: Establish video broadcast network on UPSR

...........................................................................

11-168

Procedure 11-23: Establish video broadcast network on BLSR

...........................................................................

11-185

Procedure 11-24: Make cross-connections for Ethernet service

...........................................................................

11-195

Cross-Connections for Ethernet

...............................................................................................................................................

11-207

Procedure 11-25: Create preferred spanning tree configuration

...........................................................................

11-216

Procedure 11-26: Change an existing spanning tree configuration

.....................................................................

11-223

Procedure 11-27: Create/Delete MAC address on Ethernet port

.........................................................................

11-228

Procedure 11-28: Provision Q in Q stacked VLAN capability

.............................................................................

11-230

Procedure 11-29: Perform Ethernet loopback transmission test

...........................................................................

11-235

Procedure 11-30: Enable/Disable LAN port transmission

........................................................................................

11-237

Procedure 11-31: Provision Ethernet quality of service (QoS)

.............................................................................

11-238

Procedure 11-32: Provision Ethernet QoS parameters

................................................................................................

11-244

Procedure 11-33: Provision LCAS, add/enable/remove tributaries

.....................................................................

11-249

Procedure 11-34: Establish LNW74 10/100-T/F enhanced Fast Ethernet private line service on UPSR

......................................................................................................................................................................................................

Procedure 11-35: Establish LNW73/LNW73C FC-DPORT SAN transport service on UPSR

.........

11-265

Procedure 11-36: Provision LNW73/LNW73C FC-DPORT circuit pack parameters

.............................

11-271

Procedure 11-37: Provision FC-DPORT DATA port parameters

.........................................................................

11-273

Procedure 11-38: Provision FC-DPORT VCG parameters

.......................................................................................

11-277

Procedure 11-39: Make cross-connections for LNW73/LNW73C FC-DPORT SAN transport service

......................................................................................................................................................................................................

Procedure 11-40: Establish video multi-channel broadcast network on UPSR/BLSR (NOTAG mode)

......................................................................................................................................................................................................

.................................................................................................................................................................................................................................

x 365-372-301 R6.0

Issue 15, January 2006

Contents

12

13

Procedure 11-41: Provision Resilient Packet Ring (RPR)-capable VCG parameters

..............................

11-297

Procedure 11-42: Provision Resilient Packet Ring (RPR)-specific VCG parameters

.............................

11-301

Procedure 11-43: Bridge and roll Ethernet cross-connections

...............................................................................

11-305

Procedure 11-44: Establish Resilient Packet Ring (RPR) on a UPSR

.............................................................

11-313

Procedure 11-45: Provision Ethernet quality of service (QoS) - RPR

.............................................................

11-323

Ring and circuit pack upgrade procedures

Overview

.......................................................................................................................................................................................................

12-1

Before you begin

.....................................................................................................................................................................................

12-3

Procedure 12-1: Upgrade high-speed OC-48 OLIUs in UPSR/BLSR network

...............................................

12-4

Procedure 12-2: Back out high-speed OC-48 OLIU upgrade

...................................................................................

12-19

Procedure 12-3: Upgrade OC-3 UPSR to OC-12 UPSR

.............................................................................................

12-32

Procedure 12-4: Back out OC-3 UPSR to OC-12 UPSR upgrade

........................................................................

12-42

Procedure 12-5: Upgrade OC-12 UPSR to OC-48 UPSR

..........................................................................................

12-52

Procedure 12-6: Back out OC-12 UPSR to OC-48 UPSR upgrade

.....................................................................

12-93

Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

....................................................................

12-130

Procedure 12-8: Upgrade OC-48 UPSR to OC-192 UPSR

.....................................................................................

12-144

Procedure 12-9: Back out OC-48 UPSR to OC-192 UPSR upgrade

................................................................

12-182

Procedure 12-10: Suspend OC-48 UPSR to OC-192 UPSR upgrade

...............................................................

12-214

Procedure 12-11: Upgrade OC-48 BLSR to OC-192 BLSR

..................................................................................

12-223

Procedure 12-12: Back out OC-48 BLSR to OC-192 BLSR upgrade

.............................................................

12-262

Procedure 12-13: Suspend OC-48 BLSR to OC-192 BLSR upgrade

...............................................................

12-294

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a Metropolis

®

DMX OC-48/192 UPSR

......

12-303

Procedure 12-15: Upgrade low-speed electrical circuit packs

...............................................................................

12-318

Procedure 12-16: Upgrade or replace SYSCTL (LNW2) circuit pack

............................................................

12-325

Routine maintenance procedures

Overview

.......................................................................................................................................................................................................

13-1

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 xi

Contents

Before you begin

.....................................................................................................................................................................................

13-2

Procedure 13-1: Replace fan filter

................................................................................................................................................

13-3

Procedure 13-2: Replace Metropolis

®

DMX standard shelf

........................................................................................

13-5

Procedure 13-3: Replace Metropolis

®

DMX High Capacity shelf

........................................................................

13-15

Procedure 13-4: Enter/exit pluggable transmission module maintenance state

.............................................

13-25

14

Supporting procedures

Overview

.......................................................................................................................................................................................................

14-1

Before you begin

.....................................................................................................................................................................................

14-3

Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

...........................................................

14-4

Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar

®

CIT session

....................

14-24

Procedure 14-3: Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)

...........

14-34

Procedure 14-4: Perform connection and verification of optical facility

..........................................................

14-44

Procedure 14-5: Install/remove LC lightguide buildouts (LBOs)

..........................................................................

14-54

Procedure 14-6: Connect OLIU optical loopbacks

..........................................................................................................

14-56

Procedure 14-7: Perform end-to-end optical line test on Main OLIUs

..............................................................

14-61

Procedure 14-8: Perform end-to-end optical line test on Function OLIUs

......................................................

14-64

Procedure 14-9: Perform DS1/E1 transmission test

........................................................................................................

14-67

Procedure 14-10: Perform DS3 transmission test

............................................................................................................

14-74

Procedure 14-11: Perform EC-1 transmission test

...........................................................................................................

14-80

Procedure 14-12: Test function unit equipment protection switching

.................................................................

14-86

Procedure 14-13: Perform LED test

.........................................................................................................................................

14-88

Procedure 14-14: Retrieve software generic release and database information

............................................

14-90

Procedure 14-15: Check -48 V DC office battery

...........................................................................................................

14-93

Procedure 14-16: Operate/release facility or terminal loopbacks

...........................................................................

14-97

Procedure 14-17: Observe FTP progress

.............................................................................................................................

14-101

Procedure 14-18: Disable an FTP server on your PC

................................................................................................

14-103

Procedure 14-19: Reset the system

.........................................................................................................................................

14-105

.................................................................................................................................................................................................................................

xii 365-372-301 R6.0

Issue 15, January 2006

Contents

A

Glossary

Index

Procedure 14-20: Reset smart circuit pack

........................................................................................................................

14-108

Procedure 14-21: Change the network card selection

.................................................................................................

14-110

Procedure 14-22: Replace defective fan unit

....................................................................................................................

14-111

Procedure 14-23: Establish test access session in the MON(E or EF) mode

..............................................

14-114

Procedure 14-24: Establish test access session in the SPLT(E or EF) mode

...............................................

14-121

Procedure 14-25: Change test access mode of test access session

.....................................................................

14-127

Procedure 14-26: Delete test access session

.....................................................................................................................

14-129

Procedure 14-27: View test access session(s)

..................................................................................................................

14-130

Procedure 14-28: View reports

..................................................................................................................................................

14-131

Procedure 14-29: Clean optical pluggable transmission module

.........................................................................

14-135

Procedure 14-30: Connect modems to establish communication from remote CIT location

...........

14-138

Provisionable parameters

Overview

........................................................................................................................................................................................................

A-1

Port parameters

...........................................................................................................................................................................................

A-2

Channel parameters

..................................................................................................................................................................................

A-6

Ethernet parameters

.................................................................................................................................................................................

A-7

Data parameters

.......................................................................................................................................................................................

A-24

Cross-Connection parameters

.........................................................................................................................................................

A-26

Synchronization parameters

.............................................................................................................................................................

A-28

Performance monitoring parameters

...........................................................................................................................................

A-30

Operations parameters

.........................................................................................................................................................................

A-31

Security parameters

...............................................................................................................................................................................

A-41

Miscellaneous parameters

.................................................................................................................................................................

A-45

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 xiii

List of tables

1

11

14

Safety

1-1

1-2

Optical circuit pack laser safety specifications

.....................................................................................................

1-6

Pluggable transmission module laser safety specifications

............................................................................

1-7

Ethernet/Data network provisioning procedures

11-1

ED-EPORT command provisionable parameters

............................................................................................

11-73

11-2

ED-VCG command provisionable parameters

..................................................................................................

11-87

11-3

ED-EQPT command provisionable parameters

................................................................................................

11-97

11-4

Provisioning for example 1

........................................................................................................................................

11-231

11-5

Expected results for frame headers in example 1

........................................................................................

11-232

11-6

Provisioning for example 2

........................................................................................................................................

11-233

11-7

Expected results for frame headers in example 2

........................................................................................

11-234

11-8

ENT-ERATE command provisionable parameters

.......................................................................................

11-245

11-9

ED-EQPT command provisionable parameters

.............................................................................................

11-272

11-10

ED-DPORT command provisionable parameters

.........................................................................................

11-274

11-11

ED-VCG-DATA command provisionable parameters

...............................................................................

11-278

11-12

ED-VCG-RPR command provisionable parameters

...................................................................................

11-298

11-13

ED-RPR command provisionable parameters

................................................................................................

11-302

Supporting procedures

14-1

Modem cable assembly and pin connections

.................................................................................................

14-139

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 xv

List of tables

A Provisionable parameters

A-1

Port parameters

.........................................................................................................................................................................

A-2

A-2

Channel parameters

...............................................................................................................................................................

A-6

A-3

Ethernet parameters

...............................................................................................................................................................

A-7

A-4

Data parameters

.....................................................................................................................................................................

A-24

A-5

Cross-Connection parameters

.......................................................................................................................................

A-26

A-6

Synchronization parameters

...........................................................................................................................................

A-28

A-7

Performance monitoring parameters

.........................................................................................................................

A-30

A-8

Operations parameters

.......................................................................................................................................................

A-31

A-9

Security parameters

.............................................................................................................................................................

A-41

A-10

Miscellaneous parameters

...............................................................................................................................................

A-45

.................................................................................................................................................................................................................................

xvi 365-372-301 R6.0

Issue 15, January 2006

List of figures

1

2

Safety

1-1

1-2

1-3

Laser warning labels

............................................................................................................................................................

1-13

Static control wrist strap

...................................................................................................................................................

1-15

Electrostatic discharge warning label (barred-hand symbol)

.....................................................................

1-16

2-4

2-5

2-6

Software installation and upgrades, and database backup procedures

2-1

CIT OSI neighbor

....................................................................................................................................................................

2-7

2-2

2-3

CIT OSI neighbor

CIT OSI neighbor

.................................................................................................................................................................

.................................................................................................................................................................

2-25

2-42

CIT OSI neighbor

CIT OSI neighbor

CIT OSI neighbor

.................................................................................................................................................................

.................................................................................................................................................................

.................................................................................................................................................................

2-51

2-74

2-84

4 Install and provision circuit packs/OLIUs procedures

4-1

4-2

4-3

4-4

4-5

4-6

4-7

4-8

Channel select option label on LNW137B

Jumper settings for LNW121B-159B

Jumper settings for LNW221-259

Jumper settings for enhanced mode

Channel select option label on LNW437

Jumper settings for LNW421-459

Jumper settings for LNW16

..............................................................................................................

.......................................................................................................................

..............................................................................................................................

...........................................................................................................................

...............................................................................................................

..............................................................................................................................

...........................................................................................................................................

Pluggable transmission module with dust plug (Optical PTMs only)

.................................................

4-9

4-10

4-10

4-12

4-17

4-18

4-34

4-64

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 xvii

List of figures

9

10

4-9

Examples of dust plugs

.....................................................................................................................................................

4-64

4-10

Latch type 3 (opened and closed)

...............................................................................................................................

4-67

4-11

Latch type 4, 5, 6, 7 and 8 (opened and closed)

...............................................................................................

4-68

4-12

Insert pluggable transmission module into socket

............................................................................................

4-69

9-4

9-5

9-6

9-7

Network configuration procedures

9-1

Adding a node example

....................................................................................................................................................

9-35

9-2

9-3

Discontinuing a node example

1+1 extension example 1

......................................................................................................................................

..................................................................................................................................................

9-52

9-74

1+1 extension example 2

..................................................................................................................................................

Single-homed configuration example

.......................................................................................................................

Dual-Homed network configuration example 1

Dual-Homed network configuration example 2

.................................................................................................

.................................................................................................

9-74

9-83

9-91

9-91

9-8

OC-48 0x1 unprotected extension

..............................................................................................................................

9-94

9-9

Subtending UPSR configuration example

...........................................................................................................

9-104

9-10

Subtending 2-fiber BLSR example

..........................................................................................................................

9-111

9-11

Local access over LAN

...................................................................................................................................................

9-113

9-12

Access over IP WAN

........................................................................................................................................................

9-115

9-13

Multi-Area operations

......................................................................................................................................................

9-118

9-14

IP NEs on the fringe

.........................................................................................................................................................

9-123

9-15

Multiple GNEs scenario

.................................................................................................................................................

9-127

9-16

Example of 1+1 unprotected optical linear extension

.................................................................................

9-133

TDM service provisioning procedures

10-1

Path protected OC-48 ring network (DS1 to DS1) with VT1.5 cross-connections

..................

10-20

10-2

Path protected OC-48 ring network (DS3 to DS3) with STS-1 cross-connections

..................

10-20

10-3

Cross-Connection examples

.........................................................................................................................................

10-23

10-4

Two Metropolis

®

DMX UPSRs connected in a 1+1 (linear extension)

..........................................

10-27

.................................................................................................................................................................................................................................

xviii 365-372-301 R6.0

Issue 15, January 2006

List of figures

10-5

1+1 STS-3c cross-connection examples

...............................................................................................................

10-29

10-6

Single-Homed Metropolis

®

DMX ring example

............................................................................................

10-33

10-7

Network with single-homed cross-connections example

...........................................................................

10-36

10-8

Dual-Homed Metropolis

®

DMX ring example

................................................................................................

10-40

10-9

Example of final DRI configuration

.......................................................................................................................

10-58

10-10

Example cross-connections at node 3

....................................................................................................................

10-59

10-11

Example cross-connections at node 2

....................................................................................................................

10-59

10-12

Example cross-connections for DRI with UPSR protected OC-n add/drop ports

.....................

10-61

10-13

Basic UPSR DRI cross-connections with UPSR protected OC-n add/drop port

........................

10-61

10-14

Basic UPSR DRI cross-connections with EC-1 add/drop port

..............................................................

10-61

10-15

Basic UPSR DRI cross-connections with 1+1 protected OC-n add/drop port

.............................

10-62

10-16

Basic UPSR DRI cross-connections with BLSR protected OC-n add/drop port

........................

10-62

10-17

Basic UPSR DRI cross-connections with 0X1Sn protected OCn add/drop port

........................

10-62

10-18

DS1 locked cross-connections on a UPSR (unprotected)

.........................................................................

10-68

10-19

DS3 locked cross-connections on a UPSR (unprotected)

.........................................................................

10-68

10-20

DS3 locked cross-connections on a UPSR (protected externally)

.......................................................

10-69

10-21

BLSR VT cross-connection examples

...................................................................................................................

10-75

11 Ethernet/Data network provisioning procedures

11-1

Point-to-Point 1GbE full rate private line example

.......................................................................................

11-17

11-2

Point-to-Point GbE using 802.1q tagging mode

..............................................................................................

11-27

11-3

Point-to-Point GbE using transparent tagging mode

....................................................................................

11-36

11-4

Ethernet packet ring on a UPSR

...............................................................................................................................

11-45

11-5

Example 1 service on UPSR using 802.1q tagging mode

........................................................................

11-49

11-6

Example 2 service on UPSR using 802.1q tagging mode

........................................................................

11-49

11-7

Example service on UPSR using transparent tagging mode

...................................................................

11-54

11-8

SONET layer BLSR protected Ethernet packet ring on a BLSR without NUT

.........................

11-63

11-9

Example service on BLSR using 802.1q tagging mode

.............................................................................

11-67

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 xix

List of figures

11-10

Example service on BLSR using transparent tagging mode

...................................................................

11-71

11-11

Point-to-Point 1GbE full rate private line example

....................................................................................

11-105

11-12

Point-to-Point GbE using 802.1q tagging mode

...........................................................................................

11-114

11-13

Point-to-Point GbE using transparent tagging mode

.................................................................................

11-123

11-14

Ethernet packet ring on a BLSR with NUT

....................................................................................................

11-133

11-15

Example of adding bandwidth on UPSR

..........................................................................................................

11-138

11-16

Example of adding bandwidth on BLSR

..........................................................................................................

11-138

11-17

Dedicated multiple point GbE using transparent tagging mode

.........................................................

11-148

11-18

Dedicated multiple point GbE private line cross-connections

.............................................................

11-148

11-19

Ethernet packet ring on a UPSR

............................................................................................................................

11-158

11-20

FE to GbE Ethernet hairpin cross-connections and provisioning on packet ring

....................

11-158

11-21

Point-to-Point 10/100-PL private line service, STS1 cross-connect mode, one STS1

.........

11-164

11-22

Point-to-Point 10/100-PL private line service, STS1 cross-connect mode, two STS1s

.......

11-164

11-23

Two point-to-point 10/100-PL private line services, STS3c cross-connect mode, one STS1 service and one STS3c service

............................................................................................................................

11-165

11-24

Unprotected 10/100-PL private line services using multipoint cross-connections, STS1 cross-connect mode, external customer protected

....................................................................................

11-166

11-25

Provisioning Ethernet nodes for video broadcast ring

..............................................................................

11-181

11-26

Provisioning cross-connections for video broadcast ring

........................................................................

11-181

11-27

Provisioning Ethernet nodes for control packet ring

.................................................................................

11-182

11-28

Provisioning cross-connections for control packet ring

...........................................................................

11-183

11-29

Provisioning Ethernet nodes for video broadcast ring

..............................................................................

11-193

11-30

Provisioning cross-connections for video broadcast ring

........................................................................

11-193

11-31

UPSR Ring Add/Drop cross-connections

..........................................................................................................

11-199

11-32

Multipoint mixed GbE and FE cross-connections on a UPSR

...........................................................

11-199

11-33

Multipoint GbE cross-connections on a UPSR

.............................................................................................

11-200

11-34

SONET protected 2F BLSR Add/Drop cross-connections on a BLSR without NUT

..........

11-201

11-35

Multipoint (1way unswitched) cross-connections on a BLSR with NUT

....................................

11-202

.................................................................................................................................................................................................................................

xx 365-372-301 R6.0

Issue 15, January 2006

List of figures

11-36

Point-to-Point 10/100-PL private line service, STS1 cross-connect mode, One STS1

........

11-203

11-37

Multipoint 10/100-PL private line service, STS1 cross-connect mode, External Customer

Protected

.............................................................................................................................................................................

11-204

11-38

Two point-to-point 10/100-T/F private line services, STS3c and VT1.5

......................................

11-205

11-39

2-Way Point-to-Point, Through cross-connection

........................................................................................

11-212

11-40

UPSR Ring Add/Drop cross-connection

............................................................................................................

11-212

11-41

FE to GbE 2-Way Hairpin cross-connection

..................................................................................................

11-213

11-42

2F BLSR Add/Drop cross-connection

.................................................................................................................

11-214

11-43

Multipoint (unswitched) cross-connection

........................................................................................................

11-215

11-44

Spanning tree odd node example

...........................................................................................................................

11-218

11-45

Spanning tree even node example

.........................................................................................................................

11-220

11-46

Existing spanning tree configuration

...................................................................................................................

11-226

11-47

New spanning tree configuration

...........................................................................................................................

11-226

11-48

Example 1 configuration

.............................................................................................................................................

11-231

11-49

Example 2 configuration

.............................................................................................................................................

11-233

11-50

2-way cross-connections on a UPSR

...................................................................................................................

11-255

11-51

Multipoint GbE cross-connections on a UPSR

.............................................................................................

11-255

11-52

Point-to-Point 10/100-T/F private line service, three STS1s

................................................................

11-262

11-53

Two point-to-point 10/100-T/F private line services, STS1 and STS3c

........................................

11-262

11-54

Two point-to-point 10/100-T/F private line services, STS3c and VT1.5

......................................

11-263

11-55

Point-to-point Fibre Channel service

...................................................................................................................

11-270

11-56

2-Way Point-to-Point, Through cross-connection

........................................................................................

11-284

11-57

UPSR Ring Add/Drop cross-connection

............................................................................................................

11-284

11-58

2F BLSR Add/Drop cross-connection

.................................................................................................................

11-285

11-59

Point-to-point Fibre Channel service

...................................................................................................................

11-285

11-60

Provisioning cross-connections for video broadcast on UPSR ring

.................................................

11-295

11-61

Provisioning cross-connections for video broadcast on BLSR ring

.................................................

11-295

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 xxi

List of figures

12

13

11-62

Resilient packet ring (RPR) on a UPSR

...........................................................................................................

11-320

11-63

Resilient packet ring (RPR) with multiple RPR circuit packs in same node

.............................

11-320

11-64

Resilient packet ring (RPR) on a BLSR

...........................................................................................................

11-321

Ring and circuit pack upgrade procedures

12-1

Initial configuration for upgrade

............................................................................................................................

12-305

12-2

First figure in upgrade sequence

............................................................................................................................

12-309

12-3

Second figure in upgrade sequence

......................................................................................................................

12-311

12-4

Third figure in upgrade sequence

..........................................................................................................................

12-312

12-5

Fourth figure in upgrade sequence

.......................................................................................................................

12-314

12-6

Fifth figure in upgrade sequence

...........................................................................................................................

12-315

12-7

Final configuration in upgrade sequence

..........................................................................................................

12-317

12-8

CIT OSI neighbor

............................................................................................................................................................

12-328

12-9

CIT OSI neighbor

............................................................................................................................................................

12-336

12-10

CIT OSI neighbor

............................................................................................................................................................

12-357

Routine maintenance procedures

13-1

Metropolis

®

DMX standard shelf fan filter

..........................................................................................................

13-4

13-2

Metropolis

®

DMX High Capacity shelf fan filter

............................................................................................

13-4

13-3

Metropolis

®

DMX mounting bracket positions - 23-inch frame

.............................................................

13-9

13-4

Metropolis

®

DMX mounting bracket positions - 19-inch frame

.............................................................

13-9

13-5

Typical Metropolis

®

DMX standard shelf bay mounting arrangements

..........................................

13-11

13-6

Metropolis

®

DMX shelf mounted to the rear of a 23-inch frame

.......................................................

13-12

13-7

Metropolis

®

DMX High Capacity mounting bracket positions - 23-inch frame

........................

13-19

13-8

Metropolis

®

DMX High Capacity mounting bracket positions - 19-inch frame

........................

13-19

13-9

Typical Metropolis

®

DMX High Capacity shelf bay mounting arrangements

............................

13-21

13-10

Metropolis

®

DMX High Capacity shelf mounted to the rear of a 23-inch frame

.....................

13-22

.................................................................................................................................................................................................................................

xxii 365-372-301 R6.0

Issue 15, January 2006

List of figures

14 Supporting procedures

14-1

WaveStar

®

CIT welcome screen

...............................................................................................................................

14-26

14-2

WaveStar

®

CIT login screen

........................................................................................................................................

14-27

14-3

Legal notice

............................................................................................................................................................................

14-28

14-4

Example of network view

.............................................................................................................................................

14-29

14-5

NE login

...................................................................................................................................................................................

14-31

14-6

NE level legal notice

........................................................................................................................................................

14-32

14-7

Example of system view (graphical)

......................................................................................................................

14-33

14-8

Stand-Alone shelf with OLIU loopback

...............................................................................................................

14-69

14-9

Stand-Alone shelf with DSX loopback

.................................................................................................................

14-69

14-10

End-to-End DS1/E1 circuit with far-end loopback

.......................................................................................

14-69

14-11

Stand-Alone shelf with OLIU loopback

...............................................................................................................

14-76

14-12

End-to-End DS3 circuit with far-end loopback

...............................................................................................

14-76

14-13

Stand-Alone shelf with OLIU loopback

...............................................................................................................

14-81

14-14

End-to-End EC-1 circuit with far-end loopback

.............................................................................................

14-81

14-15

Facility loopback example

............................................................................................................................................

14-97

14-16

Terminal loopback example

.........................................................................................................................................

14-98

14-17

Metropolis

®

DMX fan unit screws

.......................................................................................................................

14-112

14-18

Metropolis

®

DMX High Capacity shelf fan unit screws

........................................................................

14-112

14-19

Dial-Up networking to TCP/IP LAN/WAN network

.................................................................................

14-143

14-20

Modem-to-Modem connection

.................................................................................................................................

14-143

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 xxiii

List of procedures

2

3

Software installation and upgrades, and database backup procedures

2-5

2-6

2-7

2-8

2-1

2-2

2-3

2-4

Install software generic (initial) via FTAM

Install software generic (initial) via FTP

Upgrade software generic via FTAM

Upgrade software generic via FTP

.............................................................................................................

................................................................................................................

.......................................................................................................................

.............................................................................................................................

Upgrade software generic via FTTD (6.0.0 to 6.0.x)

Copy software generic to a remote shelf

Apply software generic

Backup and restore NE database via FTP

..................................................................................

.............................................................................................................

...................................................................................................................................................

..........................................................................................................

2-3

2-21

2-40

2-72

2-109

2-115

2-120

2-123

2-9

Backup and restore NE database via FTTD

......................................................................................................

2-135

2-10

Backup and restore NE database via FTAM

.....................................................................................................

2-150

Acceptance procedures

3-1

3-2

Accept Metropolis

®

DMX shelf (looped-back)

....................................................................................................

3-3

Accept Metropolis

®

DMX network

..............................................................................................................................

3-9

4 Install and provision circuit packs/OLIUs procedures

4-1

Install SYSCTL (LNW2) in new Metropolis

®

DMX shelf

...........................................................................

4-4

4-2

4-3

Install OLIU circuit packs in Main slots

...................................................................................................................

4-7

Install OLIU circuit packs in Function slots

........................................................................................................

4-14

4-4

4-5

Provision OLIU circuit packs/ports for service

..................................................................................................

4-22

Provision unprotected operation on optical ports

..............................................................................................

4-26

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 xxv

List of procedures

5

6

4-6

4-7

4-8

Install DS3/EC1 circuit packs

.......................................................................................................................................

4-32

Provision DS3/EC1 circuit packs/ports for service

..........................................................................................

4-37

Install DS1/E1 circuit packs

...........................................................................................................................................

4-39

4-9

Provision DS1/E1 circuit packs/ports for service

..............................................................................................

4-42

4-10

Install TMUX circuit packs

............................................................................................................................................

4-45

4-11

Provision TMUX ports for service

.............................................................................................................................

4-48

4-12

Install 10/100 Ethernet circuit packs

.........................................................................................................................

4-50

4-13

Install Gigabit Ethernet circuit packs

.......................................................................................................................

4-54

4-14

Provision Ethernet circuit pack/LAN port/VCG for service

......................................................................

4-59

4-15

Install pluggable transmission modules

...................................................................................................................

4-62

4-16

Install LNW80 switch pack

............................................................................................................................................

4-72

4-17

Install Fibre Channel circuit packs

.............................................................................................................................

4-74

4-18

Provision Fibre Channel circuit pack/Data port/VCG for service

..........................................................

4-77

4-19

Provision pluggable transmission module

..............................................................................................................

4-80

4-20

Provision non-volatile memory cards

.......................................................................................................................

4-82

4-21

Provision STS-n/VT1.5 tributary

.................................................................................................................................

4-83

4-22

Change circuit pack mode of LNW26B, LNW28, LNW77, or LNW121B-159B OC-48 OLIU circuit packs

..........................................................................................................................................................................

4-84

Node turnup procedures

5-1

Equip new Metropolis

®

DMX Access Multiplexer with OLIUs in Main slots

................................

5-3

5-2

Equip new Metropolis

®

DMX Access Multiplexer with LNW80 switch packs in Main slots

..............................................................................................................................................................................................

System configuration procedures

6-1

6-2

6-3

6-4

Provision system configuration parameters

Provision shelf/system parameters

Provision DCC terminations

.............................................................................................................

.................................................................................................................................

Provision miscellaneous discrete inputs and outputs

......................................................................................

...........................................................................................................................................

6-3

6-7

6-11

6-13

.................................................................................................................................................................................................................................

xxvi 365-372-301 R6.0

Issue 15, January 2006

List of procedures

6-5

6-6

6-7

Network Element synchronization provisioning

................................................................................................

6-16

Provision system alarm configuration

......................................................................................................................

6-33

Provision new alarm severity assignment profile

..............................................................................................

6-34

6-8

6-9

Change existing alarm severity assignment profile

..........................................................................................

6-36

Delete alarm severity assignment profile

...............................................................................................................

6-39

6-10

Assign alarm severity assignment profile

..............................................................................................................

6-41

6-11

Evaluate bandwidth utilization

......................................................................................................................................

6-44

6-12

Optimize backplane bandwidth

.....................................................................................................................................

6-46

7 System administration procedures

7-7

7-8

7-9

7-1

7-2

7-3

7-4

7-5

7-6

Provision system administration parameters

...........................................................................................................

7-4

Change your own password

............................................................................................................................................

7-10

Edit, delete, or enter a user’s login

............................................................................................................................

7-12

Enable/disable lockout security state

........................................................................................................................

7-16

Provision system SNMP management features

..................................................................................................

7-17

Edit, delete, or enter SNMP users

..............................................................................................................................

7-20

Allow/inhibit autonomous message reporting

.....................................................................................................

7-24

Create or edit login banner

.............................................................................................................................................

7-26

Set NE defaults — alarm gateway, alarm group, remote NE status, FTP/FTTD, security and history log thresholds

......................................................................................................................................................

7-28

7-10

Set date and time

...................................................................................................................................................................

7-33

7-11

Set/change system TID

......................................................................................................................................................

7-38

7-12

Enable/disable OSI on an IAO LAN port

.............................................................................................................

7-39

7-13

Provision network layer 3 parameters

......................................................................................................................

7-40

7-14

Set TARP parameters

..........................................................................................................................................................

7-43

7-15

Provision TCP/IP and Proxy ARP on an IAO LAN port

.............................................................................

7-46

7-16

Provision/enable/disable the NE as a TL1 TCP/IP GNE

.............................................................................

7-49

7-17

Provision static IP routes on DCC links

.................................................................................................................

7-52

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 xxvii

List of procedures

8

9

7-18

Provision RS232 CIT (CIT-1) and/or MODEM (CIT-2) serial port parameters

............................

7-54

7-19

Map TL1 message types to OS applications

........................................................................................................

7-57

7-20

Enable/disable user ID(s)

.................................................................................................................................................

7-59

7-21

Provision network element security

...........................................................................................................................

7-61

7-22

Log out user(s)

........................................................................................................................................................................

7-63

8-4

8-5

8-6

8-7

8-8

System performance monitoring procedures

8-1

View performance monitoring (PM) thresholds

....................................................................................................

8-3

8-2

8-3

Provision performance monitoring (PM) thresholds

Initialize performance monitoring (PM) registers

..........................................................................................

................................................................................................

8-4

8-5

View performance monitoring (PM) settings

View performance monitoring (PM) reports

Clear threshold crossing alert (TCA) counts

.........................................................................................................

Provision performance monitoring (PM) settings

Schedule performance monitoring (PM) reports

................................................................................................

........................................................................................................

................................................................................................

........................................................................................................

8-7

8-8

8-11

8-14

8-17

9-6

9-7

9-8

9-9

Network configuration procedures

9-1

Establish high-speed end-to-end Metropolis

®

DMX system

........................................................................

9-3

9-2

9-3

Add new Metropolis

®

DMX node to network

...................................................................................................

9-29

Discontinue Metropolis

®

DMX node from network

.......................................................................................

9-48

9-4

9-5

Provision manual ring map

.............................................................................................................................................

Establish low-speed 1+1 linear optical extension

.............................................................................................

9-63

9-69

Establish single-homed network configurations

Establish dual-homed network configurations

Establish OC-48 0x1 unprotected extensions

Establish subtending low-speed UPSR/BLSR

.................................................................................................

.....................................................................................................

......................................................................................................

.....................................................................................................

9-76

9-84

9-93

9-98

9-10

Add IP route(s) through network

..............................................................................................................................

9-113

9-11

Establish low-speed 1+1 unprotected linear optical extension

...............................................................

9-132

.................................................................................................................................................................................................................................

xxviii 365-372-301 R6.0

Issue 15, January 2006

List of procedures

10

11

TDM service provisioning procedures

10-1

Establish DS1 or E1 service

...........................................................................................................................................

10-3

10-2

Discontinue DS1 or E1 service

....................................................................................................................................

10-7

10-3

Establish DS3 or EC-1 service

..................................................................................................................................

10-10

10-4

Discontinue DS3 or EC-1 service

............................................................................................................................

10-13

10-5

Make VT1.5 or STS-n cross-connections, single OC-3/OC-12 UPSR configuration

..............

10-16

10-6

Make Function unit UPSR, hairpin, and Main to Function unit UPSR cross-connections

..

10-22

10-7

Make 1+1 (linear extension) cross-connections

..............................................................................................

10-26

10-8

Make single-homed cross-connections

..................................................................................................................

10-32

10-9

Make dual-homed cross-connections

......................................................................................................................

10-39

10-10

Bridge and roll cross-connections

............................................................................................................................

10-48

10-11

Establish dual ring interworking (DRI) connections

....................................................................................

10-56

10-12

Provision DS1/DS3 locked cross-connections on a UPSR

.......................................................................

10-64

10-13

Provision VT1.5 cross-connections on a BLSR

..............................................................................................

10-71

Ethernet/Data network provisioning procedures

11-1

Establishing Ethernet services

.......................................................................................................................................

11-5

11-2

Establish point-to-point UPSR protected 1GbE full rate private line service (NOTAG mode)

..........................................................................................................................................................................................

11-3

Establish point-to-point UPSR protected GbE service (802.1q mode)

.............................................

11-18

11-4

Establish point-to-point UPSR protected GbE service (transparent mode)

....................................

11-28

11-5

Establish Ethernet packet ring on a UPSR

.........................................................................................................

11-37

11-6

Establish 802.1q mode Ethernet service on established packet ring (UPSR)

...............................

11-46

11-7

Establish transparent mode Ethernet service on established packet ring (UPSR)

......................

11-51

11-8

Establish Ethernet packet ring on a BLSR without NUT

.........................................................................

11-55

11-9

Establish 802.1q mode Ethernet service on established packet ring (BLSR protected)

.........

11-64

11-10

Establish transparent mode Ethernet service on established packet ring (BLSR protected)

..............

11-6811-6811-68

11-68

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 xxix

List of procedures

11-11

Provision Ethernet LAN port parameters

............................................................................................................

11-72

11-12

Provision Ethernet VCG parameters

.......................................................................................................................

11-86

11-13

Provision Ethernet circuit pack parameters

........................................................................................................

11-96

11-14

Establish point-to-point BLSR protected 1GbE full rate private line service (NOTAG mode)

.........................................................................................................................................................................................

11-15

Establish point-to-point BLSR protected GbE service (802.1q mode)

...........................................

11-106

11-16

Establish point-to-point BLSR protected GbE service (transparent mode)

.................................

11-115

11-17

Establish Ethernet packet ring on a BLSR with non-preemptible unprotected traffic (NUT)

....................................................................................................................................................................................

11-18

Add bandwidth to a point-to-point UPSR/BLSR protected GbE service (802.1q mode)

...

11-134

11-19

Establish a dedicated multiple point private line UPSR protected GbE service (transparent mode)

...................................................................................................................................................................................

11-140

11-20

Add Fast Ethernet services to Ethernet packet ring – FE to GbE hairpin

...................................

11-150

11-21

Establish LNW71 10/100-PL Fast Ethernet private line service on UPSR

.................................

11-160

11-22

Establish video broadcast network on UPSR

.................................................................................................

11-168

11-23

Establish video broadcast network on BLSR

.................................................................................................

11-185

11-24

Make cross-connections for Ethernet service

.................................................................................................

11-195

11-25

Create preferred spanning tree configuration

.................................................................................................

11-216

11-26

Change an existing spanning tree configuration

...........................................................................................

11-223

11-27

Create/Delete MAC address on Ethernet port

................................................................................................

11-228

11-28

Provision Q in Q stacked VLAN capability

...................................................................................................

11-230

11-29

Perform Ethernet loopback transmission test

.................................................................................................

11-235

11-30

Enable/Disable LAN port transmission

..............................................................................................................

11-237

11-31

Provision Ethernet quality of service (QoS)

...................................................................................................

11-238

11-32

Provision Ethernet QoS parameters

......................................................................................................................

11-244

11-33

Provision LCAS, add/enable/remove tributaries

...........................................................................................

11-249

11-34

Establish LNW74 10/100-T/F enhanced Fast Ethernet private line service on UPSR

........

11-257

11-35

Establish LNW73/LNW73C FC-DPORT SAN transport service on UPSR

...............................

11-265

.................................................................................................................................................................................................................................

xxx 365-372-301 R6.0

Issue 15, January 2006

List of procedures

11-36

Provision LNW73/LNW73C FC-DPORT circuit pack parameters

...................................................

11-271

11-37

Provision FC-DPORT DATA port parameters

...............................................................................................

11-273

11-38

Provision FC-DPORT VCG parameters

.............................................................................................................

11-277

11-39

Make cross-connections for LNW73/LNW73C FC-DPORT SAN transport service

............

11-280

11-40

Establish video multi-channel broadcast network on UPSR/BLSR (NOTAG mode)

...........

11-287

11-41

Provision Resilient Packet Ring (RPR)-capable VCG parameters

....................................................

11-297

11-42

Provision Resilient Packet Ring (RPR)-specific VCG parameters

...................................................

11-301

11-43

Bridge and roll Ethernet cross-connections

.....................................................................................................

11-305

11-44

Establish Resilient Packet Ring (RPR) on a UPSR

...................................................................................

11-313

11-45

Provision Ethernet quality of service (QoS) - RPR

...................................................................................

11-323

12 Ring and circuit pack upgrade procedures

12-1

Upgrade high-speed OC-48 OLIUs in UPSR/BLSR network

...................................................................

12-4

12-2

Back out high-speed OC-48 OLIU upgrade

......................................................................................................

12-19

12-3

Upgrade OC-3 UPSR to OC-12 UPSR

................................................................................................................

12-32

12-4

Back out OC-3 UPSR to OC-12 UPSR upgrade

............................................................................................

12-42

12-5

Upgrade OC-12 UPSR to OC-48 UPSR

..............................................................................................................

12-52

12-6

Back out OC-12 UPSR to OC-48 UPSR upgrade

.........................................................................................

12-93

12-7

Suspend OC-12 UPSR to OC-48 UPSR upgrade

........................................................................................

12-130

12-8

Upgrade OC-48 UPSR to OC-192 UPSR

........................................................................................................

12-144

12-9

Back out OC-48 UPSR to OC-192 UPSR upgrade

...................................................................................

12-182

12-10

Suspend OC-48 UPSR to OC-192 UPSR upgrade

.....................................................................................

12-214

12-11

Upgrade OC-48 BLSR to OC-192 BLSR

........................................................................................................

12-223

12-12

Back out OC-48 BLSR to OC-192 BLSR upgrade

...................................................................................

12-262

12-13

Suspend OC-48 BLSR to OC-192 BLSR upgrade

.....................................................................................

12-294

12-14

Upgrade OC-3 or OC-12 UPSR to a Metropolis

®

DMX OC-48/192 UPSR

.............................

12-303

12-15

Upgrade low-speed electrical circuit packs

.....................................................................................................

12-318

12-16

Upgrade or replace SYSCTL (LNW2) circuit pack

...................................................................................

12-325

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 xxxi

List of procedures

13 Routine maintenance procedures

13-1

Replace fan filter

...................................................................................................................................................................

13-3

13-2

Replace Metropolis

®

DMX standard shelf

............................................................................................................

13-5

13-3

Replace Metropolis

®

DMX High Capacity shelf

...........................................................................................

13-15

13-4

Enter/exit pluggable transmission module maintenance state

.................................................................

13-25

14 Supporting procedures

14-1

Install generic and WaveStar

®

CIT software on the PC

...............................................................................

14-4

14-2

Connect Personal Computer (PC) and establish WaveStar

®

CIT session

.......................................

14-24

14-3

Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)

..............................

14-34

14-4

Perform connection and verification of optical facility

..............................................................................

14-44

14-5

Install/remove LC lightguide buildouts (LBOs)

..............................................................................................

14-54

14-6

Connect OLIU optical loopbacks

.............................................................................................................................

14-56

14-7

Perform end-to-end optical line test on Main OLIUs

..................................................................................

14-61

14-8

Perform end-to-end optical line test on Function OLIUs

..........................................................................

14-64

14-9

Perform DS1/E1 transmission test

...........................................................................................................................

14-67

14-10

Perform DS3 transmission test

...................................................................................................................................

14-74

14-11

Perform EC-1 transmission test

.................................................................................................................................

14-80

14-12

Test function unit equipment protection switching

.......................................................................................

14-86

14-13

Perform LED test

...............................................................................................................................................................

14-88

14-14

Retrieve software generic release and database information

...................................................................

14-90

14-15

Check -48 V DC office battery

..................................................................................................................................

14-93

14-16

Operate/release facility or terminal loopbacks

.................................................................................................

14-97

14-17

Observe FTP progress

...................................................................................................................................................

14-101

14-18

Disable an FTP server on your PC

.......................................................................................................................

14-103

14-19

Reset the system

...............................................................................................................................................................

14-105

14-20

Reset smart circuit pack

..............................................................................................................................................

14-108

14-21

Change the network card selection

.......................................................................................................................

14-110

.................................................................................................................................................................................................................................

xxxii 365-372-301 R6.0

Issue 15, January 2006

List of procedures

14-22

Replace defective fan unit

..........................................................................................................................................

14-111

14-23

Establish test access session in the MON(E or EF) mode

.....................................................................

14-114

14-24

Establish test access session in the SPLT(E or EF) mode

.....................................................................

14-121

14-25

Change test access mode of test access session

...........................................................................................

14-127

14-26

Delete test access session

...........................................................................................................................................

14-129

14-27

View test access session(s)

........................................................................................................................................

14-130

14-28

View reports

........................................................................................................................................................................

14-131

14-29

Clean optical pluggable transmission module

................................................................................................

14-135

14-30

Connect modems to establish communication from remote CIT location

.................................

14-138

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006 xxxiii

About this information product

Purpose

This User Operations Guide (UOG) provides the detailed procedural information for the Metropolis

®

DMX Access Multiplexer (Metropolis

®

DMX), Release 6.0.1.

Reason for reissue

This document, Metropolis

®

DMX Access Multiplexer User Operations Guide,

365-372-301, Issue 15, is reissued to update existing information and provide information about Release 6.0.1 features.

Safety information

This information product contains hazard statements for your safety. Hazard statements are given at points where safety consequences to personnel, equipment, and operation may exist. Failure to follow these statements may result in serious consequences.

Intended audience

This User Operations Guide is intended primarily for telecommunications technicians and communications network providers.

Procedural information in this document is intended primarily for maintenance, operation, and provisioning personnel responsible for operating and maintaining the

Metropolis

®

DMX Access Multiplexer.

How to use this information product

This User Operations Guide includes procedure chapters and supporting information

(for example, safety instructions, provisionable parameters, glossary, and index).

Assumptions

This document assumes that users have an understanding of the following:

•

Basic principles of telecommunication transmission

•

Common telecommunication and system terminology (a glossary is provided in this document to assist you)

.................................................................................................................................................................................................................................

,

365-372-301 R6.0

Issue 15, January 2006 xxxv

About this information product

•

Test sets and tools used in the telecommunication industry

•

Local operations and functional procedures of your company

•

Personal computer (PC) operation, common PC terminology, and navigational procedures in a windows-style user interface

Chapter contents

The following table provides a brief description of each chapter in this document.

Chapter

Chapter 1, “Safety”

Chapter 2, “Software installation and upgrades, and database backup procedures”

Chapter 3, “Acceptance procedures”

Chapter 4, “Install and provision circuit packs/OLIUs procedures”

Chapter 5, “Node turnup procedures”

Chapter 6, “System configuration procedures”

Chapter 7, “System administration procedures”

Chapter 8, “System performance monitoring procedures”

Contents

This chapter provides important safety instructions for

Metropolis

®

DMX.

This chapter provides procedures to install new system software or upgrade the existing system software.

Procedures to back up and restore the network element database are also included in this chapter.

This chapter provides procedures to test an out-of-service

Metropolis

®

DMX or network after another organization has installed and equipped it.

This chapter provides procedures to install and provision circuit packs in Metropolis

®

DMX.

This chapter provides procedures to equip and turn-up a node.

This chapter provides procedures to provision system configuration parameters, for example, timing, DCC terminations, miscellaneous discretes.

This chapter provides procedures to provision optional system administration parameters from the System View

Administration

menu.

This chapter provides procedures to view or provision performance monitoring parameters from the System View

Performance

menu.

This chapter provides procedures to turn-up a network.

Chapter 9, “Network configuration procedures”

Chapter 10, “TDM service provisioning procedures”

Chapter 11, “Ethernet/Data network provisioning procedures”

This chapter provides procedures to provision TDM services.

This chapter provides procedures to provision Ethernet services.

.................................................................................................................................................................................................................................

xxxvi 365-372-301 R6.0

Issue 15, January 2006

,

About this information product

Chapter

Chapter 12, “Ring and circuit pack upgrade procedures”

Chapter 13, “Routine maintenance procedures”

Chapter 14, “Supporting procedures”

Appendix A, “Provisionable parameters”

“Glossary”

Index

Contents

This chapter provides procedures to:

• upgrade rings

• backout of ring upgrades

• suspend ring upgrades temporarily

• upgrade circuit packs at a node

This chapter provides a single routine maintenance procedure, replacing a fan filter.

This chapter provides detailed step-by-step instructions that support other procedures.

This appendix identifies the provisionable parameters and the user-settable values.

Defines terms used throughout the Metropolis

®

documentation.

DMX

Provides detailed access to the contents of this document.

Conventions used

The following conventions are used in this document.

•

This font

indicates a command.

Example:

ent-user-secu

•

This font indicates a document reference.

Example, Document Title, xxx-xxx-xxx (ordering number):

Metropolis

®

DMX Access Multiplexer Applications and Planning Guide,

365-372-300

•

This font

indicates buttons, icons, or menu items.

Example:

Configuration

→

Equipment

•

This font indicates window and screen names or special emphasis.

Example:

The Configure Equipment screen appears.

•

This font

indicates lettering designations on the backplane, shelf, and circuit packs.

Example:

Release the

ACO TEST

push-button on the SYSCTL when the

8.

disappears in the

IND

display.

.................................................................................................................................................................................................................................

,

365-372-301 R6.0

Issue 15, January 2006 xxxvii

About this information product

•

This font indicates information output by the system or displayed on the computer.

Example:

The response will be

/* SYSTEM TID: LT-DMX */

.

•

Underlined phrases indicate hyperlinks to other text in the document or another step in the procedure.

Example: Cross-Reference (chapter-page number):

Procedure 14-2: “Connect

Personal Computer (PC) and establish WaveStar

®

CIT session” (p. 14-24)

•

Important messages are displayed as follows:

Important! This is important information.

User interface to system

Users interact with the Metropolis

®

DMX Access Multiplexer using a PC and a windows-based graphical user interface (GUI). The GUI is called theWaveStar

®

Craft

Interface Terminal (WaveStar

®

CIT), which permits users to perform system operations such as administration, provisioning, fault management, and more.

Using the

WaveStar

®

CIT

Procedures presented in this document expect users to be familiar with the WaveStar

®

CIT and navigating through the screens of information relating to a particular operation. The screens are designed to be straightforward and to contain all information relating to a particular operation. The procedures presented in this document rely on the information provided in the screen displays. Therefore, it is imperative that users read all the information provided in a screen before continuing an operational function.

Using procedures

To find instructions for performing a specific job, first determine the procedure category (for example, acceptance or node turn-up). After determining the procedure category, go to the corresponding procedure chapter and find the procedure in the chapter Contents table.

The procedures in the following chapters contain step-by-step instructions to accomplish a distinct user job:

•

Chapter 2, “Software installation and upgrades, and database backup procedures”

•

Chapter 3, “Acceptance procedures”

•

Chapter 4, “Install and provision circuit packs/OLIUs procedures”

•

Chapter 5, “Node turnup procedures”

•

Chapter 6, “System configuration procedures”

•

Chapter 7, “System administration procedures”

•

Chapter 8, “System performance monitoring procedures”

•

Chapter 9, “Network configuration procedures”

.................................................................................................................................................................................................................................

xxxviii 365-372-301 R6.0

Issue 15, January 2006

,

About this information product

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

•

Chapter 12, “Ring and circuit pack upgrade procedures”

•

Chapter 13, “Routine maintenance procedures”

The procedures in

Chapter 14, “Supporting procedures”

are referenced from multiple procedures to support a job function you are performing. Go to a supporting procedure only when it is referred to by another procedure. Supporting procedures are not to be accessed directly except by very experienced personnel.

Important! Perform all steps in a procedure sequentially, unless that step sends you to another step or procedure.

Unless otherwise instructed, if one procedure sends you to another procedure, you must return to the first procedure after you complete the second. After you have completed the first procedure element, you have finished.

If/Then statements in a procedure

If {/Then { columns in a procedure contain only one condition that is true in a table cell under the If { column. You perform the action in the related table cell under the

Then { column. You then continue to the next sequential step or as directed by the action under the Then { column.

Verifying actions

Sometimes you will be asked to verify that actions have occurred. This may take the form of a formal statement of the expected response. At other times, the instructions will merely state verify that the action occurred. If the expected response is not observed and a specific trouble-clearing reference is not made, you should reference the chapter entitled Trouble-Clearing Procedures in the Metropolis

®

DMX Access

Multiplexer Alarm Messages and Trouble Clearing Guide, 365-372-302 to start trouble clearing.

Related information

The following table lists the documents included in the Metropolis

®

DMX documentation set.

Comcode

NA

109 251 496

109 587 105

Document Number

365-372-330

365-372-300

365-372-301 R6.0

Title

WaveStar

®

User Guide, 365-372-330

Metropolis

®

DMX Access Multiplexer Applications and Planning Guide, 365-372-300

Metropolis

®

DMX Access Multiplexer User

Operations Guide, 365-372-301

.................................................................................................................................................................................................................................

,

365-372-301 R6.0

Issue 15, January 2006 xxxix

About this information product

Comcode

109 587 113

109 587 121

109 587 139

109 595 892

109 595 900

109 596 528

NA

NA

NA

Document Number

365-372-302 R6.0

365-372-304 R6.0

365-372-306 R6.0

Title

Metropolis

®

DMX Access Multiplexer Alarm

Messages and Trouble Clearing Guide, 365-372-302

Metropolis

®

DMX Access Multiplexer Installation

Manual, 365-372-304

Metropolis

®

DMX Access Multiplexer TL1 Message

Details, 365-372-306

Metropolis

®

DMX Access Multiplexer Software

Release Description (Paper)

Metropolis

®

DMX Access Multiplexer Software

Release Description (CD-ROM)

Metropolis

®

DMX Access Multiplexer Release 6.0

Documents (CD-ROM)

Information product support

For questions or concerns about this or any other Lucent Technologies information product, please contact us at one of the following numbers:

•

1-888-727-3615 (for the continental United States)

•

1-630-713-5000 (for all countries)

Technical support

For technical support, contact your local customer support team. You can reach them via the Web at the Lucent Customer Support Web Site ( http://support.lucent.com

) or the customer support telephone number listed at the Lucent Contact Us Web Site

( http://www.lucent.com/contact/ ).

How to order

North American region (NAR)

To order Lucent Technologies information products, use the following websites or the email, phone, and fax contacts linked from “Contact Us” on those sites:

•

Lucent’s Product Documentation Web Site ( http://www.lucentdocs.com

)

•

Lucent Technologies Training Catalog Web Site ( http://training.lucent.com

)

Other regions

.................................................................................................................................................................................................................................

xl 365-372-301 R6.0

Issue 15, January 2006

,

About this information product

To order Lucent Technologies information products, contact your local sales representative, use the following websites, or use the email, phone, and fax contacts linked from “Contact Us” on those sites:

•

Lucent’s Product Documentation Web Site ( http://www.lucentdocs.com

)

•

Lucent Technologies Training Catalog Web Site ( http://training.lucent.com

)

How to comment

To comment on this information product, go to the Online Comment Form

( http://www.lucent-info.com/comments/enus/ ) or email your comments to the

Comments Hotline ([email protected]).

.................................................................................................................................................................................................................................

,

365-372-301 R6.0

Issue 15, January 2006 xli

1

1

Overview

.................................................................................................................................................................................................................................

Purpose

This chapter provides important safety instructions for Metropolis

®

DMX.

Contents

Structure of hazard statements

General notes on safety

Laser safety

Electrostatic discharge

Save these safety instructions

1-2

1-4

1-6

1-14

1-17

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

1-1

Safety

Structure of hazard statements

.................................................................................................................................................................................................................................

Overview

Hazard statements describe the safety risks relevant while performing tasks on Lucent

Technologies products during deployment and/or use. Failure to avoid the hazards may have serious consequences.

General structure

Hazard statements include the following structural elements:

5

6

7

2

3

4

Item Structure element

1 Personal injury symbol

Hazard type symbol

Signal word

Hazard type

Damage statement

Avoidance message

Identifier

Purpose

Indicates the potential for personal injury

(optional)

Indicates hazard type (optional)

Indicates the severity of the hazard

Describes the source of the risk of damage or injury

Consequences if protective measures fail

Protective measures to take to avoid the hazard

The reference ID of the hazard statement

(optional)

.................................................................................................................................................................................................................................

1-2 365-372-301 R6.0

Issue 15, January 2006

Safety Structure of hazard statements

Signal words

The signal words identify the hazard severity levels as follows:

Signal word

DANGER

WARNING

CAUTION

Meaning

Indicates an imminently hazardous situation (high risk) which, if not avoided, will result in death or serious injury.

Indicates a potentially hazardous situation (medium risk) which, if not avoided, could result in death or serious injury.

When used with the personal injury symbol:

Indicates a potentially hazardous situation (low risk) which, if not avoided, may result in personal injury.

When used without the personal injury symbol:

Indicates a potentially hazardous situation (low risk) which, if not avoided, may result in property damage, such as service interruption or damage to equipment or other materials.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

1-3

Safety

General notes on safety

.................................................................................................................................................................................................................................

Overview

This chapter must be read by the responsible technical personnel before servicing the system. The most recent issue of this document must always be kept close to the equipment.

In addition to the general safety instructions in this chapter, users must also observe the specific safety instructions in the individual chapters.

The equipment complies with the current national and international safety requirements. It is provided with a high degree of operational safety resulting from many years of development experience and continuous stringent quality checks.

Potential sources of danger

The equipment is safe in normal operation. There are, however, some potential sources of danger that cannot be completely eliminated. In particular, these arise during the following:

• opening of housings or equipment covers,

• manipulation of any kind within the equipment, even if it has been disconnected from the power supply,

• disconnection of optical or electrical connections,

• through possible contact with live pairs, laser light, hot surfaces, sharp edges, or components sensitive to electrostatic discharge.

Special safety instructions

Laser safety and handling components sensitive to electrostatic discharge (ESD) are vitally important to the equipment. For special safety instructions concerning laser safety and electrostatic discharge, refer to sections

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14) .

General safety requirements

In order to keep the technically unavoidable residual risk to a minimum, it is imperative to observe the following rules.

•

Transport, storage and operation of the unit/system must be under the permissible

conditions only.

See accompanying documentation and information on the unit/system.

•

Installation, configuration, and disassembly must be carried out only by expert

personnel and with reference to the respective documentation.

Due to the complexity of the unit/system, the personnel requires special training.

.................................................................................................................................................................................................................................

1-4 365-372-301 R6.0

Issue 15, January 2006

Safety General notes on safety

•

The unit/system must be operated by expert and authorized users only.

The user must operate the unit/system only after having read and understood the chapter on safety and the parts of the documentation relevant to operation. For complex systems, additional training is recommended. Any obligatory training for operating and service personnel must be carried out and documented.

•

The unit/system must not be operated unless it is in perfect working order.

Any faults and errors that might affect safety must be reported immediately by the user to a person in responsibility.

•

The unit/system must be operated only with the connections and under the environmental conditions as described in the documentation.

•

Any conversions or changes to the system or parts of the system (including the software) must be carried out by qualified Lucent Technologies personnel or by expert personnel authorized by Lucent Technologies.

All changes carried out by other persons lead to a complete exemption from

liability.

No components/spare parts must be used other than those recommended by the manufacturer and those listed in the procurement documents.

•

The removal or disabling of safety facilities, the clearing of faults and errors, and the maintenance of the equipment must be carried out by specially qualified

personnel only.

The respective parts of the documentation must be strictly observed. The documentation must also be consulted during the selection of measuring and test equipment.

•

Calibrations, special tests after repairs and regular safety checks must be carried out, documented and archived.

•

Non-system software is used at one’s own risk. The use/installation of non-system software can adversely affect the normal functioning of the unit/system.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

1-5

Safety

Laser safety

.................................................................................................................................................................................................................................

System compliance

Metropolis

®

DMX complies with the following laser safety regulations and standards:

•

International Electrotechnical Commission (IEC) 60825-2: 2004 rules classify

Metropolis

®

DMX as a Class 1M laser product.

•

Food and Drug Administration’s Center for Devices and Radiological Health

(FDA/CDRH) 21 CFR 1040.10 and 1040.11 rules classify Metropolis

®

DMX as a

Class IIIb laser product

The following table shows the optical circuit pack laser safety specifications. The pluggable transmission modules (and their circuit packs) are covered in

Table 1-2,

“Pluggable transmission module laser safety specifications” (p. 1-7) .

Laser Circuit

Pack Code

Table 1-1 Optical circuit pack laser safety specifications

Wavelength

(nm)

Output

Power

(dBm)

Fiber Type

(µm)

Connector

Type

LNW36 OC-3

LNW46 OC-12

LNW48 OC-12

LNW50 OC-12

1310

1310

1310

1310

0.0

+2.0

-8.0

+2.0

Single Mode (9)

Single Mode (9)

Single Mode (9)

Single Mode (9)

LC

LC

LC

LC

LNW54 OC-12 1550

LNW26B OC-48 1310

LNW27 OC-48

LNW28 OC-48

LNW29 OC-48

1310

1310

1550

LNW31 OC-48

LNW32 OC-48

LNW76 OC-48

LNW77 OC-48

LNW121B-159B

OC-48

LNW221-259

OC-48

LNW421-459

OC-48

1310

1310

1310

1310

1550-range

1550-range

1550-range

+2.0

+3.0

+3.0

+3.0

+3.0

0.0

+3.0

-3.0

0.0

+2.0

+2.0

+2.0

Single Mode (9)

Single Mode (9)

Single Mode (9)

Single Mode (9)

Single Mode (9)

Single Mode (9)

Single Mode (9)

Single Mode (9)

Single Mode (9)

Single Mode (9)

Single Mode (9)

Single Mode (9)

LC

LC

LC

LC

LC

LC

LC

LC

LC

LC

LC

LC

FDA Class/

IEC Class

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

.................................................................................................................................................................................................................................

1-6 365-372-301 R6.0

Issue 15, January 2006

Safety Laser safety

Laser Circuit

Pack Code

Table 1-1 Optical circuit pack laser safety specifications (continued)

Wavelength

(nm)

Output

Power

(dBm)

Fiber Type

(µm)

Connector

Type

FDA Class/

IEC Class

LNW56 OC-192 1550

LNW57 OC-192 1550

+2.0

+6.0

Single Mode (9)

Single Mode (9)

LC

LC

I(LN50)/1

I(LN50)/1

LNW58 OC-192

LNW60 OC-192 1550

LNW523

OC-192

LNW527

OC-192

LNW554

OC-192

LNW555

OC-192

1310

1550-range

1550-range

1550-range

1553.465

-1.0

+12.5

+6.0

+6.0

+6.0

+6.0

Single Mode (9)

Single Mode (9)

Single Mode (9)

Single Mode (9)

Single Mode (9)

Single Mode (9)

LC

LC

LC

LC

LC

LC

I(LN50)/1

IIIb/1M

I(LN50)/1

I(LN50)/1

I(LN50)/1

I(LN50)/1

The following table shows the pluggable transmission module (PTM) laser safety specifications. The supported circuit packs are also listed in this table.

Module

Code

Table 1-2 Pluggable transmission module laser safety specifications

Supported

Circuit

Pack(s)

Wavelength

(nm)

Output

Power

(dBm)

Fiber Type

(µm)

Connector

Type

FDA Class/

IEC Class

1310 -8.0

LC I(LN50)/1 OC3IR1-I1 LNW37,

LNW45

OC3LR1-I1 LNW37,

LNW45

OC12IR1-I1 LNW49

1310

1310

0.0

-8.0

Single Mode

(9)

Single Mode

(9)

LC

LC

I(LN50)/1

I(LN50)/1

OC12LR1-I1

100BASE-

LX-I1

LNW49 1310

1310

+2.0

-8.0

Single Mode

(9)

Single Mode

(9)

Single Mode

(9)

LC

LC

I(LN50)/1

I(LN50)/1

1000BASE-

ZX-I1

LNW70,

LNW74,

LNW78

LNW63,

LNW70,

LNW78

1550 +5.0

Single Mode

(9)

LC I(LN50)/1

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

1-7

Safety Laser safety

Module

Code

GE-1X2XFC-

SX-C1

Table 1-2 Pluggable transmission module laser safety specifications

(continued)

Supported

Circuit

Pack(s)

Wavelength

(nm)

Output

Power

(dBm)

Fiber Type

(µm)

Connector

Type

FDA Class/

IEC Class

LNW70,

LNW73/73C,

LNW78

GE-1X2XFC-

LX-C1

LNW73/73C,

LNW78

850

1310

-2.5

-3.0

Multimode (50 and 62.5)

LC

LC

I(LN50)/1

I(LN50)/1

GE-1X2XFC-

SX-I1

LNW63

GE-1X2XFC-

LX-I1

LNW63

ESCON-

MM-I1

BASE-T-C1

- electrical

LNW73/73C 1310

LNW70

850

1310

NA

-2.5

-3.0

-14.0

NA

Single Mode

(9)

Multimode (50 and 62.5)

Single Mode

(9)

Multimode (50 and 62.5)

NA

LC

LC

LC

RJ45

I(LN50)/1

I(LN50)/1

I(LN50)/1

NA

Use only the following Lucent Approved Class 1 SFP transceivers.

Pluggable Transmission

Module Code/Comcode

OC3IR1-I1

10945389

OC3LR1-I1

109453886

OC12IR1-I1

109453902

OC12LR1-I1

109467522

100BASE-LX-I1

109527812

1000BASE-ZX-I1

109541862

Name

OM155 1.3IR1

OM155 1.3LR1

OM622 1.3IR1

OM622 1.3LR1

OMFE 100BASE-LX-SM

OM1G 1000BASE-ZX

Description

OC3 SFP TRCVR

Intermediate Reach - IR1

OC3 SFP TRCVR Long

Reach - LR1

OC12 SFP TRCVR

Intermediate Reach - IR1

OC12 SFP TRCVR Long

Reach - LR1

100 Mb/s optical Fast

Ethernet SFP TRCVR

1000 Mb/s optical Fast

Ethernet SFP TRCVR

.................................................................................................................................................................................................................................

1-8 365-372-301 R6.0

Issue 15, January 2006

Safety Laser safety

Pluggable Transmission

Module Code/Comcode

GE-1X2XFC-SX-C1

109527796

GE-1X2XFC-LX-C1

109527804

GE-1X2XFC-LX-l1

109568782

GE-1X2XFC-SX-l1

109570606

ESCON-MM-I1

109523886

BASE-T-C1

109565549

Name

OM1G//OMFC

1000BASE-SX//100/

200-M5/M6-SN-S

OM1G//OMFC

1000BASE-LX//100/

200-SM-LL-L-I

OM1G//OMFC

1000BASE-LX//100/200-

SM-LL-L-I

OM1G//OMFC

1000BASE-SX//100/200-

M5/M6-SN-S

OMESCON MMF

EM1G//EMFE FE and GbE

Description

1X Fibre Channel or 2X

Fibre Channel or GbE MM

SFP TRCVR

1X Fibre Channel or 2X

Fibre Channel or GbE SM

SFP TRCVR

1X Fibre Channel or 2X

Fibre Channel GbE SM

SFP TRCVR

1X Fibre Channel or 2X

Fibre Channel GbE MM

SFP TRCVR

ESCON MM SFP TRCVR

FE and GbE electical SFP

TRCVR

General laser information

Optical fiber telecommunication systems, their associated test sets, and similar operating systems use semiconductor laser transmitters that emit infrared (IR) light at wavelengths between approximately 800 nanometers (nm) and 1600 nm. The emitted light is above the red end of the visible spectrum, which is normally not visible to the human eye. Although radiant energy at near-IR wavelengths is officially designated invisible, some people can see the shorter wavelength energy even at power levels several orders of magnitude below any that have been shown to cause injury to the eye.

Conventional lasers can produce an intense beam of monochromatic light.

Monochromatic light is a single wavelength output of pure color that may be visible or invisible to the eye. A conventional laser produces a small-size beam of light, and because the beam size is small the power density (also called irradiance) is very high.

Consequently, lasers and laser products are subject to federal and applicable state regulations as well as international standards for their safe operation.

A conventional laser beam expands very little over distance, or is said to be very well collimated. Thus, conventional laser irradiance remains relatively constant over distance. However, lasers used in lightwave systems have a large beam divergence,

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

1-9

Safety Laser safety typically 10 to 20 degrees. Here, irradiance obeys the inverse square law (doubling the distance reduces the irradiance by a factor of 4) and rapidly decreases over distance.

Lasers and eye damage

The optical energy emitted by laser and high-radiance LEDs in the 400-1400 nm range may cause eye damage if absorbed by the retina. When a beam of light enters the eye, the eye magnifies and focuses the energy on the retina magnifying the irradiance. The irradiance of the energy that reaches the retina is approximately 105 or 100,000 times more than at the cornea and, if sufficiently intense, may cause a retinal burn.

The damage mechanism at the wavelengths used in an optical fiber telecommunications is thermal in origin, for example, damage caused by heating. Therefore, a specific amount of energy is required for a definite time to heat an area of retinal tissue.

Damage to the retina occurs only when one looks at the light sufficiently long that the product of the retinal irradiance and the viewing time exceeds the damage threshold.

Optical energies above 1400 nm cause corneal and skin burns, but do not affect the retina. The thresholds for injury at wavelengths greater than 1400 nm are significantly higher that for wavelengths in the retinal hazard region.

Classification of lasers

Manufacturers of lasers and laser products in the U.S. are regulated by the Food and

Drug Administration’s Center for Devices and Radiological Health (FDA/CDRH) under

21 CFR 1040. These regulations require manufacturers to certify each laser or laser product as belonging to one of four major Classes I, II, lla, IlIa, lllb, or IV.

The International Electrotechnical Commission (IEC) is an international standards body that writes laser safety standards under IEC-60825. Classification schemes are similar and divided into Classes 1, 1M, 2, 2M, 3B, 3R and 4. Lasers are classified according to the accessible emission limits and their potential for causing injury.

Optical fiber telecommunication systems are generally classified as Class I/1, because, under normal operating conditions, all energized laser transmitting circuit packs are terminated on optical fibers which enclose the laser energy with the fiber sheath forming a protective housing. Also, a protective housing/access panel is typically installed in front of the laser circuit pack shelves. The circuit packs themselves, however, may be FDA/CDRH Class I, IIIb, or IV or IEC Class 1, 1M, 3B, 3R or 4.

State of the art Raman and EDFA optical amplifiers have now extended into the Class

IV/4 designations

Laser safety precautions for optical fiber telecommunications systems

In its normal operating mode, an optical fiber telecommunication system is totally enclosed and presents no risk of eye injury. It is a Class I/1 system under the

FDA/CDRH and IEC classifications.

.................................................................................................................................................................................................................................

1-10 365-372-301 R6.0

Issue 15, January 2006

Safety Laser safety

The fiber optic cables that interconnect various components of an optical fiber telecommunication system can disconnect or break, and may expose people to lightwave emission. Also, certain measures and maintenance procedures may expose the technician to emission from the semiconductor laser during installation and servicing. Unlike more familiar laser devices, such as solid-state and gas lasers, the emission pattern of a semiconductor laser results in a highly divergent beam. In a divergent beam, the irradiance (power density) decreases rapidly with distance. The greater the distance, the less energy will enter the eye and the less potential risk for eye injury. Inadvertently viewing an unterminated fiber or damaged fiber with the unaided eye at distances greater than 5 to 6 inches normally will not cause eye injury provided the power in the fiber is less than a few milliwatts at the near IR wavelengths and a few tens of milliwatts at the far IR wavelengths. However, damage may occur if an optical instrument such as a microscope, magnifying glass, or eye loupe is used to stare at the energized fiber end.

Laser Radiation

CAUTION

Laser hazard

Use of controls, adjustments, and procedures other than those specified herein may result in hazardous laser radiation exposure.

Use controls, adjustments, and procedures specified in this document.

Laser safety precautions for enclosed systems

Under normal operating conditions, optical fiber telecommunication systems are completely enclosed. Observe the following laser safety precautions for enclosed systems:

•

Because of the potential for eye damage, technicians should not stare into optical connectors or broken fibers.

•

Under no circumstance shall laser/fiber optic operations be performed by a technician before satisfactorily completing laser safety training.

•

Since viewing lightwave emission directly in excess of Class I/1 limits with an optical instrument such as an eye loupe greatly increases the risk of eye damage, appropriate labels must appear in plain view, in close proximity to the optical port on the protective housing/access panel of the terminal equipment.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

1-11

Safety Laser safety

Laser safety precautions for unenclosed systems

During service, maintenance, or restoration, an optical fiber telecommunication system is considered unenclosed. Observe the following laser safety precautions for unenclosed systems:

•

Only authorized, trained personnel shall be permitted to do service, maintenance, and restoration. Avoid exposing the eye to emissions from unterminated, energized optical connectors at close distances. Laser modules associated with the optical ports of laser circuit packs are typically recessed, which limits the exposure distance. Optical port shutters and automatic power reduction (APR), and automatic power shut down (APSD) are engineering controls that are also used to limit the emissions. However, technicians removing or replacing laser circuit packs should not stare or look directly into the optical port with optical instruments or magnifying lenses. (Normal eye wear or indirect viewing instruments, such as a

Find-R-Scopes, are not considered magnifying lenses or optical instruments.)

•

Only authorized, trained personnel shall use the optical test equipment during installation or servicing since this equipment contains semiconductor lasers. (Some examples of optical test equipment are Optical Time Domain Reflectometers

[OTDRs] and Hand-Held Loss Test Sets.)

•

Under no circumstances shall any personnel scan a fiber with an optical test set without verifying that all laser sources on the fiber are turned off.

•

All unauthorized personnel shall be excluded from the immediate area of the optical fiber telecommunication systems during installation and service.

Consult ANSI Z136.2, American National Standard for Safe Use of Optical Fiber

Communication Systems Utilizing Laser Diodes and LED Sources in the United States or outside the United States, IEC-60825, Part 2 for guidance on the safe use of optical fiber optic communication systems in the workplace.

.................................................................................................................................................................................................................................

1-12 365-372-301 R6.0

Issue 15, January 2006

Safety

Laser warning labels

The following figure shows the different types of laser warning labels.

Figure 1-1 Laser warning labels

1

Laser safety

2

CLASS 1 LASER

PRODUCT

HAZARD

LEVEL

1M

3

DANGER

INVISIBLE LASER RADIATION

WHEN OPEN AND FIBER

DISCONNECTED

Avoid direct exposure to beam

Do not view beam directly with optical instruments

CAUTION

CLASS 1M INVISIBLE

LASER RADIATION

WHEN OPEN

AND FIBER

DISCONNECTED.

Do not view directly with optical instruments.

ATTENTION

RAYONNEMENT

LASER DE CLASSE

1M INVISIBLE

LORSQUE

L’APPAREIL EST

OUVERT ET QUE

LA FIBRE EST

É

Ne pas regarder directement au moyen d’un instrument optique.

848950572

MA-DMX-416

Legend

1. Laser symbol.

2. Laser classification labels. This label may show only the laser class or both the laser class and the maximum output power.

3. Laser warning labels.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

1-13

Safety

Electrostatic discharge

.................................................................................................................................................................................................................................

Overview

Electrostatic discharge (ESD) (for example, caused by touching with the hand) can destroy semiconductor components. The correct operation of the complete system is then no longer assured.

Electrostatic discharge (ESD) warning

CAUTION

ESD hazard

Electronic components can be destroyed by electrostatic discharge.

Circuit packs must always be kept in antistatic covers. Use the original packaging if

possible. Use a static ground wrist strap whenever handling circuit packs or working

on the Metropolis

®

DMX system to prevent electrostatic discharge damage to sensitive components.

All semiconductor components are basically sensitive to electrostatic discharge. The electrostatic discharge can also affect the components indirectly using contacts or conductor tracks.

Electrostatic discharge (ESD) considerations

This section describes the precautions required to prevent damage by electrostatic discharge.

Circuit pack handling precautions

Industry experience has shown that all integrated circuit packs can be damaged by static electricity that builds up on work surfaces and personnel. The static charges are produced by various charging effects of movement and contact with other objects. Dry air allows greater static charges to accumulate. Higher potentials are measured in areas with low relative humidity, but potentials high enough to cause damage can occur anywhere.

Observe the following precautions when handling circuit packs/units to prevent damage by electrostatic discharge:

•

Assume all circuit packs contain solid-state electronic components that can be damaged by ESD.

•

When handling circuit packs (storing, installing, removing, etc.) or when working on the backplane, always wear a grounded wrist strap or wear a heel strap and stand on a grounded, static-dissipating floor mat.

•

Wear working garment made of 100% cotton to avoid electrostatic discharge.

.................................................................................................................................................................................................................................

1-14 365-372-301 R6.0

Issue 15, January 2006

Safety Electrostatic discharge

•

Handle all circuit packs by the faceplate or latch and by the top and bottom outermost edges. Never touch the components, conductors, or connector pins.

•

Store and ship circuit packs and components in their shipping packing. Circuit packs and components must be packed and unpacked only at workplaces suitably protected against build-up of charge.

•

Observe all warning labels on bags and cartons. Whenever possible, do not remove circuit packs from antistatic packaging until ready to insert them into slots.

•

If possible, open all circuit packs at a static-safe work position, using properly grounded wrist straps and static-dissipating table mats.

•

Always store and transport circuit packs in static-safe packaging. Shielding is not required unless specified.

•

Keep all static-generating materials such as food wrappers, plastics, and

Styrofoam® containers away from all circuit packs. When removing circuit packs from a shelf, immediately place the circuit packs in static-safe packages.

•

Whenever possible, maintain relative humidity above 20 percent.

Important! Any connectors on the shelf interconnection panel that are not cabled should be fitted with a plastic dust cap to provide ESD protection.

Static control wrist straps

To reduce the possibility of ESD damage, the Metropolis

®

DMX shelf is equipped with an ESD grounding jack to enable personnel to ground themselves using wrist straps

( Figure 1-2, “Static control wrist strap” (p. 1-15) ), while handling circuit packs or

working on the shelf. The wrist straps should be checked periodically with a wrist strap tester to ensure that they are working properly.

Figure 1-2 Static control wrist strap

To

Ground

Connection

NC-USM-110

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

1-15

Safety Electrostatic discharge

Important! The grounding jack is located on the front of the shelf, on the lower right-hand corner. Another grounding jack is also located on the rear panel.

Barred-hand symbol

Circuit packs containing components that are especially sensitive to electrostatic discharge are identified by warning labels bearing the barred-hand symbol. The following figure shows the barred-hand symbol.

Figure 1-3 Electrostatic discharge warning label (barred-hand symbol)

MA-metro-429

.................................................................................................................................................................................................................................

1-16 365-372-301 R6.0

Issue 15, January 2006

Safety

Save these safety instructions

.................................................................................................................................................................................................................................

READ AND UNDERSTAND ALL INSTRUCTIONS.

The exclamation point within an equilateral triangle is intended to alert the user to the presence of important operating and maintenance (servicing) instructions in the literature accompanying this product.

When installing, operating, or maintaining this equipment, basic safety precautions should always be followed to reduce the risk of fire, electric shock, and injury to persons, including the following:

1. Read and understand all instructions.

2. Follow all warnings and instructions marked on this product.

3. This product should be only operated from the type of power sources indicated on the marking label.

4. Connect this product only to the type of power sources recommended by Lucent

Technologies. For information on the powering instructions, consult the

Metropolis

®

DMX Access Multiplexer Installation Manual, 365-372-304.

5. This equipment is suitable for mounting on a concrete or other non combustible surface only.

6. For information on proper mounting instructions, consult the Metropolis

®

Access Multiplexer Installation Manual, 365-372-304.

DMX

7. Install only equipment identified in the Metropolis

®

DMX Access Multiplexer

Installation Manual, 365-372-304. Use of other equipment may result in improper connection of circuitry leading to fire or injury to persons.

8. All metallic telecommunication interfaces (traffic ports) should not leave the building premises unless connected to telecommunication devices providing primary and secondary protection, as applicable.

9. Do not use this product near water, for example, in a wet basement.

10. Do not place this product on an unstable cart, stand, or table. The product may fall, causing serious damage to the product.

11. Use caution when installing or modifying telecommunications lines.

12. Never install telecommunications wiring during a lightning storm.

13. Never install telecommunications connections in wet locations.

14. Never touch uninsulated telecommunications wires or terminals unless the telecommunications line has been disconnected at the network interface.

15. Never touch uninsulated wiring or terminals carrying direct current or ringing current, or leave this wiring exposed. Protect and tape uninsulated wiring and terminals to avoid risk of fire, electric shock, and injury to service personnel.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

1-17

Safety Save these safety instructions

16. Never push objects of any kind into this product through slots as they may touch dangerous voltage points or short out parts that could result in a risk of fire or electrical shock. Never spill liquids of any kind on the product.

17. Slots and openings in the unit are provided for ventilation, to protect it from overheating. Do not block or cover these openings. This product should not be placed in a built-in installation unless proper ventilation is provided.

18. To reduce the risk of an electrical shock, do not disassemble this product. Service should be performed by trained personnel only. Opening or removing covers and/or circuit boards may expose you to dangerous voltages or other risks. Incorrect reassembly can cause electrical shock when the unit is subsequently used.

19. Some of the Metropolis

®

DMX family hardware modules contain FDA/CDRH

Class IIIb/IEC Class 1M single-mode laser products that are enclosed lightwave transmission systems.

Under normal operating conditions, lightwave transmission systems are completely enclosed; however, the following precautions must be observed because of the potential for eye damage:

•

Do not connect any lightwave cable or splice and stare into the optical connectors terminating the cables.

•

Lightwave/lightguide operations should not be performed by a technician who has not satisfactorily completed an approved training course.

•

Do not use optical instruments such as an eye loupe to view a fiber or unterminated connector.

•

More information about laser safety can be found in the Metropolis

®

DMX

Access Multiplexer Installation Manual, 365-372-304.

20. For a unit intended to be powered from -48 V DC voltage sources, read and understand the following:

•

To be powered only by Safety Extra Low Voltage (SELV) -48 V DC sources.

•

Disconnect up to two power supply connections when removing power from the system.

•

This equipment must be provided with a readily accessible disconnect device as part of the building installation.

•

Ensure that there is no exposed wire when the input power cables are connected to the unit.

•

Installation must include an independent frame ground drop to building ground.

Refer to the Metropolis

®

DMX Access Multiplexer Installation Manual,

365-372-304.

.................................................................................................................................................................................................................................

1-18 365-372-301 R6.0

Issue 15, January 2006

Safety Save these safety instructions

This electrical ground symbol is marked on the product, adjacent to the ground

(earth) area for the connection of the ground (earth) conductor.

•

This equipment is to be installed only in Restricted Access Areas on Business and Customer Premises Applications in Accordance with Articles 110-16,

110-17, and 110-18 of the National Electrical Code, ANSI/NFPA No. 70. Other installations exempt from the enforcement of the National Electrical Code may be engineered according to the accepted practices of the local telecommunications utility.

21. For a unit intended to be powered from 100-120/200-240 V AC voltage sources, read and understand the following:

•

Unplug this product from the wall outlet before cleaning. Do not use liquid cleaners or aerosol cleaners. Use a damp cloth for cleaning.

•

Do not staple or otherwise attach the power supply cord to the building surfaces.

•

Do not overload wall outlets and extension cords as this can result in the risk of fire or electrical shock.

•

The socket outlet shall be installed near the equipment and shall be readily accessible.

•

This product is equipped with a three-wire grounding type plug, a plug having a third (grounding) pin. This plug is intended to fit only into a grounding type power outlet. This is a safety feature. If you are unable to insert the plug into the outlet, contact your electrician to replace your obsolete outlet. Do not defeat the safety purpose of the grounding type plug. Do not use a 3-to-2-prong adapter at the receptacle. Use of this type adapter may result in risk of electrical shock and/or damage to this product.

•

Do not allow anything to rest on the power cord. Do not locate this product where the cord may be abused by persons walking on it.

22. Unplug this product from the wall outlet and refer servicing to qualified service personnel under the following conditions:

•

When the powers supply cord or plug is damaged or frayed.

•

If liquid has been spilled into the product.

•

If the product has been exposed to rain or water.

•

If the product does not operate normally by following the operating instructions.

Adjust only those controls that are covered by the operating instructions because improper adjustment of other controls may result in damage and will often require extensive work by qualified technician to restore the product to normal operation.

•

If the product has been dropped or the cabinet has been damaged.

•

If the product exhibits a distinct change in performance.

SAVE THESE INSTRUCTIONS.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

1-19

Safety Save these safety instructions

Recycling / Take-Back / Disposal of Product

Electronic products bearing or referencing the symbol shown below when put on the market within the European Union, shall be collected and treated at the end of their useful life, in compliance with applicable European Union and local legislation. They shall not be disposed of as part of unsorted municipal waste. Due to materials that may be contained in the product, such as heavy metals or batteries, the environment and human health may be negatively impacted as a result of inappropriate disposal.

Note

: In the European Union, a solid bar under the crossed-out wheeled bin indicates that the product was put on the market after 13 August 2005.

Moreover, in compliance with legal requirements and contractual agreements, where applicable, Lucent Technologies will offer to provide for the collection and treatment of Lucent Technologies products at the end of their useful life, or products displaced by Lucent Technologies equipment offers.

For information regarding take-back of equipment by Lucent Technologies, or for more information regarding the requirements for recycling/disposal of product, please contact your Lucent Account Manager or Lucent Takeback Support at [email protected].

.................................................................................................................................................................................................................................

1-20 365-372-301 R6.0

Issue 15, January 2006

2

2

upgrades, and database backup procedures

Overview

.................................................................................................................................................................................................................................

Purpose

This chapter includes procedures used to:

•

Install a new generic software program

•

Download a generic software program

•

Copy a generic software program to a remote NE

•

Apply (activate) a generic software program

•

Backup the network element database

•

Restore the network element database

Contents

Before you begin

Procedure 2-1: Install software generic (initial) via FTAM

Procedure 2-2: Install software generic (initial) via FTP

Procedure 2-3: Upgrade software generic via FTAM

Procedure 2-4: Upgrade software generic via FTP

Procedure 2-5: Upgrade software generic via FTTD (6.0.0 to 6.0.x)

Procedure 2-6: Copy software generic to a remote shelf

Procedure 2-7: Apply software generic

Procedure 2-8: Backup and restore NE database via FTP

Procedure 2-9: Backup and restore NE database via FTTD

Procedure 2-10: Backup and restore NE database via FTAM

2-2

2-3

2-21

2-40

2-72

2-109

2-115

2-120

2-123

2-135

2-150

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-1

Software installation and upgrades, and database backup procedures

Before you begin

.................................................................................................................................................................................................................................

Before you begin

Prior to performing most procedures in this chapter,

1. If not previously completed, install generic and WaveStar

®

CIT software on the PC.

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

2. Connect PC and establish a WaveStar

®

CIT session.

Refer to

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24) .

Required equipment

The procedures in this chapter require the following equipment:

•

Personal Computer (PC) with WaveStar

®

CIT software installed

•

Wrist strap

Important! If additional equipment is required to perform a specific procedure, that additional equipment is listed in that procedure.

.................................................................................................................................................................................................................................

2-2 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

.................................................................................................................................................................................................................................

Overview

Use this procedure to install the software generic via the File Transfer and Access

Management (FTAM) protocol in a factory-fresh LNW2 SYSCTL. A factory-fresh

SYSCTL circuit pack does not contain a software generic; it only contains the information loaded at the factory (boot code).

To install the software generic via FTP, refer to

Procedure 2-2: “Install software generic (initial) via FTP” (p. 2-21) .

Important! You must have OSI connectivity (via your OSI LAN or DCC) to the network element to use FTAM.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

In addition to

“Required equipment” (p. 2-2)

listed in this chapter, the following equipment is also required:

•

CAT5 Ethernet cable with either a 10/100 hub or a cross-over cable for the

LAN

or

IAO LAN

port (required for TCP/IP connectivity)

•

Copy of the new system generic software program accessible from your PC

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

•

Factory-fresh LNW2, system controller (SYSCTL), with two factory-installed non-volatile memory (NVM) cards installed

•

Current Metropolis

®

DMX Access Multiplexer Software Release Description for the software generic being installed

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 2-2)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

2. Verify that new software generic program is available.

3. Refer to the Metropolis

®

DMX Access Multiplexer Software Release Description for a description of any special considerations required when installing this version of software.

4. Unseat all circuit packs in the shelf, except the LNW2 SYSCTL to which you are downloading the new software generic.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-3

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

Important! This procedure is intended for new shelf installations only. Do not use this procedure to upgrade an in-service shelf.

Step

1

2

Complete the following steps to install the software generic program via FTAM in a new shelf installation with only a factory-fresh LNW2 SYSCTL installed.

.................................................................................................................................................................................................

Important! A factory-fresh SYSCTL circuit pack does not contain a software generic; it only contains the information loaded at the factory (boot code).

Verify that only a factory-fresh LNW2 SYSCTL is present in your Metropolis

®

DMX shelf; no other circuit packs should be seated in the shelf. An LNW2 SYSCTL is required to install 6.0 software; you cannot install 6.0 into an LNW1 SYSCTL.

.................................................................................................................................................................................................

Important! For software installation, two NVMs should be present in the LNW2

SYSCTL. After the LNW2 is installed, if one or two NVMs are missing,

NVM removed alarm(s) are issued. If both NVM sockets are empty, the

IND

displays an alternating

E

and

0

and

1

.

Refer to

Step 3

for the complete listing of codes and required actions.

Seat the new LNW2 SYSCTL circuit pack and allow a few minutes for the pack to complete initialization.

Result:

The LNW2 SYSCTL exhibits the following visible cycles during initialization:

1. The

FAULT

LED lights and remains lighted for approximately 90 seconds. After approximately 15 seconds, a flashing

b

appears in the

IND

display on the

SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 75 seconds and then

IND

display is blank.

2. The

FAULT

LED remains lighted for approximately another 20 seconds and then extinguishes.

3. The

ACTIVE

LED lights and remains lighted and the

CR

LED flashes 10 times.

While the

CR

LED is flashing, the

MJ

,

ABN

, and

NE

LEDs light and remain lighted.

Because the LNW2 SYSCTL is in 6.0 Maintenance Mode, an alternating

M

and

P

and

6

and “

.

” (“.” is a red, four-segment square [2 x 2] representing a period) and

0

appear in the

IND

display.

4. Continue with

Step 3 .

.................................................................................................................................................................................................................................

2-4 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

3

.................................................................................................................................................................................................

Observe the

IND

display on the LNW2 SYSCTL; the display indicates the state of the

SYSCTL.

If...

alternating

M

and

P

and

6

and “

.

”

(“.” is a red, four-segment square

[2 x 2] representing a period) and

0

alternating

E

and

0

and

0

alternating alternating alternating alternating

Letter

F

alternating

E

E

E

E

N

and and and and and

0

0

0

1

O

and and and and and

1

2

3

0 x

Then...

6.0 Maintenance Mode. Continue with

Step 4 .

LNW2 SYSCTL must be replaced.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

No NVMs are detected on the LNW2 SYSCTL.

Install two Lucent-supplied NVMs in the LNW2 or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

NVMs are present but not readable. Check to make sure they are properly seated and repeat this procedure.

Not Supported.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

LNW2 SYSCTL will not boot.

No compatible generic on the NVMs in the

LNW2 SYSCTL.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure or contact your next level of support.

LNW2 SYSCTL faceplate latches are not fully seated.

Unseat the LNW2 SYSCTL and repeat this procedure, properly seating the faceplate latch.

“x” indicates that the NVM socket (1 or 2) is empty or the NVM installed is failed. Replace the indicated NVM or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-5

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

If...

Letter

U

flashing

b

A red, four-segment square (2 x 2) appears in the

IND

display on the

LNW2 SYSCTL.

Then...

LNW2 SYSCTL will not boot due to unexpected or unreadable shelf type.

Repair the problem generally caused by bent pins and repeat this procedure.

Boot in progress.

Acknowledges the

UPD/INIT

button was momentarily pushed.

Pushing the

UPD/INIT

button while in

Maintenance Mode has no effect.

4

5

.................................................................................................................................................................................................

Connect the cross-over LAN cable from the PC’s Network Interface Card (NIC) to the rear

J16 IAO LAN

port on the Metropolis

®

DMX shelf backplane or the front

LAN

port on the SYSCTL circuit pack faceplate and establish a WaveStar

®

CIT session. (When

TCP/IP is enabled on the rear LAN port, OSI is disabled.)

Start the WaveStar

®

CIT software on the PC by double-clicking on the WaveStar

®

CIT icon on your desktop and login (if necessary). Refer to

Procedure 14-2: “Connect

Personal Computer (PC) and establish WaveStar

®

CIT session” (p. 14-24) .

Result:

The Network View appears.

.................................................................................................................................................................................................

From the

View:

pull-down menu, select

CIT OSI Neighbors

.

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................................................

2-6 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

Result:

The CIT OSI Neighbor(s) are automatically detected.

Figure 2-1 CIT OSI neighbor

6

7

.................................................................................................................................................................................................

In the Network View,

Figure 2-1, “CIT OSI neighbor” (p. 2-7) , right-click on the

LT-DMX NE icon and select

Graphical Using

→

OSI

from the resulting menu.

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX Access Multiplexer and click

OK

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-7

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

8

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

Important! Because the shelf is in Maintenance Mode, your logins and passwords are default.

Enter the following in the NE Login Dialog window (login information is case sensitive) to log in to the NE:

User ID:

LUC01

Password:

DMX2.5G10G

Click

OK

.

Important! LUC01, LUC02, and LUC03 are the default privileged User IDs, and

DMX2.5G10G is the default privileged password for Metropolis

®

DMX. To preserve the security of your equipment, it is highly recommended that you change all three logins and passwords during your first session after completing this initial installation procedure.

.................................................................................................................................................................................................................................

2-8 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

Result:

Screen 1 of 4 in the Maintenance Mode Wizard appears.

This screen picks up the time format preference from the WaveStar

®

CIT.

You can provision the time format display for your WaveStar

®

CIT from the

Network View by selecting

View

→

Preferences

and clicking on the Display tab.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-9

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

9

This screen allows you to choose your preference for time format, either a 12-hour clock or a 24-hour clock.

•

If your time format preference is a 12-hour clock, from the

Time

panel, select

Hour:

(0-12),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus.

You must also specify am or pm by selecting one of the radio buttons.

•

If your time format preference is a 24-hour clock, From the

Time

panel, select the

Hour:

(0-23),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus.

.................................................................................................................................................................................................

Important! The actual time and date are preset from your PC.

On Screen 1 of 4 in the Maintenance Mode Wizard, read the information, verify the date and time, make any required changes, and click

Next

.

.................................................................................................................................................................................................................................

2-10 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

Result:

Screen 2 of 4 in the Maintenance Mode Wizard appears.

10

.................................................................................................................................................................................................

On Screen 2 of 4 in the Maintenance Mode Wizard, click

Download

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-11

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

Result:

Screen 1 of 3 in the Download Generic Wizard appears.

11

.................................................................................................................................................................................................

On Screen 1 of 3 in the Download Generic Wizard, read the information, select

FTAM

and click

Next

.

.................................................................................................................................................................................................................................

2-12 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

Result:

Screen 2 of 3 in the Download Generic Wizard appears.

12

.................................................................................................................................................................................................

Important! LAN-1 is the

LAN

port on the faceplate of the LNW2 SYSCTL circuit pack. LAN-2 is the

J16 IAO LAN

port on the rear of the Metropolis

®

DMX shelf.

On Screen 2 of 3 in the Download Generic Wizard, read the information, verify that the LAN port you are connected to has OSI Function Enable selected and click

Next

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-13

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

Result:

Screen 3 of 3 in the Download Generic Wizard appears.

13

.................................................................................................................................................................................................

On Screen 3 of 3 in the Download Generic Wizard in the

Path

panel, enter the current location of the generic to be downloaded in the Path field or use the

Browse

button to select the generic to be downloaded. Click

Download

.

The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:/Program

Files/Lucent Technologies/WaveStar CIT/generics/DMX/6.0.1/p/

. The syntax

.................................................................................................................................................................................................................................

2-14 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

14

of the relative path must start with the path name; for example:

/generics/DMX/6.0.1/p/

. (If necessary, replace 6.0.1 with your current release, for example 6.0.2.)

Result:

A warning message appears listing the options you provisioned in the previous screens.

.................................................................................................................................................................................................

Verify the information and either click

Yes

to start the download process or click

No

to return to the download screen and change your selections.

Result:

If you choose yes, the following initial software download progress indicator runs for approximately 10 minutes.

15

.................................................................................................................................................................................................

Once the software generic download is complete, the following confirmation message appears. Click

Yes

to use the generic that is now in the Dormant area.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-15

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

Result:

Screen 3 of 4 in the Maintenance Mode Wizard appears.

16

.................................................................................................................................................................................................

On Screen 3 of 4 in the Maintenance Mode Wizard, click the check box next to

Default to create a default database and click

Next

.

.................................................................................................................................................................................................................................

2-16 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

Result:

Screen 4 of 4 in the Maintenance Mode Wizard appears. In this screen,

6.0.1 is an example; your selected generic could be different, for example 6.0.2.

17

.................................................................................................................................................................................................

On Screen 4 of 4 in the Maintenance Mode Wizard, read the information, verify that you have selected the correct 6.0.x generic and the default 6.0.x database and click

Finish

to restart the system and apply the generic and default database.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-17

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

18

19

20

Result:

The Maintenance Mode Wizard closes and your connection to the shelf is terminated.

The LNW2 SYSCTL exhibits the following visible cycles while the generic and database are installed and validated and the SYSCTL reboots:

1. For approximately 10 minutes, the alternating

M

and

P

and

6

and “

.

” (“.” is a red, four-segment square [2 x 2] representing a period) and

0

continue to appear in the

IND

display on the SYSCTL.

2. After approximately 10 minutes, all LEDs extinguish and the

IND

display on the

SYSCTL is blank for approximately 5 seconds.

3. A flashing

b

appears in the

IND

display on the SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 60 seconds and then

IND

display is blank for approximately 20 seconds.

4. The

ACTIVE

LED lights and remains lighted.

5. A flashing

b

appears again in the

IND

display on the SYSCTL, indicating that a boot is in progress. After approximately 30 seconds, the

CR

LED flashes 10 times and then extinguishes, and the

b

continues flashing for approximately another 30 seconds, and then

IND

display is blank.

6. The

ABN

and

NE

LEDs light and remain lighted for approximately 6 minutes.

The active generic and database are being validated and copied to the second

NVM.

7. When the

ABN

and

NE

LEDs extinguish and only the

ACTIVE

LED is lighted, and nothing appears in the

IND

display, the NE software and database installation is complete.

8. Continue with

Step 18 .

.................................................................................................................................................................................................

To verify that the download was successful, depress and hold the

ACO TEST

push-button on the LNW2 SYSCTL for about 4 seconds.

Result:

All LEDs on the shelf light. A red, 35-segment (5 x 7) rectangle appears in the

IND

display on the SYSCTL. Since the

IND

display is a 35-segment display, this test indicates all segments are working.

.................................................................................................................................................................................................

Release the

ACO TEST

push-button on the LNW2 SYSCTL when the red rectangle disappears in the

IND

display.

Result:

The current software generic appears in the

IND

display on the LNW2

SYSCTL and the shelf LEDs return to their previous status.

.................................................................................................................................................................................................

From the Network View of the WaveStar

®

CIT session you established in

Step 4 ,

select the

View:

pull-down menu and select

CIT OSI Neighbors

.

.................................................................................................................................................................................................................................

2-18 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

21

22

23

24

25

Procedure 2-1: Install software generic (initial) via FTAM

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................

From the Network View, select

View

→

Refresh OSI View

.

Result:

The CIT OSI neighbor(s) are automatically detected.

.................................................................................................................................................................................................

In the Network View, right-click on the LT-DMX NE icon that was detected, and select

Graphical Using

→

OSI

from the resulting menu.

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX and click

OK

.

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

Enter the following in the NE Login Dialog window (login information is case sensitive) to log in to the NE:

User ID:

LUC01

Password:

DMX2.5G10G

Click

OK

.

Important! LUC01, LUC02, and LUC03 are the default privileged User IDs, and

DMX2.5G10G is the default privileged password for Metropolis

®

DMX. It is highly recommended that you change all three logins and passwords during your first session to preserve the security of your equipment.

Result:

The title bar of the System View and the legal notice text should both reflect the current NE software generic, for example: R6.0.1.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Is the Generic Software Version correct?

If...

Yes

No

Then...

STOP! End of Procedure.

Contact your next level of support.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-19

Software installation and upgrades, and database backup procedures

Procedure 2-1: Install software generic (initial) via FTAM

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

2-20 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

.................................................................................................................................................................................................................................

Overview

Use this procedure to install software generic in a factory-fresh LNW2 SYSCTL via

File Transfer Protocol (FTP). A factory-fresh SYSCTL circuit pack does not contain a software generic; it only contains the information loaded at the factory (boot code).

To install the software generic via FTAM, refer to

Procedure 2-1: “Install software generic (initial) via FTAM” (p. 2-3) .

Important! You must have direct TCP/IP connectivity to your NE via LAN-1 or

LAN-2 and you must know the IP address of your FTP server. (The WaveStar

®

CIT may be the FTP server.)

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

In addition to

“Required equipment” (p. 2-2)

listed in this chapter, the following equipment is also required:

•

CAT5 Ethernet cable with either a 10/100 hub or a cross-over cable for the

LAN

or

IAO LAN

port (required for TCP/IP connectivity)

•

Copy of the new system generic software program on your PC or FTP server

•

Factory-fresh LNW2, system controller (SYSCTL), with two factory-installed non-volatile memory (NVM) cards installed

•

Current Metropolis

®

DMX Access Multiplexer Software Release Description for the software generic being installed

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 2-2)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

2. Verify that new software generic program is available.

3. Refer to the Metropolis

®

DMX Access Multiplexer Software Release Description for a description of any special considerations required when installing this version of software.

4. Unseat all circuit packs in the shelf, except the SYSCTL to which you are downloading the new software generic.

5. If the WaveStar

®

CIT is the FTP server, determine the IP address assigned to your

PC LAN card that will be used to connect to the shelf.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-21

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

Important! This procedure is intended for new shelf installations only. Do not use this procedure to upgrade an in-service shelf.

Step

1

2

Complete the following steps to install the software generic program via FTP in a new shelf installation with only a factory-fresh SYSCTL installed.

.................................................................................................................................................................................................

Important! A factory-fresh SYSCTL circuit pack does not contain a software generic; it only contains the information loaded at the factory (boot code).

Verify that only a factory-fresh LNW2 SYSCTL is installed in your Metropolis

®

DMX shelf; no other circuit packs should be seated in the shelf. An LNW2 SYSCTL is required to install 6.0 software; you cannot install 6.0 into an LNW1 SYSCTL.

.................................................................................................................................................................................................

Important! For software installation, two NVMs should be present in the LNW2

SYSCTL. After the LNW2 is installed, if one or two NVMs are missing,

NVM removed alarm(s) are issued. If both NVM sockets are empty, the

IND

displays an alternating

E

and

0

and

1

.

Refer to

Step 3

for the complete listing of codes and required actions.

Seat the new LNW2 SYSCTL circuit pack and allow a few minutes for the pack to complete initialization.

Result:

The LNW2 SYSCTL exhibits the following visible cycles during initialization:

1. The

FAULT

LED lights and remains lighted for approximately 90 seconds. After approximately 15 seconds, a flashing

b

appears in the

IND

display on the

SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 75 seconds and then

IND

display is blank.

2. The

FAULT

LED remains lighted for approximately another 20 seconds and then extinguishes.

3. The

ACTIVE

LED lights and remains lighted and the

CR

LED flashes 10 times.

While the

CR

LED is flashing, the

MJ

,

ABN

, and

NE

LEDs light and remain lighted.

Because the LNW2 SYSCTL is in 6.0 Maintenance Mode, an alternating

M

and

P

and

6

and “

.

” (“.” is a red, four-segment square [2 x 2] representing a period) and

0

appear in the

IND

display.

4. Continue with

Step 3 .

.................................................................................................................................................................................................................................

2-22 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

3

.................................................................................................................................................................................................

Observe the

IND

display on the LNW2 SYSCTL; the display indicates the state of the

SYSCTL.

If...

alternating

M

and

P

and

6

and “

.

”

(“.” is a red, four-segment square

[2 x 2] representing a period) and

0

alternating

E

and

0

and

0

alternating alternating alternating alternating

Letter

F

alternating

E

E

E

E

N

and and and and and

0

0

0

1

O

and and and and and

1

2

3

0 x

Then...

6.0 Maintenance Mode. Continue with

Step 4 .

LNW2 SYSCTL must be replaced.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

No NVMs are detected on the LNW2 SYSCTL.

Install two Lucent-supplied NVMs in the LNW2 or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

NVMs are present but not readable. Check to make sure they are properly seated and repeat this procedure.

Not Supported.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

LNW2 SYSCTL will not boot.

No compatible generic on the NVMs in the

LNW2 SYSCTL.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure or contact your next level of support.

LNW2 SYSCTL faceplate latches are not fully seated.

Unseat the LNW2 SYSCTL and repeat this procedure, properly seating the faceplate latch.

“x” indicates that the NVM socket (1 or 2) is empty of the NVM installed is failed. Replace the indicated NVM or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-23

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

If...

Letter

U

flashing

b

A red, four-segment square (2 x 2) appears in the

IND

display on the

LNW2 SYSCTL.

Then...

LNW2 SYSCTL will not boot due to unexpected or unreadable shelf type.

Repair the problem generally caused by bent pins and repeat this procedure.

Boot in progress.

Acknowledges the

UPD/INIT

button was momentarily pushed.

Pushing the

UPD/INIT

button while in

Maintenance Mode has no effect.

4

5

.................................................................................................................................................................................................

Connect the cross-over LAN cable from the PC’s Network Interface Card (NIC) to the rear

J16 IAO LAN

port on the Metropolis

®

DMX shelf backplane or the front

LAN

port on the LNW2 SYSCTL circuit pack faceplate. (When TCP/IP is enabled on the rear

LAN port, OSI is disabled.)

Start the WaveStar

®

CIT software on the PC by double-clicking on the WaveStar

®

CIT icon on your desktop and login (if necessary). Refer to

Procedure 14-2: “Connect

Personal Computer (PC) and establish WaveStar

®

CIT session” (p. 14-24) .

Result:

The Network View appears.

.................................................................................................................................................................................................

From the

View:

pull-down menu, select

CIT OSI Neighbors

.

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................................................

2-24 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

Result:

The CIT OSI Neighbor(s) are automatically detected.

If you were previously logged in to the NE and/or you do not see your NE, from the Network View, select

View

→

Refresh OSI View

.

Figure 2-2 CIT OSI neighbor

6

7

.................................................................................................................................................................................................

In the Network View,

Figure 2-2, “CIT OSI neighbor” (p. 2-25) , right-click on the

LT-DMX NE icon that was detected, and select

Graphical Using

→

OSI

from the resulting menu.

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX and click

OK

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-25

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

8

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

Important! Because the shelf is in Maintenance Mode, your logins and passwords are default.

Enter the following in the NE Login Dialog window (login information is case sensitive) to log in to the NE:

User ID:

LUC01

Password:

DMX2.5G10G

Click

OK

.

Important! LUC01, LUC02, and LUC03 are the default privileged User IDs, and

DMX2.5G10G is the default privileged password for Metropolis

®

DMX. To preserve the security of your equipment, it is highly recommended that you change all three logins and passwords during your first session after completing this initial installation procedure.

.................................................................................................................................................................................................................................

2-26 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

Result:

Screen 1 of 4 in the Maintenance Mode Wizard appears.

This screen picks up the time format preference from the WaveStar

®

CIT.

You can provision the time format display for your WaveStar

®

CIT from the

Network View by selecting

View

→

Preferences

and clicking on the Display tab.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-27

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

9

This screen allows you to choose your preference for time format, either a 12-hour clock or a 24-hour clock.

•

If your time format preference is a 12-hour clock, from the

Time

panel, select

Hour:

(0-12),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus.

You must also specify am or pm by selecting one of the radio buttons.

•

If your time format preference is a 24-hour clock, From the

Time

panel, select the

Hour:

(0-23),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus.

.................................................................................................................................................................................................

Important! The actual time and date are preset from your PC.

On Screen 1 of 4 in the Maintenance Mode Wizard, read the information, verify the date and time, make any required changes, and click

Next

.

.................................................................................................................................................................................................................................

2-28 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

Result:

Screen 2 of 4 in the Maintenance Mode Wizard appears.

10

.................................................................................................................................................................................................

On Screen 2 of 4 in the Maintenance Mode Wizard, click

Download

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-29

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

Result:

Screen 1 of 3 in the Download Generic Wizard appears.

11

.................................................................................................................................................................................................

On Screen 1 of 3 in the Download Generic Wizard, read the information, select

FTP

and click

Next

.

.................................................................................................................................................................................................................................

2-30 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

Result:

Screen 2 of 3 in the Download Generic Wizard appears.

12

.................................................................................................................................................................................................

Important! LAN-1 is the

LAN

port on the faceplate of the LNW2 SYSCTL circuit pack. LAN-2 is the

J16 IAO LAN

port on the rear of the Metropolis

®

DMX shelf.

On Screen 2 of 3 in the Download Generic Wizard, follow the instructions to enable

TCP/IP Control on the LAN port to which you are connected. Click

Modify

to enter the IP Address, IP Subnet Mask, and/or IP Default Router Address. Click

Next

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-31

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

Result:

Screen 3 of 3 in the Download Generic Wizard appears.

.................................................................................................................................................................................................................................

2-32 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

13

14

15

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and proceed to

Step 15 . OR

Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

CIT is the FTP server, you can determine its IP address by entering

ipconfig

from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the download to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar

®

CIT as your FTP server, the default user name/password for the WaveStar

®

CIT is

LUC01

/

LUC+01

, however your user ID/password may be different.)

.................................................................................................................................................................................................

If you entered connection information in

Step 13

and wish to keep the information for future FTP activities:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Important! Entries to the

Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

.................................................................................................................................................................................................

On Screen 3 of 3 in the Download Generic Wizard in the

Path

panel, enter the current location of the generic to be downloaded in the Path field or use the

Browse

button to select the generic to be downloaded. (If the FTP server is not the local host, the

Browse

button is greyed out.) Click

Download

.

The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:/Program

Files/Lucent Technologies/WaveStar CIT/generics/DMX/6.0.1/p/

. The syntax of the relative path must start with the path name; for example:

/generics/DMX/6.0.1/p/

. (If necessary, replace 6.0.1 with your current release, for example 6.0.1.)

If the FTP server is not the WaveStar

®

CIT, then enter the path starting at the FTP home directory on the server.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-33

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

16

Result:

A warning message appears listing the options you provisioned in the previous screens.

.................................................................................................................................................................................................

Verify the information and either click

Yes

to start the download process or click

No

to return to the download screen and change your selections.

Result:

If you choose yes, the following initial software download progress indicator runs for approximately 10 minutes.

17

.................................................................................................................................................................................................

Do you wish to observe the FTP download progress?

If...

Yes

No

Then...

Proceed to

Procedure 14-17: “Observe FTP progress”

(p. 14-101)

and then continue with

Step 18 .

Continue with

Step 18 .

18

.................................................................................................................................................................................................

Once the software generic download is complete, the following confirmation message appears. Click

Yes

to use the generic that is now in the Dormant area.

.................................................................................................................................................................................................................................

2-34 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

Result:

Screen 3 of 4 in the Maintenance Mode Wizard appears.

19

.................................................................................................................................................................................................

On Screen 3 of 4 in the Maintenance Mode Wizard, click the check box next to

Default to create a default database and click

Next

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-35

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

Result:

Screen 4 of 4 in the Maintenance Mode Wizard appears. In this screen,

6.0.1 is an example; your selected generic could be different, for example 6.0.2.

20

.................................................................................................................................................................................................

On Screen 4 of 4 in the Maintenance Mode Wizard, read the information, verify that you have selected the correct 6.0.x generic and the default 6.0.x database and click

Finish

to restart the system and apply the generic and default database.

.................................................................................................................................................................................................................................

2-36 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

21

22

23

Result:

The Maintenance Mode Wizard closes and your connection to the shelf is terminated.

The LNW2 SYSCTL exhibits the following visible cycles while the generic and database are installed and validated and the SYSCTL reboots:

1. For approximately 10 minutes, the alternating

M

and

P

and

6

and “

.

” (“.” is a red, four-segment square [2 x 2] representing a period) and

0

continue to appear in the

IND

display on the SYSCTL.

2. After approximately 10 minutes, all LEDs extinguish and the

IND

display on the

SYSCTL is blank for approximately 5 seconds.

3. A flashing

b

appears in the

IND

display on the SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 60 seconds and then

IND

display is blank for approximately 20 seconds.

4. The

ACTIVE

LED lights and remains lighted.

5. A flashing

b

appears again in the

IND

display on the SYSCTL, indicating that a boot is in progress. After approximately 30 seconds, the

CR

LED flashes 10 times and then extinguishes, and the

b

continues flashing for approximately another 30 seconds, and then

IND

display is blank.

6. The

ABN

and

NE

LEDs light and remain lighted for approximately 6 minutes.

The active generic and database are being validated and copied to the second

NVM.

7. When the

ABN

and

NE

LEDs extinguish and only the

ACTIVE

LED is lighted, and nothing appears in the

IND

display, the NE software and database installation is complete.

8. Continue with

Step 21 .

.................................................................................................................................................................................................

To verify that the download was successful, depress and hold the

ACO TEST

push-button on the LNW2 SYSCTL for about 4 seconds.

Result:

All LEDs on the shelf light. A red, 35-segment (5 x 7) rectangle appears in the

IND

display on the SYSCTL. Since the

IND

display is a 35-segment display, this test indicates all segments are working.

.................................................................................................................................................................................................

Release the

ACO TEST

push-button on the LNW2 SYSCTL when the red rectangle disappears in the

IND

display.

Result:

The current software generic appears in the

IND

display on the LNW2

SYSCTL and the shelf LEDs return to their previous status.

.................................................................................................................................................................................................

From the Network View of the WaveStar

®

CIT session you established in

Step 4 ,

select the

View:

pull-down menu and select

CIT OSI Neighbors

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-37

Software installation and upgrades, and database backup procedures

24

25

26

27

28

Procedure 2-2: Install software generic (initial) via FTP

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................

From the Network View, select

View

→

Refresh OSI View

.

Result:

The CIT OSI neighbor(s) are automatically detected.

.................................................................................................................................................................................................

In the Network View, right-click on the LT-DMX NE icon that was detected, and select

Graphical Using

→

OSI

from the resulting menu.

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX and click

OK

.

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

Enter the following in the NE Login Dialog window (login information is case sensitive) to log in to the NE:

User ID:

LUC01

Password:

DMX2.5G10G

Click

OK

.

Important! LUC01, LUC02, and LUC03 are the default privileged User IDs, and

DMX2.5G10G is the default privileged password for Metropolis

®

DMX. It is highly recommended that you change all three logins and passwords during your first session to preserve the security of your equipment.

Result:

The title bar of the System View and the legal notice text should both reflect the current NE software generic, for example: R6.0.1.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Is the Generic Software Version correct?

If...

Yes

No

Then...

STOP! End of Procedure.

Contact your next level of support.

.................................................................................................................................................................................................................................

2-38 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-2: Install software generic (initial) via FTP

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-39

Software installation and upgrades, and database backup procedures

Procedure 2-3: Upgrade software generic via FTAM

.................................................................................................................................................................................................................................

Overview

Use this procedure to upgrade the software generic from Metropolis

®

DMX Release

5.0/5.1 to Release 6.0, or Release 6.0.0 to Release 6.0.x via the File Transfer and

Access Management (FTAM) protocol.

To download the software generic to a local shelf via FTP, refer to

Procedure 2-4:

“Upgrade software generic via FTP” (p. 2-72) .

Important! You must have OSI connectivity (via your OSI LAN or DCC) to the network element to use FTAM.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

In addition to

“Required equipment” (p. 2-2)

listed in this chapter, the following equipment is also required:

•

CAT5 Ethernet cable with either a 10/100 hub or a cross-over cable for the

LAN

or

IAO LAN

port (required for TCP/IP connectivity)

•

Copy of the new system generic software program accessible from your PC.

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

•

Factory-fresh LNW2, system controller (SYSCTL), with two factory-installed non-volatile memory (NVM) cards installed

•

Current Metropolis

®

DMX Access Multiplexer Software Release Description for the software generic being installed

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 2-2)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

2. Verify that new software generic program is available.

3. Refer to the Metropolis

®

DMX Access Multiplexer Software Release Description for a description of any special considerations required when installing this version of software.

4. The LNW1 SYSCTL must have Metropolis

®

DMX R5.0/5.1 or later software generic to upgrade the software generic program to R6.0 via FTAM.

.................................................................................................................................................................................................................................

2-40 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Step

1

2

Procedure 2-3: Upgrade software generic via FTAM

Complete the following steps to upgrade the software generic via the FTAM protocol.

.................................................................................................................................................................................................

Connect the cross-over LAN cable from the PC’s Network Interface Card (NIC) to the rear

J16 IAO LAN

port on the Metropolis

®

DMX shelf backplane or the front

LAN

port on the SYSCTL circuit pack faceplate and establish a WaveStar

®

CIT session. (When

TCP/IP is enabled on the rear LAN port, OSI is disabled.)

Start the WaveStar

®

CIT software on the PC by double-clicking on the WaveStar

®

CIT icon on your desktop and login (if necessary). Refer to

Procedure 14-2: “Connect

Personal Computer (PC) and establish WaveStar

®

CIT session” (p. 14-24) .

Result:

The Network View appears.

.................................................................................................................................................................................................

From the

View:

pull-down menu, select

CIT OSI Neighbors

.

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-41

Software installation and upgrades, and database backup procedures

Procedure 2-3: Upgrade software generic via FTAM

Result:

The CIT OSI neighbor(s) are automatically detected.

If you were previously logged in to the NE and/or you do not see your NE, from the Network View, select

View

→

Refresh OSI View

.

Figure 2-3 CIT OSI neighbor

3

4

.................................................................................................................................................................................................

In the Network View,

Figure 2-3, “CIT OSI neighbor” (p. 2-42) , right-click on the NE

icon that was detected (default TID is LT-DMX, your TID may be different), and select

Graphical Using

→

OSI

from the resulting menu.

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX and click

OK

.

.................................................................................................................................................................................................................................

2-42 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3: Upgrade software generic via FTAM

5

6

7

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

In the NE login window, login to the shelf using your user ID and password.

Click

OK

.

.................................................................................................................................................................................................

After you login to the SYSCTL from the System View menu, select

View

→

Software

Generic

.

Result:

The View Software Generic window appears.

.................................................................................................................................................................................................

What is the apparatus code of your SYSCTL and what generic is it currently running?

If...

LNW1, running Release 4.x or earlier as the Active Software

Version

LNW1, running Release 5.x or greater as the Active Software

Version

LNW2, running Release 6.0.0 as the Active Generic

Then...

You must upgrade your software to Release 5.1.2

and the repeat this procedure from

Step 1 .

Proceed to

Procedure 2-3.1: “Verify proper equipage in Main slots” (p. 2-44) .

Proceed to

Procedure 2-3.3: “Upgrade software generic via FTAM (6.0.0 to 6.0.x)” (p. 2-69) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-43

Software installation and upgrades, and database backup procedures

Procedure 2-3.1: Verify proper equipage in Main slots

.................................................................................................................................................................................................................................

Overview

Use this procedure to verify that the Main slots are equipped with circuit packs that are supported in 6.0.

LNW26 circuit packs are not supported in R6.0.

Since LNW26B-type circuit packs with the jumper set to NORMAL are identical to

LNW26 circuit packs, LNW26B-type circuit packs (LNW26B, LNW28, LNW77,

LNW121B-151B) with the circuit pack mode jumper set to NORMAL (6 STS-1 switch fabric) are not supported in R6.0. The jumper on LNW26B-type circuit packs must be set to ENHANCED (12 STS-1 switch fabric) to use these circuit packs in 6.0.

Important! If you determine that the Main slots in your NE are equipped with unsupported circuit packs, you must upgrade those circuit packs before upgrading to 6.0.x.

Required equipment

Refer to

“Required equipment” (p. 2-40)

in

Procedure 2-3: “Upgrade software generic via FTAM” (p. 2-40)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure:

1. Complete

Procedure 2-3: “Upgrade software generic via FTAM” (p. 2-40) .

2. You must have access to supported circuit packs if your Main slots contain unsupported circuit packs.

Step

1

Complete the following steps to verify that supported equipment is installed in your shelf.

.................................................................................................................................................................................................

From the System View menu, select

Reports

→

Equipment Lists

→

Pack

, highlight

Shelf

, and click

Select

.

.................................................................................................................................................................................................................................

2-44 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3.1: Verify proper equipage in Main slots

2

Result:

The Circuit Pack List screen appears.

.................................................................................................................................................................................................

In the Circuit Pack List screen, locate the main-1-cp and main-2-cp AIDs in the Circuit

Pack AID column. Are the Apparatus Codes for those AIDs either LNW26 or

LNW26B-type (LNW26B, LNW28, LNW77, LNW121B-151B)?

If...

Yes (LNW26)

Yes (LNW26B, LNW28, LNW77,

LNW121B-151B)

No

Then...

You must upgrade the LNW26 circuit packs in the Main slots to supported circuit packs. Proceed to

Procedure 12-1:

“Upgrade high-speed OC-48 OLIUs in

UPSR/BLSR network” (p. 12-4)

and then repeat this procedure.

Continue with

Step 3

to determine the circuit pack mode of the packs.

The Main slots are equipped with circuit packs that are compatible with R6.0.x.

Proceed to

Procedure 2-3.2: “Upgrade software generic via FTAM (5.x to 6.0)”

(p. 2-47) .

3

4

5

6

.................................................................................................................................................................................................

From the System View menu, select

View

→

Equipment

→

Circuit Pack

, highlight

CP main-1, and click

Select

.

Result:

The View Equipment screen appears.

.................................................................................................................................................................................................

In the View Equipment screen, locate the Circuit Pack Mode parameter in the

Equipment Details panel. Note the value of the Circuit Pack Mode for CP Main-1, either NORMAL or ENHANCED.

Do NOT click

Close

on the View Equipment screen.

.................................................................................................................................................................................................

Highlight CP main-2 and click

Select

.

.................................................................................................................................................................................................

In the View Equipment screen, locate the Circuit Pack Mode parameter in the

Equipment Details panel. Note the value of the Circuit Pack Mode for CP Main-2, either NORMAL or ENHANCED.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-45

Software installation and upgrades, and database backup procedures

Procedure 2-3.1: Verify proper equipage in Main slots

7

.................................................................................................................................................................................................

Refer to

Step 4

and

Step 6 . Is the Circuit Pack Mode for CP main-1 and/or CP main-2

NORMAL (6 STS-1 switch fabric)?

If...

Yes

No

Then...

The LNW26B-type circuit packs with the

Circuit Pack Mode jumper set as

NORMAL are NOT supported in 6.0.x.

Choose one of the following two options:

1. Change Circuit Pack Mode to

ENHANCED by physically changing the jumper setting on the circuit packs.

Proceed to

Procedure 4-22: “Change circuit pack mode of LNW26B,

LNW28, LNW77, or LNW121B-159B

OC-48 OLIU circuit packs” (p. 4-84)

and then repeat this procedure.

2. Upgrade the LNW26B-type circuit packs to LNW27, LNW29, LNW32,

LNW76, or LNW221-259 OC-48

OLIU circuit packs. These circuit packs can cross-connect VT1.5 signals in up to 48 STS-1 signals.

Proceed to

Procedure 12-1: “Upgrade high-speed OC-48 OLIUs in

UPSR/BLSR network” (p. 12-4)

and then repeat this procedure.

The LNW26B-type circuit packs with the

Circuit Pack Mode jumper set as

ENHANCED are supported in 6.0.x.

Proceed to

Procedure 2-3.2: “Upgrade software generic via FTAM (5.x to 6.0)”

(p. 2-47)

to upgrade the 5.x shelf to 6.0.x.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

2-46 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x to

6.0)

.................................................................................................................................................................................................................................

Overview

Use this procedure to upgrade a software generic from Release 5.x to Release 6.0.x via

FTAM.

Required equipment

Refer to

“Required equipment” (p. 2-40)

in

Procedure 2-3: “Upgrade software generic via FTAM” (p. 2-40)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure:

1. Complete

Procedure 2-3: “Upgrade software generic via FTAM” (p. 2-40) .

2. You must be able to perform a backup of the R5.x database.

Step

1

2

3

Complete the following steps to upgrade a software generic from Release 5.0/5.1 to

Release 6.0.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Remote Backup

.

.................................................................................................................................................................................................

In the pull-down

Backup To/Via:

menu, select

FTAM

.

.................................................................................................................................................................................................

In the

Source/Destination Directory Path

field, enter

backups/<filename>

.

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-47

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

4

5

If you wish to store your data in a subdirectory, you may enter

backups/<subdirectory>/<filename>

if the subdirectory exists before the command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.

.................................................................................................................................................................................................

Click

OK

.

You will be asked to verify that you wish to backup to the directory that you entered above. Click

Yes

if you typed the path correctly.

Result:

The Progress Indicator screen appears, indicating that the backup is in progress. When the backup completes, a

Remote Backup successful screen appears. Click

OK

. The backup file is now stored. If the default path and a subdirectory were used, the file may be found at:

C:/Program Files/Lucent Technologies/WaveStar

IT/backups/<subdirectory>/<filename>

.................................................................................................................................................................................................

Close your WaveStar

®

CIT session with the 5.x NE. From the System View, select

File

→

NE Disconnect

and click

Yes

in the confirmation window.

Result:

The System View closes.

6

7

8

.................................................................................................................................................................................................

Disconnect the LAN and/or serial cables from the

LAN

and/or

RS232

port(s) on the front of the LNW1 SYSCTL.

.................................................................................................................................................................................................

Initiate a ten-second countdown (9, 8, 7, 6, 5, 4, 3, 2, 1, 0) in the

IND

display on the

LNW1 SYSCTL by simultaneously depressing the

ACO TEST

and

SEL

buttons on the front of the LNW1 SYSCTL.

Important! Removing the LNW1 without initiating the ten-second countdown may result in unexpected and undesirable protection switches, incorrect circuit fault indications, or incoming signal failure alarms. All SYSCTL functions are suspended during the countdown.

.................................................................................................................................................................................................

Remove the LNW1 SYSCTL circuit pack during the 10-second countdown.

Important! While the SYSCTL circuit pack is removed, do NOT remove or replace any transmission circuit packs.

.................................................................................................................................................................................................

9

Important! For software installation, two NVMs should be present in the LNW2

SYSCTL. After the LNW2 is installed, if one or two NVMs are missing,

NVM

.................................................................................................................................................................................................................................

2-48 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

10

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0) removed alarm(s) are issued. If both NVM sockets are empty, the

IND

displays an alternating

E

and

0

and

1

.

Refer to

Step 10

for the complete listing of codes and required actions.

Seat the new LNW2 SYSCTL circuit pack and allow a few minutes for the pack to complete initialization.

Result:

The LNW2 SYSCTL exhibits the following visible cycles during initialization:

1. The

FAULT

LED lights and remains lighted for approximately 90 seconds. After approximately 15 seconds, a flashing

b

appears in the

IND

display on the

SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 75 seconds and then

IND

display is blank.

2. The

FAULT

LED remains lighted for approximately another 20 seconds and then extinguishes.

3. The

ACTIVE

LED lights and remains lighted and the

CR

LED flashes 10 times.

While the

CR

LED is flashing, the

MJ

,

ABN

, and

NE

LEDs light and remain lighted.

Because the LNW2 SYSCTL is in 6.0 Maintenance Mode, an alternating

M

and

P

and

6

and “

.

” (“.” is a red, four-segment square [2 x 2] representing a period) and

0

appear in the

IND

display.

4. Continue with

Step 10 .

.................................................................................................................................................................................................

Observe the

IND

display on the LNW2 SYSCTL; the display indicates the state of the

SYSCTL.

If...

alternating

M

and

P

and

6

and “

.

”

(“.” is a red, four-segment square

[2 x 2] representing a period) and

0

alternating

E

and

0

and

0

alternating

E

and

0

and

1

Then...

6.0 Maintenance Mode. Continue with

Step 11 .

LNW2 SYSCTL must be replaced.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

No NVMs are detected on the LNW2 SYSCTL.

Install two Lucent-supplied NVMs in the LNW2 or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-49

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

If...

alternating alternating alternating

Letter

F

alternating

Letter

U

E

E

E

N

and and and and

0

0

1

O

and and and and

2

3

0 x

flashing

b

A red, four-segment square (2 x 2) appears in the

IND

display on the

LNW2 SYSCTL.

Then...

NVMs are present but not readable. Check to make sure they are properly seated and repeat this procedure.

Not Supported.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

LNW2 SYSCTL will not boot.

No compatible generic on the NVMs in the

LNW2 SYSCTL.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure or contact your next level of support.

LNW2 SYSCTL faceplate latches are not fully seated.

Unseat the LNW2 SYSCTL and repeat this procedure, properly seating the faceplate latch.

“x” indicates that the NVM socket (1 or 2) is empty or the NVM installed is failed. Replace the indicated NVM or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

LNW2 SYSCTL will not boot due to unexpected or unreadable shelf type.

Repair the problem generally caused by bent pins and repeat this procedure.

Boot in progress.

Acknowledges the

UPD/INIT

button was momentarily pushed.

Pushing the

UPD/INIT

button while in

Maintenance Mode has no effect.

11

.................................................................................................................................................................................................

Connect the cross-over LAN cable from the PC’s Network Interface Card (NIC) to the rear

J16 IAO LAN

port on the Metropolis

®

DMX shelf backplane or the front

LAN

port on the LNW2 SYSCTL circuit pack faceplate. (When TCP/IP is enabled on the rear

LAN port, OSI is disabled.)

.................................................................................................................................................................................................................................

2-50 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

12

13

.................................................................................................................................................................................................

From the Network View of the WaveStar

®

CIT session you established in

Procedure

2-3: “Upgrade software generic via FTAM” (p. 2-40) , select the

View:

pull-down menu and select

CIT OSI Neighbors

.

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................

From the Network View, select

View

→

Refresh OSI View

.

Result:

The CIT OSI neighbor(s) are automatically detected.

Your TID will be LT-DMX; when in Maintenance Mode, the TID is always default.

Figure 2-4 CIT OSI neighbor

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-51

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

14

15

16

.................................................................................................................................................................................................

In the Network View,

Figure 2-4, “CIT OSI neighbor” (p. 2-51) , right-click on the

LT-DMX NE icon that was detected, and select

Graphical Using

→

OSI

from the resulting menu.

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX and click

OK

.

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

Important! Because the shelf is in Maintenance Mode, your logins and passwords are default.

Enter the following in the NE Login Dialog window (login information is case sensitive) to log in to the NE:

User ID:

LUC01

Password:

DMX2.5G10G

Click

OK

.

Important! After you select your backup database, complete the Maintenance

Mode Wizard, and the NE restarts, your original User IDs and Passwords will be restored.

.................................................................................................................................................................................................................................

2-52 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

Result:

Screen 1 of 4 in the Maintenance Mode Wizard appears.

This screen picks up the time format preference from the WaveStar

®

CIT.

You can provision the time format display for your WaveStar

®

CIT from the

Network View by selecting

View

→

Preferences

and clicking on the Display tab.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-53

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

17

This screen allows you to choose your preference for time format, either a 12-hour clock or a 24-hour clock.

•

If your time format preference is a 12-hour clock, from the

Time

panel, select

Hour:

(0-12),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus.

You must also specify am or pm by selecting one of the radio buttons.

•

If your time format preference is a 24-hour clock, From the

Time

panel, select the

Hour:

(0-23),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus.

.................................................................................................................................................................................................

Important! The actual time and date are preset from your PC.

On Screen 1 of 4 in the Maintenance Mode Wizard, read the information, verify the date and time, make any required changes, and click

Next

.

.................................................................................................................................................................................................................................

2-54 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

Result:

Screen 2 of 4 in the Maintenance Mode Wizard appears.

18

.................................................................................................................................................................................................

On Screen 2 of 4 in the Maintenance Mode Wizard, click

Download

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-55

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

Result:

Screen 1 of 3 in the Download Generic Wizard appears.

19

.................................................................................................................................................................................................

On Screen 1 of 3 in the Download Generic Wizard, read the information, select

FTAM

and click

Next

.

.................................................................................................................................................................................................................................

2-56 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

Result:

Screen 2 of 3 in the Download Generic Wizard appears.

20

.................................................................................................................................................................................................

Important! LAN-1 is the

LAN

port on the faceplate of the LNW2 SYSCTL circuit pack. LAN-2 is the

J16 IAO LAN

port on the rear of the Metropolis

®

DMX shelf.

On Screen 2 of 3 in the Download Generic Wizard, read the information, verify that the LAN port you are connected to has OSI Function Enable selected and click

Next

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-57

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

Result:

Screen 3 of 3 in the Download Generic Wizard appears.

21

.................................................................................................................................................................................................

On Screen 3 of 3 in the Download Generic Wizard in the

Path

panel, enter the current location of the generic to be downloaded in the Path field or use the

Browse

button to select the generic to be downloaded. Click

Download

.

The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:/Program

Files/Lucent Technologies/WaveStar CIT/generics/DMX/6.0.1/p/

. The syntax

.................................................................................................................................................................................................................................

2-58 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

22

of the relative path must start with the path name; for example:

/generics/DMX/6.0.1/p/

. (If necessary, replace 6.0.1 with your current release, for example 6.0.2.)

Result:

A warning message appears listing the options you provisioned in the previous screens.

.................................................................................................................................................................................................

Verify the information and either click

Yes

to start the download process or click

No

to return to the download screen and change your selections.

Result:

If you choose yes, the following initial software download progress indicator runs for approximately 15 minutes.

23

.................................................................................................................................................................................................

Once the software generic download is complete, the following confirmation message appears. Click

Yes

to use the generic that is now in the Dormant area.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-59

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

Result:

Screen 3 of 4 in the Maintenance Mode Wizard appears.

24

.................................................................................................................................................................................................

On Screen 3 of 4 in the Maintenance Mode Wizard, click

Download

.

.................................................................................................................................................................................................................................

2-60 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

Result:

Screen 1 of 3 in the Download Database Wizard appears.

25

.................................................................................................................................................................................................

On Screen 1 of 3 in the Download Database Wizard, read the information, select

FTAM

and click

Next

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-61

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

Result:

Screen 2 of 3 in the Download Database Wizard appears.

26

.................................................................................................................................................................................................

On Screen 2 of 3 in the Download Database Wizard, read the information, verify that the LAN port you are connected to has OSI Function Enable selected and click

Next

.

.................................................................................................................................................................................................................................

2-62 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

Result:

Screen 3 of 3 in the Download Database Wizard appears.

27

.................................................................................................................................................................................................

On Screen 3 of 3 in the Download Database Wizard in the

Path

panel, enter the location where the database information is stored. Enter the path and filename exactly as it was entered in

Step 3 . For example:

backups/<subdirectory>/<filename>

.

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and select the required file.

Click

Download

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-63

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

28

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

Result:

A warning message appears listing the options you provisioned in the previous screens.

.................................................................................................................................................................................................

Verify the information and click

Yes

.

Result:

If you choose Yes, the database download progress indicator runs for approximately two minutes.

29

.................................................................................................................................................................................................

Once the database download is complete, the following confirmation message appears.

Click

Yes

to use the database that is now in the Backup area.

.................................................................................................................................................................................................................................

2-64 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

Result:

Screen 4 of 4 in the Maintenance Mode Wizard appears. In this screen,

6.0.1 is an example; your selected generic could be different, for example 6.0.2.

5.1.1 is an example too; your selected database could be 5.0.x or 5.1.x.

30

.................................................................................................................................................................................................

On Screen 4 of 4 in the Maintenance Mode Wizard, read the information, verify that you have selected the correct generic and database and click

Finish

to restart the system and apply the generic and database.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-65

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

31

32

Result:

The Maintenance Mode Wizard closes and your connection to the shelf is terminated.

The LNW2 SYSCTL exhibits the following visible cycles while the generic and database are installed and validated and the SYSCTL reboots:

1. For approximately 10 minutes, the alternating

M

and

P

and

6

and “

.

” (“.” is a red, four-segment square [2 x 2] representing a period) and

0

continue to appear in the

IND

display on the SYSCTL.

2. After approximately 10 minutes, all LEDs extinguish and the

IND

display on the

SYSCTL is blank for approximately 5 seconds.

3. A flashing

b

appears in the

IND

display on the SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 60 seconds and then

IND

display is blank for approximately 20 seconds.

4. The

ACTIVE

LED lights and remains lighted.

5. A flashing

b

appears again in the

IND

display on the SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 2.5 minutes while the database is being converted and then

IND

display is blank.

6. When nothing appears in the

IND

display and the

ACTIVE

LED is lighted and the other LEDs return to their previous state (pre-LNW1 backup), the NE software and database installation is complete.

However, smart circuit packs may be upgrading their firmware. If flashing green

ACTIVE

LEDs are present on a circuit pack, firmware is currently being downloaded to that pack. Wait until all smart circuit packs finish upgrading their firmware before proceeding.

If an alarm condition existed prior to the upgrade, the NE will rediscover the alarm condition and activate the appropriate LEDs on the shelf.

7. Continue with

Step 31 .

.................................................................................................................................................................................................

To verify that the upgrade was successful, depress and hold the

ACO TEST

push-button on the LNW2 SYSCTL for about 4 seconds.

Result:

All LEDs on the shelf light. A red, 35-segment (5 x 7) rectangle appears in the

IND

display on the SYSCTL. Since the

IND

display is a 35-segment display, this test indicates all segments are working.

.................................................................................................................................................................................................

Release the

ACO TEST

push-button on the LNW2 SYSCTL when the red rectangle disappears in the

IND

display.

.................................................................................................................................................................................................................................

2-66 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

33

34

35

36

37

38

Result:

The current software generic appears in the

IND

display on the LNW2

SYSCTL and the shelf LEDs return to their previous status.

.................................................................................................................................................................................................

From the Network View of the WaveStar

®

CIT session you established in

Procedure

2-3: “Upgrade software generic via FTAM” (p. 2-40) , select the

View:

pull-down menu and select

CIT OSI Neighbors

.

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................

From the Network View, select

View

→

Refresh OSI View

.

Result:

The CIT OSI neighbor(s) are automatically detected.

Your TID will be your original TID, the same TID provisioned on your 5.x NE.

.................................................................................................................................................................................................

In the Network View, right-click on the NE icon that was detected, and select

Graphical Using

→

OSI

from the resulting menu.

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX and click

OK

.

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

In the NE login window, login to the shelf using your original user ID and password; the same user ID and password provisioned on your 5.x NE.

Click

OK

.

Result:

The title bar of the System View and the legal notice text should both reflect the current NE software generic, for example: R6.0.1.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Is the Generic Software Version correct?

If...

Yes

No

Then...

STOP! End of Procedure.

Contact your next level of support.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-67

Software installation and upgrades, and database backup procedures

Procedure 2-3.2: Upgrade software generic via FTAM (5.x

to 6.0)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

2-68 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3.3: Upgrade software generic via FTAM (6.0.0 to

6.0.x)

.................................................................................................................................................................................................................................

Overview

Use this procedure to download the software generic via the File Transfer and Access

Management (FTAM) protocol from the WaveStar

®

CIT to the local network element or a remote network element via DCC with OSI connectivity to the network element.

To download the software generic to a local shelf via FTP, refer to

Procedure 2-4:

“Upgrade software generic via FTP” (p. 2-72) . To download the software generic to a

remote shelf via FTTD, refer to

Procedure 2-5: “Upgrade software generic via FTTD

(6.0.0 to 6.0.x)” (p. 2-109) .

Important! Your NE must be running Release 6.0.0 or later to use this procedure.

Required equipment

Refer to

“Required equipment” (p. 2-40)

in

Procedure 2-3: “Upgrade software generic via FTAM” (p. 2-40)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 2-3: “Upgrade software generic via FTAM” (p. 2-40) .

Step

1

2

3

Complete the following steps to download system software via FTAM to the

WaveStar

®

CIT to a 6.0.x Metropolis

®

DMX.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Download

Software

.

Result:

The Download Generic window appears.

.................................................................................................................................................................................................

In the pull-down

Download From/Via:

menu, select

FTAM

.

.................................................................................................................................................................................................

In the

Source/Destination Directory Path

panel, enter the current location of the generic to be downloaded or use the

Browse

button (if available) to select the generic to be downloaded.

Important! If you selected the default installation location for the WaveStar

®

CIT and software generic:

generics/DMX/6.0.1/p/

(If necessary, replace 6.0.1 with

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-69

Software installation and upgrades, and database backup procedures

4

5

6

Procedure 2-3.3: Upgrade software generic via FTAM

(6.0.0 to 6.0.x) your current release, for example 6.0.2.) The WaveStar

®

CIT automatically populates the FTAM Responder and NSAP fields. Click

Next

.

The value of the Path field can be either an absolute path or a relative path that is relative to the FTAM server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:/Program

Files/Lucent Technologies/WaveStar CIT/generics/DMX/6.0.1/p/

. The syntax of the relative path must start with the path name; for example:

/generics/DMX/6.0.1/p/

. (If necessary, replace 6.0.1 with your current release, for example 6.0.2.)

.................................................................................................................................................................................................

In the

Product Type

panel, select the product type of the software generic that you are downloading (not necessarily the same as the NE to which you are downloading).

.................................................................................................................................................................................................

Click

OK

.

Result:

A warning message appears asking you to confirm executing this command. Verify the information and click

Yes

.

While the download is in progress (approximately 15 minutes), a progress indicator window is present.

The download may be cancelled any time by pressing the

Cancel

button on the progress screen.

When the transfer is complete, the Progress Indicator window closes and the download software successful window appears. Click

OK

.

.................................................................................................................................................................................................

Important! Do NOT insert a new circuit pack in the shelf until after you apply the new software generic and clear the dormant/exec version mismatch condition.

Do you wish to apply (activate) the software generic that you recently downloaded to the dormant area of the Metropolis

®

DMX shelf?

If...

Yes

No

Then...

Proceed to

Procedure 2-7: “Apply software generic”

(p. 2-120)

and then continue with

Step 7 .

Continue with

Step 7 .

.................................................................................................................................................................................................................................

2-70 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-3.3: Upgrade software generic via FTAM

(6.0.0 to 6.0.x)

7

.................................................................................................................................................................................................

Do you wish to upgrade additional shelves via FTAM?

If...

Yes

No

Then...

Repeat this procedure from

Step 1 for each shelf

that you wish to upgrade via FTAM.

STOP! End of Procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-71

Software installation and upgrades, and database backup procedures

Procedure 2-4: Upgrade software generic via FTP

.................................................................................................................................................................................................................................

Overview

Use this procedure to upgrade the software generic from Metropolis

®

DMX Release

5.0/5.1 to Release 6.0, or Release 6.0.0 to Release 6.0.x via File Transfer Protocol

(FTP).

To download the software generic to a local shelf via FTAM, refer to

Procedure 2-3:

“Upgrade software generic via FTAM” (p. 2-40) .

Important! You must have direct TCP/IP connectivity to your NE and the NE must have a defined IP address.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

In addition to

“Required equipment” (p. 2-2)

listed in this chapter, the following equipment is also required:

•

CAT5 Ethernet cable with either a 10/100 hub or a cross-over cable for the

LAN

or

IAO LAN

port

•

Copy of the new system generic software program on your PC or FTP server

•

Current Metropolis

®

DMX Access Multiplexer Software Release Description for the software generic being installed

Important! If the FTP server fails to start, it could mean that another program using an FTP server is already running. Depending on what operating system you are using, you must go to the device file and disable the FTP server. Refer to

Procedure 14-18: “Disable an FTP server on your PC” (p. 14-103)

for instructions for each allowed operating system.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 2-2)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

2. Verify that new software generic program is available.

3. Refer to the Metropolis

®

DMX Access Multiplexer Software Release Description for a description of any special considerations required when installing this version of software.

.................................................................................................................................................................................................................................

2-72 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Step

1

2

Procedure 2-4: Upgrade software generic via FTP

Complete the following steps to retrieve the generic software version ID.

.................................................................................................................................................................................................

Connect the cross-over LAN cable from the PC’s Network Interface Card (NIC) to the rear

J16 IAO LAN

port on the Metropolis

®

DMX shelf backplane or the front

LAN

port on the SYSCTL circuit pack faceplate and establish a WaveStar

®

CIT session. (When

TCP/IP is enabled on the rear LAN port, OSI is disabled.)

Start the WaveStar

®

CIT software on the PC by double-clicking on the WaveStar

®

CIT icon on your desktop and login (if necessary). Refer to

Procedure 14-2: “Connect

Personal Computer (PC) and establish WaveStar

®

CIT session” (p. 14-24) .

Result:

The Network View appears.

.................................................................................................................................................................................................

From the

View:

pull-down menu, select

CIT OSI Neighbors

.

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-73

Software installation and upgrades, and database backup procedures

Procedure 2-4: Upgrade software generic via FTP

Result:

The CIT OSI neighbor(s) are automatically detected.

If you were previously logged in to the NE and/or you do not see your NE, from the Network View, select

View

→

Refresh OSI View

.

Figure 2-5 CIT OSI neighbor

3

4

.................................................................................................................................................................................................

In the Network View,

Figure 2-5, “CIT OSI neighbor” (p. 2-74) , right-click on the NE

icon that was detected (default TID is LT-DMX, your TID may be different), and select

Graphical Using

→

OSI

from the resulting menu.

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX and click

OK

.

.................................................................................................................................................................................................................................

2-74 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4: Upgrade software generic via FTP

5

6

7

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

In the NE login window, login to the shelf using your user ID and password.

Click

OK

.

.................................................................................................................................................................................................

After you login to the SYSCTL from the System View menu, select

View

→

Software

Generic

.

Result:

The View Software Generic window appears.

.................................................................................................................................................................................................

What is the apparatus code of your SYSCTL and what generic is it currently running?

If...

LNW1, running Release 4.x or earlier as the Active Software

Version

LNW1, running Release 5.x or greater as the Active Software

Version

LNW2, running Release 6.0.0 as the Active Generic

Then...

You must upgrade your software to Release 5.1.2

and the repeat this procedure from

Step 1 .

Proceed to

Procedure 2-4.1: “Verify proper equipage in Main slots” (p. 2-76) .

Proceed to

Procedure 2-4.3: “Upgrade software generic via FTP (6.0.0 to 6.0.x)” (p. 2-104) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-75

Software installation and upgrades, and database backup procedures

Procedure 2-4.1: Verify proper equipage in Main slots

.................................................................................................................................................................................................................................

Overview

Use this procedure to verify that the Main slots are equipped with circuit packs that are supported in 6.0.

LNW26 circuit packs are not supported in R6.0.

Since LNW26B-type circuit packs with the jumper set to NORMAL are identical to

LNW26 circuit packs, LNW26B-type circuit packs (LNW26B, LNW28, LNW77,

LNW121B-151B) with the circuit pack mode jumper set to NORMAL (6 STS-1 switch fabric) are not supported in R6.0. The jumper on LNW26B-type circuit packs must be set to ENHANCED (12 STS-1 switch fabric) to use these circuit packs in 6.0.

Important! If you determine that the Main slots in your NE are equipped with unsupported circuit packs, you must upgrade those circuit packs before upgrading to 6.0.x.

Required equipment

Refer to

“Required equipment” (p. 2-72)

in

Procedure 2-4: “Upgrade software generic via FTP” (p. 2-72)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure:

1. Complete

Procedure 2-4: “Upgrade software generic via FTP” (p. 2-72) .

2. You must have access to supported circuit packs if your Main slots contain unsupported circuit packs.

Step

1

Complete the following steps to verify that supported equipment is installed in your shelf.

.................................................................................................................................................................................................

From the System View menu, select

Reports

→

Equipment Lists

→

Pack

, highlight

Shelf

, and click

Select

.

.................................................................................................................................................................................................................................

2-76 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.1: Verify proper equipage in Main slots

2

Result:

The Circuit Pack List screen appears.

.................................................................................................................................................................................................

In the Circuit Pack List screen, locate the main-1-cp and main-2-cp AIDs in the Circuit

Pack AID column. Are the Apparatus Codes for those AIDs either LNW26 or

LNW26B-type (LNW26B, LNW28, LNW77, LNW121B-151B)?

If...

Yes (LNW26)

Yes (LNW26B, LNW28,

LNW77, LNW121B-151B)

No

Then...

You must upgrade the LNW26 circuit packs in the

Main slots to supported circuit packs. Proceed to

Procedure 12-1: “Upgrade high-speed OC-48 OLIUs in

UPSR/BLSR network” (p. 12-4)

and then repeat this procedure.

Continue with

Step 3

to determine the circuit pack mode of the packs.

The Main slots are equipped with circuit packs that are compatible with R6.0.x. Proceed to

Procedure 2-4.2:

“Upgrade software generic via FTP (5.x to 6.0)”

(p. 2-79) .

3

4

5

6

.................................................................................................................................................................................................

From the System View menu, select

View

→

Equipment

→

Circuit Pack

, highlight

CP main-1, and click

Select

.

Result:

The View Equipment screen appears.

.................................................................................................................................................................................................

In the View Equipment screen, locate the Circuit Pack Mode parameter in the

Equipment Details panel. Note the value of the Circuit Pack Mode for CP Main-1, either NORMAL or ENHANCED.

Do NOT click

Close

on the View Equipment screen.

.................................................................................................................................................................................................

Highlight CP main-2 and click

Select

.

.................................................................................................................................................................................................

In the View Equipment screen, locate the Circuit Pack Mode parameter in the

Equipment Details panel. Note the value of the Circuit Pack Mode for CP Main-2, either NORMAL or ENHANCED.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-77

Software installation and upgrades, and database backup procedures

Procedure 2-4.1: Verify proper equipage in Main slots

7

.................................................................................................................................................................................................

Refer to

Step 4

and

Step 6 . Is the Circuit Pack Mode for CP main-1 and/or CP main-2

NORMAL (6 STS-1 switch fabric)?

If...

Yes

No

Then...

The LNW26B-type circuit packs with the Circuit Pack

Mode jumper set as NORMAL are NOT supported in

6.0.x.

Choose one of the following two options:

1. Change Circuit Pack Mode to ENHANCED by physically changing the jumper setting on the circuit packs.

Proceed to

Procedure 4-22: “Change circuit pack mode of LNW26B, LNW28, LNW77, or LNW121B-159B

OC-48 OLIU circuit packs” (p. 4-84) and then repeat

this procedure.

2. Upgrade the LNW26B-type circuit packs to LNW27,

LNW29, LNW32, LNW76, or LNW221-259 OC-48

OLIU circuit packs. These circuit packs can cross-connect VT1.5 signals in up to 48 STS-1 signals.

Proceed to

Procedure 12-1: “Upgrade high-speed

OC-48 OLIUs in UPSR/BLSR network” (p. 12-4)

and then repeat this procedure.

The LNW26B-type circuit packs with the Circuit Pack

Mode jumper set as ENHANCED are supported in 6.0.x.

Proceed to

Procedure 2-4.2: “Upgrade software generic via FTP (5.x to 6.0)” (p. 2-79)

to upgrade the 5.x shelf to

6.0.x.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

2-78 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x to 6.0)

.................................................................................................................................................................................................................................

Overview

Use this procedure to upgrade a software generic from Release 5.x to Release 6.0.x via

FTP.

Required equipment

Refer to

“Required equipment” (p. 2-72)

in

Procedure 2-4: “Upgrade software generic via FTP” (p. 2-72)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure:

1. Complete

Procedure 2-4: “Upgrade software generic via FTP” (p. 2-72) .

2. You must be able to perform a backup of the LNW1 database.

Step

1

2

3

Complete the following steps to upgrade a software generic from Release 5.0/5.1 to

Release 6.0 via FTP.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Remote Backup

.

.................................................................................................................................................................................................

In the pull-down

Backup To/Via:

menu, select

FTP

.

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and proceed to

Step 5 . OR

Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

ipconfig

CIT is the FTP server, you can determine its IP address by entering from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the backup to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar

®

CIT as your FTP server, the default user name/password for the WaveStar

®

CIT is

LUC01

/

LUC+01

, however your user ID/password may be different.)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-79

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

4

5

.................................................................................................................................................................................................

If you entered connection information in

Step 3

and wish to keep the information for future backups:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Entries to the

Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

.................................................................................................................................................................................................

In the

Source/Destination Directory Path

field, enter

backups/<filename>

if you wish to save the backup file to the default location. (If the WaveStar

®

CIT is the FTP server, a maximum of 80 characters is suggested for this field.)

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and over-write the default entry. The

Browse

button is not available (greyed out) if the FTP server is not the local WaveStar

®

CIT or the IP address of the FTP server is not in the same subnet as the IP address of the shelf.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

If you wish to store your data in a subdirectory within the default path, you may enter

backups/<subdirectory>/<filename>

if the subdirectory exists before the command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.

6

.................................................................................................................................................................................................

Click

OK

.

You will be asked to verify that you wish to backup to the directory that you entered above. Click

Yes

if you typed the path correctly.

Result:

The Progress Indicator screen appears, indicating that the backup is in progress. When the backup completes, a

Remote Backup successful screen appears. Click

OK

.

The backup file is now stored. If the default path and a subdirectory were used, the file may be found at:

.................................................................................................................................................................................................................................

2-80 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

7

8

9

10

11

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

C:/Program Files/Lucent Technologies/WaveStar

CIT/backups/<subdirectory>/<filename>

.................................................................................................................................................................................................

Close your WaveStar

®

→

NE Disconnect

CIT session with the 5.x NE. From the System View, select and click

Yes

in the confirmation window.

File

Result:

The System View closes.

.................................................................................................................................................................................................

Disconnect the LAN and/or serial cables from the

LAN

and/or

RS232

port(s) on the front of the LNW1 SYSCTL.

.................................................................................................................................................................................................

Initiate a ten-second countdown (9, 8, 7, 6, 5, 4, 3, 2, 1, 0) in the

IND

display on the

LNW1 SYSCTL by simultaneously depressing the

ACO TEST

and

SEL

buttons on the front of the LNW1 SYSCTL.

Important! Removing the LNW1 without initiating the ten-second countdown may result in unexpected and undesirable protection switches, incorrect circuit fault indications, or incoming signal failure alarms. All SYSCTL functions are suspended during the countdown.

.................................................................................................................................................................................................

Remove the LNW1 SYSCTL circuit pack during the 10-second countdown.

Important! While the SYSCTL circuit pack is removed, do NOT remove or replace any transmission circuit packs.

.................................................................................................................................................................................................

Important! For software installation, two NVMs should be present in the LNW2

SYSCTL. After the LNW2 is installed, if one or two NVMs are missing,

NVM removed alarm(s) are issued. If both NVM sockets are empty, the

IND

displays an alternating

E

and

0

and

1

.

Refer to

Step 12

for the complete listing of codes and required actions.

Seat the new LNW2 SYSCTL circuit pack and allow a few minutes for the pack to complete initialization.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-81

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

12

Result:

The LNW2 SYSCTL exhibits the following visible cycles during initialization:

1. The

FAULT

LED lights and remains lighted for approximately 90 seconds. After approximately 15 seconds, a flashing

b

appears in the

IND

display on the

SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 75 seconds and then

IND

display is blank.

2. The

FAULT

LED remains lighted for approximately another 20 seconds and then extinguishes.

3. The

ACTIVE

LED lights and remains lighted and the

CR

LED flashes 10 times.

While the

CR

LED is flashing, the

MJ

,

ABN

, and

NE

LEDs light and remain lighted.

Because the LNW2 SYSCTL is in 6.0 Maintenance Mode, an alternating

M

and

P

and

6

and “

.

” (“.” is a red, four-segment square [2 x 2] representing a period) and

0

appear in the

IND

display.

4. Continue with

Step 12 .

.................................................................................................................................................................................................

Observe the

IND

display on the LNW2 SYSCTL; the display indicates the state of the

SYSCTL.

If...

alternating

M

and

P

and

6

and “

.

”

(“.” is a red, four-segment square

[2 x 2] representing a period) and

0

alternating

E

and

0

and

0

Then...

6.0 Maintenance Mode. Continue with

Step 13 .

alternating

E

and

0

and

1

alternating

E

and

0

and

2

alternating

E

and

0

and

3

LNW2 SYSCTL must be replaced.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

No NVMs are detected on the LNW2 SYSCTL.

Install two Lucent-supplied NVMs in the LNW2 or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

NVMs are present but not readable. Check to make sure they are properly seated and repeat this procedure.

Not Supported.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

.................................................................................................................................................................................................................................

2-82 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

If...

alternating

Letter

F

alternating

Letter

U

E

N

and and

1

O

and and

0 x

flashing

b

A red, four-segment square (2 x 2) appears in the

IND

display on the

LNW2 SYSCTL.

Then...

LNW2 SYSCTL will not boot.

No compatible generic on the NVMs in the

LNW2 SYSCTL.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure or contact your next level of support.

LNW2 SYSCTL faceplate latches are not fully seated.

Unseat the LNW2 SYSCTL and repeat this procedure, properly seating the faceplate latch.

“x” indicates that the NVM socket (1 or 2) is empty or the NVM installed is failed. Replace the indicated NVM or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

LNW2 SYSCTL will not boot due to unexpected or unreadable shelf type.

Repair the problem generally caused by bent pins and repeat this procedure.

Boot in progress.

Acknowledges the

UPD/INIT

button was momentarily pushed.

Pushing the

UPD/INIT

button while in

Maintenance Mode has no effect.

13

14

.................................................................................................................................................................................................

Connect the cross-over LAN cable from the PC’s Network Interface Card (NIC) to the rear

J16 IAO LAN

port on the Metropolis

®

DMX shelf backplane or the front

LAN

port on the LNW2 SYSCTL circuit pack faceplate. (When TCP/IP is enabled on the rear

LAN port, OSI is disabled.)

.................................................................................................................................................................................................

From the Network View of the WaveStar

®

CIT session you established in

Procedure

2-4: “Upgrade software generic via FTP” (p. 2-72) , select the

View:

pull-down menu and select

CIT OSI Neighbors

.

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-83

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

Result:

The CIT OSI Neighbor(s) are automatically detected.

If you were previously logged in to the NE and/or you do not see your NE, from the Network View, select

View

→

Refresh OSI View

.

Figure 2-6 CIT OSI neighbor

15

16

.................................................................................................................................................................................................

In the Network View,

Figure 2-6, “CIT OSI neighbor” (p. 2-84) , right-click on the

LT-DMX NE icon that was detected, and select

Graphical Using

→

OSI

from the resulting menu.

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX and click

OK

.

.................................................................................................................................................................................................................................

2-84 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

17

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

Important! Because the shelf is in Maintenance Mode, your logins and passwords are default.

Enter the following in the NE Login Dialog window (login information is case sensitive) to log in to the NE:

User ID:

LUC01

Password:

DMX2.5G10G

Click

OK

.

Important! After you select your backup database, complete the Maintenance

Mode Wizard, and the NE restarts, your original User IDs and Passwords will be restored.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-85

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

Result:

Screen 1 of 4 in the Maintenance Mode Wizard appears.

This screen picks up the time format preference from the WaveStar

®

CIT.

You can provision the time format display for your WaveStar

®

CIT from the

Network View by selecting

View

→

Preferences

and clicking on the Display tab.

.................................................................................................................................................................................................................................

2-86 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

18

This screen allows you to choose your preference for time format, either a 12-hour clock or a 24-hour clock.

•

If your time format preference is a 12-hour clock, from the

Time

panel, select

Hour:

(0-12),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus.

You must also specify am or pm by selecting one of the radio buttons.

•

If your time format preference is a 24-hour clock, From the

Time

panel, select the

Hour:

(0-23),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus.

.................................................................................................................................................................................................

Important! The actual time and date are preset from your PC.

On Screen 1 of 4 in the Maintenance Mode Wizard, read the information, verify the date and time, make any required changes, and click

Next

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-87

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

Result:

Screen 2 of 4 in the Maintenance Mode Wizard appears.

19

.................................................................................................................................................................................................

On Screen 2 of 4 in the Maintenance Mode Wizard, click

Download

.

.................................................................................................................................................................................................................................

2-88 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

Result:

Screen 1 of 3 in the Download Generic Wizard appears.

20

.................................................................................................................................................................................................

On Screen 1 of 3 in the Download Generic Wizard, read the information, select

FTP

and click

Next

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-89

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

Result:

Screen 2 of 3 in the Download Generic Wizard appears.

21

.................................................................................................................................................................................................

Important! LAN-1 is the

LAN

port on the faceplate of the LNW2 SYSCTL circuit pack. LAN-2 is the

J16 IAO LAN

port on the rear of the Metropolis

®

DMX shelf.

On Screen 2 of 3 in the Download Generic Wizard, follow the instructions to enable

TCP/IP Control on the LAN port to which you are connected. Click

Modify

to enter the IP Address, IP Subnet Mask, and/or IP Default Router Address. Click

Next

.

.................................................................................................................................................................................................................................

2-90 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

Result:

Screen 3 of 3 in the Download Generic Wizard appears.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-91

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

22

23

24

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and proceed to

Step 24 . OR

Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

CIT is the FTP server, you can determine its IP address by entering

ipconfig

from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the backup to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar

®

CIT as your FTP server, the default user name/password for the WaveStar

®

CIT is

LUC01

/

LUC+01

, however your user ID/password may be different.)

.................................................................................................................................................................................................

If you entered connection information in

Step 22

and wish to keep the information for future FTP activities:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Important! Entries to the

Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

.................................................................................................................................................................................................

On Screen 3 of 3 in the Download Generic Wizard in the

Path

panel, enter the current location of the generic to be downloaded in the Path field or use the

Browse

button to select the generic to be downloaded. (If the FTP server is not the local host, the

Browse

button is greyed out.) Click

Download

.

The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:/Program

Files/Lucent Technologies/WaveStar CIT/generics/DMX/6.0.1/p

. The syntax of the relative path must start with the path name; for example:

/generics/DMX/6.0.1/p/

. (If necessary, replace 6.0.1 with your current release, for example 6.0.2.)

If the FTP server is not the WaveStar

®

CIT, then enter the path starting at the FTP home directory on the server.

.................................................................................................................................................................................................................................

2-92 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

25

Result:

A warning message appears listing the options you provisioned in the previous screens.

.................................................................................................................................................................................................

Verify the information and either click

Yes

to start the download process or click

No

to return to the download screen and change your selections.

Result:

If you choose yes, the following initial software download progress indicator runs for approximately 15 minutes.

26

.................................................................................................................................................................................................

Do you wish to observe the FTP download progress?

If...

Yes

No

Then...

Proceed to

Procedure 14-17: “Observe FTP progress”

(p. 14-101)

and then continue with

Step 27 .

Continue with

Step 27 .

27

.................................................................................................................................................................................................

Once the software generic download is complete, the following confirmation message appears. Click

Yes

to use the generic that is now in the Dormant area.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-93

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

Result:

Screen 3 of 4 in the Maintenance Mode Wizard appears.

28

.................................................................................................................................................................................................

On Screen 3 of 4 in the Maintenance Mode Wizard, click

Download

.

.................................................................................................................................................................................................................................

2-94 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

Result:

Screen 1 of 3 in the Download Database Wizard appears.

29

.................................................................................................................................................................................................

On Screen 1 of 3 in the Download Database Wizard, read the information, select

FTP

and click

Next

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-95

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

Result:

Screen 2 of 3 in the Download Database Wizard appears.

.................................................................................................................................................................................................

30

Important! LAN-1 is the

LAN

port on the faceplate of the LNW2 SYSCTL circuit pack. LAN-2 is the

J16 IAO LAN

port on the rear of the Metropolis

®

DMX shelf.

On Screen 2 of 3 in the Download Generic Wizard, the information entered in

Step 21

should still be present and valid. If the information is not present, follow the instructions to enable TCP/IP Control on the LAN port to which you are connected.

Click

Modify

to enter the IP Address, IP Subnet Mask, and/or IP Default Router

Address.

.................................................................................................................................................................................................................................

2-96 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

Click

Next

.

Result:

Screen 3 of 3 in the Download Database Wizard appears.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-97

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

31

32

33

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and proceed to

Step 33 . OR

Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

CIT is the FTP server, you can determine its IP address by entering

ipconfig

from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the backup to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar

®

CIT as your FTP server, the default user name/password for the WaveStar

®

CIT is

LUC01

/

LUC+01

, however your user ID/password may be different.)

.................................................................................................................................................................................................

If you entered connection information in

Step 31

and wish to keep the information for future FTP activities:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Important! Entries to the

Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

.................................................................................................................................................................................................

On Screen 3 of 3 in the Download Database Wizard in the

Path

panel, enter the location where the database information is stored. Enter the path and filename exactly as it was entered in

Step 5 . For example:

backups/<subdirectory>/<filename>

.

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and over-write the default entry. The

Browse

button is not available (greyed out) if the FTP server is not the local WaveStar

®

CIT or the IP address of the FTP server is not in the same subnet as the IP address of the shelf.

Click

Download

.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

.................................................................................................................................................................................................................................

2-98 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

34

Result:

A warning message appears listing the options you provisioned in the previous screens.

.................................................................................................................................................................................................

Verify the information and click

Yes

.

Result:

If you choose Yes, the database download progress indicator runs for approximately two minutes.

35

.................................................................................................................................................................................................

Do you wish to observe the FTP download progress?

If...

Yes

No

Then...

Proceed to

Procedure 14-17: “Observe FTP progress”

(p. 14-101)

and then continue with

Step 36 .

Continue with

Step 36 .

36

.................................................................................................................................................................................................

Once the database download is complete, the following confirmation message appears.

Click

Yes

to use the database that is now in the Backup area.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-99

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

Result:

Screen 4 of 4 in the Maintenance Mode Wizard appears. In this screen,

6.0.1 is an example; your selected generic could be different, for example 6.0.2.

5.1.1 is an example too; your selected database could be 5.0.x or 5.1.x.

37

.................................................................................................................................................................................................

On Screen 4 of 4 in the Maintenance Mode Wizard, read the information, verify that you have selected the correct generic and database and click

Finish

to restart the system and apply the generic and database.

.................................................................................................................................................................................................................................

2-100 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

38

39

Result:

The Maintenance Mode Wizard closes and your connection to the shelf is terminated.

The LNW2 SYSCTL exhibits the following visible cycles while the generic and database are installed and validated and the SYSCTL reboots:

1. For approximately 10 minutes, the alternating

M

and

P

and

6

and “

.

” (“.” is a red, four-segment square [2 x 2] representing a period) and

0

continue to appear in the

IND

display on the SYSCTL.

2. After approximately 10 minutes, all LEDs extinguish and the

IND

display on the

SYSCTL is blank for approximately 5 seconds.

3. A flashing

b

appears in the

IND

display on the SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 60 seconds and then

IND

display is blank for approximately 20 seconds.

4. The

ACTIVE

LED lights and remains lighted.

5. A flashing

b

appears again in the

IND

display on the SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 2.5 minutes while the database is being converted and then

IND

display is blank.

6. When nothing appears in the

IND

display and the

ACTIVE

LED is lighted and the other LEDs return to their previous state (pre-LNW1 backup), the NE software and database installation is complete.

However, smart circuit packs may be upgrading their firmware. If flashing green

ACTIVE

LEDs are present on a circuit pack, firmware is currently being downloaded to that pack. Wait until all smart circuit packs finish upgrading their firmware before proceeding.

If an alarm condition existed prior to the upgrade, the NE will rediscover the alarm condition and activate the appropriate LEDs on the shelf.

7. Continue with

Step 38 .

.................................................................................................................................................................................................

To verify that the upgrade was successful, depress and hold the

ACO TEST

push-button on the LNW2 SYSCTL for about 4 seconds.

Result:

All LEDs on the shelf light. A red, 35-segment (5 x 7) rectangle appears in the

IND

display on the SYSCTL. Since the

IND

display is a 35-segment display, this test indicates all segments are working.

.................................................................................................................................................................................................

Release the

ACO TEST

push-button on the LNW2 SYSCTL when the red rectangle disappears in the

IND

display.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-101

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

40

41

42

43

44

45

Result:

The current software generic appears in the

IND

display on the LNW2

SYSCTL and the shelf LEDs return to their previous status.

.................................................................................................................................................................................................

From the Network View of the WaveStar

®

CIT session you established in

Procedure

2-4: “Upgrade software generic via FTP” (p. 2-72) , select the

View:

pull-down menu and select

CIT OSI Neighbors

.

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................

From the Network View, select

View

→

Refresh OSI View

.

Result:

The CIT OSI neighbor(s) are automatically detected.

Your TID will be your original TID, the same TID provisioned on your 5.x NE.

.................................................................................................................................................................................................

In the Network View, right-click on the NE icon that was detected, and select

Graphical Using

→

OSI

from the resulting menu.

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX and click

OK

.

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

In the NE login window, login to the shelf using your original user ID and password; the same user ID and password provisioned on your 5.x NE.

Click

OK

.

Result:

The title bar of the System View and the legal notice text should both reflect the current NE software generic, for example: R6.0.1.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Is the Generic Software Version correct?

If...

Yes

No

Then...

STOP! End of Procedure.

Contact your next level of support.

.................................................................................................................................................................................................................................

2-102 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.2: Upgrade software generic via FTP (5.x

to 6.0)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-103

Software installation and upgrades, and database backup procedures

Procedure 2-4.3: Upgrade software generic via FTP (6.0.0 to

6.0.x)

.................................................................................................................................................................................................................................

Overview

Use this procedure to download the software generic via the FTP from the WaveStar

®

CIT to the local network element. To download the software generic to a local shelf via FTP, refer to

Procedure 2-4: “Upgrade software generic via FTP” (p. 2-72) . To

download the software generic to a remote shelf via FTTD, refer to

Procedure 2-5:

“Upgrade software generic via FTTD (6.0.0 to 6.0.x)” (p. 2-109) .

Important! Your NE must be running Release 6.0.0 or later to use this procedure.

Required equipment

Refer to

“Required equipment” (p. 2-72)

in

Procedure 2-4: “Upgrade software generic via FTP” (p. 2-72)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 2-4: “Upgrade software generic via FTP” (p. 2-72) .

Step

1

2

3

Complete the following steps to download system software via FTP.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

View NE Administration

.

Verify that File Transfer Protocol (FTP) is Enabled and click

Close

.

.................................................................................................................................................................................................

If required, select

Administration

→

Set NE

and enable

File Transfer Protocol

. Click

OK

.

.................................................................................................................................................................................................

Provision the destination shelf for TCP/IP communications. From the System View menu, select

Administration

→

Data Communications

.

.................................................................................................................................................................................................................................

2-104 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.3: Upgrade software generic via FTP

(6.0.0 to 6.0.x)

4

Result:

The Data Communications window appears.

.................................................................................................................................................................................................

Which port are you provisioning for TCP/IP?

If...

LAN-1 for the front

LAN

port on the SYSCTL

(LAN-1 is intended to be used for local [direct] software downloads.)

LAN-2 for the rear

J16 IAO LAN

port on the backplane

Then...

Continue with

Step 5 .

Proceed to

Step 6 .

5

6

7

.................................................................................................................................................................................................

From the Data Communications window, click on the

TCP/IP

tab and provision the following fields accordingly for LAN-1:

1.

Port AID:

select the port that you are using for FTP: LAN-1

2.

TCP/IP Function:

select Enable

3. Click

Modify

to either enter or change the following:

•

IP Address

•

IP Subnet Mask

•

IP Default Router Address (Because LAN-1 is intended to be used for local

[direct] software downloads, the IP Default Router Address is not required when using LAN-1).

4. Proceed to

Step 7 .

.................................................................................................................................................................................................

From the Data Communications window, click on the

TCP/IP

tab and provision the following fields accordingly for LAN-2:

1.

Port AID:

select the port that you are using for FTP: LAN-2

2.

TCP/IP Function:

select Enable

3. Click

Modify

to either enter or change the following:

•

IP Address

•

IP Subnet Mask

•

IP Default Router Address

.................................................................................................................................................................................................

Click

Apply

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-105

Software installation and upgrades, and database backup procedures

Procedure 2-4.3: Upgrade software generic via FTP

(6.0.0 to 6.0.x)

8

9

10

11

12

Important! If the TCP/IP information for one of the LAN ports is already provisioned, then reprovisioning that port, or provisioning the other LAN port may cause the shelf to reset.

Result:

A warning message appears.

.................................................................................................................................................................................................

Click

Yes

and then click

Close

on the Data Communications window.

.................................................................................................................................................................................................

Specifying either OSI or Serial in the

Connection Type:

field, log in to the destination shelf again.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Download

Software

.

Result:

The Download Software window appears.

.................................................................................................................................................................................................

In the pull-down

Download From/Via:

menu, select

FTP

. Select the connection from the

Profile

pull-down menu and proceed to

Step 13 . OR Enter information for a new

profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

CIT is the FTP server, you can determine its IP address by entering

ipconfig

from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the backup to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar the WaveStar

®

®

CIT as your FTP server, the default user name/password for

CIT is

LUC01

/

LUC+01

, however your user ID/password may be different.)

.................................................................................................................................................................................................

If you entered connection information in

Step 11

and wish to keep the information for future FTP activities:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Important! Entries to the

Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

.................................................................................................................................................................................................................................

2-106 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-4.3: Upgrade software generic via FTP

(6.0.0 to 6.0.x)

13

14

15

.................................................................................................................................................................................................

In the

Source/Destination Directory Path

panel, enter the current location of the generic to be downloaded or use the

Browse

button (if available) to select the generic to be downloaded. If the FTP server is not the local host, the

Browse

button is greyed out.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

If you are using the WaveStar

®

CIT as your FTP server, the WaveStar

®

CIT fills in the beginning of the default path (C:/Program Files/Lucent Technologies/WaveStar

CIT/).

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

If the FTP server is not the WaveStar

®

CIT, then enter the path starting at the FTP home directory on the server.

.................................................................................................................................................................................................

In the

Product Type

panel, select the product type of the software generic that you are downloading (not necessarily the same as the NE to which you are downloading).

.................................................................................................................................................................................................

Click

OK

.

Result:

A warning message appears asking you to confirm executing this command. Verify the information and click

Yes

. While the download is in progress, a progress indicator window is present.

The download takes approximately 15 minutes.

The download may be cancelled any time by pressing the

Cancel

button on the progress screen.

When the transfer is complete, the Progress Indicator window closes and the download software successful window appears. Click

OK

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-107

Software installation and upgrades, and database backup procedures

Procedure 2-4.3: Upgrade software generic via FTP

(6.0.0 to 6.0.x)

16

.................................................................................................................................................................................................

Is the WaveStar

®

progress?

CIT your FTP server and do you wish to observe the FTP download

If...

Yes

No

Then...

Proceed to

Procedure 14-17: “Observe FTP progress”

(p. 14-101)

and then continue with

Step 17 .

Continue with

Step 17 .

17

.................................................................................................................................................................................................

Important! Do NOT insert a new circuit pack in the shelf until after you apply the new software generic and clear the dormant/exec version mismatch condition.

Do you wish to apply (activate) the software generic that you recently downloaded to the dormant area of the Metropolis

®

DMX shelf?

If...

Yes

No

Then...

Proceed to

Procedure 2-7: “Apply software generic”

(p. 2-120)

and then continue with

Step 18 .

Continue with

Step 18 .

18

.................................................................................................................................................................................................

Do you wish to upgrade additional shelves via FTP?

If...

Yes

No

Then...

Repeat this procedure from

Step 1

for each shelf that you wish to upgrade via FTP.

STOP! End of Procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

2-108 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-5: Upgrade software generic via FTTD (6.0.0 to

6.0.x)

.................................................................................................................................................................................................................................

Overview

Use this procedure to download the software generic to a shelf without TCP/IP connectivity via FTTD (FTAM-FTP gateway).

To download the software generic to a local shelf via FTP, refer to

Procedure 2-4:

“Upgrade software generic via FTP” (p. 2-72) . To download the software generic to a

local or remote shelf via FTAM, refer to

Procedure 2-3: “Upgrade software generic via

FTAM” (p. 2-40) .

Important! Your NE must be running Release 6.0.0 or later to use this procedure.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

In addition to

“Required equipment” (p. 2-2)

listed in this chapter, the following equipment is also required:

•

CAT5 Ethernet cable with either a 10/100 hub or a cross-over cable for the

LAN

or

IAO LAN

port

•

Copy of the new system generic software program on your PC or FTP server

•

Current Metropolis

®

DMX Access Multiplexer Software Release Description for the software generic being installed

Important! If the FTP server fails to start, it could mean that another program using an FTP server is already running. Depending on what operating system you are using, you must go to the device file and disable the FTP server. Refer to

Procedure 14-18: “Disable an FTP server on your PC” (p. 14-103)

for instructions for each allowed operating system.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 2-2)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

2. Verify that new software generic program is available.

3. Refer to the Metropolis

®

DMX Access Multiplexer Software Release Description for a description of any special considerations required when installing this version of software.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-109

Software installation and upgrades, and database backup procedures

Procedure 2-5: Upgrade software generic via FTTD (6.0.0

to 6.0.x)

This procedure uses FTP (file transfer protocol) and FTAM-FTP gateway/file transfer translation device (FTTD) to download software to a shelf. FTTD allows Metropolis

®

DMX to function as a gateway network element (GNE) that facilitates file downloads between FTP servers and remote network elements (RNEs) connected to the

Metropolis

®

DMX.

Important! If you log in via TCP/IP, your PC must be part of the GNE’s TCP/IP

Gateway Host List. Refer to

Procedure 7-16: “Provision/enable/disable the NE as a

TL1 TCP/IP GNE” (p. 7-49) .

Step

1

2

3

4

Complete the following steps to download system software via FTTD.

.................................................................................................................................................................................................

Connect the PC and establish a WaveStar

®

Element.

CIT session to the gateway Network

Important! You must login via either OSI or TCP/IP.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Set NE

and enable

File

Transfer Protocol (FTP)

and

FTAM-FTP (FTTD) Gateway Control

.

.................................................................................................................................................................................................

Click

OK

.

.................................................................................................................................................................................................

Is your remote NE in the same OSI network as your gateway NE?

If

Yes

No

Then

Proceed to

Step 6 .

Continue with

Step 5 .

5

.................................................................................................................................................................................................

From the System View, select

Administration

→

Data Communications

.

Select the

Network Layer

tab and record the NSAP from the

Network Service

Access Point

panel (the NSAP is a 40-digit hex number). This NSAP is required later in this procedure.

.................................................................................................................................................................................................................................

2-110 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-5: Upgrade software generic via FTTD (6.0.0

to 6.0.x)

6

7

8

9

.................................................................................................................................................................................................

Establish a WaveStar

®

CIT session to the remote Network Element to which you wish to download the NE software generic.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Download

Software

.

Result:

The Download Generic window appears.

.................................................................................................................................................................................................

In the pull-down

Download From/Via:

menu, select

FTTD

and verify that the

FTTD

tab is selected.

.................................................................................................................................................................................................

Define the FTAM-FTP Gateway in one of the following ways:

•

If the TID of the FTAM-FTP Gateway has been previously defined, select it from the

TID

pull-down menu.

OR

•

If the gateway NE and the remote NE are in the same OSI area:

1. Enter the TID of the FTAM-FTP Gateway in the

TID

field and click

Get NSAP

.

(If any fields on this screen are populated, click

Clear

before you enter the

TID.)

2. Click

Add

and then

Save

. The TID is added to the pull-down menu for this

CIT and you should never need to re-enter the NSAP address for this gateway

NE’s TID.

OR

•

If the gateway NE and the remote NE are not in the same OSI area:

1. In the

FTTD

panel, select

_template_

from the

TID:

pull-down menu. This will pre-populate most of the fields on this form (required value for

Psel

is 02,

Ssel

is 5353, and

Tsel

is 5454).

2. Click

Modify

.

3. Replace

_template_

with the TID of the FTAM-FTP gateway.

4. Complete the NSAP Address panel with the NSAP of the FTTD gateway recorded in

Step 5 .

In most cases, you will only need to replace the System Identifier (

Sys:

) field with the Mac Address of the FTTD gateway.

Note: The Mac Address is the first 12 digits of the last 14 digits of the NSAP.

The Mac Address of Lucent Technologies products begin with “00601D”.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-111

Software installation and upgrades, and database backup procedures

Procedure 2-5: Upgrade software generic via FTTD (6.0.0

to 6.0.x)

10

11

12

Example: The Mac Address for NSAP Address

39840F800000000000000000000 00601D2CBC1800 is 00601D2CBC18.

5. Replace the Selector (

Sel:

) field with “1d”.

6. Click

Add

and then

Save

. The TID has been added to the pull-down menu for this CIT and you should never need to re-enter the NSAP address for this gateway NE’s TID, unless you replace the SYSCTL in the GNE.

.................................................................................................................................................................................................

Select the

FTP

tab.

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and then proceed to

Step 13 .

OR Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

ipconfig

CIT is the FTP server, you can determine its IP address by entering from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the download to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar

®

CIT as your FTP server, the default user name/password for the WaveStar

®

CIT is

LUC01

/

LUC+01

, however your user name/password may be different.)

.................................................................................................................................................................................................

If you entered connection information in

Step 11

and wish to keep the information for future backups:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Important! Entries to the

Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

13

.................................................................................................................................................................................................

In the

Source/Destination Directory Path

panel, enter the current location of the generic to be downloaded or use the

Browse

button (if available) to select the generic to be downloaded. If the FTP server is not the local host, the

Browse

button is greyed out.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

.................................................................................................................................................................................................................................

2-112 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

14

15

16

Procedure 2-5: Upgrade software generic via FTTD (6.0.0

to 6.0.x)

If you are using the WaveStar

®

CIT as your FTP server, the WaveStar

®

CIT fills in the beginning of the default path (C:/Program Files/Lucent Technologies/WaveStar

CIT/).

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

If the FTP server is not the WaveStar

®

CIT, then enter the path starting at the FTP home directory on the server.

.................................................................................................................................................................................................

In the

Product Type

panel, select the product type of the software generic that you are downloading (not necessarily the same as the NE to which you are downloading).

.................................................................................................................................................................................................

Click

OK

.

Result:

A warning message appears asking you to confirm executing this command. Verify the information and click

Yes

. While the download is in progress, a progress indicator window is present.

The download takes approximately 15 minutes.

The download may be cancelled any time by pressing the

Cancel

button on the progress screen.

When the transfer is complete, the Progress Indicator window closes and the download software successful window appears. Click

OK

.

.................................................................................................................................................................................................

Do you wish to observe the FTP download progress?

If...

Yes

No

Then...

Proceed to

Procedure 14-17: “Observe FTP progress”

(p. 14-101)

and then continue with

Step 17 .

Continue with

Step 17 .

17

.................................................................................................................................................................................................

Important! Do NOT insert a new circuit pack in the shelf until after you apply the new software generic and clear the dormant/exec version mismatch condition.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-113

Software installation and upgrades, and database backup procedures

Procedure 2-5: Upgrade software generic via FTTD (6.0.0

to 6.0.x)

Do you wish to apply (activate) the software generic that you recently downloaded to the dormant area of the Metropolis

®

DMX shelf?

If...

Yes

No

Then...

Proceed to

Procedure 2-7: “Apply software generic”

(p. 2-120)

and then continue with

Step 18 .

Continue with

Step 18 .

18

.................................................................................................................................................................................................

Do you wish to upgrade additional shelves via FTTD?

If...

Yes

No

Then...

Repeat this procedure from

Step 2

for each shelf that you wish to upgrade via FTTD.

STOP! End of Procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

2-114 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-6: Copy software generic to a remote shelf

.................................................................................................................................................................................................................................

Overview

Use this procedure to copy a supported software generic from your Metropolis

®

6.0 shelf to a supported remote NE.

DMX

Important! This procedure requires that the software generic to be copied be installed in the Dormant areas of the NVMs installed in the LNW2 in your source

Metropolis

®

DMX shelf.

You must also have OSI connectivity (via your OSI LAN or DCC) between the source and the destination NEs.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

The following equipment is required:

•

CAT5 Ethernet cable with either a 10/100 hub or a cross-over cable for the

LAN

or

IAO LAN

port

•

Software generic in the Dormant areas of the NVMs installed in the LNW2 in your source Metropolis

®

DMX shelf.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 2-2)

in this chapter and

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

This procedure requires that the software generic being copied is installed in the

Dormant areas of the NVMs installed in the LNW2 of the source Metropolis

®

DMX shelf. You must also have OSI connectivity (via OSI LAN or DCC) between the source and the destination NEs.

This procedure uses the

cpy-prgm

command to copy a software generic from an in-service Metropolis

®

DMX 6.0 shelf to the following types of remote NEs:

•

Metropolis

®

DMX

•

Metropolis

®

DMXtend

•

Metropolis

®

DMXpress

•

Metropolis

®

DMXplore

•

DDM-2000 OC-3

•

DDM-2000 OC-12

•

DDM-2000 FiberReach

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-115

Software installation and upgrades, and database backup procedures

Procedure 2-6: Copy software generic to a remote shelf

Important! Metropolis

®

DMX and Metropolis

®

DMXtend are the only NEs that can accept a software generic of another product type. For example, if your remote

NE is a Metropolis

®

DMXplore shelf, the only product type that you can copy to the Metropolis

®

DMXplore shelf is dmxplore.

Step

1

2

3

Complete the following steps to copy a supported software generic from your

Metropolis

®

DMX 6.0 shelf to a supported remote NE.

.................................................................................................................................................................................................

Establish a WaveStar

®

CIT session and log in to the

source

shelf (the shelf with the desired generic in the in the Dormant areas of the NVMs installed in the LNW2).

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Copy Software

.

Result:

The Copy Software screen appears.

.................................................................................................................................................................................................

In the Copy Software screen, what are the Product Type and Release of the Dormant

Software Generic?

If...

dmx and Release 6.x

or dmxtend and Release 4.x

dmx and 5.x or earlier or dmxtend and 3.x

Then...

Your destination shelf must be either a

Metropolis

®

DMX 6.0 NE or Metropolis

®

DMXtend 4.0 NE, equipped with an LNW2.

You cannot copy the 6.x/4.x generic to a

Metropolis

®

DMX or Metropolis

®

DMXtend destination shelf equipped with an LNW1; the

6.x/4.x generic will not physically fit in the

LNW1 controller.

Your destination shelf may be either a

Metropolis

®

DMX or Metropolis

®

DMXtend NE.

If your destination shelf is equipped with an

LNW2, you will not able to apply the generic on the destination shelf but you may then copy the generic to another NE from that shelf.

.................................................................................................................................................................................................................................

2-116 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-6: Copy software generic to a remote shelf

If...

dmxpress dmxplore ddmoc3 ddmoc12 fbrrch

Release is not a concern for these product types.

Then...

Your destination shelf must be of the same product type as the Dormant generic you are copying. The generic may be applied to that destination shelf.

Your destination shelf may also be either a

Metropolis

®

DMX or Metropolis

®

DMXtend NE.

However, you will not able to apply the generic on the destination shelf but you may then copy the generic to another NE from that shelf.

.................................................................................................................................................................................................

4

From the Copy Software screen, select the following fields accordingly:

1. In the pull-down menu entitled

Destination TID:

field, select the TID of the remote

NE to which you wish to copy the software generic.

Currently, Metropolis

®

DMX and Metropolis

®

DMXtend are the only products that can store a second software generic for either Metropolis

®

DMX, Metropolis

®

DMXtend, Metropolis

®

DMXpress, Metropolis

®

DMXplore, DDM-2000 OC-3,

DDM-2000 OC-12, or FiberReach. For example, if your remote NE is a

Metropolis

®

DMXpress shelf, then your software generic type must also be

Metropolis

®

DMXpress.

2. In the pull-down menu entitled

Product Type:

select the type of software that you are copying. Your choices are:

•

DMX

•

DMXpress

•

DMXtend

•

DMXplore

•

DDM-2000 OC-3

•

DDM-2000 OC-12

•

FIBER REACH

3. The

Software Generic

panel displays the generic that currently resides in the

Dormant area of the NVMs installed in the LNW2 in your source Metropolis

®

DMX. The type of software can be identified by the following entry in the Product

Type column:

• dmx = Metropolis

®

DMX

• dmxtend = Metropolis

®

DMXtend

• dmxpress = Metropolis

®

DMXpress

• dmxplore = Metropolis

®

DMXplore

• ddmoc3 = DDM OC-3

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-117

Software installation and upgrades, and database backup procedures

5

6

Procedure 2-6: Copy software generic to a remote shelf

• ddmoc12 = DDM-2000 OC-12

• fbrrch = FIBER REACH

It is not necessary (or possible) to select the generic. The NE automatically selects the generic in the Dormant area. The information is provided so you are aware of the release number of the specific generic.

4. Click

OK

.

Important! During the remote copy, the destination shelf (assuming Metropolis

®

DMX, Metropolis

®

DMXtend, or Metropolis install/copy program IP

®

DMXplore) produces the remote

Standing Condition (SC) autonomous message.

The source shelf (assuming Metropolis

®

DMX, Metropolis

®

DMXtend,

Metropolis

®

DMXplore, or Metropolis

®

DMXpress) produces the copy program

IP

Standing Condition (SC) autonomous message.

If logged in to the NE, each condition is visible in the alarm list (click on the

Alarm List

button from the System View) and the NE History log (select

→

NE History Log

from the System View).

Reports

Result:

While the copy is in progress, a progress indicator window is present.

The download takes approximately 15 minutes.

The copy may be cancelled any time by pressing the

Cancel

button on the progress screen.

.................................................................................................................................................................................................

When the transfer is complete, a message window appears, stating Copy Software

Complete. Click

OK

.

Result:

The software generic is now on the destination shelf.

.................................................................................................................................................................................................

Important! If your destination shelf is either a Metropolis

®

DMX NE (5.x or earlier) or a Metropolis

®

DMXtend NE (3.x or earlier), do NOT insert a new circuit pack in the shelf until after you apply the new software generic and clear the dormant/exec version mismatch condition.

Do you wish to apply (activate) the software generic that you recently downloaded to the dormant area of the destination shelf?

If...

Yes

No

Then...

Continue with

Step 7 .

Proceed to

Step 8 .

.................................................................................................................................................................................................................................

2-118 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-6: Copy software generic to a remote shelf

7

.................................................................................................................................................................................................

Is your destination shelf a Metropolis

®

NE?

DMX 6.0 NE or Metropolis

®

DMXtend 4.0

If...

Then...

Metropolis

®

DMX 6.0 NE If the copied generic was dmx 6.0.x, proceed to

Procedure

2-7: “Apply software generic” (p. 2-120)

and then continue with

Step 8 .

Metropolis

NE

®

DMXtend 4.0

Proceed to the Metropolis

®

DMXtend Access Multiplexer

User Operations Guide, 365-372-325 to apply or copy the software and then continue with

Step 8 .

Other Refer to the appropriate product documentation to apply or copy the software and then continue with

Step 8 .

8

.................................................................................................................................................................................................

Do you wish to copy the software generic to another destination NE?

If...

Yes

No

Then...

Repeat this procedure from

Step 1 .

STOP! End of Procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-119

Software installation and upgrades, and database backup procedures

Procedure 2-7: Apply software generic

.................................................................................................................................................................................................................................

Overview

Use this procedure to apply (activate) a software generic currently in the Dormant area of an NVM in the LNW2.

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Required equipment” (p. 2-2)

and

“Before you begin” (p. 2-2)

in this chapter.

Important! Do NOT insert circuit packs into the shelf until after the apply is complete. The apply is not complete if the Alarm List contains either a dormant/exec code mismatch or a waiting for download condition. Waiting for download indicates that there is at least one circuit pack that requires a firmware upgrade.

Step

1

2

Complete the following steps to apply (activate) a Dormant or Previous software generic.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Apply Software

.

Result:

The Apply Software window appears.

.................................................................................................................................................................................................

Select and/or enter the following information in the Apply Software window:

1. From the

Available Generics

panel, select the software generic (Previous or

Dormant) to be activated.

2. From the

Activation Scheduling

panel, you may schedule the activation time and date in one of the following ways:

•

Select

Install Immediately

. The software installs as soon as possible after you click

OK

and accept the warning screen.

This install option cannot be cancelled.

•

Select

Install In 15 Minutes

. The software installs 15 minutes after you click

OK

.

•

Select

Specify Install Date/Time

and select the

Year

,

Month

,

Date

and

Time

.

.................................................................................................................................................................................................................................

2-120 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

3

4

Procedure 2-7: Apply software generic

You can provision the time format display for your WaveStar

®

CIT from the

Network View by selecting

View

→

Preferences

and clicking on the Display tab.

This screen allows you to choose your preference for time format, either a 12-hour clock or a 24-hour clock.

•

If your time format preference is a 12-hour clock, select

Hour:

(0-12),

Minutes:

(0-59), and

Seconds:

(0-59) from the pull-down menus. You must also specify am or pm by selecting one of the radio buttons.

•

If your time format preference is a 24-hour clock, select the

Hour:

(0-23),

Minutes:

(0-59), and

Seconds:

(0-59) from the pull-down menus.

3. From the

Apply Type

panel, select Type: Smart.

4. Click

OK

.

A warning message appears asking you to confirm the execution of this command.

5. Click

OK

to continue or

Cancel

to return to the Apply Software screen.

While the Apply is in progress, two conditions appear in the Alarm List, install program IP

(software is installing) and generic validation IP

(the generic and the databases on the NVMs are being compared).

Important! You may cancel a scheduled apply that was scheduled by selecting either Install In 15 Minutes or Specify Install Date/Time any time before the software applies. Select

Configuration

→

Software

→

Apply Software

menu, select the generic that is scheduled to install, select

Cancel Install

, and then click

OK

.

.................................................................................................................................................................................................

Approximately 15 minutes after the scheduled apply time, the apply is complete.

A flashing

b

in the

IND

display on the SYSCTL indicates that a boot is in progress.

When the confirmation screen appears, click

OK

.

Result:

The System View closes.

.................................................................................................................................................................................................

Establish a WaveStar

®

CIT session (depending on the physical connection used) and re-log in to your Metropolis

®

DMX shelf.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-121

Software installation and upgrades, and database backup procedures

Procedure 2-7: Apply software generic

5

Result:

The title bars of the System View and the legal notice should both reflect the current NE software generic, for example 6.0.1.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Is the Generic Software Version correct?

If...

Yes

No

Then...

The generic was successfully installed on the

SYSCTL. If required, the firmware on the smart circuit packs is now upgraded. In the Alarm List, the waiting for download condition is present for the circuit packs that are waiting for their firmware to be upgraded.

STOP! End of Procedure.

Contact your next level of support.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

2-122 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-8: Backup and restore NE database via FTP

.................................................................................................................................................................................................................................

Overview

Use this procedure to backup and restore the NE database or to set up an automatic backup schedule via FTP.

Important! You must have direct TCP/IP connectivity to your NE and the NE must have a defined IP address.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

In addition to

“Required equipment” (p. 2-2)

listed in this chapter, CAT5 Ethernet cable with either a 10/100 hub or a cross-over cable for the

LAN

or

IAO LAN

port

(required for TCP/IP connectivity) is also required.

Before you begin

Prior to performing this procedure,

1. Refer to

“Before you begin” (p. 2-2)

and

“Required equipment” (p. 2-2) in this

chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

The WaveStar

®

CIT is not a fully implemented FTP server, but it can handle backup and restore capabilities. For automatic backups, a Navis

®

Optical Element Management

System (Navis

®

Optical EMS) or another large capacity FTP server should be used.

The WaveStar

®

CIT is not recommended for automatic backups.

The backup feature can be forced or scheduled to complete automatically at specified intervals.

If you log in via TCP/IP, your PC must be part of the GNE’s TCP/IP Gateway Host

List (refer to

Procedure 7-16: “Provision/enable/disable the NE as a TL1 TCP/IP GNE”

(p. 7-49) ).

Important! If the FTP server associated with the WaveStar

®

CIT fails to start, it could mean that another program using an FTP server is already running.

Depending on what operating system you are using, you must go to the device file and disable the FTP server. Refer to

Procedure 14-18: “Disable an FTP server on your PC” (p. 14-103)

for instructions for each allowed operating system.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-123

Software installation and upgrades, and database backup procedures

Step

Procedure 2-8: Backup and restore NE database via FTP

1

Complete the following steps to backup and restore the system.

.................................................................................................................................................................................................

Connect the PC and establish a WaveStar

®

CIT session with the gateway NE.

Important! You must have direct TCP/IP connectivity to your NE and the NE must have a defined IP address.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

2

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Set NE

and enable

File

Transfer Protocol

.

.................................................................................................................................................................................................

Click

OK

.

3

.................................................................................................................................................................................................

4 If...

performing an immediate system backup, scheduling or discontinuing an automatic system backup, performing a system restore,

Then...

Proceed to

Procedure 2-8.1: “Backup NE database via FTP” (p. 2-125) .

Proceed to

Procedure 2-8.2: “Provision automatic database backup schedule via FTP” (p. 2-128) .

Proceed to

Procedure 2-8.3: “Restore NE database via FTP” (p. 2-132) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

2-124 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-8.1: Backup NE database via FTP

.................................................................................................................................................................................................................................

Overview

Use this procedure to backup the NE database via FTP.

Important! You must have direct TCP/IP connectivity to your NE and the NE must have a defined IP address.

Required equipment

Refer to

“Required equipment” (p. 2-123)

in

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123) .

Step

1

2

3

Complete the following steps to backup the NE database via FTP.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Remote Backup

.

.................................................................................................................................................................................................

In the pull-down

Backup To/Via:

menu, select

FTP

.

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and proceed to

Step 5 . OR

Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

ipconfig

CIT is the FTP server, you can determine its IP address by entering from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the backup to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar

®

CIT as your FTP server, the default user name/password for the WaveStar

®

CIT is

LUC01

/

LUC+01

, however your user ID/password may be different.)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-125

Software installation and upgrades, and database backup procedures

Procedure 2-8.1: Backup NE database via FTP

4

5

6

.................................................................................................................................................................................................

If you entered connection information in

Step 3

and wish to keep the information for future backups:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Entries to the

Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

.................................................................................................................................................................................................

In the

Source/Destination Directory Path

field, enter

backups/<filename>

if you wish to save the backup file to the default location. (If the WaveStar

®

CIT is the FTP server, a maximum of 80 characters is suggested for this field.)

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and over-write the default entry. The

Browse

button is not available (greyed out) if the FTP server is not the local WaveStar

®

CIT or the IP address of the FTP server is not in the same subnet as the IP address of the shelf.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

If you wish to store your data in a subdirectory within the default path, you may enter

backups/<subdirectory>/<filename>

if the subdirectory exists before the command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.

.................................................................................................................................................................................................

Click

OK

.

You will be asked to verify that you wish to backup to the directory that you entered above. Click

Yes

if you typed the path correctly.

.................................................................................................................................................................................................................................

2-126 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-8.1: Backup NE database via FTP

Result:

The Progress Indicator screen appears, indicating that the backup is in progress. When the backup completes, a

Remote Backup successful screen appears. Click

OK

. The backup file is now stored. If the default path and a subdirectory were used, the file may be found at:

C:/Program Files/Lucent Technologies/WaveStar

IT/backups/<subdirectory>/<filename>

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-127

Software installation and upgrades, and database backup procedures

Procedure 2-8.2: Provision automatic database backup schedule via FTP

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision an automatic backup schedule via FTP.

Required equipment

Refer to

“Required equipment” (p. 2-123)

in

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123) .

Step

1

2

3

Complete the following steps to provision an automatic backup schedule.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Configure Auto

Backup Interval

.

Important! The WaveStar

®

CIT is not intended to serve as an FTP server, although it may be used for this application if the WaveStar

®

CIT is guaranteed to be available (connected and running) at all scheduled backup times. Otherwise a

Navis

®

Optical Element Management System (Navis

®

Optical EMS) or another large capacity FTP server should be used.

.................................................................................................................................................................................................

From the Configure Auto Backup screen, select the

Files

tab at the top of the screen.

.................................................................................................................................................................................................

In the pull-down

Backup To/Via:

menu, select

FTP

.

.................................................................................................................................................................................................................................

2-128 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-8.2: Provision automatic database backup schedule via FTP

4

5

6

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and then proceed to

Step 6 . OR

Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

CIT is the FTP server, you can determine its IP address by entering

ipconfig

from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the backup to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar

®

CIT as your FTP server, the default user name/password for the WaveStar

®

CIT is

LUC01

/

LUC+01

, however your user ID/password may be different.)

.................................................................................................................................................................................................

If you entered connection information in

Step 4

(rather than selected an established profile), you should assign a new profile name to this information to allow Automatic

Backup to store the FTP login password. To do this:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Entries to the

FTP Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

.................................................................................................................................................................................................

In the

File Path:

field, enter

backups/<filename>

if you wish to save the backup file to the default location. (If the WaveStar

®

CIT is the FTP server, a maximum of 80 characters is suggested for this field.)

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and over-write the default entry. The

Browse

button is not available (greyed out) if the FTP server is not the local WaveStar

®

CIT or the IP address of the FTP server is not in the same subnet as the IP address of the shelf.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-129

Software installation and upgrades, and database backup procedures

Procedure 2-8.2: Provision automatic database backup schedule via FTP

7

8

9

10

If you wish to store your data in a subdirectory within the default path, you may enter

backups/<subdirectory>/<filename>

if the subdirectory exists before the command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.

.................................................................................................................................................................................................

From the

Type:

menu in the

Backup Type

panel, select

Forced

from the pull-down menu. NOTE: No other options are available at this time.

.................................................................................................................................................................................................

From the

Files:

menu in the

Number Of Files

panel, select a number from 1 to 9

(default is 2) from the pull-down menu, which indicates the number of backup files to be stored automatically before the files begin to overwrite.

Once established, the filename that you supplied in

Step 6

will initially be appended with “1” (FILENAME1). In subsequent backups, the “1” will increase by one until the number selected in this step is reached; then the files will begin overwriting beginning with FILENAME1.

.................................................................................................................................................................................................

Select the

Schedule

tab at the top of the screen.

.................................................................................................................................................................................................

From the

Days

menu in the

Update Interval

panel, select a number from 1 to 99

(default is 30), which indicates the number of days between automatic backups. The number may be selected by sliding the arrow over the scale until the desired number appears in the field.

Important! Setting this field to “0” cancels automatic backup.

.................................................................................................................................................................................................

11

If you...

wish to provision a start date and start time for the automatic backup, wish to only provision the start time for the automatic backup,

Then...

Perform the following to provision the start date:

1. Select

Specify Date

in the

Backup Start

Date/Time

panel,

2. Select the

Year:

and

Month:

from the pull-down menus

3. Select a day from the calendar.

Proceed to

Step 12

to provision the start time.

Proceed to

Step 12

to provision the start time.

.................................................................................................................................................................................................................................

2-130 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-8.2: Provision automatic database backup schedule via FTP

If you...

do not wish to provision the start date or start time for the automatic backup,

Then...

Proceed to

Step 13 . The first backup will begin

immediately upon completion of this procedure and the next backup will begin after the requested number of days.

12

13

.................................................................................................................................................................................................

To provision a start time for the automatic backup:

1. Select

Specify Time

in the

Backup Start Date/Time

panel,

2. You can provision the time format display for your WaveStar

®

CIT from the

Network View by selecting

View

→

Preferences

and clicking on the Display tab.

This screen allows you to choose your preference for time format, either a 12-hour clock or a 24-hour clock.

•

If your time format preference is a 12-hour clock, select

Hour:

(0-12),

Minutes:

(0-59), and

Seconds:

(0-59) from the pull-down menus. You must also specify am or pm by selecting one of the radio buttons.

•

If your time format preference is a 24-hour clock, select the

Hour:

(0-23),

Minutes:

(0-59), and

Seconds:

(0-59) from the pull-down menus.

It is recommended that only one backup occur at a time for the CIT. However, larger servers may be able to handle multiple backups at the same time. It is suggested that the backups for the networks be performed a few minutes apart.

.................................................................................................................................................................................................

Click

OK

.

A warning screen will appear, indicating that execution of provision may temporarily affect service. If this is acceptable, select

Yes

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-131

Software installation and upgrades, and database backup procedures

Procedure 2-8.3: Restore NE database via FTP

.................................................................................................................................................................................................................................

Overview

Use this procedure to restore the NE database using FTP.

Required equipment

Refer to

“Required equipment” (p. 2-123)

in

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123) .

Step

1

2

Complete the following steps to restore the NE database via FTP.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Restoring the network element database can be service-affecting.

If provisioning changes were made after the last backup files were created, examine

the Security Log and use the appropriate WaveStar

®

CIT commands to manually apply the recent provisioning changes to the just-restored database.

From the System View menu, select

Configuration

→

Software

→

Remote Restore

.

Important! If the TID has changed since the backup was performed, then the restore will not work. The software release of the backup database must be the same as the current software generic. In addition, if any service-related parameters

(for example, cross-connections) have been changed since the last backup file was created, those changes will be lost and service may be affected. These changes must be reentered.

.................................................................................................................................................................................................

In the pull-down

Restore From/Via:

menu, select

FTP

.

.................................................................................................................................................................................................................................

2-132 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-8.3: Restore NE database via FTP

3

4

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and then proceed to

Step 5 . OR

Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

CIT is the FTP server, you can determine its IP address by entering

ipconfig

from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the backup to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar

®

CIT as your FTP server, the default user name/password for the WaveStar

®

CIT is

LUC01

/

LUC+01

, however your user ID/password may be different.)

.................................................................................................................................................................................................

If you entered connection information in

Step 3

and wish to keep the information for future restores:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Entries to the

Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

5

.................................................................................................................................................................................................

In the

Source/Destination Directory Path

panel, enter the location where the database information is stored. Enter the path and filename exactly as it was entered in

Procedure 2-8.1: “Backup NE database via FTP” (p. 2-125)

or

Procedure 2-8.2:

“Provision automatic database backup schedule via FTP” (p. 2-128)

(For example:

backups/<subdirectory>/<filename>)

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and over-write the default entry. The

Browse

button is not available (greyed out) if the FTP server is not the local WaveStar

®

CIT or the IP address of the FTP server is not in the same subnet as the IP address of the shelf.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-133

Software installation and upgrades, and database backup procedures

Procedure 2-8.3: Restore NE database via FTP

6

7

8

.................................................................................................................................................................................................

Click

OK

.

You will be asked to verify that you wish to restore from the directory that you entered above. Click

Yes

if you typed the path correctly.

A second warning screen will appear that states that Execution of RESTORE will cause a System Reset. If this is acceptable, click

Yes

.

Result:

The Progress Indicator screen appears, indicating that the restore is in progress. When the restore is complete, a WaveStar

®

CIT warning screen appears, stating NE reset after successful restore, CIT is going to log out.

.................................................................................................................................................................................................

Click

OK

.

Result:

A second WaveStar

®

CIT warning screen appears, stating Communication

to network element is lost, system view will now be closed.

.................................................................................................................................................................................................

Click

OK

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

2-134 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-9: Backup and restore NE database via FTTD

.................................................................................................................................................................................................................................

Overview

Use this procedure to backup and restore the NE database or to set up an automatic backup schedule via FTAM-FTP gateway or file transfer translation device (FTTD) for a remote NE without direct TCP/IP connectivity.

Privilege level

You must login as a Privileged user to complete this procedure.

Required equipment

In addition to

“Required equipment” (p. 2-2)

listed in this chapter, CAT5 Ethernet cable with either a 10/100 hub or a cross-over cable for the

LAN

or

IAO LAN

port

(required for TCP/IP connectivity) is also required.

Before you begin

Prior to performing this procedure,

1. Refer to

“Before you begin” (p. 2-2)

and

“Required equipment” (p. 2-2)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

Metropolis

®

DMX may also act as an FTAM-FTP gateway or file transfer translation device (FTTD). The FTTD allows Metropolis

®

DMX to function as a gateway network element (GNE) that facilitates file downloads between FTP servers and remote network elements (RNEs) connected to the Metropolis

®

DMX.

This procedure uses FTP (file transfer protocol) and FTAM (file transfer and access management) to backup and restore all Metropolis

®

DMX provisionable data on a shelf.

The WaveStar

®

CIT is not a fully implemented FTP server, but it can handle backup and restore capabilities. For automatic backups, a Navis

®

Optical Element Management

System (Navis

®

Optical EMS) or another large capacity FTP server should be used.

The WaveStar

®

CIT is not recommended for automatic backups.

The backup feature can be forced or scheduled to complete automatically at specified intervals.

If you log in via TCP/IP, your PC must be part of the GNE’s TCP/IP Gateway Host

List (refer to

Procedure 7-16: “Provision/enable/disable the NE as a TL1 TCP/IP GNE”

(p. 7-49) ).

Important! If the FTP server associated with the WaveStar

®

CIT fails to start, it could mean that another program using an FTP server is already running.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-135

Software installation and upgrades, and database backup procedures

Procedure 2-9: Backup and restore NE database via

FTTD

Depending on what operating system you are using, you must go to the device file and disable the FTP server. Refer to

Procedure 14-18: “Disable an FTP server on your PC” (p. 14-103)

for instructions for each allowed operating system.

Step

1

2

3

4

Complete the following steps to backup and restore the system.

.................................................................................................................................................................................................

Connect the PC and establish a WaveStar

®

CIT session to the gateway Network

Element.

Important! You must have direct TCP/IP connectivity to your NE and the NE must have a defined IP address.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Set NE

and enable

File

Transfer Protocol (FTP)

and FTAM-FTP (FTTD) Gateway Control.

.................................................................................................................................................................................................

Click

OK

.

.................................................................................................................................................................................................

Is your remote NE in the same OSI network as your gateway NE?

If

Yes

No

Then

Proceed to

Step 6 .

Continue with

Step 5 .

5

6

.................................................................................................................................................................................................

From the System View, select

Administration

→

Data Communications

.

Select the

Network Layer

tab and record the NSAP from the

Network Service

Access Point

panel (the NSAP is a 40-digit hex number). This NSAP is required later in this procedure.

.................................................................................................................................................................................................

Establish a WaveStar

®

CIT session to the remote Network Element.

.................................................................................................................................................................................................................................

2-136 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-9: Backup and restore NE database via

FTTD

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

7

If...

performing an immediate system backup, scheduling or discontinuing an automatic system backup, performing a system restore,

Then...

Proceed to

Procedure 2-9.1: “Backup NE database via FTTD” (p. 2-138) .

Proceed to

Procedure 2-9.2: “Provision automatic database backup schedule via FTTD” (p. 2-141) .

Proceed to

Procedure 2-9.3: “Restore NE database via FTTD” (p. 2-146) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-137

Software installation and upgrades, and database backup procedures

Procedure 2-9.1: Backup NE database via FTTD

.................................................................................................................................................................................................................................

Overview

Use this procedure to backup the NE database via FTAM-FTP gateway or file transfer translation device (FTTD) for a remote NE without direct TCP/IP connectivity.

Required equipment

Refer to

“Required equipment” (p. 2-135)

in

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135) .

Step

1

2

3

Complete the following steps to backup the NE database via FTTD.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Remote Backup

.

.................................................................................................................................................................................................

In the pull-down

Backup To/Via:

menu, select

FTTD

and verify that the

FTTD

tab is selected.

.................................................................................................................................................................................................

Define the FTAM-FTP Gateway in one of the following ways:

•

If the TID of the FTAM-FTP Gateway has been previously defined, select it from the

TID

pull-down menu.

OR

•

If the gateway NE and the remote NE are in the same OSI area:

1. Enter the TID of the FTAM-FTP Gateway in the

TID

field and click

Get NSAP

.

(If any fields on this screen are populated, click

Clear

before you enter the

TID.)

2. Click

Add

and then

Save

. The TID is added to the pull-down menu for this

CIT and you should never need to re-enter the NSAP address for this gateway

NE’s TID.

OR

.................................................................................................................................................................................................................................

2-138 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-9.1: Backup NE database via FTTD

4

5

6

•

If the gateway NE and the remote NE are not in the same OSI area:

1. In the

FTTD

panel, select

_template_

from the

TID:

pull-down menu. This will pre-populate most of the fields on this form (required value for

Psel

is 02,

Ssel

is 5353, and

Tsel

is 5454).

2. Click

Modify

.

3. Replace

_template_

with the TID of the FTAM-FTP gateway NE.

4. Edit the NSAP Address fields as required. Refer to

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135) ,

Step 5 .

5. Verify that the Selector (

Sel:

) field is “1d”.

6. Click

Add

and then

Save

. The TID has been added to the pull-down menu for this CIT and you should never need to re-enter the NSAP address for this gateway NE’s TID.

.................................................................................................................................................................................................

Select the

FTP

tab.

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and then proceed to

Step 7 . OR

Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

CIT is the FTP server, you can determine its IP address by entering

ipconfig

from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the backup to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar

®

CIT as your FTP server, the default user name/password for the WaveStar

®

CIT is

LUC01

/

LUC+01

, however your user ID/password may be different.)

.................................................................................................................................................................................................

If you entered connection information in

Step 5

and wish to keep the information for future backups:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Important! Entries to the

FTP Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

.................................................................................................................................................................................................

7

In the

Source/Destination Directory Path

field, enter

backups/<filename>

. (If the

WaveStar

®

CIT is the FTP server, a maximum of 80 characters is suggested for this field.)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-139

Software installation and upgrades, and database backup procedures

Procedure 2-9.1: Backup NE database via FTTD

8

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and over-write the default entry. The

Browse

button is not available (greyed out) if the FTP server is not the local WaveStar

®

CIT or the IP address of the FTP server is not in the same subnet as the IP address of the shelf.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

If you wish to store your data in a subdirectory, you may enter

backups/<subdirectory>/<filename>

if the subdirectory exists before the command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.

.................................................................................................................................................................................................

Click

OK

.

You will be asked to verify that you wish to backup to the directory that you entered above. Click

Yes

if you typed the path correctly.

Result:

The Progress Indicator screen appears, indicating that the backup is in progress. When the backup completes, a

Remote Backup successful screen appears. Click

OK

. The backup file is now stored. If the default path and a subdirectory were used, the file may be found at:

C:/Program Files/Lucent Technologies/WaveStar

IT/backups/<subdirectory>/<filename>

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

2-140 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-9.2: Provision automatic database backup schedule via FTTD

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision an automatic backup schedule via FTAM-FTP gateway or file transfer translation device (FTTD) for a remote NE without direct TCP/IP connectivity.

Required equipment

Refer to

“Required equipment” (p. 2-135)

in

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135) .

Step

1

2

3

Complete the following steps to provision an automatic backup schedule via FTTD.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Configure Auto

Backup Interval

.

Important! The WaveStar

®

CIT is not intended to serve as an FTP server, although it may be used for this application if the WaveStar

®

CIT is guaranteed to be available (connected and running) at all scheduled backup times. Otherwise a

Navis

®

Optical Element Management System (Navis

®

Optical EMS) or another large capacity FTP server should be used.

.................................................................................................................................................................................................

From the

Configure Auto Backup

screen, and select the

Files

tab at the top of the screen.

.................................................................................................................................................................................................

In the pull-down

Backup To/Via:

menu, select

FTTD

and select the

FTTD

tab.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-141

Software installation and upgrades, and database backup procedures

Procedure 2-9.2: Provision automatic database backup schedule via FTTD

4

5

6

.................................................................................................................................................................................................

Define the FTAM-FTP Gateway in

one

of the following ways:

•

If the TID of the FTAM-FTP Gateway has been previously defined, select it from the

TID

pull-down menu.

OR

•

If the gateway NE and the remote NE are in the same OSI area:

1. Enter the TID of the FTAM-FTP Gateway in the

TID

field and click

Get NSAP

.

(If any fields on this screen are populated, click

Clear

before you enter the

TID.)

2. Click

Add

and then

Save

. The TID is added to the pull-down menu for this

CIT and you should never need to re-enter the NSAP address for this gateway

NE’s TID.

OR

•

If the gateway NE and the remote NE are not in the same OSI area:

1. In the

FTTD

panel, select

_template_

from the

TID:

pull-down menu. This will pre-populate most of the fields on this form (required value for

Psel

is 02,

Ssel

is 5353, and

Tsel

is 5454).

2. Click

Modify

.

3. Replace

_template_

with the TID of the FTAM-FTP gateway NE.

4. Edit the NSAP Address fields as required. Refer to

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135) ,

Step 5 .

5. Verify that the Selector (

Sel:

) field is “1d”.

6. Click

Add

and then

Save

. The TID has been added to the pull-down menu for this CIT and you should never need to re-enter the NSAP address for this gateway NE’s TID.

.................................................................................................................................................................................................

Select the

FTP

tab.

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and then proceed to

Step 8 . OR

Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

CIT is the FTP server, you can determine its IP address by entering

ipconfig

from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the backup to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar the WaveStar

®

®

CIT as your FTP server, the default user name/password for

CIT is

LUC01

/

LUC+01

, however, your user ID/password may be different.)

.................................................................................................................................................................................................................................

2-142 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-9.2: Provision automatic database backup schedule via FTTD

7

8

.................................................................................................................................................................................................

If you entered connection information in

Step 6

(rather than selected an established profile), you should assign a new profile name to this information to allow Automatic

Backup to store the FTP login and password. To do this:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Entries to the

FTP Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

.................................................................................................................................................................................................

In the

File Path:

field, enter

backups/<filename>

. (If the WaveStar

®

CIT is the FTP server, a maximum of 80 characters is suggested for this field.)

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and over-write the default entry. The

Browse

button is not available (greyed out) if the FTP server is not the local WaveStar

®

CIT or the IP address of the FTP server is not in the same subnet as the IP address of the shelf.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

If you wish to store your data in a subdirectory, you may enter

backups/<subdirectory>/<filename>

if the subdirectory exists before the command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.

9

.................................................................................................................................................................................................

From the

Type:

menu in the

Backup Type

panel, select

Forced

from the pull-down menu. NOTE: No other options are available at this time.

10

.................................................................................................................................................................................................

From the

Files:

menu in the

Number Of Files

panel, select a number from 1 to 9

(default is 2) from the pull-down menu, which indicates the number of backup files to be stored automatically before the files begin to overwrite.

Once established, the filename that you supplied in

Step 8

will initially be appended with “1” (FILENAME1). In subsequent backups, the “1” will increase by one until the

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-143

Software installation and upgrades, and database backup procedures

Procedure 2-9.2: Provision automatic database backup schedule via FTTD

11

12

number selected in this step is reached; then the files will begin overwriting beginning with FILENAME1.

.................................................................................................................................................................................................

Select the

Schedule

tab at the top of the screen.

.................................................................................................................................................................................................

From the

Days

menu in the

Update Interval

panel, select a number from 1 to 99

(default is 30), which indicates the number of days between automatic backups. The number may be selected by sliding the arrow over the scale until the desired number appears in the field.

Important! Setting this field to “0” cancels automatic backup.

.................................................................................................................................................................................................

13

If you...

wish to provision a start date and start time for the automatic backup,

Then...

Perform the following to provision the start date:

1. Select

Specify Date

in the

Backup Start Date/Time

panel,

2. Select the

Year:

and

Month:

from the pull-down menus

3. Select a day from the calendar.

Proceed to

Step 14

to provision the start time.

Proceed to

Step 14

to provision the start time.

wish to only provision the start time for the automatic backup, do not wish to provision the start date or start time for the automatic backup,

Proceed to

Step 15 . The first backup will begin

immediately upon completion of this procedure and the next backup will begin after the requested number of days.

.................................................................................................................................................................................................................................

2-144 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-9.2: Provision automatic database backup schedule via FTTD

14

15

.................................................................................................................................................................................................

To provision a start time for the automatic backup:

1. Select

Specify Time

in the

Backup Start Date/Time

panel,

2. You can provision the time format display for your WaveStar

®

CIT from the

Network View by selecting

View

→

Preferences

and clicking on the Display tab.

This screen allows you to choose your preference for time format, either a 12-hour clock or a 24-hour clock.

•

If your time format preference is a 12-hour clock, select

Hour:

(0-12),

Minutes:

(0-59), and

Seconds:

(0-59) from the pull-down menus. You must also specify am or pm by selecting one of the radio buttons.

•

If your time format preference is a 24-hour clock, select the

Hour:

(0-23),

Minutes:

(0-59), and

Seconds:

(0-59) from the pull-down menus.

It is recommended that only one backup occur at a time for the CIT. However, larger servers may be able to handle multiple backups at the same time. It is suggested that the backups for the networks be performed a few minutes apart.

.................................................................................................................................................................................................

Click

OK

.

A warning screen will appear, indicating that execution of provision may temporarily affect service. If this is acceptable, select

Yes

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-145

Software installation and upgrades, and database backup procedures

Procedure 2-9.3: Restore NE database via FTTD

.................................................................................................................................................................................................................................

Overview

Use this procedure to restore the NE database via FTAM-FTP gateway or file transfer translation device (FTTD) for a remote NE without direct TCP/IP connectivity.

Required equipment

Refer to

“Required equipment” (p. 2-135)

in

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135) .

Step

1

2

Complete the following steps to restore the NE database via FTAM-FTP gateway or file transfer translation device (FTTD).

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Restoring the network element database can be service-affecting.

If provisioning changes were made after the last backup files were created, examine

the Security Log and use the appropriate WaveStar

®

CIT commands to manually apply the recent provisioning changes to the just-restored database.

From the System View menu, select

Configuration

→

Software

→

Remote Restore

.

Important! If the TID has changed since the backup was performed, then the restore will not work. The software release of the backup database must be the same as the current software generic. In addition, if any service-related parameters

(for example, cross-connections) have been changed since the last backup file was created, those changes will be lost and service may be affected. These changes must be reentered.

.................................................................................................................................................................................................

In the pull-down

Restore From/Via:

menu, select

FTTD

and select the

FTTD

tab.

.................................................................................................................................................................................................................................

2-146 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-9.3: Restore NE database via FTTD

3

4

5

.................................................................................................................................................................................................

Define the FTAM-FTP Gateway in one of the following ways:

•

If the TID of the FTAM-FTP Gateway has been previously defined, select it from the

TID

pull-down menu.

OR

•

If the gateway NE and the remote NE are in the same OSI area:

1. Enter the TID of the FTAM-FTP Gateway in the

TID

field and click

Get NSAP

.

(If any fields on this screen are populated, click

Clear

before you enter the

TID.)

2. Click

Add

and then

Save

. The TID is added to the pull-down menu for this

CIT and you should never need to re-enter the NSAP address for this gateway

NE’s TID.

OR

•

If the gateway NE and the remote NE are not in the same OSI area:

1. In the

FTTD

panel, select

_template_

from the

TID:

pull-down menu. This will pre-populate most of the fields on this form (required value for

Psel

is 02,

Ssel

is 5353, and

Tsel

is 5454).

2. Click

Modify

.

3. Replace

_template_

with the TID of the FTAM-FTP gateway NE.

4. Edit the NSAP Address fields as required. Refer to

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135) ,

Step 5 .

5. Verify that the Selector (

Sel:

) field is “1d”.

6. Click

Add

and then

Save

. The TID has been added to the pull-down menu for this CIT and you should never need to re-enter the NSAP address for this gateway NE’s TID.

.................................................................................................................................................................................................

Select the

FTP

tab.

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and then proceed to

Step 7 . OR

Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

CIT is the FTP server, you can determine its IP address by entering

ipconfig

from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the backup to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar the WaveStar

®

®

CIT as your FTP server, the default user name/password for

CIT is

LUC01

/

LUC+01

, however your user ID/password may be different.)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-147

Software installation and upgrades, and database backup procedures

Procedure 2-9.3: Restore NE database via FTTD

6

7

8

.................................................................................................................................................................................................

If you entered connection information in

Step 5

and wish to keep the information for future restores:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Important! Entries to the

FTP Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

.................................................................................................................................................................................................

In the

Source/Destination Directory Path

panel, enter the location where the database information is stored. Enter the path and filename exactly as it was entered in

Procedure 2-9.1: “Backup NE database via FTTD” (p. 2-138)

or

Procedure 2-9.2:

“Provision automatic database backup schedule via FTTD” (p. 2-141) . For example:

backups/<subdirectory>/<filename>

.

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and over-write the default entry. The

Browse

button is not available (greyed out) if the FTP server is not the local WaveStar

®

CIT or the IP address of the FTP server is not in the same subnet as the IP address of the shelf.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

.................................................................................................................................................................................................

Click

OK

.

You will be asked to verify that you wish to restore from the directory that you entered above. Click

Yes

if you typed the path correctly.

A second warning screen will appear that states that Execution of RESTORE will cause a System Reset. If this is acceptable, click

Yes

.

.................................................................................................................................................................................................................................

2-148 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-9.3: Restore NE database via FTTD

9

10

Result:

The Progress Indicator screen appears, indicating that the restore is in progress. When the restore is complete, a WaveStar

®

CIT warning screen appears, stating NE reset after successful restore, CIT is going to log out.

.................................................................................................................................................................................................

Click

OK

.

Result:

A second WaveStar

®

CIT warning screen appears, stating Communication

to network element is lost, system view will now be closed.

.................................................................................................................................................................................................

Click

OK

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-149

Software installation and upgrades, and database backup procedures

Procedure 2-10: Backup and restore NE database via FTAM

.................................................................................................................................................................................................................................

Overview

Use this procedure to backup and restore the local NE database via the File Transfer and Access Management (FTAM) protocol. Scheduled automatic backups are not supported using FTAM.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

In addition to

“Required equipment” (p. 2-2)

listed in this chapter, CAT5 Ethernet cable with either a 10/100 hub or a cross-over cable for the

LAN

or

IAO LAN

port

(required for TCP/IP connectivity) is also required.

Before you begin

Prior to performing this procedure,

1. Refer to

“Before you begin” (p. 2-2)

and

“Required equipment” (p. 2-2)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

Step

Complete the following steps to backup and restore the system.

1

.................................................................................................................................................................................................

Connect the PC and establish a WaveStar

®

that is to be backed up or restored.

CIT session to the local Network Element

Important! You must login via OSI.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

2 If...

performing an immediate system backup, performing a system restore,

Then...

Proceed to

Procedure 2-10.1: “Backup NE database via FTAM” (p. 2-152) .

Proceed to

Procedure 2-10.2: “Restore NE database via FTAM” (p. 2-154) .

.................................................................................................................................................................................................................................

2-150 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-10: Backup and restore NE database via

FTAM

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-151

Software installation and upgrades, and database backup procedures

Procedure 2-10.1: Backup NE database via FTAM

.................................................................................................................................................................................................................................

Overview

Use this procedure to backup the local NE database or a remote NE database (with

DCC connectivity) via the File Transfer and Access Management (FTAM) protocol to the WaveStar

®

CIT.

Required equipment

Refer to

“Required equipment” (p. 2-150)

in

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150) .

Step

1

2

3

Complete the following steps to backup an NE database using FTAM.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Remote Backup

.

.................................................................................................................................................................................................

In the pull-down

Backup To/Via:

menu, select

FTAM

.

.................................................................................................................................................................................................

In the

Source/Destination Directory Path

field, enter

backups/<filename>

.

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and over-write the default entry.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

If you wish to store your data in a subdirectory, you may enter

backups/<subdirectory>/<filename>

if the subdirectory exists before the

.................................................................................................................................................................................................................................

2-152 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-10.1: Backup NE database via FTAM

4

command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.

.................................................................................................................................................................................................

Click

OK

.

You will be asked to verify that you wish to backup to the directory that you entered above. Click

Yes

if you typed the path correctly.

Result:

The Progress Indicator screen appears, indicating that the backup is in progress. When the backup completes, a

Remote Backup successful screen appears. Click

OK

. The backup file is now stored. If the default path and a subdirectory were used, the file may be found at:

C:/Program Files/Lucent Technologies/WaveStar

IT/backups/<subdirectory>/<filename>

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-153

Software installation and upgrades, and database backup procedures

Procedure 2-10.2: Restore NE database via FTAM

.................................................................................................................................................................................................................................

Overview

Use this procedure to restore the local NE database or a remote NE database (with OSI or DCC connectivity) via the File Transfer and Access Management (FTAM) protocol from the WaveStar

®

CIT.

Required equipment

Refer to

“Required equipment” (p. 2-150)

in

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150) .

Step

1

2

Complete the following steps to restore the local NE database.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Restoring the network element database can be service-affecting.

If provisioning changes were made after the last backup files were created, examine

the Security Log and use the appropriate WaveStar

®

CIT commands to manually apply the recent provisioning changes to the just-restored database.

From the System View menu, select

Configuration

→

Software

→

Remote Restore

.

Important! If the TID has changed since the backup was performed, then the restore will not work. The software release of the backup database must be the same as the current software generic. In addition, if any service-related parameters

(for example, cross-connections) have been changed since the last backup file was created, those changes will be lost and service may be affected. These changes must be reentered.

.................................................................................................................................................................................................

In the pull-down

Restore From/Via:

menu, select

FTAM

.

.................................................................................................................................................................................................................................

2-154 365-372-301 R6.0

Issue 15, January 2006

Software installation and upgrades, and database backup procedures

Procedure 2-10.2: Restore NE database via FTAM

3

4

5

6

.................................................................................................................................................................................................

In the

Source/Destination Directory Path

panel, enter the location where the database information is stored. Enter the path and filename exactly as it was entered in

Procedure 2-10.1: “Backup NE database via FTAM” (p. 2-152) . For example:

backups/<subdirectory>/<filename>

.

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and select the required file.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

.................................................................................................................................................................................................

Click

OK

.

You will be asked to verify that you wish to restore from the directory that you entered above. Click

Yes

if you typed the path correctly.

A second warning screen will appear that states that Execution of RESTORE will cause a System Reset. If this is acceptable, click

Yes

.

Result:

The Progress Indicator screen appears, indicating that the restore is in progress. When the restore is complete, a WaveStar

®

CIT warning screen appears, stating NE reset after successful restore, CIT is going to log out.

.................................................................................................................................................................................................

Click

OK

.

Result:

A second WaveStar

®

CIT warning screen appears, stating Communication

to network element is lost, system view will now be closed.

.................................................................................................................................................................................................

Click

OK

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

2-155

3

3

Overview

.................................................................................................................................................................................................................................

Purpose

Use the following procedures to test an out-of-service Metropolis

®

DMX Access

Multiplexer or network after another organization has installed and equipped it.

If installation is not complete, notify the installation personnel or refer to Metropolis

®

DMX Access Multiplexer Installation Manual, 365-372-304.

If circuit pack installation is not complete, notify the installation personnel or refer to

Chapter 4, “Install and provision circuit packs/OLIUs procedures” .

The procedures test a stand-alone Metropolis

®

DMX system after all circuit packs have been installed and the shelf is looped back or after a system has been established end-to-end. They are not intended to be used to equip and turn up a shelf or establish a network.

Contents

Before you begin

Procedure 3-1: Accept Metropolis

®

DMX shelf (looped-back)

Procedure 3-2: Accept Metropolis

®

DMX network

3-2

3-3

3-9

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

3-1

Acceptance procedures

Before you begin

.................................................................................................................................................................................................................................

Before you begin

Prior to performing all procedures in this chapter,

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. If not previously completed, install generic and WaveStar

®

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC.

CIT software on the PC”

(p. 14-4) .

3. Connect PC and establish a WaveStar

®

CIT session. Refer to

Procedure 14-2:

“Connect Personal Computer (PC) and establish WaveStar

®

CIT session” (p. 14-24)

.

Required equipment

The procedures in this chapter require the following equipment:

•

Personal Computer (PC) with WaveStar

®

CIT software installed

•

Wrist strap

Important! If additional equipment is required to perform a specific procedure, that additional equipment is listed in that procedure.

.................................................................................................................................................................................................................................

3-2 365-372-301 R6.0

Issue 15, January 2006

Acceptance procedures

Procedure 3-1: Accept Metropolis

®

DMX shelf (looped-back)

.................................................................................................................................................................................................................................

Overview

Use this procedure to test and accept an out-of-service Metropolis

®

DMX Access

Multiplexer shelf in a stand-alone state. This procedure is used only if the Metropolis

®

DMX Access Multiplexer shelf was installed by someone else.

Important! It is assumed that the Metropolis

®

equipped, and free of alarms.

DMX is installed, powered,

If installation is not complete, notify the installation personnel or refer to

Metropolis

®

DMX Access Multiplexer Installation Manual, 365-372-304.

If circuit pack installation is not complete, notify the installation personnel or refer to

Chapter 4, “Install and provision circuit packs/OLIUs procedures” .

If the shelf fails to respond in the indicated manner, notify the installation organization that installed the Metropolis

®

DMX or refer to Metropolis

®

DMX

Access Multiplexer Alarm Messages and Trouble Clearing Guide, 365-372-302.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 3-2) , the following

equipment is also required:

•

Line buildouts (LBOs)

•

Fiber jumpers (LC-Type Connectors)

•

DSX-1 or DSX-3 patch cords.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 3-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure which state the quantity and type of circuit packs that were installed.

4. If system and circuit pack port parameters were provisioned, ensure that you have a full set of work instructions detailing the provisioned parameter values.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

3-3

Acceptance procedures Procedure 3-1: Accept Metropolis

®

DMX shelf

(looped-back)

Step

1

2

3

Complete the following steps to accept a Metropolis

®

DMX.

.................................................................................................................................................................................................

Inspect the Metropolis

®

DMX shelf for obvious damage.

.................................................................................................................................................................................................

From the System View select

Reports

→

Equipment Lists

→

Pack

. Highlight Shelf and click

Select

to obtain the Circuit Pack List for the shelf. Verify that the correct number and type of circuit packs have been installed, as required.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Improperly-seated circuit packs or missing apparatus blanks may cause service hits on in-service systems.

All slots in Metropolis

®

DMX must be equipped with fully-seated circuit packs or apparatus blanks to prevent service hits on in-service systems.

4

5

6

Verify 177D Apparatus Blanks or LNW98 circuit packs have been installed in any unused Function/Growth slots on the shelf.

Verify 177E Apparatus Blanks or LNW97 circuit packs have been installed in any unused Main 2 slot.

Important! All slots in the Metropolis

®

circuit packs or apparatus blanks.

DMX must be equipped with fully-seated

.................................................................................................................................................................................................

From the System View menu select

View

→

Software Generic

and verify that the proper version of software is installed.

Reference:

Procedure 14-14: “Retrieve software generic release and database information” (p. 14-90)

.................................................................................................................................................................................................

Test the SYSCTL circuit pack. From the System View menu, select

Fault

→

Test

→

System Controller

. Verify the SYSCTL circuit pack passes the test.

.................................................................................................................................................................................................

If LNW121B-159B or LNW221-259 OLIU circuit packs are installed in the MAIN M1 and M2 slots, ensure that the proper box has been checked on the faceplate Channel

Select Option Label. To further verify correct settings, the circuit pack must be removed, option jumpers checked, and the circuit pack reinserted.

.................................................................................................................................................................................................................................

3-4 365-372-301 R6.0

Issue 15, January 2006

Acceptance procedures Procedure 3-1: Accept Metropolis

®

DMX shelf

(looped-back)

7

8

9

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

If LNW26B, LNW28, or LNW77 OLIU circuit packs are installed in the MAIN M1 and M2 slots, verify circuit pack mode (Normal or Enhanced) is set to

Enhanced

.

From the System View menu, select

View

→

Equipment

. Highlight the circuit pack, then click

Select

. The Normal mode is not supported.F

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

If OLIUs are installed in the Main slots, install optical loopbacks with attenuators between the

IN

and

OUT

connectors on the Main 1 and Main 2 OLIU circuit packs, if required and not already performed.

Important! If OSI over DCC is enabled for the Main ports, an inconsistent DCC values alarm is reported when the Main ports are looped back.

If desired, clear the inconsistent DCC values alarm by disabling OSI over DCC for the Main ports. From the System View menu, select

Configuration

→

DCC

Terminations

and disable

OSI Over DCC

for the required DCC ports.

Reference:

Procedure 14-6: “Connect OLIU optical loopbacks” (p. 14-56)

.................................................................................................................................................................................................

Are any low-speed OLIU circuit packs installed in any Function Unit or Growth slots?

If...

Yes,

No,

Then...

Continue with

Step 10 .

Proceed to

Step 13 .

10

11

.................................................................................................................................................................................................

If LNW421-459 OLIU circuit packs are installed in any Function Unit or Growth slots, ensure that the proper box has been checked on the faceplate Channel Select Option

Label. To further verify correct settings, the circuit pack must be removed, option jumpers checked, and the circuit pack reinserted.

Reference:

Procedure 4-3: “Install OLIU circuit packs in Function slots” (p. 4-14)

.................................................................................................................................................................................................

If LNW37 4OC-3, LNW45 8OC-3, and/or LNW49 4OC-12 circuit packs are installed in any Function Unit or Growth slots, ensure that any required pluggable transmission modules have been installed. Verify that all unused sockets are equipped with dust covers.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

3-5

Acceptance procedures Procedure 3-1: Accept Metropolis

®

DMX shelf

(looped-back)

12

13

14

15

16

Reference:

Procedure 4-3: “Install OLIU circuit packs in Function slots” (p. 4-14)

.................................................................................................................................................................................................

Test each low-speed OLIU port for proper operation, if required.

1. Install optical fiber loopback on low-speed port being tested. Verify proper responses.

2. Remove optical loopback. Verify that the OLIU

FAULT

LED or port LED associated with the pluggable transmission module starts flashing. The

MN

(default level) and

NE

LEDs on the SYSCTL light.

3. From the System View menu, select

Configuration

→

Update System

→

Update

All

. Verify that the OLIU

FAULT

LED or port LED associated with the pluggable transmission module stops flashing and all alarms clear.

Repeat this step for all low-speed OLIU ports being tested, if required.

Reference:

Procedure 14-6: “Connect OLIU optical loopbacks” (p. 14-56)

.................................................................................................................................................................................................

From your work order, verify option settings have been set correctly, if required, and not already performed.

Reference:

•

Chapter 6, “System configuration procedures”

•

Chapter 7, “System administration procedures”

•

Chapter 8, “System performance monitoring procedures”

•

Appendix A, “Provisionable parameters”

.................................................................................................................................................................................................

Perform the LED test to verify that all LEDs are operating properly.

Reference:

Procedure 14-13: “Perform LED test” (p. 14-88)

.................................................................................................................................................................................................

Test IAO LAN ports. From the System View menu, select

Fault

→

Test

→

IAO LAN

.

Verify the LAN ports pass the test.

.................................................................................................................................................................................................

Important! This procedure assumes that the Metropolis

®

DMX shelf has been connected to the DSX cross-connect panel or equivalent connection point, as required.

Perform stand-alone transmission tests in the terminal and/or facility directions, as required, to verify proper circuit pack operation and cabling. Refer any failures to the organization that installed the Metropolis

®

DMX.

.................................................................................................................................................................................................................................

3-6 365-372-301 R6.0

Issue 15, January 2006

Acceptance procedures Procedure 3-1: Accept Metropolis

®

DMX shelf

(looped-back)

17

18

19

Reference:

•

Procedure 14-9: “Perform DS1/E1 transmission test” (p. 14-67)

•

Procedure 14-10: “Perform DS3 transmission test” (p. 14-74)

•

Procedure 14-11: “Perform EC-1 transmission test” (p. 14-80)

.................................................................................................................................................................................................

Important! This step is optional. If the provisionable parameters for the system and installed circuit pack ports have already been provisioned for your application, do not perform this step. This step resets all system provisionable parameters and cross-connections to factory default values. If the system and circuit pack port provisionable parameters have not been provisioned for your application, perform this step to clear the system of any unnecessary settings that may have been made during testing.

If required, from the System View menu, select

Fault

→

Reset

→

Initialize System

to reset all system provisionable parameters to default values.

Result:

You will be logged off the system during the controller reset and provisionable parameters will be set to factory default.

A flashing

b

in the

IND

display on the SYSCTL indicates that a boot is in progress.

During the boot, the

b

may extinguish for up to 20 seconds and then resume flashing.

If OLIUs are installed and looped, an inconsistent DCC values alarm is reported after the command is executed and communication is reestablished with the network element.

If desired, clear the inconsistent DCC values alarm by disabling OSI over DCC for the ports. From the System View menu, select

Configuration

→

DCC

Terminations

and disable

OSI Over DCC

for the required DCC ports.

The system may also report the holdover mode active condition since the Timing

Mode reverts to External. If desired, use the

Configuration

→

Timing/Sync

command to provision the

Timing Mode

to Free Running.

.................................................................................................................................................................................................

If required, remove optical loopbacks and reconnect the original OC-n lines.

.................................................................................................................................................................................................

The Metropolis

®

DMX shelf has passed the acceptance tests. After each shelf in the network has been tested, the Metropolis

®

DMX network is ready for the acceptance testing.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

3-7

Acceptance procedures Procedure 3-1: Accept Metropolis

®

DMX shelf

(looped-back)

Reference:

Procedure 3-2: “Accept Metropolis

®

DMX network” (p. 3-9)

If required, refer to

Chapter 9, “Network configuration procedures”

to place the

Metropolis

®

DMX shelf in a network.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

3-8 365-372-301 R6.0

Issue 15, January 2006

Acceptance procedures

Procedure 3-2: Accept Metropolis

®

DMX network

.................................................................................................................................................................................................................................

Overview

Use this procedure to test an out-of-service Metropolis

®

DMX Access Multiplexer in a network. This procedure is used only if the Metropolis

®

DMX Access Multiplexer network was installed by someone else.

Important! It is assumed that the Metropolis

®

DMX is installed in a network and each shelf has previously been tested in a stand-alone looped-back configuration. If each shelf has not been tested in a stand-alone looped-back configuration, refer to

Procedure 3-1: “Accept Metropolis

®

DMX shelf (looped-back)” (p. 3-3) .

Important! If the Metropolis

®

DMX fails to respond in the indicated manner, notify the installation organization that installed the Metropolis

®

DMX or refer to

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble Clearing

Guide, 365-372-302.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 3-2) , an optical power

meter is also required.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 3-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

3. Obtain the engineering data for the network.

4. Verify that the engineering data shows the node target identifiers (TIDs) and fiber connections.

Step

1

Complete the following steps to test an out-of-service Metropolis

®

DMX network.

.................................................................................................................................................................................................

At each node in the network, select

Administration

→

View NE Administration

from the System View menu and verify that the network element parameters agree with the engineering data.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

3-9

Acceptance procedures Procedure 3-2: Accept Metropolis

®

DMX network

2

3

4

5

6

7

.................................................................................................................................................................................................

Important! At least one node in the network should be set for DS1 External or

Free Running. No more than one node in the network should be Free Running.

In order to enable sync autoreconfiguration, Sbyte (sync messaging) must also be enabled.

At each node in the network, select

View

→

Timing/Sync

from the System View menu and verify that the system timing information agrees with the engineering data.

Reference:

(p. 6-16)

Procedure 6-5: “Network Element synchronization provisioning”

.................................................................................................................................................................................................

Determine the optical loss of each optical span from office records or by making the required measurements. Verify that the correct LBOs have been installed and the fiber are connected.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

At each node in the network, select

View

→

DCC Terminations

from the System View menu and verify that the DCC Channel Status parameters agree with the engineering data.

.................................................................................................................................................................................................

At each node in the network, select

Administration

→

OSI Neighbor Map

from the

System View menu. Verify that the nodes are properly connected with adjacent nodes, as required.

.................................................................................................................................................................................................

Perform the end-to-end optical line test on all optical spans. Report any failures to the organization that installed the Metropolis

®

DMX shelf.

Reference:

•

Procedure 14-7: “Perform end-to-end optical line test on Main OLIUs”

(p. 14-61)

•

Procedure 14-8: “Perform end-to-end optical line test on Function OLIUs”

(p. 14-64)

.................................................................................................................................................................................................

Perform end-to-end transmission tests, if required.

.................................................................................................................................................................................................................................

3-10 365-372-301 R6.0

Issue 15, January 2006

Acceptance procedures Procedure 3-2: Accept Metropolis

®

DMX network

8

9

10

Reference:

•

Procedure 14-9: “Perform DS1/E1 transmission test” (p. 14-67)

•

Procedure 14-10: “Perform DS3 transmission test” (p. 14-74)

•

Procedure 14-11: “Perform EC-1 transmission test” (p. 14-80)

.................................................................................................................................................................................................

Test protection switching function, if required.

Reference:

(p. 14-86)

Procedure 14-12: “Test function unit equipment protection switching”

.................................................................................................................................................................................................

Activate remaining optional features as required.

Reference:

•

Chapter 6, “System configuration procedures”

•

Chapter 7, “System administration procedures”

•

Chapter 8, “System performance monitoring procedures”

•

Appendix A, “Provisionable parameters”

.................................................................................................................................................................................................

The network is ready for service to be established.

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

3-11

4

4

packs/OLIUs procedures

Overview

.................................................................................................................................................................................................................................

Purpose

This chapter includes procedures necessary to install and provision circuit packs and

OLIUs in Metropolis

®

DMX.

Contents

Before you begin

Procedure 4-1: Install SYSCTL (LNW2) in new Metropolis

®

DMX shelf

Procedure 4-2: Install OLIU circuit packs in Main slots

Procedure 4-3: Install OLIU circuit packs in Function slots

Procedure 4-4: Provision OLIU circuit packs/ports for service

Procedure 4-5: Provision unprotected operation on optical ports

Procedure 4-6: Install DS3/EC1 circuit packs

Procedure 4-7: Provision DS3/EC1 circuit packs/ports for service

Procedure 4-8: Install DS1/E1 circuit packs

Procedure 4-9: Provision DS1/E1 circuit packs/ports for service

Procedure 4-10: Install TMUX circuit packs

Procedure 4-11: Provision TMUX ports for service

Procedure 4-12: Install 10/100 Ethernet circuit packs

Procedure 4-13: Install Gigabit Ethernet circuit packs

Procedure 4-14: Provision Ethernet circuit pack/LAN port/VCG for service

Procedure 4-15: Install pluggable transmission modules

Procedure 4-16: Install LNW80 switch pack

4-37

4-39

4-42

4-45

4-48

4-3

4-4

4-7

4-14

4-22

4-26

4-32

4-50

4-54

4-59

4-62

4-72

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-1

Install and provision circuit packs/OLIUs procedures

Procedure 4-17: Install Fibre Channel circuit packs

Procedure 4-18: Provision Fibre Channel circuit pack/Data port/VCG for service

Procedure 4-19: Provision pluggable transmission module

Procedure 4-20: Provision non-volatile memory cards

Procedure 4-21: Provision STS-n/VT1.5 tributary

Procedure 4-22: Change circuit pack mode of LNW26B, LNW28,

LNW77, or LNW121B-159B OC-48 OLIU circuit packs

Overview

4-74

4-77

4-80

4-82

4-83

4-84

.................................................................................................................................................................................................................................

4-2 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures

Before you begin

.................................................................................................................................................................................................................................

Before you begin

Prior to performing all procedures in this chapter,

1. If not previously completed, install generic and WaveStar

®

CIT software on the PC.

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

2. Connect PC and establish a WaveStar

®

CIT session.

Refer to

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24) .

Required equipment

All procedures in this chapter require that the following equipment is available:

•

Personal Computer (PC) with WaveStar

®

CIT software installed

•

Wrist strap

Important! If additional equipment is required to perform a specific procedure, that additional equipment is listed in that procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-3

Install and provision circuit packs/OLIUs procedures

Procedure 4-1: Install SYSCTL (LNW2) in new Metropolis

®

DMX shelf

.................................................................................................................................................................................................................................

Overview

Use this procedure to install a factory-fresh SYSCTL (LNW2) in a new Metropolis

®

DMX shelf (no circuit packs installed).

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

In addition to

“Required equipment” (p. 4-3)

listed in this chapter, a factory-fresh

LNW2, system controller (SYSCTL), with two non-volatile memory (NVM) cards installed is also required.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 4-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure.

Step

Complete the following steps to install the LNW2 SYSCTL in a new shelf without other circuit packs installed.

.................................................................................................................................................................................................

1

Important! For software installation, both NVMs must be present in the LNW2

SYSCTL.

After the LNW2 is installed, if one or both NVMs are missing,

NVM removed alarm(s) are issued and:

•

If one NVM socket is empty or an NVM is failed, the

IND

displays an alternating

N

and

O

and

x

(x=1 or 2, indicating the offending NVM socket).

•

If both NVM sockets are empty, the

IND

displays an alternating

E

and

0

and

1

.

Refer to

Step 2

for the complete listing of codes.

Insert the LNW2 (SYSCTL) circuit pack into the slot labeled

CTL

in the center of the shelf using a steady pressure on both faceplate latches. Allow a few minutes for the pack to complete initialization.

.................................................................................................................................................................................................................................

4-4 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures

2

Procedure 4-1: Install SYSCTL (LNW2) in new

Metropolis

®

DMX shelf

Result:

The LNW2 SYSCTL exhibits the following visible cycles during initialization:

1. The

FAULT

LED lights and remains lighted for approximately 90 seconds. After approximately 15 seconds, a flashing

b

appears in the

IND

display on the

SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 75 seconds and then

IND

display is blank.

2. The

FAULT

LED remains lighted for approximately another 20 seconds and then extinguishes.

3. The

ACTIVE

LED lights and remains lighted and the

CR

LED flashes 10 times.

While the

CR

LED is flashing, the

MJ

,

ABN

, and

NE

LEDs light and remain lighted.

Because the LNW2 SYSCTL is in 6.0 Maintenance Mode, an alternating

M

and

P

and

6

and “

.

” (“.” is a red, four-segment square [2 x 2] representing a period) and

0

appear in the

IND

display.

4. Continue with

Step 2 .

.................................................................................................................................................................................................

Observe the

IND

display on the LNW2 SYSCTL; the display indicates the state of the

SYSCTL.

If...

alternating

M

and

P

and

6

and “

.

”

(“.” is a red, four-segment square

[2 x 2] representing a period) and

0

alternating

E

and

0

and

0

alternating alternating alternating

E

E

E

and and and

0

0

0

and and and

1

2

3

Then...

6.0 Maintenance Mode. Proceed to

Procedure

2-1: “Install software generic (initial) via FTAM”

(p. 2-3)

or

Procedure 2-2: “Install software generic (initial) via FTP” (p. 2-21) .

LNW2 SYSCTL must be replaced.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

No NVMs are detected on the LNW2 SYSCTL.

Install two Lucent-supplied NVMs in the LNW2 or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

NVMs are present but not readable. Check to make sure they are properly seated and repeat this procedure.

Not Supported.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-5

Install and provision circuit packs/OLIUs procedures Procedure 4-1: Install SYSCTL (LNW2) in new

Metropolis

®

DMX shelf

If...

alternating

Letter

F

alternating

Letter

U

E

N

and and

1

O

and and

0 x

flashing

b

A red, four-segment square (2 x 2) appears in the

IND

display on the

LNW2 SYSCTL.

Then...

LNW2 SYSCTL will not boot.

No compatible generic on the NVMs in the

LNW2 SYSCTL.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure or contact your next level of support.

LNW2 SYSCTL faceplate latches are not fully seated.

Unseat the LNW2 SYSCTL and repeat this procedure, properly seating the faceplate latch.

“x” indicates that the NVM socket (1 or 2) is empty of the NVM installed is failed. Replace the indicated NVM or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

LNW2 SYSCTL will not boot due to unexpected or unreadable shelf type.

Repair the problem generally caused by bent pins and repeat this procedure.

Boot in progress.

Acknowledges the

UPD/INIT

button was momentarily pushed.

Pushing the

UPD/INIT

button while in

Maintenance Mode has no effect.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

4-6 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures

Procedure 4-2: Install OLIU circuit packs in Main slots

.................................................................................................................................................................................................................................

Overview

Use this procedure to install OC-12/OC-48/OC-192 OLIU circuit packs in the Main slots.

Important! The OLIU circuit packs in the Main slots must both have the same optical line rate and VT cross-connect size. If the circuit packs in the Main slots have different optical line rates or VT cross-connect sizes, the system reports an unexpected CP type alarm and service may be impacted.

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to complete this procedure.

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 4-3) , the following

equipment is also required:

•

Erasable marker or pencil

•

Optical loopback cables, LBOs, and optical fiber cleaning tools (if loopbacks are performed)

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 4-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure. It is especially important to know desired wavelengths and enhanced mode requirements (12 STS-1s) when applicable.

4. Ensure that correct OC-12/OC-48/OC-192 OLIU circuit packs are available for installation.

The OLIU circuit packs in Main slots must have the same size VT cross-connect fabric. For example, the LNW27 and LNW29 OC-48 OLIU circuit packs have full

(up to 48 STS-1s) VT mapping; therefore, they can be used together in the Main slots. If the circuit packs in the Main slots have different VT cross-connect fabric sizes, the system reports an unexpected CP type alarm.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-7

Install and provision circuit packs/OLIUs procedures Procedure 4-2: Install OLIU circuit packs in Main slots

The following is a list of Main OLIU circuit packs grouped by switch fabric:

•

OC-12 OLIUs with 12 STS-1 switch fabric: LNW48 LNW50 LNW54

•

OC-48 OLIUs with 12 STS-1 switch fabric: LNW26B (jumper set to enhanced)

LNW28 (jumper set to enhanced) LNW77 (jumper set to enhanced)

LNW121B—LNW159B (jumper set to enhanced)

LNW26B, LNW28, LNW77, LNW121B—LNW159B OC-48 OLIUs with 6

STS-1 switch fabric (jumper set to normal) are not supported in Release 6.0.

•

OC-48 OLIUs with 48 STS-1 switch fabric: LNW27 LNW29 LNW32 LNW76

LNW221—LNW259

•

OC-192 OLIUs with 48 STS-1 switch fabric: LNW56 LNW57 LNW58 LNW60

LNW523 LNW527 LNW554 LNW555

Step

1

Complete the following steps to install OC-12/OC-48/OC-192 OLIU circuit packs in the Main slots.

.................................................................................................................................................................................................

Are you installing an LNW121B-159B or LNW221-259 OLIU circuit pack?

If...

Yes

No

Then...

Continue with

Step 2 .

Proceed to

Step 5 .

2

.................................................................................................................................................................................................

From your work orders, determine the wavelength that you wish to set on the

LNW121B-LNW159B or LNW221-LNW259 circuit pack. Use the Channel Select

Option Label on the faceplate of the circuit pack to determine the correct channel.

.................................................................................................................................................................................................................................

4-8 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-2: Install OLIU circuit packs in Main slots

From the Channel Select Option Label on the faceplate of the LNW137B, refer to

Figure 4-1, “Channel select option label on LNW137B” (p. 4-9) , we determine that for

the desired CH37 wavelength (193.700 THz; 1547.715 nm), we must select CH X.

Figure 4-1 Channel select option label on LNW137B

LNW137B

FAULT

ACTIVE

OC-48

OLIU

OUT IN

Channel Select Option Label nc-dmx-196

3

.................................................................................................................................................................................................

If you are installing an:

•

LNW121B-159B ( Figure 4-2, “Jumper settings for LNW121B-159B” (p. 4-10) )

– Set the channel selection jumper on your circuit pack to either

CH X

or

CH Y

for your desired wavelength/channel.

– Set the enhanced/normal jumper on your circuit pack to

Enhanced

(switch fabric can cross-connect VT across any 12 STS-1s).

Normal

(switch fabric can cross-connect VT across any 6 STS-1s) is not supported in Release 6.0.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-9

Install and provision circuit packs/OLIUs procedures Procedure 4-2: Install OLIU circuit packs in Main slots

LNW221-259 ( Figure 4-3, “Jumper settings for LNW221-259” (p. 4-10) )

– Set the channel selection jumper on your circuit pack to either

CH X

or

CH Y

for your desired wavelength/channel.

Figure 4-2 Jumper settings for LNW121B-159B

Enhanced

Normal

Enhanced

Normal

X

Y

CH X

CH Y nc-dmx-245

.................................................................................................................................................................................................................................

4-10 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-2: Install OLIU circuit packs in Main slots

Figure 4-3 Jumper settings for LNW221-259

X

Y

CH X

CH Y nc-dmx-244

4

5

.................................................................................................................................................................................................

Using an erasable marker or pencil, check the appropriate box on the Channel Select

Option Label ( Figure 4-1, “Channel select option label on LNW137B” (p. 4-9) ) that

corresponds to your jumper setting.

Important! This label is the only means available to identify the wavelength selected when the pack is fully-seated and/or in-service.

.................................................................................................................................................................................................

Are you installing either an LNW26B, LNW28, LNW77, LNW121B-159B OLIU circuit pack?

If...

Yes

No

Then...

Continue with

Step 6 .

Proceed to

Step 7 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-11

Install and provision circuit packs/OLIUs procedures Procedure 4-2: Install OLIU circuit packs in Main slots

6

.................................................................................................................................................................................................

Set the enhanced/normal jumper on your circuit pack to

Enhanced

(switch fabric can cross-connect VT across any 12 STS-1s).

Normal

(switch fabric can cross-connect VT across any 6 STS-1s) is not supported in Release 6.0. Refer to

Figure 4-4, “Jumper settings for enhanced mode” (p. 4-12) .

Figure 4-4 Jumper settings for enhanced mode

Enhanced

Normal

Enhanced

Normal nc-dmx-246

7

.................................................................................................................................................................................................

Ensure all optical fiber connectors and couplings are properly cleaned.

Important! Signal performances may be degraded if the connections and couplings are not cleaned properly.

.................................................................................................................................................................................................................................

4-12 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-2: Install OLIU circuit packs in Main slots

8

9

10

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Seat the first OLIU circuit pack in Main slot

M1

by applying steady pressure to both faceplate latches.

Result:

The

FAULT

LED and

ACTIVE

LED lights. The

FAULT

LED flashes after about 20 seconds.

MJ

or

MN

and

NE

alarm LEDs on the SYSCTL circuit pack light when the OLIU circuit pack is installed.

If response is not correct, replace the OLIU circuit pack. Refer to the Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble Clearing Guide,

365-372-302.

.................................................................................................................................................................................................

Seat the second OLIU circuit pack in Main slot

M2

by applying steady pressure to both faceplate latches.

Result:

The

FAULT

LED and

ACTIVE

LED lights. The

FAULT

LED flashes after about 20 seconds.

MJ

or

MN

and

NE

alarm LEDs on the SYSCTL circuit pack light when the OLIU circuit pack is installed.

If response is not correct, replace the OLIU circuit pack. Refer to the Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble Clearing Guide,

365-372-302.

.................................................................................................................................................................................................

Important! Ensure that proper attenuation is used to prevent damage to the optical receiver.

If required, install optical loopbacks on the OLIU circuit packs just installed to clear inc. OCN LOS alarms.

Result:

values

If OSI over DCC is enabled for the Main ports, an inconsistent DCC alarm is reported when the Main ports are looped back.

If desired, clear the inconsistent DCC values alarm by disabling OSI over DCC for the Main ports. From the System View menu, select

Configuration

→

DCC

Terminations

and disable

OSI Over DCC

for the required DCC ports.

Reference:

•

Procedure 14-6: “Connect OLIU optical loopbacks” (p. 14-56)

•

Procedure 14-4: “Perform connection and verification of optical facility”

(p. 14-44)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-13

Install and provision circuit packs/OLIUs procedures

Procedure 4-3: Install OLIU circuit packs in Function slots

.................................................................................................................................................................................................................................

Overview

Use this procedure to install the following OLIU circuit packs in Function/Growth slots

A1/A2, B1/B2, C1/C2, D1/D2, and G1/G2.

•

LNW31 OC-48 OLIU

•

LNW36 OC-3 OLIU

•

LNW37 4OC-3 OLIU with up to four OM155 1.3LR1 and/or OM155 1.3IR1

pluggable transmission modules

•

LNW45 8OC-3 OLIU with up to eight OM155 1.3LR1 and/or OM155 1.3IR1

pluggable transmission modules

•

LNW46 OC-12 OLIU

•

LNW49 4OC-12 OLIU with up to four OM622 1.3LR1 and/or OM622 1.3IR1

pluggable transmission modules

•

LNW421-459 OC-48 PWDM OLIU

Important! A maximum equivalent of 24 2-way STS-1 cross-connections is supported on OC-N low-speed OLIUs in Function Groups A, B or C, when the

Main slots are equipped with LNW26B, LNW28, LNW77, and LNW121B-159B

OC-48 OLIUs, or with LNW48 and LNW50 OC-12 OLIUs.

For detailed information about cross-connections and restrictions regarding circuit pack types, rates, and VT granularity, refer to Metropolis

®

DMX Access Multiplexer

TL1 Message Details, 365-372-306.

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to complete this procedure.

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 4-3) , an erasable

marker or pencil is required.

Use only the following Lucent Approved Class 1 SFP transceivers.

Name

OM155 1.3LR1

OM155 1.3IR1

Pluggable Transmission

Module Code/Comcode

OC3LR1-I1

109453886

OC3IR1-I1

10945389

Description

OC3 SFP TRCVR Long

Reach - LR1

OC3 SFP TRCVR

Intermediate Reach - IR1

.................................................................................................................................................................................................................................

4-14 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-3: Install OLIU circuit packs in Function slots

Name

OM622 1.3IR1

OM622 1.3LR1

Pluggable Transmission

Module Code/Comcode

OC12IR1-I1

109453902

OC12LR1-I1

109467522

Description

OC12 SFP TRCVR

Intermediate Reach - IR1

OC12 SFP TRCVR Long

Reach - LR1

Refer to the Metropolis

®

DMX Access Multiplexer Installation Manual, 365-372-304, as required, when removing and/or installing pluggable transmission modules.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 4-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain work instructions for this procedure.

4. Ensure that the correct OLIU circuit pack(s) and pluggable transmission modules

(if required) are available for installation.

The OLIU circuit packs in a Function/Growth group must both have the same optical line rate and VT cross-connect size. For example, the LNW36 and LNW37

OC-3 OLIU circuit packs have the same optical line rate (OC-3) and VT cross-connect fabric size (up to 12 STS-1s); therefore, they can be used together in the same Function/Growth group. If the circuit packs in a Function/Growth group have different optical line rates or VT cross-connect sizes, the system reports an unexpected circuit pack type alarm and service may be impacted.

The following is a list of low-speed OLIU circuit packs grouped by optical line rate and switch fabric size:

•

OC-3 OLIUs with 12 STS-1 switch fabric: LNW36 LNW37

•

OC-3 OLIUs with 48 STS-1 switch fabric: LNW45

•

OC-12 OLIUs with 12 STS-1 switch fabric: LNW46

•

OC-12 OLIUs with 48 STS-1 switch fabric: LNW49

•

OC-48 OLIUs with 12 STS-1 switch fabric: LNW31, LWW421-459

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-15

Install and provision circuit packs/OLIUs procedures

Step

Procedure 4-3: Install OLIU circuit packs in Function slots

1

2

3

4

Complete the following steps to install OLIU circuit packs in Function Unit slots

(A1/A2, B1/B2, C1/C2, D1/D2) and Growth Unit slots (G1/G2).

.................................................................................................................................................................................................

Determine the Function Unit slot(s) (A1/A2, B1/B2, C1/C2, D1/D2) or Growth Unit slot(s) (G1/G2) being equipped with OLIU circuit packs.

.................................................................................................................................................................................................

Ensure all optical fiber connectors and couplings are properly cleaned.

Important! Signal performances may be degraded if the connections and couplings are not cleaned properly.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Important! Pluggable transmission modules are shipped with a dust plug installed into the optical ports to maintain cleanliness during storage and/or transportation. It is recommended that the dust plug be kept in place to maintain cleanliness until the optical fiber is connected. With proper care and handling, cleaning the pluggable transmission modules should not be necessary.

If required, clean the optical pluggable transmission module(s).

Reference:

(p. 14-135)

Procedure 14-29: “Clean optical pluggable transmission module”

.................................................................................................................................................................................................

Are you installing an LNW421-459 OLIU circuit pack?

If...

Yes

No

Then...

Continue with

Step 5 .

Proceed to

Step 8 .

5

.................................................................................................................................................................................................

From your work orders, determine the wavelength that you wish to set on the

LNW421-459 circuit pack. Use the Channel Select Option Label on the faceplate of the circuit pack to determine the correct channel.

.................................................................................................................................................................................................................................

4-16 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-3: Install OLIU circuit packs in Function slots

Example

From the Channel Select Option Label on the faceplate of the LNW437, refer to

Figure 4-5, “Channel select option label on LNW437” (p. 4-17) , we

determine that for the desired CH37 wavelength (193.700 THz; 1547.715 nm), we must select CH X.

Figure 4-5 Channel select option label on LNW437

LNW437

Sx:x

OC-48

CH37, CH38

LUCENT

FAULT

ACTIVE

OC-48

OUT IN

Channel Select

Option Label nc-dmx-275

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-17

Install and provision circuit packs/OLIUs procedures Procedure 4-3: Install OLIU circuit packs in Function slots

6

.................................................................................................................................................................................................

Set the channel selection jumper on your circuit pack to either

CH X

or

CH Y

for your desired wavelength/channel, refer to

Figure 4-6, “Jumper settings for LNW421-459”

(p. 4-18) .

Figure 4-6 Jumper settings for LNW421-459

X

Y

CH X

CH Y nc-dmx-276

7

8

.................................................................................................................................................................................................

Using an erasable marker or pencil, check the appropriate box on the Channel Select

Option Label ( Figure 4-5, “Channel select option label on LNW437” (p. 4-17) ) that

corresponds to your jumper setting.

Important! This label is the only means available to identify the wavelength selected when the pack is fully-seated and/or in-service.

.................................................................................................................................................................................................

Open both faceplate latches and seat the first OLIU circuit pack into the required

Function/Growth slot by applying steady pressure to both faceplate latches.

.................................................................................................................................................................................................................................

4-18 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-3: Install OLIU circuit packs in Function slots

Result:

The

FAULT

LED lights for approximately 15 seconds then goes off, indicating successful installation. The OLIU circuit pack appears in the WaveStar

®

CIT System View.

If response is not correct, replace the OLIU circuit pack. Refer to the Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble Clearing Guide,

365-372-302 for more information.

.................................................................................................................................................................................................

9

Important! The LNW37 4OC-3 and LNW49 4OC-12 OLIU circuit packs may be equipped with up to four pluggable transmission modules. The LNW45 8OC-3

OLIU circuit packs may be equipped with up to eight pluggable transmission modules.

If required, install pluggable transmission module(s).

Reference:

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62)

10

.................................................................................................................................................................................................

If optical port testing is...

required and has not already been performed,

not required or has already been performed,

Then...

Continue with

Step 11 .

Proceed to

Step 15 .

11

12

13

.................................................................................................................................................................................................

To test the optical port(s) on the installed OLIU, loop back the first optical port.

Reference:

Procedure 14-6: “Connect OLIU optical loopbacks” (p. 14-56)

.................................................................................................................................................................................................

Remove the lightguide jumper used to loop back the port and the LBO, if required.

Result:

The OLIU

FAULT

LED or the port LED associated with the pluggable transmission module starts flashing. The

MN

and

NE

LEDs are lighted on the

SYSCTL circuit pack.

.................................................................................................................................................................................................

Important! It is recommended that the dust plug be installed into the optical ports on the pluggable transmission module to maintain cleanliness until the optical fiber is connected.

If required, reinstall the dust plug into the optical ports on the pluggable transmission module to maintain cleanliness.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-19

Install and provision circuit packs/OLIUs procedures Procedure 4-3: Install OLIU circuit packs in Function slots

14

15

.................................................................................................................................................................................................

From the System View window, select

Configuration

→

Update System

→

Update

All

.

Result:

The OLIU

FAULT

LED or the port LED associated with the pluggable transmission module stops flashing. All alarms are cleared.

Repeat

Step 11

through

Step 14

to test all optical ports on the OLIU just installed.

.................................................................................................................................................................................................

Is a second (protection) OLIU circuit pack required in the companion Function/Growth slot?

If...

Yes

No

Then...

Repeat

Step 4

through

Step 14 , as required, to

install the second (protection) OLIU circuit pack in the companion Function/Growth slot.

Insert 177D Application Blank or LNW98

Detectable Blank circuit pack into the unequipped

Function/Growth slot. If an LNW98 Detectable

Blank circuit pack was installed, select

View

→

Refresh Equipment

. Click on the slot just equipped and

Select

to view the circuit pack in the system view.

16

17

.................................................................................................................................................................................................

From the System View window, click the

Alarm List

button to view alarms, protection switches, protection switch lockouts, and loopbacks for the ports on the circuit packs just installed.

Result:

The NE Alarm List appears. No alarms should be present for the OLIU circuit packs just installed.

.................................................................................................................................................................................................

Do you wish to install OLIU circuit packs in other Function/Growth slots?

If...

Yes

No

Then...

Repeat this procedure from

Step 1 .

Continue with

Step 18 .

.................................................................................................................................................................................................................................

4-20 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-3: Install OLIU circuit packs in Function slots

18

.................................................................................................................................................................................................

Do you wish to provision circuit pack and/or port parameters for service at this time?

If...

Yes

No

Then...

Proceed to

Procedure 4-4: “Provision OLIU circuit packs/ports for service” (p. 4-22) .

STOP! End of Procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-21

Install and provision circuit packs/OLIUs procedures

Procedure 4-4: Provision OLIU circuit packs/ports for service

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision OLIU circuit pack/ports for service.

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Ensure appropriate OLIU circuit pack(s) is installed. If required, refer to

Procedure

4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

and/or

Procedure 4-3:

“Install OLIU circuit packs in Function slots” (p. 4-14) .

4. Ensure appropriate pluggable transmission module(s) is installed. If required, refer to

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62) .

Step

1

Complete the following steps to provision OLIU circuit pack/ports for service.

.................................................................................................................................................................................................

From the System View window, click the

Alarm List

button to verify that no alarms, loopbacks, protection switch lockouts, or protection switches are present for the OLIU circuit pack/ports to be provisioned.

Result:

The NE Alarm List appears.

2

3

.................................................................................................................................................................................................

From the System View window, select

Configuration

→

Equipment

.

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Find and highlight the OLIU circuit pack being provisioned, then click

Select

at the bottom of the window.

Result:

The circuit pack parameters appear.

.................................................................................................................................................................................................

4

Important! If one or more ports on a low-speed OLIU circuit pack are to carry

SDH signals, the

SS Bits

parameter must be provisioned

SS10

. The provisioned

.................................................................................................................................................................................................................................

4-22 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-4: Provision OLIU circuit packs/ports for service

5

value of the SS Bits parameter has no effect on SONET signals or network elements that carry SONET signals.

Provision the required circuit pack parameters according to the work instructions, then click

Apply

if changes were made. If no changes were made, go to the next step.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

to apply the changes.

.................................................................................................................................................................................................

Click

Close

to exit or continue with

Step 6

to provision a port(s).

6

.................................................................................................................................................................................................

Find the OLIU circuit pack with the ports being provisioned, then expand the equipment list by clicking on the plus (+) sign next to the OLIU circuit pack.

.................................................................................................................................................................................................

7

If the circuit pack is...

equipped with pluggable transmission modules,

not equipped with pluggable transmission modules,

Then...

Perform the following:

1. Click (highlight) the required pluggable transmission module (PTM) being provisioned, then click

Select

at the bottom of the window.

2. Provision the required pluggable transmission module parameters according to the work instructions, then click

Apply

if changes were made. If no changes were made, continue with

Step 8 .

continue with

Step 8 .

8

.................................................................................................................................................................................................

Click (highlight) the OLIU port being provisioned, then click

Select

at the bottom of the window.

Result:

The port parameters appear.

9

.................................................................................................................................................................................................

Select and provision the required port parameters, according to the work instructions.

.................................................................................................................................................................................................

10

Important! All the current parameter settings may be applied to both ports of the port pair, or only the parameter settings that changed may be applied to both ports of the port pair.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-23

Install and provision circuit packs/OLIUs procedures Procedure 4-4: Provision OLIU circuit packs/ports for service

11

12

If required, select Port Pair in the

Apply to:

field to apply the current parameter settings to both ports of the port pair or only the parameter settings that changed.

.................................................................................................................................................................................................

Click

Apply

to make provisioning changes. If no changes were made, continue with the next step.

Result:

If Port Pair was selected in the

Apply to:

field, a dialog box appears asking if you want to apply all parameter settings on the screen. Click

Yes

or

No

as required.

A dialog box may appear asking you to confirm executing this command. Click

Yes

to apply changes.

.................................................................................................................................................................................................

In

Step 9 , did you provision the Application parameter to 1+1 or Bidirectional 1+1?

If...

Yes

No

Then...

Continue with

Step 13

to provision the Revertive

Mode parameter for the protection group.

Proceed to

Step 15 .

13

14

.................................................................................................................................................................................................

From the System View,

1. Select

Configuration

→

Equipment

.

2. Click the

Ptn Grp

tab and highlight the required

1+1 Line

or

1+1_BIDIR Line

protection group.

3. Click

Select

.

4. Provision the required protection group parameters according to the work instructions.

5. Click

Apply

and

Close

. If no changes were made, click

Close

and go to the next step.

.................................................................................................................................................................................................

From the System View menu,

1. Select

View

→

Protection

.

2. Click the

Ptn Grp

tab and highlight the required

1+1 Line

or

1+1_BIDIR Line

protection group.

3. Click

Select

.

4. Verify that the protection group parameters were provisioned correctly.

5. Click

Close

.

.................................................................................................................................................................................................................................

4-24 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-4: Provision OLIU circuit packs/ports for service

15

.................................................................................................................................................................................................

Are there additional OLIU ports to be provisioned on the OLIU circuit pack?

If...

Yes

No

Then...

Repeat this procedure from

Step 8

for each port.

Continue with

Step 16 .

16

.................................................................................................................................................................................................

Are there additional OLIU circuit packs to be provisioned?

If...

Yes

No

Then...

Repeat procedure from

Step 3

for each circuit pack.

Click

Close

to exit.

17

.................................................................................................................................................................................................

Are you provisioning unprotected operation on the optical port of a Function group?

If...

Yes

No

Then...

Proceed to

Procedure 4-5: “Provision unprotected operation on optical ports” (p. 4-26) .

STOP! End of Procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-25

Install and provision circuit packs/OLIUs procedures

Procedure 4-5: Provision unprotected operation on optical ports

.................................................................................................................................................................................................................................

Overview

This procedure identifies the following two operations for provisioning unprotected operation on the optical ports of low-speed Function groups with or without a protection circuit pack:

•

Initial provisioning of 0x1 unprotected operation for low-speed optical ports.

•

Changing pre Release 5.0 unprotected operation application parameters to Release

5.0 application parameters.

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Important! The 1+1, Bidirectional 1+1, Optimized 1+1, UPSR, BLSR, and 0x1Sn unprotected applications may be mixed between port pairs of a Function group. For

example, a Function group may have a 1+1 application on a port pair, a UPSR application on a port pair, and/or an unprotected application on a single port of a port pair.

However, two separate unprotected applications are not allowed on the same port pair of a Function group. For example, a Function group does not support an unprotected application on port 3 of the primary circuit pack and another unprotected application on port 3 of the protection circuit pack. However, a

Function group does support an unprotected application on port 3 of the primary circuit pack and another unprotected application on port 4 of the protection circuit pack.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Verify that the work instructions specify the slots, circuit packs, ports, and network element parameters to be used for this procedure.

5. Verify that the slots have been equipped with circuit packs and any required pluggable transmission modules have been installed.

.................................................................................................................................................................................................................................

4-26 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-5: Provision unprotected operation on optical ports

6. Verify that the network ring containing the host Metropolis

®

DMX shelf is established and operating properly using the procedures in this manual.

7. Verify that all systems being connected to the host Metropolis

®

been equipped and operating properly.

DMX shelf have

Step

1

Complete the following steps to provision unprotected operation on the optical ports of a Function group or change an existing application.

.................................................................................................................................................................................................

Are you provisioning an optical port(s) in a Function group for the first time or changing an existing application?

If...

Provisioning unprotected application for the first time,

Changing an existing unprotected application,

Then

Proceed to

Procedure 4-5.1: “Provision unprotected operation in a low-speed Function group” (p. 4-28) .

Proceed to

Procedure 4-5.2: “Change existing unprotected application to 0x1S1 or 0x1S2 unprotected application” (p. 4-30) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-27

Install and provision circuit packs/OLIUs procedures

Procedure 4-5.1: Provision unprotected operation in a low-speed Function group

.................................................................................................................................................................................................................................

Overview

Use this procedure to initially provision unprotected operation for optical ports in

Function groups.

Step

1

2

3

4

5

6

7

Complete the following steps to provision the port.

.................................................................................................................................................................................................

From the System View window, select

Configuration

→

Equipment

.

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Find the OLIU circuit pack with the port being provisioned, then expand the equipment list by clicking on the plus (+) sign next to the OLIU circuit pack.

.................................................................................................................................................................................................

Click (highlight) the OLIU port being provisioned, then click

Select

at the bottom of the window.

Result:

The port parameters appear on the right side of the window.

.................................................................................................................................................................................................

Provision the Application parameter (

0x1S1

or

0x1S2

) according to your work instructions.

If the port being provisioned is in slot 1, choose

0x1S1

. For a port in slot 2, choose

0x1S2

.

.................................................................................................................................................................................................

Provision the Port Monitoring Mode parameter for the selected port as

AUTO

.

.................................................................................................................................................................................................

Click

Apply

and

Close

.

Important! If a companion port is equipped for the port being provisioned, the port state for the companion port is automatically set to Not Monitored (NMON) and is

not provisionable. The inactive companion port, if equipped, always outputs STS1

UNEQ or AIS-P on all tributaries.

.................................................................................................................................................................................................

If required, repeat this procedure to provision other ports in the Function group

.................................................................................................................................................................................................................................

4-28 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-5.1: Provision unprotected operation in a low-speed Function group

When a port is ready to be cross-connected, select

Configuration

→

Cross-Connections

from the System View. Use the Cross-Connection Wizard to provision the cross-connections.

Establishing service requires that the proper slots in each terminating node be properly equipped with the correct circuit pack(s) for the type of service being established. It also requires numerous cross-connections in each of the nodes representing the path of the required service. Additionally, transmission tests should be performed to verify the continuity and quality of the established circuit.

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-29

Install and provision circuit packs/OLIUs procedures

Procedure 4-5.2: Change existing unprotected application to

0x1S1 or 0x1S2 unprotected application

.................................................................................................................................................................................................................................

Overview

Use this procedure to change an existing unprotected 1+1, Bidirectional 1+1,

Optimized 1+1, or UPSR application to an 0x1S1 or 0x1S2 application.

This procedure allows you to change an existing unprotected application, implemented using prescribed methods prior to Release 5.0, to an 0x1S1 or 0x1S2 application.

Before you begin

Existing 1+1, Bidirectional 1+1, Optimized 1+1, or UPSR applications may be changed to 0x1S1 or 0x1S2 applications if the following conditions are met:

•

There are no cross-connections to UPSR ring channels. Cross-connections on

0x1Sn ports are provisioned only with channel aids.

•

There are no unswitched cross-connections on UPSR ports. Unswitched cross-connections are not supported on 0x1Sn ports.

•

Service for all provisioned cross-connections on the port(s) is carried on the port in slot n.

Step

1

2

3

4

Complete the following steps to change provisioning for the required port.

.................................................................................................................................................................................................

From the System View window, select

Configuration

→

Equipment

.

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Find the OLIU circuit pack with the port being provisioned, then expand the equipment list by clicking on the plus (+) sign next to the OLIU circuit pack.

.................................................................................................................................................................................................

Click (highlight) the OLIU port being provisioned, then click

Select

at the bottom of the window.

Result:

The port parameters display on the right side of the window.

.................................................................................................................................................................................................

Provision the Application parameter according to the work instructions. Select

0x1S1

for a port in slot 1 or

0x1S2

for a port in slot 2.

.................................................................................................................................................................................................................................

4-30 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-5.2: Change existing unprotected application to 0x1S1 or 0x1S2 unprotected application

5

6

7

.................................................................................................................................................................................................

Provision the Port Monitoring Mode parameter as

AUTO

.

.................................................................................................................................................................................................

Click

Apply

and

Close

.

Important! If a companion port is equipped for the port being provisioned, the port state for the companion port is automatically set to Not Monitored (NMON) and is

not provisionable. The inactive companion port, if equipped, always outputs STS1

UNEQ or AIS-P on all tributaries.

.................................................................................................................................................................................................

If required, repeat this procedure for any other ports in the Function group being provisioned.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-31

Install and provision circuit packs/OLIUs procedures

Procedure 4-6: Install DS3/EC1 circuit packs

.................................................................................................................................................................................................................................

Overview

Use this procedure to install the following DS3/EC1 circuit packs:

•

LNW16 12DS3/EC1

•

LNW19/19B 48DS3/EC1

Important! The high-density LNW19/19B 48DS3/EC1 circuit pack is only compatible with the Metropolis

®

DMX High Capacity Shelf. The standard

Metropolis

®

DMX Shelf does not support the high-density LNW19/19B

48DS3/EC1 circuit pack. If a high-density LNW19/19B 48DS3/EC1 circuit pack is installed in the standard Metropolis

®

DMX Shelf, the system will not recognize the circuit pack as an allowable type.

The system does not support mixing standard density LNW16 12DS3/EC1 and high-density LNW19/19B 48DS3/EC1 circuit packs in the same Function group.

It is assumed that the DS3/EC-1 cables have already been installed. Refer to the

Metropolis

®

DMX Access Multiplexer Installation Manual, 365-372-304 for cabling information.

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to complete this procedure.

Before you begin

Prior to beginning this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Ensure that DS3/EC1 circuit pack(s) is available for installation.

4. If installing high-density LNW19/19B 48DS3/EC1 circuit packs in the Metropolis

®

DMX High Capacity Shelf, verify that the new DS3/EC-1 cables are installed to the bottom connectors (J1-J8) and middle connectors (J20-J27) of the shelf backplane as required. Refer to the Metropolis

®

DMX Access Multiplexer

Installation Manual, 365-372-304 for cabling information.

.................................................................................................................................................................................................................................

4-32 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures

Step

Procedure 4-6: Install DS3/EC1 circuit packs

1

2

Complete the following steps to install a DS3/EC1 circuit pack(s).

.................................................................................................................................................................................................

Important! If the Main slots are equipped with LNW26B, 28, 77, or 121B-159B

OC-48 OLIU circuit packs and LNW19/19B DS3/EC1 circuit packs are installed in

Function Units A, B, or C, then STS-25 through STS-48 are not available for cross-connections.

Determine the Function Unit slots (A, B, C, or D) being equipped with DS3/EC1 circuit packs.

.................................................................................................................................................................................................

Determine from office records or circuit order the length of the DS3/EC-1 cabling between the shelf and the DSX-3 panel or equivalent connection point and any other circuit pack parameters to be set.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-33

Install and provision circuit packs/OLIUs procedures Procedure 4-6: Install DS3/EC1 circuit packs

3

.................................................................................................................................................................................................

If required, set the jumper on the LNW16 12DS3/EC1 circuit pack(s) for either DS3 or

EC-1 service as illustrated in

Figure 4-7, “Jumper settings for LNW16” (p. 4-34) .

Figure 4-7 Jumper settings for LNW16

EC-1

JP1

DS3 nc-dmx-030

4

Important! The LNW19/19B 48DS3/EC1 circuit packs do not have the illustrated jumper; the LNW19/19B circuit pack defaults to DS3 upon installation.

Port provisioning using the WaveStar

®

CIT is supported. The electrical interface

(EIF) parameter has possible values of DS3 or EC-1. If you set the jumper on the

LNW16 and therefore the whole pack for DS3 or EC-1, you can still provision the ports individually for either DS3 or EC-1 service. The jumper setting only determines how the ports will come up during the initial installation of the circuit pack.

.................................................................................................................................................................................................

Open the faceplate latches and seat the first DS3/EC1 circuit pack in Function Unit slot A1, B1, C1, or D1 by applying steady pressure to both faceplate latches.

.................................................................................................................................................................................................................................

4-34 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-6: Install DS3/EC1 circuit packs

5

Result:

The

FAULT

LED on the DS3/EC1 circuit pack lights for approximately 30 seconds then goes off and then

ACTIVE

LED lights, indicating successful installation. (Firmware updates may take place that add additional wait time.) The new circuit pack appears in the WaveStar

®

CIT System View.

.................................................................................................................................................................................................

Is a second (protection) DS3/EC1 circuit pack required in Function Unit slot A2, B2,

C2, or D2?

If...

Yes

No

Then...

Continue with

Step 6 .

Insert 177D Application Blank or LNW98

Detectable Blank circuit pack into the unequipped

Function Unit slot A2, B2, C2, or D2. If an

LNW98 Detectable Blank circuit pack was installed, select

View

→

Refresh Equipment

. Click on the slot just equipped and

Select

to view the circuit pack in the system view.

Proceed to

Step 7 .

6

7

8

.................................................................................................................................................................................................

Open the faceplate latches and seat the second (protection) DS3/EC1 circuit pack in

Function Unit slot A2, B2, C2, or D2 by applying steady pressure to both faceplate latches.

Result:

The

FAULT

LED on the DS3/EC1 circuit pack lights for approximately 30 seconds then goes off, indicating successful installation. (Firmware updates may take place that add additional wait time.) The new circuit pack appears in the

WaveStar

®

CIT System View.

.................................................................................................................................................................................................

From the System View window, click the

Alarm List

button to verify that no alarms, loopbacks, protection switch lockouts, or protection switches are present for the ports on the circuit packs just installed.

Result:

The NE Alarm List appears. No alarms should be present for the DS3/EC1 circuit pack(s) just installed.

.................................................................................................................................................................................................

If required, repeat this procedure from

Step 1

to install DS3/EC1 circuit packs in another Function unit.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-35

Install and provision circuit packs/OLIUs procedures Procedure 4-6: Install DS3/EC1 circuit packs

9

.................................................................................................................................................................................................

Do you wish to provision circuit pack and/or port parameters at this time?

If...

Yes

No

Then...

Proceed to

Procedure 4-7: “Provision DS3/EC1 circuit packs/ports for service” (p. 4-37) .

STOP! End of Procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

4-36 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures

Procedure 4-7: Provision DS3/EC1 circuit packs/ports for service

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision a DS3/EC-1 circuit packs/ports for service.

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure

4. Ensure DS3/EC1 circuit packs are installed.

Step

1

2

3

4

Complete the following steps to provision a DS3/EC1 circuit packs/ports for service.

.................................................................................................................................................................................................

From the System View window, click the

Alarm List

button to verify that no alarms, loopbacks, protection switch lockouts, or protection switches are present for the ports to be provisioned.

Result:

The NE Alarm List appears.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Equipment

.

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Find and highlight the DS3/EC1 circuit pack being provisioned, then click

Select

at the bottom of the window.

Result:

The circuit pack parameters appear.

.................................................................................................................................................................................................

Provision the required circuit pack parameters according to the work instructions, then click

Apply

if changes were made. If no changes were made, go to the next step.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-37

Install and provision circuit packs/OLIUs procedures Procedure 4-7: Provision DS3/EC1 circuit packs/ports for service

5

6

7

8

9

10

11

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

to apply the changes.

.................................................................................................................................................................................................

Click

Close

to exit or continue with the next step to provision ports.

.................................................................................................................................................................................................

Find the DS3/EC-1 circuit pack with the ports being provisioned, then expand the equipment list by clicking on the plus (+) sign next to the DS3/EC-1 circuit pack.

.................................................................................................................................................................................................

Click (highlight) the DS3/EC-1 port being provisioned, then click

Select

at the bottom of the window.

Result:

The port parameters appear.

.................................................................................................................................................................................................

Select and provision the required port parameters, according to your work instructions.

.................................................................................................................................................................................................

Important! The parameter settings may be applied to the selected port only or all ports on the circuit pack.

Select This Port or All Ports, This Pack in the

Apply to:

field according to the work instructions.

.................................................................................................................................................................................................

Click

Apply

to make provisioning changes. If no changes were made, continue with the next step.

Result:

If All Ports, This Pack was selected in the

Apply to:

field, a dialog box appears asking if you want to apply all parameter settings on the screen . Click

Yes

or

No

as required.

A dialog box may appear asking you to confirm executing this command. Verify that you are provisioning the correct DS3/EC-1 port, then click

Yes

to apply your changes.

.................................................................................................................................................................................................

If required, repeat this procedure to provision another DS3/EC-1 circuit pack/port.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

4-38 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures

Procedure 4-8: Install DS1/E1 circuit packs

.................................................................................................................................................................................................................................

Overview

Use this procedure to install the following circuit packs:

•

LNW6 28DS1

•

LNW7 28DS1PM

•

LNW8 56DS1/E1

Important! The high-density LNW8 56DS1/E1 circuit pack is only compatible with the Metropolis

®

DMX High Capacity Shelf. The standard Metropolis

®

DMX

Shelf does not support the high-density LNW8 56DS1/E1 circuit pack. If a high-density LNW8 56DS1/E1 circuit pack is installed in the standard Metropolis

®

DMX Shelf, the system will not recognize the circuit pack as an allowable type.

The system does not support mixing standard density (LNW6 and LNW7) and high-density (LNW8) DS1 circuit packs in the same Function group.

It is assumed that the DS1 cables have already been installed. Refer to the

Metropolis

®

DMX Access Multiplexer Installation Manual, 365-372-304 for cabling information.

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Ensure that the DS1 or DS1/E1 circuit pack(s) is available for installation.

4. If installing high-density LNW8 56DS1/E1 circuit packs in the Metropolis

®

DMX

High Capacity Shelf, verify that the DS1 cables are installed to the bottom connectors (J1-J8) and middle connectors (J20-J27) of the shelf backplane as required. Refer to the Metropolis

®

DMX Access Multiplexer Installation Manual,

365-372-304 for cabling information.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-39

Install and provision circuit packs/OLIUs procedures

Step

Procedure 4-8: Install DS1/E1 circuit packs

1

2

3

4

Complete the following steps to install a DS1 or DS1/E1 circuit pack(s).

.................................................................................................................................................................................................

Determine the Function Unit slots (A, B, C, or D) being equipped with DS1 or DS1/E1 circuit packs.

.................................................................................................................................................................................................

Determine from office records or circuit order the length of the DS1 cabling between the Metropolis

®

DMX and the DSX-1 cross-connect point and any other circuit pack parameters to be set.

.................................................................................................................................................................................................

Open the faceplate latches and seat the first DS1 or DS1/E1 circuit pack in Function

Unit slot A1, B1, C1, or D1 by applying steady pressure to both faceplate latches.

Result:

The

FAULT

LED on the DS1 or DS1/E1 circuit pack lights for approximately 30 seconds then goes off and then

ACTIVE

LED lights, indicating successful installation. (Firmware updates may take place that add additional wait time.) The new circuit pack appears in the WaveStar

®

CIT System View.

.................................................................................................................................................................................................

Is a second (protection) DS1 or DS1/E1 circuit pack required in Function Unit slot A2,

B2, C2, or D2?

If...

Yes

No

Then...

Continue with

Step 5 .

Insert 177D Application Blank or LNW98

Detectable Blank circuit pack into the unequipped

Function Unit slot A2, B2, C2, or D2. If an

LNW98 Detectable Blank circuit pack was installed, select

View

→

Refresh Equipment

. Click on the slot just equipped and

Select

to view the circuit pack in the system view.

Proceed to

Step 6 .

5

.................................................................................................................................................................................................

Open the faceplate latches and seat the second (protection) DS1 or DS1/E1 circuit pack in Function Unit slot A2, B2, C2, or D2 by applying steady pressure to both faceplate latches.

.................................................................................................................................................................................................................................

4-40 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-8: Install DS1/E1 circuit packs

6

7

8

Result:

The

FAULT

LED on the DS1 or DS1/E1 circuit pack lights for approximately 30 seconds then goes off, indicating successful installation.

(Firmware updates may take place that add additional wait time.) The new circuit pack appears in the WaveStar

®

CIT System View.

.................................................................................................................................................................................................

From the System View window, click the

Alarm List

button to verify that no alarms, loopbacks, protection switch lockouts, or protection switches are present for the ports on the circuit packs just installed.

Result:

The NE Alarm List appears. No alarms should be present for the DS1 or

DS1/E1 circuit pack(s) just installed.

.................................................................................................................................................................................................

If required, repeat this procedure to install DS1 or DS1/E1 circuit packs in another

Function Unit.

.................................................................................................................................................................................................

Do you wish to provision circuit pack and/or port parameters at this time?

If...

Yes

No

Then...

Proceed to

Procedure 4-9: “Provision DS1/E1 circuit packs/ports for service” (p. 4-42) .

STOP! End of Procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-41

Install and provision circuit packs/OLIUs procedures

Procedure 4-9: Provision DS1/E1 circuit packs/ports for service

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision DS1/E1 circuit packs/ports for service.

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions specify the circuit pack/port addresses and the parameters/values to be provisioned.

4. Ensure the circuit pack(s) is installed.

Step

1

2

3

4

Complete the following steps to provision a DS1/E1 circuit packs/ports for service.

.................................................................................................................................................................................................

From the System View window, click the

Alarm List

button to verify that no alarms, loopbacks, protection switch lockouts, or protection switches are present for the ports on the circuit packs to be provisioned.

Result:

The NE Alarm List appears.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Equipment

.

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Find and highlight the DS1/E1 circuit pack being provisioned, then click

Select

at the bottom of the window.

Result:

The circuit pack parameters appear.

.................................................................................................................................................................................................

Important! All the ports on an LNW8 56DS1/E1 circuit pack are provisioned for either DS1 or E1; DS1 and E1 ports cannot be mixed on a single circuit pack.

.................................................................................................................................................................................................................................

4-42 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-9: Provision DS1/E1 circuit packs/ports for service

5

6

7

8

9

10

Provision the required circuit pack parameters according to the work instructions, then click

Apply

if changes were made. If no changes were made, go to the next step.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

to apply the changes.

.................................................................................................................................................................................................

Click

Close

to exit or continue with the next step to provision ports.

.................................................................................................................................................................................................

Find the circuit pack with the ports being provisioned, then expand the equipment list by clicking on the plus (+) signs.

.................................................................................................................................................................................................

Click (highlight) the DS1/E1 port being provisioned, then click Select at the bottom of the window.

Result:

The port parameters appear.

.................................................................................................................................................................................................

Select and provision the required port parameters, according to the work instructions.

Important! If connecting to any DLC terminal, then select

Yes

for the

Bi-Polar

Violations

(BPV) parameter. The BPV parameter does not apply to the high-density LNW8 56DS1/E1 circuit pack.

.................................................................................................................................................................................................

Important! The parameter settings may be applied to the selected port only or all ports on the circuit pack.

Select This Port or All Ports, This Pack in the

Apply to:

field according to the work instructions.

.................................................................................................................................................................................................

Click

Apply

to make provisioning changes. If no changes were made, continue with the next step.

Result:

If All Ports, This Pack was selected in the

Apply to:

field, a dialog box appears asking if you want to apply all parameter settings on the screen. Click

Yes

or

No

as required.

A dialog box may appear asking you to confirm executing this command. Verify that you are provisioning the correct port(s), then click

Yes

to apply your changes.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-43

Install and provision circuit packs/OLIUs procedures Procedure 4-9: Provision DS1/E1 circuit packs/ports for service

11

.................................................................................................................................................................................................

If required, repeat this procedure to provision another DS1/E1 circuit pack/port.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

4-44 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures

Procedure 4-10: Install TMUX circuit packs

.................................................................................................................................................................................................................................

Overview

Use this procedure to install the LNW18 TMUX circuit pack(s).

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Ensure that the TMUX circuit pack(s) is available for installation.

Step

1

2

Complete the following steps to install TMUX circuit pack(s).

.................................................................................................................................................................................................

Determine the Function Unit slots (A, B, C, or D) being equipped with TMUX circuit packs.

.................................................................................................................................................................................................

Open both faceplate latches and seat the circuit pack in Function Unit slot A1, B1, C1, or D1 by applying steady pressure to both faceplate latches.

Result:

For circuit packs with the current firmware installed, the

FAULT

LED lights for approximately 30 seconds and then the

ACTIVE

LED lights to indicate success.

For older circuit packs, the following sequence occurs:

•

The

FAULT

LED on the TMUX circuit pack lights for approximately 60 seconds,

• then the

ACTIVE

LED flashes for approximately 20 seconds.

•

The

FAULT

LED goes off and the

ACTIVE

LED goes off indicating successful installation.

•

The new circuit pack appears in the WaveStar

®

CIT System View.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-45

Install and provision circuit packs/OLIUs procedures Procedure 4-10: Install TMUX circuit packs

3

.................................................................................................................................................................................................

Is a second (protection) TMUX circuit pack required in Function Unit slot A2, B2, C2, or D2

If...

Yes

No

Then...

Continue with

Step 4 .

Insert 177D Application Blank or LNW98

Detectable Blank circuit pack into the unequipped

Function Unit slot A2, B2, C2, or D2. If an

LNW98 Detectable Blank circuit pack was installed, select

View

→

Refresh Equipment

. Click on the slot just equipped and

Select

to view the circuit pack in the system view.

Proceed to

Step 5 .

4

5

6

.................................................................................................................................................................................................

Open both faceplate latches and seat the second (protection) TMUX circuit pack in

Function Unit slot A2, B2, C2, or D2 by applying steady pressure to both faceplate latches.

Result:

For circuit packs with the current firmware installed, the

FAULT

LED lights for approximately 30 seconds to indicate success.

For older circuit packs, the following sequence occurs:

•

The

FAULT

LED on the TMUX circuit pack lights for approximately 60 seconds,

• then the

ACTIVE

LED flashes for approximately 20 seconds.

•

The

FAULT

LED goes off and the

ACTIVE

LED goes off indicating successful installation.

•

The new circuit pack appears in the WaveStar

®

CIT System View.

.................................................................................................................................................................................................

From the System View window, click the

Alarm List

button to verify that no alarms, loopbacks, protection switch lockouts, or protection switches are present for the ports on the circuit packs just installed.

Result:

The NE Alarm List appears. No alarms should be present for the circuit pack just installed.

.................................................................................................................................................................................................

If required, repeat this procedure to install circuit packs in other Function Units.

.................................................................................................................................................................................................................................

4-46 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-10: Install TMUX circuit packs

7

.................................................................................................................................................................................................

Do you wish to provision circuit pack and/or port parameters at this time?

If...

Yes

No

Then...

Proceed to

Procedure 4-11: “Provision TMUX ports for service” (p. 4-48) .

STOP! End of Procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-47

Install and provision circuit packs/OLIUs procedures

Procedure 4-11: Provision TMUX ports for service

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision LNW18 TMUX circuit packs/ports for service.

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Ensure that TMUX circuit pack(s) are installed.

Step

1

2

3

4

Complete the following steps to provision TMUX circuit packs/ports for service.

.................................................................................................................................................................................................

From the System View window, click the

Alarm List

button to verify that no alarms, loopbacks, protection switch lockouts, or protection switches are present for the ports on the circuit packs just installed.

Result:

The NE Alarm List appears.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Equipment

.

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Find and highlight the TMUX circuit pack being provisioned, then click

Select

at the bottom of the window.

Result:

The circuit pack parameters appear.

.................................................................................................................................................................................................

Provision the required circuit pack parameters according to the work instructions, then click

Apply

if changes were made. If no changes were made, go to the next step.

.................................................................................................................................................................................................................................

4-48 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-11: Provision TMUX ports for service

5

6

7

8

9

10

11

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

to apply the changes.

.................................................................................................................................................................................................

Click

Close

to exit or continue with the next step to provision ports.

.................................................................................................................................................................................................

Find the TMUX circuit pack with the ports being provisioned, then expand the equipment list by clicking on the plus (+) signs.

.................................................................................................................................................................................................

Click (highlight) the port being provisioned, then click

Select

at the bottom of the window.

Result:

The port parameters appear.

.................................................................................................................................................................................................

Select and provision the required port parameters, according to your work instructions.

.................................................................................................................................................................................................

Important! The parameter settings may be applied to the selected port only or all ports on the circuit pack.

Select This Port or All Ports, This Pack in the

Apply to:

field according to the work instructions.

.................................................................................................................................................................................................

Click

Apply

to make provisioning changes. If no changes were made, continue with the next step.

Result:

If All Ports, This Pack was selected in the

Apply to:

field, a dialog box appears asking if you want to apply all parameter settings on the screen. Click

Yes

or

No

as required.

A dialog box may appear asking you to confirm executing this command. Verify that you are provisioning the correct port(s), then click

Yes

to apply your changes.

.................................................................................................................................................................................................

If required, repeat this procedure to provision other TMUX circuit packs/ports.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-49

Install and provision circuit packs/OLIUs procedures

Procedure 4-12: Install 10/100 Ethernet circuit packs

.................................................................................................................................................................................................................................

Overview

Use this procedure to install the following 10/100 Ethernet circuit packs:

•

LNW66 10/100-FE

•

LNW71 10/100-PL

•

LNW74 10/100-T/F

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to complete this procedure.

Required equipment

Use only the following Lucent Approved Class 1 SFP transceivers in the LNW74

10/100-T/F circuit pack.

Name

OMFE 100BASE-LX-SM

Pluggable Transmission

Module Code/Comcode

100BASE-LX-I1

109527812

Description

100 Mb/s optical Fast

Ethernet SFP TRCVR

Refer to the Metropolis

®

DMX Access Multiplexer Installation Manual, 365-372-304, as required, when removing and/or installing pluggable transmission modules.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Ensure that the appropriate Ethernet circuit pack(s) is available for installation.

5. If required, ensure that correct pluggable transmission modules are available for installation in the LNW74 circuit pack.

.................................................................................................................................................................................................................................

4-50 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures

Step

Procedure 4-12: Install 10/100 Ethernet circuit packs

1

2

3

4

Complete the following steps to install 10/100 Ethernet circuit pack(s).

.................................................................................................................................................................................................

Determine the Function Unit slots (A1, B1, C1, and/or D1) or Growth slot (G1) being equipped with circuit pack(s)

Important! The LNW66 or LNW71 circuit packs may only be installed in slot 1 of

Function groups A1, B1, C1, and/or D1. The LNW66 and LNW71 circuit packs cannot be installed in Growth slot G1.

The LNW74 circuit pack may be installed in Function groups A1, B1, C1, or D1 and/or Growth slot G1. If the LNW74 is installed in Growth slot G1, only the SFP

100Base-FX optical ports (17-24) will be available. The 10/100 Base-T electrical ports (1-16) will not be available on LNW74 circuit packs installed in Growth slot

G1.

.................................................................................................................................................................................................

For the LNW74 circuit pack only, ensure all optical fiber connectors and couplings are properly cleaned, if required.

Important! Signal performances may be degraded if the connections and couplings are not cleaned properly.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Important! Pluggable transmission modules are shipped with a dust plug installed into the optical ports to maintain cleanliness during storage and/or transportation. It is recommended that the dust plug be kept in place to maintain cleanliness until the optical fiber is connected. With proper care and handling, cleaning the pluggable transmission modules should not be necessary.

If required, clean any optical pluggable transmission module(s) being used.

Reference:

(p. 14-135)

Procedure 14-29: “Clean optical pluggable transmission module”

.................................................................................................................................................................................................

Important! If the Ethernet circuit pack is installed in Function Unit slot A2, B2,

C2, or D2 or Growth slot G2, the system reports a

CP not allowed - eqpt alarm.

Open both faceplate latches and seat the circuit pack in Function Unit slot A1, B1, C1, or D1 or Growth slot G1 (LNW74 only) by applying steady pressure to both faceplate latches.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-51

Install and provision circuit packs/OLIUs procedures Procedure 4-12: Install 10/100 Ethernet circuit packs

5

6

7

8

9

10

11

12

Result:

If a factory-fresh circuit pack is inserted, a firmware Smart Apply may begin (this is indicated by a blinking

ACTIVE

LED). The Smart Apply may take from 5-8 minutes and the user should wait for it to complete.

If the Smart Apply does not occur, the

FAULT

LED on the circuit pack lights. After approximately 100 seconds, the

ACTIVE

LED lights and the

FAULT

LED goes off.

TheWaveStar

®

CIT System View should reflect the new Ethernet pack in the appropriate slot.

.................................................................................................................................................................................................

Important! The LNW74 circuit pack ports 17-24 may be equipped with up to eight pluggable transmission modules.

If required, install pluggable transmission module(s).

Reference:

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62)

.................................................................................................................................................................................................

Install either a 177D apparatus blank or an LNW98 Detectable Blank circuit pack in the unequipped Function Unit slot A2, B2, C2, or D2 or Growth slot G2.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Equipment

.

Result:

The View Equipment window opens.

.................................................................................................................................................................................................

Verify presence of the new circuit pack in the equipment list.

.................................................................................................................................................................................................

Select (highlight) the new circuit pack, then click

Select

at bottom of window.

Result:

Circuit pack parameter values display on right side of window.

.................................................................................................................................................................................................

Verify that the

Circuit Pack State

for the circuit pack reads

In Service

.

.................................................................................................................................................................................................

Click

Close

to exit.

.................................................................................................................................................................................................

From the System View window, click the

Alarm List

button to verify that no alarms are present for the ports on the circuit packs just installed.

.................................................................................................................................................................................................................................

4-52 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-12: Install 10/100 Ethernet circuit packs

13

14

Result:

The NE Alarm List appears. No alarms should be present for the circuit pack just installed.

.................................................................................................................................................................................................

If required, repeat this procedure from

Step 1

to equip other slots with an Ethernet circuit pack.

.................................................................................................................................................................................................

If required, provision the circuit pack and/or port parameters.

Important! When a new Ethernet circuit pack is installed, Ethernet PM reporting is enabled and TCA reporting is disabled for each port and VCG. If changes are required, refer to

Procedure 8-5: “Provision performance monitoring (PM) settings”

(p. 8-8) .

Reference:

Procedure 4-14: “Provision Ethernet circuit pack/LAN port/VCG for service” (p. 4-59)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-53

Install and provision circuit packs/OLIUs procedures

Procedure 4-13: Install Gigabit Ethernet circuit packs

.................................................................................................................................................................................................................................

Overview

Use this procedure to install the following circuit packs:

•

LNW63 GBE PL

•

LNW67 1GbE-SX

•

LNW68 1GbE-LX

•

LNW70 100/1G FS

•

LNW78 100/1G FSR

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to complete this procedure.

Required equipment

Use only the following Lucent Approved Class 1 SFP transceivers in the LNW63,

LNW70, and LNW78 circuit packs.

Name Description Compatible

Circuit Packs

OM1G

1000BASE-ZX

Pluggable

Transmission

Module

Code/Comcode

1000BASE-ZX-I1

109541862

GbE SM SFP

TRCVR

LNW63

LNW70

LNW78

LNW63 OM1G//OMFC

1000BASE-LX//

100/200-SM-LL-L-I

OM1G//OMFC

1000BASE-SX//

100/200-M5/M6-

SN-S

OM1G//OMFC

1000BASE-LX//

100/200-SM-LL-L-I

GE-1X2XFC-LX-I1

109568782

GE-1X2XFC-SX-I1

109570606

GE-1X2XFC-

LX-C1

109527804

GbE SM SFP

TRCVR

GbE MM SFP

TRCVR

1X Fibre Channel or 2X Fibre

Channel or GbE

SM SFP TRCVR

LNW63

LNW70

LNW78

.................................................................................................................................................................................................................................

4-54 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-13: Install Gigabit Ethernet circuit packs

Name

OM1G//OMFC

1000BASE-SX//

100/200-M5/M6-

SN-S

OMFE

100BASE-LX-SM

EM1G//EMFE

1000BASE-T//

100BASE-T

Pluggable

Transmission

Module

Code/Comcode

GE-1X2XFC-SX-C1

109527796

100BASE-LX-I1

109527812

BASE-T-C1

109565549

Description

1X Fibre Channel or 2X Fibre

Channel or GbE

MM SFP TRCVR

100 Mb/s optical

Fast Ethernet SFP

TRCVR

10 Mb/s, 100 Mb/s and GbE Copper

SFP TRCVR

Compatible

Circuit Packs

LNW70

LNW78

LNW70

LNW78

LNW70

Refer to the Metropolis

®

DMX Access Multiplexer Installation Manual, 365-372-304, as required, when removing and/or installing pluggable transmission modules.

LNW70 circuit pack port configurations

The LNW70 circuit pack supports the following provisionable Ethernet port configurations for pluggable transmission modules:

•

GX_FX

: Ports 1-4 require optical Gigabit Ethernet pluggable transmission modules and Ports 5-8 require optical Fast Ethernet pluggable transmission modules.

•

GT_FX

: Ports 1-4 require electrical Gigabit Ethernet pluggable transmission modules and Ports 5-8 require optical Fast Ethernet pluggable transmission modules.

•

FT_FX

: Ports 1-4 require electrical Fast Ethernet pluggable transmission modules and Ports 5-8 require optical Fast Ethernet pluggable transmission modules.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure.

4. If installing the LNW70 circuit pack, verify that the work instructions specify the required pluggable transmission modules and Ethernet port configuration to be used.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-55

Install and provision circuit packs/OLIUs procedures Procedure 4-13: Install Gigabit Ethernet circuit packs

5. Ensure that the Gigabit Ethernet circuit pack(s) is available for installation.

6. If required, ensure that the correct pluggable transmission modules are available for installation in the LNW63 or LNW70 circuit pack.

Step

1

2

3

4

Complete the following steps to install the Gigabit Ethernet circuit pack(s).

.................................................................................................................................................................................................

Important! Gigabit Ethernet circuit packs may be installed in slots A1, B1, C1, D1 and/or G1. However, if you are using an LNW26B/28 (or equivalent) OLIU in

Main1 or Main2, there is a capacity limit of 24 STS-1s for circuit packs installed in slots A1, B1, and C1.

Determine the Function Unit slots (A1, B1, C1, D1 and/or G1) being equipped with

Gigabit Ethernet circuit pack(s).

.................................................................................................................................................................................................

Ensure all optical fiber connectors and couplings are properly cleaned.

Important! Signal performances may be degraded if the connections and couplings are not cleaned properly.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Important! Pluggable transmission modules are shipped with a dust plug installed into the optical ports to maintain cleanliness during storage and/or transportation. It is recommended that the dust plug be kept in place to maintain cleanliness until the optical fiber is connected. With proper care and handling, cleaning the pluggable transmission modules should not be necessary.

If required, clean the optical pluggable transmission module(s).

Reference:

(p. 14-135)

Procedure 14-29: “Clean optical pluggable transmission module”

.................................................................................................................................................................................................

Important! If the Gigabit Ethernet circuit pack is installed in Function Unit slot

A2, B2, C2, or D2 or Growth slot G2, the system reports a

CP not allowed eqpt alarm.

Open both faceplate latches and seat the Gigabit Ethernet circuit pack in Function Unit slot A1, B1, C1, D1 or G1.

.................................................................................................................................................................................................................................

4-56 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-13: Install Gigabit Ethernet circuit packs

5

6

7

8

9

10

11

12

Result:

If a factory fresh circuit pack is inserted, a firmware Smart Apply may begin (this is indicated by a blinking

ACTIVE

LED). The Smart Apply may take from 5-8 minutes and the user should wait for it to complete.

If the Smart Apply does not occur, the

FAULT

LED on the circuit pack lights. After approximately 100 seconds, the

ACTIVE

LED lights and the

FAULT

LED goes off.

The WaveStar

®

CIT System View should reflect the new circuit pack in the appropriate slot.

.................................................................................................................................................................................................

Important! The LNW63 and LNW70 Gigabit Ethernet circuit packs may be equipped with pluggable transmission modules. The LNW70 circuit pack supports three Ethernet port configurations. Refer to

“LNW70 circuit pack port configurations” (p. 4-55) .

If required, install pluggable transmission modules in the circuit pack according to the work instructions.

Reference:

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62)

.................................................................................................................................................................................................

Install either a 177D apparatus blank or an LNW98 Detectable Blank circuit pack in the unequipped Function Unit slot A2, B2, C2, D2 or G2.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Equipment

.

Result:

The View Equipment window opens.

.................................................................................................................................................................................................

Verify presence of the new circuit pack in the equipment list.

.................................................................................................................................................................................................

Select (highlight) the new circuit pack, then click

Select

at bottom of window.

Result:

Circuit pack parameter values display on right side of window.

.................................................................................................................................................................................................

Verify that the

Circuit Pack State

for the circuit pack reads

In Service

.

.................................................................................................................................................................................................

Click

Close

to exit.

.................................................................................................................................................................................................

From the System View window, click the

Alarm List

button to verify that no alarms are present for the ports on the circuit packs just installed.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-57

Install and provision circuit packs/OLIUs procedures Procedure 4-13: Install Gigabit Ethernet circuit packs

13

14

Result:

The NE Alarm List appears. No alarms should be present for the circuit pack just installed.

.................................................................................................................................................................................................

If required, repeat this procedure to equip other Function Slots with a Gigabit Ethernet circuit pack.

.................................................................................................................................................................................................

If required, provision the circuit pack and/or port parameters.

Important! When a new Ethernet circuit pack is installed, Ethernet PM reporting is enabled and TCA reporting is disabled for each port and VCG. If changes are required, refer to

Procedure 8-5: “Provision performance monitoring (PM) settings”

(p. 8-8) .

Reference:

Procedure 4-14: “Provision Ethernet circuit pack/LAN port/VCG for service” (p. 4-59)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

4-58 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures

Procedure 4-14: Provision Ethernet circuit pack/LAN port/VCG for service

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision Ethernet circuit pack/LAN ports/VCGs for service.

Important! Ethernet circuit packs/ports are provisioned for the type of service being provided. This procedure shows you how to access the parameters being provisioned, not how the parameters should be provisioned. Refer to your work instructions for parameter values or refer to

Chapter 11, “Ethernet/Data network provisioning procedures”

for examples of Ethernet service provisioning.

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions specify the circuit pack, LAN port, and/or VCG parameters/values to be provisioned.

4. Ensure that the circuit pack(s) is installed. If the circuit pack is not installed, refer to

Procedure 4-12: “Install 10/100 Ethernet circuit packs” (p. 4-50)

or

Procedure

4-13: “Install Gigabit Ethernet circuit packs” (p. 4-54) .

5. If required, ensure appropriate pluggable transmission module(s) is installed.

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62)

Step

1

2

Complete the following steps to provision the Ethernet circuit pack/LAN ports/VCGs.

.................................................................................................................................................................................................

From the System View menu, click the

Alarm List

button to verify that no alarms are present for the ports on the circuit packs to be provisioned.

Result:

The NE Alarm List appears.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Equipment

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-59

Install and provision circuit packs/OLIUs procedures Procedure 4-14: Provision Ethernet circuit pack/LAN port/VCG for service

3

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Find and click (highlight) the Ethernet circuit pack being provisioned, then click

Select

at the bottom of the window.

Result:

The circuit pack parameters appear.

4

5

6

.................................................................................................................................................................................................

Provision the circuit pack parameters as required, then click

Apply

if changes were made. If no changes were made, continue with

Step 5 .

Result:

A dialog box may appear asking you to confirm executing this command.

Click

Yes

to apply changes.

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

.................................................................................................................................................................................................

Click

Close

to exit or continue with

Step 6

to provision LAN ports/VCGs.

.................................................................................................................................................................................................

Find the circuit pack with the LAN ports/VCGs being provisioned, then expand the equipment list by clicking on the plus (+) sign next to the circuit pack.

.................................................................................................................................................................................................

7 If the circuit pack is...

equipped with pluggable transmission modules,

not equipped with pluggable transmission modules,

Then...

Perform the following:

1. Click (highlight) the required pluggable transmission module (PTM) being provisioned, then click

Select

at the bottom of the window.

2. Provision the required pluggable transmission module parameters according to the work instructions, then click

Apply

if changes were made. If no changes were made, continue with

Step 8 .

continue with

Step 8 .

8

.................................................................................................................................................................................................

Click (highlight) the LAN port/VCG being provisioned, then click

Select

at the bottom of the window.

.................................................................................................................................................................................................................................

4-60 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-14: Provision Ethernet circuit pack/LAN port/VCG for service

9

10

11

Result:

The LAN port/VCG parameters appear.

.................................................................................................................................................................................................

Select and provision the parameters, according to your work instructions.

Reference:

•

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

•

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

.................................................................................................................................................................................................

Click

Apply

to make provisioning changes. If no changes were made, continue with

Step 11 .

Result:

A dialog box may appear asking you to confirm executing this command.

Click

Yes

to apply changes.

.................................................................................................................................................................................................

If required, repeat procedure from

Step 8

through

Step 10

to provision additional LAN ports/VCGs.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-61

Install and provision circuit packs/OLIUs procedures

Procedure 4-15: Install pluggable transmission modules

.................................................................................................................................................................................................................................

Overview

Use this procedure to install a pluggable transmission module in a circuit pack.

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to complete this procedure.

Required equipment

Use only the following Lucent Approved Class 1 SFP transceivers.

Name Qualifier

EM1G//EMFE 1000BASE-

T//100BASE-T

Pluggable

Transmission

Module

Code/Comcode

BASE-T-C1

109565549

Description

OM155

OM155

OM622

OM622

OM1G

1.3LR1

1.3IR1

1.3LR1

1.3IR1

1000BASE-ZX

OM1G//OMFC 1000BASE-

LX//100/200-SM-

LL-L-I

OM1G//OMFC 1000BASE-

SX//100/200-

M5/M6-SN-S

OC3LR1-I1

109453886

OC3IR1-I1

109453894

OC12LR1-I1

109467522

OC12IR1-I1

109453902

1000BASE-ZX-I1

109541862

GE-1X2XFC-

LX-C1

109527804

GE-1X2XFC-

SX-C1

109527796

Compatible

Circuit Packs

FE and GbE electrical SFP

TRCVR

OC3 SFP TRCVR

Long Reach - LR1

OC3 SFP TRCVR

Intermediate Reach

- IR1

OC12 SFP TRCVR

Long Reach - LR1

OC12 SFP TRCVR

Intermediate Reach

- IR1

GbE SM SFP

TRCVR

1X Fibre Channel or 2X Fibre

Channel or GbE

SM SFP TRCVR

1X Fibre Channel or 2X Fibre

Channel or GbE

MM SFP TRCVR

LNW70

LNW37, LNW45

LNW37, LNW45

LNW49

LNW49

LNW63

LNW70

LNW70, LNW73,

LNW73C, LNW78

LNW70, LNW73,

LNW73C, LNW78

.................................................................................................................................................................................................................................

4-62 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-15: Install pluggable transmission modules

Name

OMFE

Qualifier

OM1G//OMFC 1000BASE-

OMESCON

LX//100/200-SM-

LL-L-I

OM1G//OMFC 1000BASE-

SX//100/200-

M5/M6-SN-S

MMF

100BASE-LX-SM

Pluggable

Transmission

Module

Code/Comcode

GE-1X2XFC-LX-I1

109568782

Description

GbE SM SFP

TRCVR

GE-1X2XFC-SX-I1

109570606

GbE MM SFP

TRCVR

ESCON-MM-I1

109523886

100BASE-LX-I1

109527812

ESCON MM SFP

TRCVR

100 Mb/s optical

Fast Ethernet SFP

TRCVR

Compatible

Circuit Packs

LNW63

LNW63

LNW73, LNW73C

LNW70, LNW74,

LNW78

Refer to the Metropolis

®

DMX Access Multiplexer Installation Manual, 365-372-304, as required, when removing and/or installing pluggable transmission modules.

LNW70 100/1G-FS circuit pack port configurations

The LNW70 100/1G-FS circuit pack supports the following provisionable Ethernet port configurations for pluggable transmission modules:

•

GX_FX

: Ports 1-4 require optical Gigabit Ethernet pluggable transmission modules and Ports 5-8 require optical Fast Ethernet pluggable transmission modules.

•

GT_FX

: Ports 1-4 require electrical Gigabit Ethernet pluggable transmission modules and Ports 5-8 require optical Fast Ethernet pluggable transmission modules.

•

FT_FX

: Ports 1-4 require electrical Fast Ethernet pluggable transmission modules and Ports 5-8 require optical Fast Ethernet pluggable transmission modules.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Verify that the work instructions specify the required pluggable transmission module, circuit pack, and socket.

5. Ensure that the correct pluggable transmission module is available for installation.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-63

Install and provision circuit packs/OLIUs procedures

Step

Procedure 4-15: Install pluggable transmission modules

1

2

Complete the following steps to install a pluggable transmission module in a circuit pack that has already been installed in the shelf.

.................................................................................................................................................................................................

Determine the circuit pack and socket being equipped with the pluggable transmission module.

.................................................................................................................................................................................................

Hold the connector/latch-end of the module in your left hand with the gold fingers facing you. The module should be positioned in manner similar to

Figure 4-8,

“Pluggable transmission module with dust plug (Optical PTMs only)” (p. 4-64) .

Figure 4-8 Pluggable transmission module with dust plug (Optical PTMs only)

MA-DMX-422

Important! Do not remove the dust plug unless you are ready to connect cabling or if you need to clean the module.

Dust plugs (Optical PTMs only)

There are a variety of different types of dust plugs. Any of the following examples could be similar to the dust plug in your pluggable transmission module.

Figure 4-9 Examples of dust plugs

MA-DMX-421

.................................................................................................................................................................................................................................

4-64 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-15: Install pluggable transmission modules

3

.................................................................................................................................................................................................

Referring to the figure below, determine the type of latching mechanism on the pluggable transmission module you have.

1

Gold Fingers

Port

2

Gold Fingers

Port

3

Port

Gold Fingers

MA-DMX-445

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-65

Install and provision circuit packs/OLIUs procedures

4

Port

5

Port

Procedure 4-15: Install pluggable transmission modules

Gold Fingers

Gold Fingers

6

Port

Gold Fingers

MA-DMX-439

7

Port

Gold Fingers

8

Gold Fingers

Port

MA-DMX-442

4

.................................................................................................................................................................................................

Important! Optical pluggable transmission modules are shipped with a dust plug installed into the ports to maintain cleanliness during storage and/or transportation.

It is recommended that the dust plug be kept in place to maintain cleanliness until

.................................................................................................................................................................................................................................

4-66 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-15: Install pluggable transmission modules

5

the cabling is connected. With proper care and handling, cleaning the pluggable transmission modules should not be necessary.

If required, clean the optical pluggable transmission module.

Reference:

(p. 14-135)

Procedure 14-29: “Clean optical pluggable transmission module”

.................................................................................................................................................................................................

Referring to

Step 3 , what type of latching mechanism does your module have?

If...

Type 1 or 2 (optical)

Type 3 (optical)

Type 4, 5, or 6 (optical)

Type 7 or 8 (electrical)

Then...

Proceed to

Step 9 .

Continue with

Step 6 .

Proceed to

Step 8 .

Proceed to

Step 8 .

6

.................................................................................................................................................................................................

Before inserting the module, the latch must be in the closed position. With the dust plug in place, the latch is in the closed position.

Figure 4-10 shows the open and closed position of the latch. Depending on your PTM type, the appearance of the port opening and latch mechanism may vary.

Figure 4-10 Latch type 3 (opened and closed)

Swivel Latch

Open Position

(to the left)

Swivel Latch

Closed Position

(to the right)

MA-DMX-423

7

.................................................................................................................................................................................................

Proceed to

Step 9 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-67

Install and provision circuit packs/OLIUs procedures Procedure 4-15: Install pluggable transmission modules

8

.................................................................................................................................................................................................

Before inserting the module, the latch must be in the closed position. With the dust plug in place, the latch is in the closed position.

Figure 4-11 shows the open and closed position of the latch. Depending on your PTM type, the appearance of the port opening and latch mechanism may vary.

Figure 4-11 Latch type 4, 5, 6, 7 and 8 (opened and closed)

Swivel Latch

Closed Position

(to the left)

Swivel Latch

Open Position

(to the right)

MA-DMX-424

9

10

.................................................................................................................................................................................................

With your left hand, hold the pluggable transmission module by the dust plug (optical) or port end (electrical). The ports are in your left hand and the gold fingers are visible

(facing you). (Do not insert pluggable transmission module).

.................................................................................................................................................................................................

Rotate the module; the dust plug or port end is facing you and the gold fingers are pointing away from you and are facing to the right. (Do not insert pluggable transmission module).

.................................................................................................................................................................................................................................

4-68 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-15: Install pluggable transmission modules

11

.................................................................................................................................................................................................

Insert the pluggable transmission module in the required socket of the circuit pack faceplate. Confirm that the pluggable transmission module is locked in the socket.

Verify that all unused sockets on the circuit pack are equipped with dust covers.

Figure 4-12 Insert pluggable transmission module into socket

Socket

Gold Fingers

MA-DMX-427

Result:

The port appears in the WaveStar

®

CIT System View indicating successful installation.

If response is not correct, replace the pluggable transmission module. If the pluggable transmission module fails when inserted, and another pluggable transmission module in the shelf fails at the same time, replace the newly-installed pluggable transmission module. Each pluggable transmission module has unique internal data for warranty purposes. If this data for any reason is not unique, both pluggable transmission modules with the duplicated information will be declared failed. For information on replacing a pluggable transmission module, refer to the

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble Clearing

Guide, 365-372-302.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-69

Install and provision circuit packs/OLIUs procedures Procedure 4-15: Install pluggable transmission modules

12

.................................................................................................................................................................................................

Push on the dust plug or port end to insert the module. The latch automatically catches when the module is inserted. The module is secure.

To verify that the pluggable transmission module is properly latched in the cage, gently pull the pluggable transmission module (parallel to the direction the pluggable transmission module was installed). Do not rotate the swivel latch or activate the de-latching feature on the pluggable transmission module.

13

.................................................................................................................................................................................................

If installing a pluggable transmission module in an...

Optical OLIU circuit pack,

Ethernet/DATA circuit pack,

Then...

Continue with

Proceed to

Step 14

Step 18 .

14

15

16

17

.................................................................................................................................................................................................

To test the OC-n optical port on installed OLIU circuit packs, loop back the OC-n optical port.

Reference:

Procedure 14-6: “Connect OLIU optical loopbacks” (p. 14-56)

.................................................................................................................................................................................................

Remove the lightguide jumper used to loop back the OC-n optical port and the LBO, if required.

Result:

The port LED starts flashing. The

MN

and

NE

LEDs are lighted on the

SYSCTL circuit pack.

.................................................................................................................................................................................................

From the System View window, select

Configuration

→

Update System

→

Update

All

.

Result:

The port LED stops flashing. All alarms are cleared.

.................................................................................................................................................................................................

Is a second (protection) pluggable transmission module required in a companion OLIU circuit pack?

If...

Yes

No

Then...

Repeat procedure from

Step 1 .

Continue with

Step 18 .

.................................................................................................................................................................................................................................

4-70 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-15: Install pluggable transmission modules

18

19

.................................................................................................................................................................................................

From the System View menu, click the

Alarm List

button to verify that no alarms are present for the ports just installed on the circuit packs.

Result:

installed.

The NE Alarm List appears. No alarms should be present for the ports just

.................................................................................................................................................................................................

Do you wish to install additional pluggable transmission modules?

If...

Yes

No

Then...

Repeat procedure from

Step 1 .

Continue with

Step 20 .

20

.................................................................................................................................................................................................

Do you wish to provision circuit pack and/or port parameters for service at this time?

If...

Yes

No

Then...

Proceed to

Procedure 4-4: “Provision OLIU circuit packs/ports for service” (p. 4-22)

,

Procedure 4-14: “Provision Ethernet circuit pack/LAN port/VCG for service” (p. 4-59) , or

Procedure 4-18: “Provision Fibre Channel circuit pack/Data port/VCG for service” (p. 4-77) .

STOP! End of Procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-71

Install and provision circuit packs/OLIUs procedures

Procedure 4-16: Install LNW80 switch pack

.................................................................................................................................................................................................................................

Overview

Use this procedure to install LNW80 Switch circuit packs in Main slots

M1

and

M2

.

The LNW80 Switch circuit pack has no optics and is used in headless main applications to allow full use of the VT1.5 switch fabric for VT1.5-type hairpin cross-connections. The LNW80 circuit pack supports equipment-related alarms.

The LNW80 Switch circuit pack requires no provisioning and does not support loopbacks, test access, performance monitoring, DCC functionality, incoming signal alarms, line timing, DS1 synchronization outputs, and upgrades. The LNW80 Switch circuit pack cannot be a cross-connection source or destination.

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

Step

1

2

Perform the following to install LNW80 Switch circuit packs in Main slots

M1

and

M2

.

.................................................................................................................................................................................................

Seat the first Switch Pack in Main slot

M1

.

Result:

The

FAULT

LED and

ACTIVE

LED lights. The

FAULT

LED flashes after about 20 seconds and then goes off (See below for exception).

MJ

or

MN

and

NE

alarm LEDs on the SYSCTL circuit pack light when the circuit pack is installed.

If this system is set to external timing and the external timing reference is not yet available, the

FAULT

LED continues blinking until a good DS1 sync reference is available.

.................................................................................................................................................................................................

Seat the second Switch Pack circuit pack in Main slot

M2

.

.................................................................................................................................................................................................................................

4-72 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-16: Install LNW80 switch pack

Result:

The

FAULT

LED and

ACTIVE

LED lights. The

FAULT

LED flashes after about 20 seconds and then goes off.

MJ

or

MN

and

NE

alarm LEDs on the SYSCTL circuit pack light when the circuit pack is installed.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-73

Install and provision circuit packs/OLIUs procedures

Procedure 4-17: Install Fibre Channel circuit packs

.................................................................................................................................................................................................................................

Overview

Use this procedure to install the LNW73/LNW73C Fibre Channel circuit pack.

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to complete this procedure.

Required equipment

Use only the following Lucent Approved Class 1 SFP transceivers in the

LNW73/LNW73C circuit pack.

Name Description

OMESCON MMF

OM1G//OMFC

1000BASE-LX//100/200-

SM-LL-L-I

OM1G//OMFC

1000BASE-SX//100/200-

M5/M6-SN-S

Pluggable Transmission

Module Code/Comcode

ESCON-MM-I1

109523886

GE-1X2XFC-LX-C1

109527804

GE-1X2XFC-SX-C1

109527796

ESCON MM SFP TRCVR

1X Fibre Channel or 2X

Fibre Channel or GbE SM

SFP TRCVR

1X Fibre Channel or 2X

Fibre Channel or GbE MM

SFP TRCVR

Refer to the Metropolis

®

DMX Access Multiplexer Installation Manual, 365-372-304, as required, when removing and/or installing pluggable transmission modules.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Ensure that the Fibre Channel circuit pack(s) is available for installation.

4. Obtain your work instructions for this procedure.

5. Ensure that the correct pluggable transmission modules are available for installation in the LNW73/LNW73C circuit pack.

.................................................................................................................................................................................................................................

4-74 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures

Step

Procedure 4-17: Install Fibre Channel circuit packs

1

2

3

4

5

Complete the following steps to install the Fibre Channel circuit pack(s).

.................................................................................................................................................................................................

Important! Fibre Channel circuit packs may be installed in slots A1, B1, C1, D1 and/or G1. However, if you are using an LNW26B/28 (or equivalent) OLIU in

Main1 or Main2, there is a capacity limit of 24 STS-1s for circuit packs installed in slots A1, B1, and C1.

Determine the Function Unit slots (A1, B1, C1, D1 and/or G1) being equipped with

Fibre Channel circuit pack(s).

.................................................................................................................................................................................................

Ensure all optical fiber connectors and couplings are properly cleaned.

Important! Signal performances may be degraded if the connections and couplings are not cleaned properly.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Important! Pluggable transmission modules are shipped with a dust plug installed into the optical ports to maintain cleanliness during storage and/or transportation. It is recommended that the dust plug be kept in place to maintain cleanliness until the optical fiber is connected. With proper care and handling, cleaning the pluggable transmission modules should not be necessary.

If required, clean the optical pluggable transmission module(s).

Reference:

(p. 14-135)

Procedure 14-29: “Clean optical pluggable transmission module”

.................................................................................................................................................................................................

Important! If the Fibre Channel circuit pack is installed in Function Unit slot A2,

B2, C2, or D2 or Growth slot G2, the system reports a

CP not allowed - eqpt alarm.

Open both faceplate latches and seat the Fibre Channel circuit pack in Function Unit slot A1, B1, C1, D1 or G1.

Result:

The circuit pack appears in the appropriate slot of the WaveStar

®

System View indicating successful installation.

CIT

.................................................................................................................................................................................................

Install the required pluggable transmission module(s).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-75

Install and provision circuit packs/OLIUs procedures Procedure 4-17: Install Fibre Channel circuit packs

6

7

8

9

10

11

12

13

14

Reference:

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62)

.................................................................................................................................................................................................

Install either a 177D apparatus blank or an LNW98 Detectable Blank circuit pack in the unequipped Function Unit slot A2, B2, C2, D2 or G2.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Equipment

.

Result:

The View Equipment window opens.

.................................................................................................................................................................................................

Verify presence of the new circuit pack in the equipment list.

.................................................................................................................................................................................................

Select (highlight) the new circuit pack, then click

Select

at bottom of window.

Result:

Circuit pack parameter values display on right side of window.

.................................................................................................................................................................................................

Verify that the

Circuit Pack State

for the circuit pack reads

In Service

.

.................................................................................................................................................................................................

Click

Close

to exit.

.................................................................................................................................................................................................

From the System View window, click the

Alarm List

button to verify that no alarms are present for the ports on the circuit packs just installed.

Result:

The NE Alarm List appears. No alarms should be present for the circuit pack just installed.

.................................................................................................................................................................................................

If required, repeat this procedure to equip other Function Slots with a Fibre Channel circuit pack.

.................................................................................................................................................................................................

If required, provision the circuit pack, Data port, and/or VCG parameters.

Important! When the circuit pack is installed, PM reporting is enabled and TCA reporting is disabled for each Data port and VCG. If changes are required, refer to

Procedure 8-5: “Provision performance monitoring (PM) settings” (p. 8-8) .

Reference:

Procedure 4-18: “Provision Fibre Channel circuit pack/Data port/VCG for service” (p. 4-77)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

4-76 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures

Procedure 4-18: Provision Fibre Channel circuit pack/Data port/VCG for service

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision Fibre Channel circuit pack/Data ports/VCGs for service.

Important! Fibre Channel circuit packs/Data ports/VCGs are provisioned for the type of service being provided. This procedure shows you how to access the parameters being provisioned, not how the parameters should be provisioned. Refer to your work instructions for parameter values or refer to

Chapter 11,

“Ethernet/Data network provisioning procedures”

for examples of service provisioning.

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Obtain work instructions for this procedure.

3. Ensure that the circuit pack(s) is installed. If the circuit pack is not installed, refer to

Procedure 4-17: “Install Fibre Channel circuit packs” (p. 4-74)

.

4. Ensure that the appropriate pluggable transmission module(s) is installed.

Procedure

4-15: “Install pluggable transmission modules” (p. 4-62)

Step

1

2

Complete the following steps to provision the Fibre Channel circuit pack/Data ports/VCGs.

.................................................................................................................................................................................................

From the System View menu, click the

Alarm List

button to verify that no alarms are present for the circuit packs to be provisioned.

Result:

The NE Alarm List appears.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Equipment

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-77

Install and provision circuit packs/OLIUs procedures Procedure 4-18: Provision Fibre Channel circuit pack/Data port/VCG for service

3

4

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Find and click (highlight) the Fibre Channel circuit pack being provisioned, then click

Select

at the bottom of the window.

Result:

The circuit pack parameters appear.

.................................................................................................................................................................................................

Important! When the

Data Type

parameter is provisioned FC-FICON, the Data ports on the circuit pack can be configured individually for Fibre Channel or

FICON. When the

Data Type

parameter is provisioned ESCON, all Data ports on the circuit pack are configured for ESCON.

Provision the circuit pack parameters as required, then click

Apply

if changes were made. If no changes were made, continue with

Step 5 .

Reference:

Procedure 11-36: “Provision LNW73/LNW73C FC-DPORT circuit pack parameters” (p. 11-271)

5

6

.................................................................................................................................................................................................

Click

Close

to exit or continue with

Step 6

to provision Data ports/VCGs.

.................................................................................................................................................................................................

Find the circuit pack with the Data ports/VCGs being provisioned, then expand the equipment list by clicking on the plus (+) sign next to the circuit pack.

.................................................................................................................................................................................................

7 If the circuit pack is...

equipped with pluggable transmission modules,

not equipped with pluggable transmission modules,

Then...

Perform the following:

1. Click (highlight) the required pluggable transmission module (PTM) being provisioned, then click

Select

at the bottom of the window.

2. Provision the required pluggable transmission module parameters according to the work instructions, then click

Apply

if changes were made. If no changes were made, continue with

Step 8 .

continue with

Step 8 .

.................................................................................................................................................................................................................................

4-78 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-18: Provision Fibre Channel circuit pack/Data port/VCG for service

8

9

10

11

.................................................................................................................................................................................................

Click (highlight) the Data port/VCG being provisioned, then click

Select

at the bottom of the window.

Result:

The Data port/VCG parameters appear.

.................................................................................................................................................................................................

Select and provision the parameters, according to your work instructions.

Reference:

(p. 11-273)

Procedure 11-37: “Provision FC-DPORT DATA port parameters”

Procedure 11-38: “Provision FC-DPORT VCG parameters” (p. 11-277)

.................................................................................................................................................................................................

Click

Apply

to make provisioning changes. If no changes were made, continue with

Step 11 .

Result:

A dialog box may appear asking you to confirm executing this command.

Click

Yes

to apply changes.

.................................................................................................................................................................................................

If required, repeat

Step 8

through

Step 10

to provision additional Data ports/VCGs.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-79

Install and provision circuit packs/OLIUs procedures

Procedure 4-19: Provision pluggable transmission module

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision pluggable transmission modules.

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify the work instruction specify the parameters and values to be provisioned.

Step

Complete the following steps to provision pluggable transmission modules.

1

2

.................................................................................................................................................................................................

From the System View window, select

Configuration

→

Equipment

.

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Find the circuit pack with the pluggable transmission modules being provisioned, then expand the equipment list by clicking on the plus (+) sign next to the required circuit pack. Select the required PTM and click

Select

.

Result:

The pluggable transmission module parameters appear.

.................................................................................................................................................................................................

3

Provision the required pluggable transmission module parameters according to the work instructions, then click

Apply

if changes were made. If no changes were made, click

Close

to exit.

Result:

A dialog box may appear asking you to confirm executing this command.

Click

Yes

to apply the changes. Click

Close

to exit.

If the Maintenance State parameter is provisioned Maint,

Pluggable transmission module maintenance IP and

ABN condition are reported. While in the Maintenance state, any subsequent removal of the pluggable transmission module is reported with an alarm severity level no higher than a standing condition regardless of the assigned ASAP alarm severity level. Changing the Maintenance state does not affect the alarm severity level of any existing removal alarms.

.................................................................................................................................................................................................................................

4-80 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-19: Provision pluggable transmission module

4

.................................................................................................................................................................................................

If required, repeat this procedure to provision other pluggable transmission modules.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-81

Install and provision circuit packs/OLIUs procedures

Procedure 4-20: Provision non-volatile memory cards

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision non-volatile memory cards in the SYSCTL.

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify the work instruction specify the parameters and values to be provisioned.

Step

1

2

3

4

Complete the following steps to provision non-volatile memory cards in the SYSCTL circuit pack.

.................................................................................................................................................................................................

From the System View window, select

Configuration

→

Equipment

.

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Expand the SYSCTL list by clicking on the plus (+) sign next to the required circuit pack. Select the required NVM and click

Select

.

Result:

The Non-Volatile Memory Information appears.

.................................................................................................................................................................................................

Provision Alarm Severity Assignment Profile according to the work instructions, then click

Apply

if changes were made. If no changes were made, click

Close

to exit.

Result:

A dialog box may appear asking you to confirm executing this command.

Click

Yes

to apply the changes. Click

Close

to exit.

.................................................................................................................................................................................................

If required, repeat this procedure to provision the other NVM.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

4-82 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures

Procedure 4-21: Provision STS-n/VT1.5 tributary

.................................................................................................................................................................................................................................

Overview

Use this procedure to an STS-n/VT1.5 tributary.

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify the work instruction specify the parameters and values to be provisioned.

Step

1

2

3

4

Complete the following steps to provision an STS-n/VT1.5 tributary.

.................................................................................................................................................................................................

From the System View window, select

Configuration

→

Equipment

.

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Find the circuit pack with the STS-n/VT1.5 tributary being provisioned, then expand the equipment list by clicking on the plus (+) sign next to the required circuit pack and port. Select the required tributary and click

Select

.

Result:

The tributary parameters appear.

.................................................................................................................................................................................................

Provision the required tributary parameters according to the work instructions, then click

Apply

if changes were made. If no changes were made, click

Close

to exit.

Result:

A dialog box may appear asking you to confirm executing this command.

Click

Yes

to apply the changes. Click

Close

to exit.

.................................................................................................................................................................................................

If required, repeat this procedure to provision other tributaries.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-83

Install and provision circuit packs/OLIUs procedures

Procedure 4-22: Change circuit pack mode of LNW26B,

LNW28, LNW77, or LNW121B-159B OC-48 OLIU circuit packs

.................................................................................................................................................................................................................................

Overview

Use this procedure to change the Circuit Pack Mode of the LNW26B, LNW28,

LNW77, or LNW121B-159B OC-48 OLIU circuit packs installed in the Main slots.

Important! This procedure supports changing the Circuit Pack Mode parameter from Normal to Enhanced only. Changing the Circuit Pack Mode parameter from

Enhanced to Normal is not supported.

Normal/Enhanced jumper

The LNW26B, LNW28, LNW77, or LNW121B-159B OC-48 OLIU circuit packs are equipped with a Normal/Enhanced jumper used to provision the Circuit Pack Mode parameter. (The Circuit Pack Mode parameter is not CIT provisionable.) If the

Normal/Enhanced jumper is in the Normal position, the circuit pack can cross-connect

VT1.5 signals in up to any 6 STS-1 signals. If the Normal/Enhanced jumper is in the

Enhanced position, the circuit pack can cross-connect VT1.5 signals in up to any 12

STS-1 signals.

.................................................................................................................................................................................................................................

4-84 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-22: Change circuit pack mode of LNW26B,

LNW28, LNW77, or LNW121B-159B OC-48 OLIU circuit packs

Refer to the following figure for the location of the Normal/Enhanced jumper and the jumper settings.

Enhanced

Normal

Enhanced

Normal nc-dmx-246

Privilege level

You must log in as a Privileged or General user to complete this procedure.

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-85

Install and provision circuit packs/OLIUs procedures Procedure 4-22: Change circuit pack mode of LNW26B,

LNW28, LNW77, or LNW121B-159B OC-48 OLIU circuit packs

Before you begin

Prior to performing this procedure:

1. Refer to

“Required equipment” (p. 4-3)

and

“Before you begin” (p. 4-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions specify the high-speed network configuration (for example, UPSR or BLSR).

Step

1

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to change the Circuit Pack Mode of the LNW26B,

LNW28, LNW77, or LNW121B-159B OC-48 OLIU circuit packs installed in the Main slots.

.................................................................................................................................................................................................

Click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the NE Alarm List and verify that no alarms are present.

Refer to the appropriate trouble clearing procedures to clear all existing alarms before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

2

.................................................................................................................................................................................................

To verify that no loopbacks, protection switch lockouts, or protection switches are present, select

View

→

Rolling Events

. Under the line reading

RTRV-COND-ALL determine if any loopbacks, protection switch lockouts, or protection switches are displayed.

Remove all existing loopbacks, protection switch lockouts, or protection switches before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

3

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and verify that no test access sessions exist.

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and delete all existing test access sessions.

.................................................................................................................................................................................................................................

4-86 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-22: Change circuit pack mode of LNW26B,

LNW28, LNW77, or LNW121B-159B OC-48 OLIU circuit packs

Reference:

•

Procedure 14-27: “View test access session(s)” (p. 14-130)

•

Procedure 14-26: “Delete test access session” (p. 14-129)

.................................................................................................................................................................................................

4

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 11 .

Continue with

Step 5 .

5

6

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before removing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-87

Install and provision circuit packs/OLIUs procedures Procedure 4-22: Change circuit pack mode of LNW26B,

LNW28, LNW77, or LNW121B-159B OC-48 OLIU circuit packs

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

7

.................................................................................................................................................................................................

If required, repeat

Step 5

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for timing.

8

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-48 OLIU circuit pack in Main slot

M1

.

If ...

UPSR,

BLSR or 1+1,

Then...

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m1-()-() paths supported by the circuit pack in Main slot

M1

(Ring

1). Record the active paths supported by the circuit pack in Main slot

M1

(Ring 1).

Click

Close

.

Select

Reports

→

Status Lists

→

Pack

.

Click Shelf and

Select

. Observe the value of the Switch State parameter for the

main-1 circuit pack. If the Switch State parameter is ACTIVE, some Function units are receiving traffic from the main-1 circuit pack. Click

Close

.

9

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, optional manual switches can be performed before removing the circuit pack in Main slot

M1

. In UPSRs, each path supported by the circuit pack in Main slot

M1

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

.................................................................................................................................................................................................................................

4-88 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-22: Change circuit pack mode of LNW26B,

LNW28, LNW77, or LNW121B-159B OC-48 OLIU circuit packs

If the OC-48 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 10 .

If...

UPSR,

BLSR,

1+1,

Then to perform an optional manual transmission switch...

Select

Fault

→

Protection Switch

. Expand

Path Protection, click on the required

m-1-() path and

Select

. Select the Manual

Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command. Click

Yes

.

The system reports a manual switch condition for the affected path.

Repeat for each path supported by the circuit pack in Main slot

M1

. Click

Close

.

Select

Fault

→

Protection Switch

. Click on

2F BLSR main-1-1 and

Select

. Select the

West Direction and Manual to Protection,

Ring Switch Type, and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command. Click

Yes

and

Close

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the Alarm List shows the

Protection Switch, OC48

Port, Manual Switch, MSR, 2F condition (Not Alarmed).

Select

Fault

→

Protection Switch

. Click on

1+1 Line main-1-1 and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command. Click

Yes

and

Close

.

The system reports a manual switch condition for the affected OC-n line.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-89

Install and provision circuit packs/OLIUs procedures Procedure 4-22: Change circuit pack mode of LNW26B,

LNW28, LNW77, or LNW121B-159B OC-48 OLIU circuit packs

.................................................................................................................................................................................................

10

If required, repeat

Step 8

to verify that the OC-48 OLIU circuit pack in Main slot is now the active circuit pack for transmission.

M2

.................................................................................................................................................................................................

11

Important! The Circuit Pack mode of the OC-48 OLIU circuit pack in Main slot

M1 must be changed first.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

and remove the circuit pack from the slot.

Result:

Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M1

. If active through traffic exists on the circuit pack in Main slot

M1

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped (UPSRs/BLSRs only).

.................................................................................................................................................................................................

12

13

Important! When the Normal/Enhanced jumper is placed in the Normal position, the circuit pack can cross-connect VT1.5 signals in up to any 6 STS-1 signals.

When the Normal/Enhanced jumper is placed in the Enhanced position, the circuit pack can cross-connect VT1.5 signals in up to any 12 STS-1 signals.

Change the Normal/Enhanced jumper on the OC-48 OLIU circuit pack to the

Enhanced position. Refer to

“Normal/Enhanced jumper” (p. 4-84)

for the location of the Normal/Enhanced jumper and the jumper settings.

.................................................................................................................................................................................................

Install the OC-48 OLIU circuit pack in Main slot

M1

, clean all fiber connectors, and connect the transmit and receive optical fibers.

Result:

The system reports an unexpected CP type alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

14

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system performs automatic protection switches. Transmission hits (less than 60 ms) occur as active traffic is automatically switched from the circuit pack in Main

.................................................................................................................................................................................................................................

4-90 365-372-301 R6.0

Issue 15, January 2006

Install and provision circuit packs/OLIUs procedures Procedure 4-22: Change circuit pack mode of LNW26B,

LNW28, LNW77, or LNW121B-159B OC-48 OLIU circuit packs slot

M2

to the circuit pack in Main slot

M1

. All traffic is now active on the circuit pack in Main slot

M1

.

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an unexpected CP type alarm for Main slot

M2

.

.................................................................................................................................................................................................

15

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

and remove the circuit pack from the slot.

Result:

Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M2

. If active through traffic exists on the circuit pack in Main slot

M2

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped (UPSRs/BLSRs only).

.................................................................................................................................................................................................

16

Important! When the Normal/Enhanced jumper is placed in the Normal position, the circuit pack can cross-connect VT1.5 signals in up to any 6 STS-1 signals.

When the Normal/Enhanced jumper is placed in the Enhanced position, the circuit pack can cross-connect VT1.5 signals in up to any 12 STS-1 signals.

Change the Normal/Enhanced jumper on the OC-48 OLIU circuit pack to the

Enhanced position. Refer to

“Normal/Enhanced jumper” (p. 4-84)

for the location of the Normal/Enhanced jumper and the jumper settings.

17

.................................................................................................................................................................................................

Install the OC-48 OLIU circuit pack in Main slot

M2

, clean all fiber connectors, and connect the transmit and receive optical fibers.

Result:

All alarms clear and service is restored.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

4-91

5

5

Overview

.................................................................................................................................................................................................................................

Purpose

This chapter includes procedures that are necessary to equip and test a new

Metropolis

®

DMX Access Multiplexer.

Contents

Before you begin

Procedure 5-1: Equip new Metropolis

®

OLIUs in Main slots

DMX Access Multiplexer with

Procedure 5-2: Equip new Metropolis

®

LNW80 switch packs in Main slots

DMX Access Multiplexer with

5-2

5-3

5-10

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

5-1

Node turnup procedures

Before you begin

.................................................................................................................................................................................................................................

Before you begin

Prior to performing all procedures in this chapter,

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

2. If not previously completed, install generic and WaveStar

®

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC.

CIT software on the PC”

(p. 14-4) .

Required equipment

All procedures in this chapter require that the following equipment is available:

•

Personal Computer (PC) with WaveStar

®

CIT software installed

•

Wrist strap

Important! If additional equipment is required to perform a specific procedure, that additional equipment is listed in that procedure.

.................................................................................................................................................................................................................................

5-2 365-372-301 R6.0

Issue 15, January 2006

Node turnup procedures

Procedure 5-1: Equip new Metropolis

®

DMX Access

Multiplexer with OLIUs in Main slots

.................................................................................................................................................................................................................................

Overview

Use this procedure to initially equip and test a new Metropolis

®

DMX in a looped-back configuration with OLIUs being installed in the Main slots. With this configuration, the Metropolis

®

DMX is expected to be incorporated into a network (for example, UPSR or BLSR) using the Main OLIUs.

This procedure assumes that all hardwired installation and testing of the unequipped

Metropolis

®

DMX shelf is done. It also assumes that power is applied to the shelf.

The basic purpose of this procedure is to:

•

Install and test system-required circuit packs and software.

•

Install and test optional circuit packs that you want to install at initial installation.

•

Test the Metropolis

®

DMX for proper and alarm-free operation before placing into the network.

Additional references are provided at the end of this procedure for provisioning optional system and circuit pack port parameters.

Privilege level

You must log in as a Privileged user to complete this procedure.

Important! Some of the steps and procedures referenced in this procedure provide information on provisioning port parameters. If you provision parameters after installing each circuit pack, then you should NOT perform the part of the procedure in

Step 26

to reset all provisionable parameters to default values.

Depending on local procedures, you may set the circuit pack and/or port parameters in this procedure, or reference the appropriate procedures in this document when you are ready to establish your network and service configurations.

Before you begin

Before you begin this procedure:

1. Refer to

“Before you begin” (p. 5-2)

and

“Required equipment” (p. 5-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure which state the quantity and type of circuit packs to be installed.

4. Verify that you have the proper type and code of circuit packs being installed.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

5-3

Node turnup procedures Procedure 5-1: Equip new Metropolis

®

DMX Access

Multiplexer with OLIUs in Main slots

5. If required, ensure that correct pluggable optical modules are available for installation. For reference, see

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62) .

6. If system and circuit pack port parameters are being set at this time, ensure you have a full set of work instructions detailing the values of the parameters being set.

It is suggested that you first install and test all the required circuit packs, perform the necessary system tests, reset all provisionable parameters to factory default values, then provision system and port parameters from values given in your work instructions.

Step

1

Complete the following steps to equip the Metropolis

®

configuration.

DMX shelf in a looped-back

.................................................................................................................................................................................................

Install SYSCTL circuit pack.

Reference:

Procedure 4-1: “Install SYSCTL (LNW2) in new Metropolis

®

shelf” (p. 4-4)

DMX

2

3

4

.................................................................................................................................................................................................

Connect personal computer and establish WaveStar

®

CIT session.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Install system software, if required.

Reference:

Procedure 2-1: “Install software generic (initial) via FTAM” (p. 2-3)

or

Procedure 2-2: “Install software generic (initial) via FTP” (p. 2-21)

.................................................................................................................................................................................................

Install high-speed OLIU circuit packs in M1 and M2 slots.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

5

If this system is going to be line timed or externally timed and the timing reference is

not yet available, use the

Configuration

→

Timing/Sync

command from the System

View menu to set the timing source to Free Running, or external timed if the external timing source is available.

Important! The system Timing Source should be set to Free Running or External to avoid Holdover alarms before the end-to-end system is established. The Timing

Source may be re-provisioned during end-to-end system configuration.

.................................................................................................................................................................................................................................

5-4 365-372-301 R6.0

Issue 15, January 2006

Node turnup procedures Procedure 5-1: Equip new Metropolis

®

DMX Access

Multiplexer with OLIUs in Main slots

6

7

8

9

10

11

Reference:

(p. 6-16)

Procedure 6-5: “Network Element synchronization provisioning”

.................................................................................................................................................................................................

Important! OLIUs may require line build outs (LBOs) during loopback.

Install high-speed OLIU optical loops, if required, and not already installed.

If OSI over DCC is enabled for the Main ports, an inconsistent DCC values alarm is reported when the Main ports are looped back.

If desired, clear the inconsistent DCC values alarm by disabling OSI over DCC for the Main ports. From the System View menu, select

Configuration

→

DCC

Terminations

and disable

OSI Over DCC

for the required DCC ports. If required, refer to

Procedure 6-4: “Provision DCC terminations” (p. 6-13) .

Reference:

Procedure 14-6: “Connect OLIU optical loopbacks” (p. 14-56)

.................................................................................................................................................................................................

Provision high-speed OLIU ports, if required at this time and not already performed.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

Install and test any required low-speed OLIU circuit packs in Function Unit or Growth slots.

Important! Be sure to test each low-speed OLIU port using optical fiber loopbacks after the circuit pack is installed.

Reference:

•

Procedure 4-3: “Install OLIU circuit packs in Function slots” (p. 4-14)

•

Procedure 14-6: “Connect OLIU optical loopbacks” (p. 14-56)

.................................................................................................................................................................................................

Provision low-speed OLIU ports, if required at this time and not already performed in the previous step.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

Install any required DS3/EC1 circuit packs.

Reference:

Procedure 4-6: “Install DS3/EC1 circuit packs” (p. 4-32)

.................................................................................................................................................................................................

Provision DS3/EC1 ports, if required at this time and not already performed.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

5-5

Node turnup procedures Procedure 5-1: Equip new Metropolis

®

DMX Access

Multiplexer with OLIUs in Main slots

12

13

14

15

16

17

18

19

Reference:

(p. 4-37)

Procedure 4-7: “Provision DS3/EC1 circuit packs/ports for service”

.................................................................................................................................................................................................

Install any required DS1/E1 circuit packs.

Reference:

Procedure 4-8: “Install DS1/E1 circuit packs” (p. 4-39)

.................................................................................................................................................................................................

Provision DS1/E1 ports, if required at this time and not already performed.

Reference:

(p. 4-42)

Procedure 4-9: “Provision DS1/E1 circuit packs/ports for service”

.................................................................................................................................................................................................

Install any required TMUX circuit packs.

Reference:

Procedure 4-10: “Install TMUX circuit packs” (p. 4-45)

.................................................................................................................................................................................................

Provision TMUX ports, if required at this time and not already performed.

Reference:

Procedure 4-11: “Provision TMUX ports for service” (p. 4-48)

.................................................................................................................................................................................................

Install any required Ethernet circuit packs.

Reference:

•

Procedure 4-12: “Install 10/100 Ethernet circuit packs” (p. 4-50)

•

Procedure 4-13: “Install Gigabit Ethernet circuit packs” (p. 4-54)

.................................................................................................................................................................................................

Provision Ethernet circuit packs/ports/VCGs, if required at this time and not already performed.

Reference:

Procedure 4-14: “Provision Ethernet circuit pack/LAN port/VCG for service” (p. 4-59)

.................................................................................................................................................................................................

Install any required Fibre Channel circuit packs.

Reference:

Procedure 4-17: “Install Fibre Channel circuit packs” (p. 4-74)

.................................................................................................................................................................................................

Provision Fibre Channel circuit packs/data ports/VCGs, if required at this time and not already performed.

.................................................................................................................................................................................................................................

5-6 365-372-301 R6.0

Issue 15, January 2006

Node turnup procedures Procedure 5-1: Equip new Metropolis

®

DMX Access

Multiplexer with OLIUs in Main slots

20

Reference:

Procedure 4-18: “Provision Fibre Channel circuit pack/Data port/VCG for service” (p. 4-77)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Improperly-seated circuit packs or missing apparatus blanks may cause service hits on in-service systems.

All slots in Metropolis

®

DMX must be equipped with fully-seated circuit packs or apparatus blanks to prevent service hits on in-service systems.

21

Install 177D Apparatus Blanks or LNW98 circuit packs in any unused

Function/Growth slots on the shelf. Install 177E Apparatus Blanks or LNW97 circuit packs in any unused Main 2 slot.

Important! All slots in the Metropolis

®

DMX must be equipped with fully-seated circuit packs or apparatus blanks.

.................................................................................................................................................................................................

Perform the LED test to verify that all LEDs are operating properly.

Reference:

Procedure 14-13: “Perform LED test” (p. 14-88)

22

.................................................................................................................................................................................................

Perform local (looped-back) terminal transmission tests, if required.

Important! This procedure assumes that the Metropolis

®

DMX high-speed signals are looped back (manual optical OLIU loopback).

Reference:

•

Procedure 14-9: “Perform DS1/E1 transmission test” (p. 14-67)

•

Procedure 14-10: “Perform DS3 transmission test” (p. 14-74)

•

Procedure 14-11: “Perform EC-1 transmission test” (p. 14-80)

.................................................................................................................................................................................................

23

Perform local cross-connect wiring (facility) transmission test (looped back), if required.

Important! This procedure assumes that the Metropolis

®

DMX has been connected to the low-speed DSX cross connect as required.

Reference:

•

Procedure 14-9: “Perform DS1/E1 transmission test” (p. 14-67)

•

Procedure 14-10: “Perform DS3 transmission test” (p. 14-74)

•

Procedure 14-11: “Perform EC-1 transmission test” (p. 14-80)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

5-7

Node turnup procedures Procedure 5-1: Equip new Metropolis

®

DMX Access

Multiplexer with OLIUs in Main slots

24

25

26

.................................................................................................................................................................................................

Test protection switching function, if required.

Reference:

(p. 14-86)

Procedure 14-12: “Test function unit equipment protection switching”

.................................................................................................................................................................................................

Check office alarm interface by local procedure, if required.

.................................................................................................................................................................................................

Perform one of the following depending on whether or not you have already provisioned circuit packs and ports for service:

•

Circuit packs and/or ports were provisioned in this procedure:

Perform the following to delete any cross-connections, loopbacks, or protection switches that may have been made during testing:

1. Select

View

→

Cross-Connections

from the System View menu. Select

Shelf

from the View Cross Connections window, then click

Select

. Print or save the cross-connections to be deleted, then click

Close

. Select

Configuration

→

Cross-Connections

from the System View window to start the Cross

Connection Wizard. Follow the instruction in the Wizard to delete the necessary cross-connections.

2. Select

View

→

Loopback

from the System View menu. Select

Shelf

from the

View Loopbacks window, then click

Select

. Print or save the existing loopbacks to be released, then click

Close

.

Select

Fault

→

Analysis

→

Loopback

from the System View menu. Expand the details in the Loopback window, select the port with the loopback to be released, then click

Select

. Select Release and the Loopback Type, then click

Apply

at the bottom of the Loopback window. Click

Yes

to the Warning message to release the loopback. Click

Close

to exit.

3. Select

View

→

Protection

from the System View menu. Click on the

Equip

tab, select the circuit pack (CP), then click

Select

. Note the Protection Switch

State. Repeat for each CP, then click

Close

.

Select

Fault

→

Protection Switch

from the System View menu. Click on the

Equip

tab, select the CP, then click

Select

. Select the Protection Switch Mode as required, then click

Apply

. Click

Yes

, then choose another CP and repeat this command or click

Close

to exit.

•

Circuit packs and/or ports were not provisioned in this procedure:

The following command resets all system provisionable parameters and cross-connections to factory default values. If you have already set provisionable parameters for the installed circuit packs/ports, they will be reset to factory default values.

From the System View menu, use the

Fault

→

Reset

→

Initialize System

command to reset system parameters to default values, if required. Read all the warnings and follow the prompts to execute the command.

.................................................................................................................................................................................................................................

5-8 365-372-301 R6.0

Issue 15, January 2006

Node turnup procedures Procedure 5-1: Equip new Metropolis

®

DMX Access

Multiplexer with OLIUs in Main slots

27

28

29

Result:

You will be logged off the system during the controller reset and provisionable parameters will be set to factory default.

A flashing

b

in the

IND

display on the SYSCTL indicates that a boot is in progress.

During the boot, the

b

may extinguish for up to 20 seconds and then resume flashing.

Holdover alarm may also occur since timing mode reverts back to External. If required to silence the alarm, select

Configuration

→

Timing/Sync

command from the System View menu to set the timing source to Free Running.

.................................................................................................................................................................................................

Set/Change system TID (NE name), as required.

Important! The TID is a case-insensitive character string from 1 to 20 characters and must be unique for each NE in the network.

Reference:

Procedure 7-11: “Set/change system TID” (p. 7-38)

.................................................................................................................................................................................................

Provision optional system parameters as required from work order or office records.

Reference:

•

Chapter 6, “System configuration procedures”

•

Chapter 7, “System administration procedures”

•

Chapter 8, “System performance monitoring procedures”

•

Appendix A, “Provisionable parameters”

.................................................................................................................................................................................................

Establish the end-to-end Metropolis

®

DMX subnetwork, when required.

Reference:

Chapter 9, “Network configuration procedures”

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

5-9

Node turnup procedures

Procedure 5-2: Equip new Metropolis

®

DMX Access

Multiplexer with LNW80 switch packs in Main slots

.................................................................................................................................................................................................................................

Overview

Use this procedure to initially equip and test a new Metropolis

®

DMX with LNW80

Switch Packs installed in the Main slots. This configuration does NOT use any optical circuit packs (OLIUs) in the Main slots of the Metropolis

®

DMX.

Metropolis

®

DMX shelves equipped with LNW80 Switch Packs in the MAIN slots act as a central hub to allow full use of the VT switch fabric for VT type hairpin cross-connections among circuit packs installed in the low-speed slots. The LNW80

Switch Pack acts only as a cross-connect switch fabric, therefore no cross-connections are allowed to the Switch Pack installed in the Main slots. Only low-speed hairpin cross-connections among the low-speed circuit packs are supported on this shelf.

A Metropolis

®

DMX equipped with LNW80 Switch Packs supports VT mapping in 48

STS1s allowing up to 96 VT-groomed STS hairpin cross-connections.

This procedure assumes that all hardwired installation and testing of the unequipped

Metropolis

®

DMX shelf is done. It also assumes that power is applied to the shelf.

The basic purpose of this procedure is to:

•

Install and test system required circuit packs and software.

•

Install and test optional circuit packs that you want to install at initial installation.

•

Test the Metropolis

®

DMX for proper and alarm free operation before placing into the network.

Additional references are provided at the end of this procedure for provisioning optional system and circuit pack port parameters.

Privilege level

You must log in as a Privileged user to complete this procedure.

Important! Some of the steps and procedures referenced in this procedure provide information on provisioning port parameters. If you provision parameters after installing each circuit pack, then you should not perform the part of the procedure in

Step 24

to reset all provisionable parameters to default values.

Depending on local procedures, you may set the circuit pack and/or port parameters in this procedure, or reference the appropriate procedures in this document when you are ready to establish your network and service configurations.

.................................................................................................................................................................................................................................

5-10 365-372-301 R6.0

Issue 15, January 2006

Node turnup procedures Procedure 5-2: Equip new Metropolis

®

DMX Access

Multiplexer with LNW80 switch packs in Main slots

Before you begin

Before you begin this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

2. If not previously completed, install generic and WaveStar

®

CIT software on the PC.

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

3. Obtain the work instructions for this procedure which state the quantity and type of circuit packs to be installed.

4. Verify that you have the proper type and code of circuit packs being installed.

5. If required, ensure that correct pluggable optical modules are available for installation. For reference, see

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62) .

6. If system and circuit pack port parameters are being set at this time, ensure you have a full set of work instructions detailing the values of the parameters being set.

It is suggested that you first install and test all the required circuit packs, perform the necessary system tests, reset all provisionable parameters to factory default values, then provision system and port parameters from values given in your work instructions.

Step

1

2

3

4

Complete the following steps to equip the Metropolis

®

DMX shelf.

.................................................................................................................................................................................................

Install SYSCTL circuit pack.

Reference:

Procedure 4-1: “Install SYSCTL (LNW2) in new Metropolis

®

shelf” (p. 4-4)

DMX

.................................................................................................................................................................................................

Connect personal computer and establish WaveStar

®

CIT session.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Install system software, if required.

Reference:

Procedure 2-2: “Install software generic (initial) via FTP” (p. 2-21)

.................................................................................................................................................................................................

Install LNW80 Switch circuit packs in M1 and M2 slots.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

5-11

Node turnup procedures Procedure 5-2: Equip new Metropolis

®

DMX Access

Multiplexer with LNW80 switch packs in Main slots

5

6

7

8

9

There are no provisionable parameters required for the LNW80 Switch Pack.

Reference:

Procedure 4-16: “Install LNW80 switch pack” (p. 4-72)

.................................................................................................................................................................................................

If this system is going to be externally timed and the timing reference is not yet available, use the

Configuration

→

Timing/Sync

command from the System View menu to set the timing source to Free Running.

Important! Only External Timing and Free Running are allowed for systems equipped with LNW80 Switch Packs. Line Timing, Line Sync Out, and External

Sync Out are not supported. If the system is going to be externally timed and the external timing source is not yet available, the system Timing Source should be set to Free Running to avoid Holdover alarms before the timing source is available.

The Timing Source may be re-provisioned after the timing source is available.

Reference:

(p. 6-16)

Procedure 6-5: “Network Element synchronization provisioning”

.................................................................................................................................................................................................

Install and test any required low-speed OLIU circuit packs in Function Unit or Growth slots.

Important! Be sure to test each low-speed OLIU port using optical fiber loopbacks after the circuit pack is installed.

Reference:

•

Procedure 4-3: “Install OLIU circuit packs in Function slots” (p. 4-14)

•

Procedure 14-6: “Connect OLIU optical loopbacks” (p. 14-56)

.................................................................................................................................................................................................

Provision low-speed OLIU ports, if required at this time and not already performed.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

Install any required DS3/EC1 circuit packs.

Reference:

Procedure 4-6: “Install DS3/EC1 circuit packs” (p. 4-32)

.................................................................................................................................................................................................

Provision DS3/EC1 ports, if required at this time and not already performed.

.................................................................................................................................................................................................................................

5-12 365-372-301 R6.0

Issue 15, January 2006

Node turnup procedures Procedure 5-2: Equip new Metropolis

®

DMX Access

Multiplexer with LNW80 switch packs in Main slots

10

11

12

13

14

15

16

17

Reference:

(p. 4-37)

Procedure 4-7: “Provision DS3/EC1 circuit packs/ports for service”

.................................................................................................................................................................................................

Install any required DS1/E1 circuit packs.

Reference:

Procedure 4-8: “Install DS1/E1 circuit packs” (p. 4-39)

.................................................................................................................................................................................................

Provision DS1/E1 ports, if required at this time and not already performed.

Reference:

(p. 4-42)

Procedure 4-9: “Provision DS1/E1 circuit packs/ports for service”

.................................................................................................................................................................................................

Install any required TMUX circuit packs.

Reference:

Procedure 4-10: “Install TMUX circuit packs” (p. 4-45)

.................................................................................................................................................................................................

Provision TMUX ports, if required at this time and not already performed.

Reference:

Procedure 4-11: “Provision TMUX ports for service” (p. 4-48)

.................................................................................................................................................................................................

Install any required Ethernet circuit packs.

Reference:

•

Procedure 4-12: “Install 10/100 Ethernet circuit packs” (p. 4-50)

•

Procedure 4-13: “Install Gigabit Ethernet circuit packs” (p. 4-54)

.................................................................................................................................................................................................

Provision Ethernet circuit packs/ports/VCGs, if required at this time and not already performed.

Reference:

Procedure 4-14: “Provision Ethernet circuit pack/LAN port/VCG for service” (p. 4-59)

.................................................................................................................................................................................................

Install any required Fibre Channel circuit packs.

Reference:

Procedure 4-17: “Install Fibre Channel circuit packs” (p. 4-74)

.................................................................................................................................................................................................

Provision Fibre Channel circuit packs/data ports/VCGs, if required at this time and not already performed.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

5-13

Node turnup procedures Procedure 5-2: Equip new Metropolis

®

DMX Access

Multiplexer with LNW80 switch packs in Main slots

18

Reference:

Procedure 4-18: “Provision Fibre Channel circuit pack/Data port/VCG for service” (p. 4-77)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Improperly-seated circuit packs or missing apparatus blanks may cause service hits on in-service systems.

All slots in Metropolis

®

DMX must be equipped with fully-seated circuit packs or apparatus blanks to prevent service hits on in-service systems.

19

20

21

22

Install 177D Apparatus Blanks or LNW98 circuit packs in any unused

Function/Growth slots on the shelf.

Important! All slots in the Metropolis

®

DMX must be equipped with fully-seated circuit packs or apparatus blanks.

.................................................................................................................................................................................................

Perform the LED test to verify that all LEDs are operating properly.

Reference:

Procedure 14-13: “Perform LED test” (p. 14-88)

.................................................................................................................................................................................................

Perform local terminal transmission tests, if required.

Reference:

•

Procedure 14-9: “Perform DS1/E1 transmission test” (p. 14-67)

•

Procedure 14-10: “Perform DS3 transmission test” (p. 14-74)

•

Procedure 14-11: “Perform EC-1 transmission test” (p. 14-80)

.................................................................................................................................................................................................

Perform local cross-connect wiring (facility) transmission test (looped back), if required.

Important! This procedure assumes that the Metropolis

®

DMX has been connected to the low-speed DSX cross connect as required.

Reference:

•

Procedure 14-9: “Perform DS1/E1 transmission test” (p. 14-67)

•

Procedure 14-10: “Perform DS3 transmission test” (p. 14-74)

•

Procedure 14-11: “Perform EC-1 transmission test” (p. 14-80)

.................................................................................................................................................................................................

Test protection switching function, if required.

.................................................................................................................................................................................................................................

5-14 365-372-301 R6.0

Issue 15, January 2006

Node turnup procedures Procedure 5-2: Equip new Metropolis

®

DMX Access

Multiplexer with LNW80 switch packs in Main slots

23

24

Reference:

(p. 14-86)

Procedure 14-12: “Test function unit equipment protection switching”

.................................................................................................................................................................................................

Check office alarm interface by local procedure, if required.

.................................................................................................................................................................................................

Perform one of the following depending on whether or not you have already provisioned circuit packs and ports for service:

•

Circuit packs and/or ports were provisioned in this procedure:

Perform the following to delete any cross-connections, loopbacks, or protection switches that may have been made during testing:

1. Select

View

→

Cross-Connections

from the System View menu. Select

Shelf

from the View Cross Connections window, then click

Select

. Print or save the cross-connections to be deleted, then click

Close

. Select

Configuration

→

Cross-Connections

from the System View window to start the Cross

Connection Wizard. Follow the instruction in the Wizard to delete the necessary cross-connections.

2. Select

View

→

Loopback

from the System View menu. Select

Shelf

from the

View Loopbacks window, then click

Select

. Print or save the existing loopbacks to be released, then click

Close

.

Select

Fault

→

Analysis

→

Loopback

from the System View menu. Expand the details in the Loopback window, select the port with the loopback to be released, then click

Select

. Select Release and the Loopback Type, then click

Apply

at the bottom of the Loopback window. Click

Yes

to the Warning message to release the loopback. Click

Close

to exit.

3. Select

View

→

Protection

from the System View menu. Click on the

Equip

tab, select the circuit pack (CP), then click

Select

. Note the Protection Switch

State. Repeat for each CP, then click

Close

.

Select

Fault

→

Protection Switch

from the System View menu. Click on the

Equip

tab, select the CP, then click

Select

. Select the Protection Switch Mode as required, then click

Apply

. Click

Yes

, then choose another CP and repeat this command or click

Close

to exit.

•

Circuit packs and/or ports were not provisioned in this procedure:

The following command resets all system provisionable parameters and cross-connections to factory default values. If you have already set provisionable parameters for the installed circuit packs/ports, they will be reset to factory default values.

From the System View menu, use the

Fault

→

Reset

→

Initialize System

command to reset system parameters to default values, if required. Read all the warnings and follow the prompts to execute the command.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

5-15

Node turnup procedures Procedure 5-2: Equip new Metropolis

®

DMX Access

Multiplexer with LNW80 switch packs in Main slots

25

26

Result:

You will be logged off the system during the controller reset and provisionable parameters will be set to factory default.

A flashing

b

in the

IND

display on the SYSCTL indicates that a boot is in progress.

During the boot, the

b

may extinguish for up to 20 seconds and then resume flashing.

Holdover alarm may also occur since timing mode reverts back to External. If required to silence alarm, select

Configuration

→

Timing/Sync

command from the

System View menu to set the timing source to Free Running.

.................................................................................................................................................................................................

Set/Change system TID (NE name), as required.

Important! The TID is a case-insensitive character string from 1 to 20 characters and must be unique for each NE in the network.

Reference:

Procedure 7-11: “Set/change system TID” (p. 7-38)

.................................................................................................................................................................................................

Provision optional system parameters as required from work order or office records.

Reference:

•

Chapter 6, “System configuration procedures”

•

Chapter 7, “System administration procedures”

•

Chapter 8, “System performance monitoring procedures”

•

Appendix A, “Provisionable parameters”

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

5-16 365-372-301 R6.0

Issue 15, January 2006

6

6

Overview

.................................................................................................................................................................................................................................

Purpose

This chapter includes procedures that necessary to provision system configuration parameters, for example, timing, DCC terminations, miscellaneous discretes.

Contents

Before you begin

Procedure 6-1: Provision system configuration parameters

Procedure 6-2: Provision shelf/system parameters

Procedure 6-3: Provision miscellaneous discrete inputs and outputs

Procedure 6-4: Provision DCC terminations

Procedure 6-5: Network Element synchronization provisioning

Procedure 6-6: Provision system alarm configuration

Procedure 6-7: Provision new alarm severity assignment profile

Procedure 6-8: Change existing alarm severity assignment profile

Procedure 6-9: Delete alarm severity assignment profile

Procedure 6-10: Assign alarm severity assignment profile

Procedure 6-11: Evaluate bandwidth utilization

Procedure 6-12: Optimize backplane bandwidth

6-34

6-36

6-39

6-41

6-44

6-46

6-2

6-3

6-7

6-11

6-13

6-16

6-33

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-1

System configuration procedures

Before you begin

.................................................................................................................................................................................................................................

Before you begin

Prior to performing all procedures in this chapter,

1. If not previously completed, install generic and WaveStar

®

CIT software on the PC.

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

2. Connect PC and establish a WaveStar

®

CIT session.

Refer to

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24) .

Required equipment

All procedures in this chapter require that the following equipment is available:

•

Personal Computer (PC) with WaveStar

®

CIT software installed

•

Wrist strap

Important! If additional equipment is required to perform a specific procedure, that additional equipment is listed in that procedure.

.................................................................................................................................................................................................................................

6-2 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures

Procedure 6-1: Provision system configuration parameters

.................................................................................................................................................................................................................................

Overview

Use this procedure as reference for provisioning optional system configuration parameters from the System View

Configuration

menu.

Depending on your requirements, default settings may be sufficient for many of the parameters. Other parameters in the Configuration menu are necessary for system and network operation but may not be listed here. They are accessed through various procedures associated with system turn-up, network configuration, and establishing service.

Configuration parameters may consist of one or more of the following:

•

Provisioning general system (aid=system), circuit pack, port, and tributary parameters

•

Provisioning miscellaneous discretes

•

Provisioning DCC terminations

•

Provisioning system timing and synchronization functions

•

Provisioning system alarm configurations

•

Provisioning system software backup intervals

Depending on local procedures, types of configurations, and shelf equipage, some or none of the optional parameters may need to be set. It is assumed that local system administration is responsible for determining these parameter settings.

Some of the parameter values may be set during the initial shelf turn-up. Other parameter values may be set after the system is integrated into the network configuration.

Step

1

Use the sections in this procedure as reference for provisioning optional system configuration parameters.

.................................................................................................................................................................................................

Reference the sections in this procedure to provision the required system configuration parameters from your work instructions.

Important! Some of the parameters may have already been provisioned from earlier procedures.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-3

System configuration procedures Procedure 6-1: Provision system configuration parameters

System, circuit packs, ports, or tributaries

The following references commands and procedures associated with provisioning system, port, and tributary parameters that may apply for the entire system or circuit pack. Certain individual parameters may be provisioned in other procedures depending on the type of service, system configuration, and/or network configuration.

•

System parameters:

Configuration

→

Equipment

, select the system (

aid=system

), then click

Select

.

Refer to

Procedure 6-2: “Provision shelf/system parameters” (p. 6-7) .

Parameters include:

–

Idle Channel Signal

(AIS, Unequipped)

–

1+1 Protection Priority

(Forced, Signal Failure)

–

Wait to Rename

: Provisioning the wait-to-rename time interval for interchanging the Primary and Secondary role designations of the 1+1 bidirectional optimized lines after a switch event has cleared.

–

Alarm Severity Assignment Profile

to be used for system-level alarm reporting.

–

Signal Degrade Thresholds

for entire system.

–

Signal Failure Thresholds

for entire system.

–

AutoLock

parameters for entire system.

For other system parameters, including system date and time, NE defaults, Target

Identifier (TID)/NE Name, and Login banner, see

Chapter 7, “System administration procedures” .

•

Circuit pack, port, and tributary parameters:

Configuration

→

Equipment

, select the circuit pack, port, or tributary, then click

Select

. Provision the parameters as required.

Refer to

Chapter 4, “Install and provision circuit packs/OLIUs procedures”

to provision circuit pack, port, and tributary parameters.

Cross-connections

Use for reference only. Invokes the Cross-Connection Wizard for establishing cross-connections.

Configuration

→

Cross-Connections

The Cross-Connection wizard is referenced in other procedures relating to establishing specific services. If you have explicit work instructions and are familiar with the

Cross-Connection Wizard, use the wizard to make your cross-connections.

Fibre Channel

Refer to the following to provision Ethernet virtual switches, VLANs, port tags, spanning tree groups, MAC addresses, and quality of service parameters.

.................................................................................................................................................................................................................................

6-4 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures Procedure 6-1: Provision system configuration parameters

Configuration

→

Data

Chapter 11, “Ethernet/Data network provisioning procedures”

Ethernet service

Refer to the following to access the Ethernet Service Wizard and provision Ethernet service.

Configuration

→

Ethernet Service

Chapter 11, “Ethernet/Data network provisioning procedures”

Miscellaneous discretes

Refer to the following to provision miscellaneous discrete environmental inputs and control outputs.

Configuration

→

Misc. Discretes

Procedure 6-3: “Provision miscellaneous discrete inputs and outputs” (p. 6-11)

DCC terminations

Refer to the following to provision DCC Terminations.

Configuration

→

DCC Terminations

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

Timing/sync

Refer to the following to provision system timing/synchronization functions.

Configuration

→

Timing/Sync

Procedure 6-5: “Network Element synchronization provisioning” (p. 6-16)

Alarm configuration

Refer to the following to provision the system alarm-clear delay interval and alarm-generate delay interval.

Configuration

→

Alarms

→

Alarm Configuration

Procedure 6-6: “Provision system alarm configuration” (p. 6-33)

Update system

Refer to the following to update the system database to reflect the current configuration and incoming signals.

Configuration

→

Update System

→

Update Inventory

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-5

System configuration procedures Procedure 6-1: Provision system configuration parameters

Normal/ring upgrade mode

Refer to the following to switch between normal and ring upgrade modes. The

Normal/Ring Update Mode is used during a hardware upgrade of OCN circuit packs in a ring.

Configuration

→

Normal Mode

Configuration

→

Ring Upgrade Mode

Chapter 12, “Ring and circuit pack upgrade procedures”

Software

Configuration

→

Update System

→

Update Reference

Configuration

→

Update System

→

Update States

Configuration

→

Update System

→

Update All

These commands are referenced in procedures throughout this guide.

Refer to the following to provision system software and database functions.

Configuration

→

Software

→

Remote Backup

Configuration

→

Software

→

Remote Restore

Configuration

→

Software

→

Configure Auto Backup Interval

Configuration

→

Software

→

Copy Software

Configuration

→

Software

→

Apply Software

Configuration

→

Software

→

Download Software

Chapter 2, “Software installation and upgrades, and database backup procedures”

.................................................................................................................................................................................................................................

6-6 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures

Procedure 6-2: Provision shelf/system parameters

.................................................................................................................................................................................................................................

Overview

This procedure uses the

Configuration

→

Equipment

command to provision parameters that apply to the entire shelf/system (aid=system) that may not have been set elsewhere. System parameters as defined in this procedure consist of the following:

•

Idle Channel Signal

Determines whether or not an AIS or Unequipped signal should be inserted toward the SONET line in VT1.5 and STS-1, STS-3c, STS-12c, STS-48c channels that are not cross-connected.

•

1+1 Protection Priority

Specifies the protection switching priority scheme used in 1+1 applications.

•

Wait to Rename

: Specifies the wait-to-rename time interval for interchanging the

Primary and Secondary role designations of the 1+1 bidirectional optimized lines after a switch event has cleared.

•

Alarm Severity Assignment Profile

: Specifies the DEFAULT or user-created

ASAP to be used for system-level alarm reporting.

•

Signal Degrade Thresholds

and

Signal Failure Thresholds

Specifies the STSn and VT1.5 Signal Degrade Thresholds and STSn Signal Failure

Thresholds for ALL system signal rates.

•

AutoLock

Specifies the switch and release intervals and switch counts for the AutoLock features.

Provision these parameters using the

Configuration

→

Equipment

command from the

System View menu, select (highlight)

Metropolis(R) DMX Access Multiplexer

or enter

system

in the

Enter AID

box.

Privilege level

You must login as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 6-2)

and

“Required equipment” (p. 6-2)

in this chapter.

2. Obtain the work instructions for this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-7

System configuration procedures Procedure 6-2: Provision shelf/system parameters

Step

1

2

Perform the following steps to provision system parameters.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Equipment

.

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Select (highlight)

Metropolis(R) DMX Access Multiplexer

or enter

system

in the

Enter AID

box, then click

Select

at the bottom of the window.

Result:

The provisionable system parameters appear.

.................................................................................................................................................................................................

3

Provision the following parameters as required:

Idle Channel Signal

•

AIS

– When idle is set to AIS (default), STS-1, STS-3c, STS-12c, or STS-48c or VT1.5 AIS is inserted towards the SONET line from the SONET interfaces

(OLIUs and STS1Es) if the channel is not cross-connected, or if a low-speed slot is not equipped but the Function unit is STS-1 cross-connected.

•

Unequipped

– When idle is set to UNEQUIPPED, the STS-1, STS-3c,

STS-12c, STS-48c or VT1.5 UNEQUIPPED signal is inserted towards the

SONET line from the SONET interfaces (OLIUs and STS1Es) if the channel is not cross-connected, or if a low-speed slot is not equipped, but the Function unit is STS-1 cross-connected

1+1 Protection Priority

•

Forced

– When Forced (default) is selected, a forced switch is not preempted by a failure of the protection line in 1+1 applications.

•

Signal Failure

– When Signal Failure is selected, a signal failure on the protection side preempts a forced switch in 1+1 applications.

Wait to Rename

•

Provisions the interval for interchanging the Primary and Secondary role designations of the 1+1 bidirectional optimized lines after a switch event has cleared. Provisionable in one minute increments from 0-60 minutes. Default is 5 minutes.

Alarm Severity Assignment Profile

•

Specifies the DEFAULT or user-created ASAP to be used for system-level alarm reporting.

Signal Degrade Thresholds

•

Provisions the VT1.5, STS-1, STS-3, STS-12, and STS-48 Signal Degrade

Threshold parameters as required.

.................................................................................................................................................................................................................................

6-8 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures Procedure 6-2: Provision shelf/system parameters

4

Signal Failure Thresholds

•

Provisions the STS-1, STS-3, and STS-12, and STS-48 Signal Failure Threshold parameters as required.

AutoLock

•

Count

– Specifies the maximum number of consecutive non-pack-removal equipment switches allowed in the provisioned switch interval before the group is put into the autolock state.

Values are from 0 to 20. The default is 0 which disables the function.

For the function equipment groups, the autolock count clears when the autolock

Release Interval

timer expires; when an Inhibit, Forced, or Normal switch-to-protection command is issued; when a Reset switch-to-working command is issued; or when a circuit pack is removed from the Function group, whichever occurs first.

For the Main slots, the autolock count clears when the autolock

Release

Interval

timer expires; when an operate-sync-switch Main Circuit Pack Reset command is issued; or when a circuit pack is removed from the group, whichever occurs first.

When the autolock count or switch interval is re-provisioned, any autolock counts that have not yet effected an autolock will be cleared and restarted.

•

Switch Interval

– Specifies the time interval for which the maximum number of non-pack-removal equipment switches (provisioned under Count) are allowed to occur before the protection group is put into the autolock state.

Values are from 1 to 1440 minutes. The default is 25 minutes.

The autolock switch interval begins when the first switch occurs. When the oldest counted switch is earlier than the provisioned interval, it is no longer counted, and the interval then begins with the next oldest switch.

•

Release Interval

– Specifies the maximum time interval the Function group is allowed to remain in the autolock state.

Values are from 1 to 1440 minutes. The default is 1440 minutes.

The autolock state clears when this autolock Release Interval timer expires; when an Inhibit or Forced switch-to-protection command is issued; when a switch-to-working Reset command is issued; or when a pack is removed from the group, whichever occurs first.

Reprovisioning of the autolock release interval has no effect on existing autolock release timers.

.................................................................................................................................................................................................

Click

Apply

to make the changes. If no changes were made, go to the next step.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-9

System configuration procedures Procedure 6-2: Provision shelf/system parameters

5

Result:

A dialog box appears asking you to confirm executing this command. Click

Yes

to apply the changes.

.................................................................................................................................................................................................

Click

Close

at the bottom of window to exit.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

6-10 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures

Procedure 6-3: Provision miscellaneous discrete inputs and outputs

.................................................................................................................................................................................................................................

Overview

Use this procedure to:

•

Provision miscellaneous discrete inputs and outputs

•

Operate/release miscellaneous discrete outputs

Privilege level

You must log in as a Privileged or General user to provision miscellaneous discretes input and outputs. You must log in as a Privileged, General, or Maintenance user to operate/release a miscellaneous discrete output.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 6-2)

and

“Required equipment” (p. 6-2)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions specify the miscellaneous discrete names and alarm information required for provisioning.

Step

Complete the following steps to provision miscellaneous discretes.

.................................................................................................................................................................................................

1

If...

provisioning miscellaneous discrete inputs and/or outputs operating/releasing a miscellaneous discrete output,

Then...

Continue with

Proceed to

Step 2

Step 6 .

.

2

.................................................................................................................................................................................................

PROVISION MISCELLANEOUS DISCRETES

From the System View menu, select

Configuration

→

Misc Discretes

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-11

System configuration procedures Procedure 6-3: Provision miscellaneous discrete inputs and outputs

3

4

5

6

7

8

9

Result:

The Configure Miscellaneous Discretes window opens.

.................................................................................................................................................................................................

Expand the appropriate Input or Output list (according to the work instructions) by clicking on the plus sign (+). Select an available Input/Output to provision or edit

(according to the work instructions) and click

Select

.

Result:

The miscellaneous discrete parameters appear.

.................................................................................................................................................................................................

Provision the miscellaneous discrete input/output parameters according to the work instructions and click

Apply

.

.................................................................................................................................................................................................

If required, repeat

Step 3

and

Step 4

to provision other miscellaneous discrete inputs/outputs; otherwise, click

Close

to exit.

STOP! End of Procedure.

.................................................................................................................................................................................................

OPERATE/RELEASE MISCELLANEOUS DISCRETE OUTPUT

From the System View menu, select

Fault

→

Operate Output Misc. Discrete

.

Result:

The Operate Miscellaneous Discrete Outputs window opens.

.................................................................................................................................................................................................

Expand the Output list by clicking on the plus sign (+). Select the required output and click

Select

.

.................................................................................................................................................................................................

Select

Operate Control Point

to operate the output, or select

Release Control Point

to turn off the output. Click

Apply

.

.................................................................................................................................................................................................

If required, repeat

Step 7

and

Step 8

to operate/release other miscellaneous discrete outputs; otherwise, click

Close

to exit.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

6-12 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures

Procedure 6-4: Provision DCC terminations

.................................................................................................................................................................................................................................

Overview

CAUTION

Service disruption hazard

Changing the DCC termination parameters may affect system operations.

Do not change the DCC termination parameters on an in-service system unless you are directed to do so from another procedure.

Use this procedure to provision the DCC termination parameters for an OC-N port.

Important! The DCC termination parameters are generally provisioned when the system/optical span is integrated into a network.

Privilege level

You must login as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure,

1. Refer to

“Before you begin” (p. 6-2)

and

“Required equipment” (p. 6-2)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions specify the OC-N port address and the required

DCC termination parameter settings.

Step

1

Perform the following steps to provision the DCC termination parameters for an OC-N port.

.................................................................................................................................................................................................

Using the work instructions, determine whether OSI over DCC or IP over DCC is to be provisioned for the required OC-N port.

If...

IP over DCC is to be provisioned for the

OC-N port,

OSI over DCC is to be provisioned for the

OC-N port,

Then...

Continue with

Step 2 .

Proceed to

Step 7 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-13

System configuration procedures Procedure 6-4: Provision DCC terminations

2

3

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Data Communications

.

Result:

The Data Communications window opens.

.................................................................................................................................................................................................

Click on the

TCP/IP

tab and select DCC-ALL from the

Port AID:

drop-down menu.

.................................................................................................................................................................................................

4

5

Important! When IP over DCC is enabled for DCC ports, each DCC port does not require a unique IP address. IP over DCC interfaces are also referred to as

unnumbered lines. Although each unnumbered line does not have a unique IP address, the network element must have the TCP/IP function enabled for the Port

AID DCC-ALL and an IP address must be assigned. The IP address assigned to the

DCC-ALL AID is used as the router ID for unnumbered lines. For DCC links that require the local network element and the far-end network element to be in the same subnet, the DCC-ALL AID of the local network element must have an IP address that is in the same subnet as the IP address of the far-end network element.

Enable the

TCP/IP Function

parameter, provision the

IP Address

according to your work instructions, and provision the

IP Subnet Mask

to be 255.255.255.255. (When your Port AID is DCC-ALL, your IP subnet mask must be 255.255.255.255.) Click

Apply

.

Result:

A WaveStar

®

CIT Warning appears stating that executing this command will cause the system view to close and may cause the system to reset, then asks you to confirm executing this command.

.................................................................................................................................................................................................

Click

Yes

to execute the command.

Result:

The WaveStar

®

CIT disconnects from the network element.

A flashing

b

in the

IND

display on the SYSCTL indicates that a boot is in progress.

During the boot, the

b

may extinguish for up to 20 seconds and then resume flashing.

If automatic synchronization is unsuccessful, the date and time must be reset manually. If required, refer to

Procedure 7-10: “Set date and time” (p. 7-33) .

6

.................................................................................................................................................................................................

Re-establish the log in session to the network element.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

7

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

DCC Terminations

.

.................................................................................................................................................................................................................................

6-14 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures Procedure 6-4: Provision DCC terminations

8

9

10

Result:

The Configure DCC Terminations window opens.

.................................................................................................................................................................................................

Select the required DCC Port being provisioned from the

Port AID:

drop-down menu.

.................................................................................................................................................................................................

Important! The DCC Channel Parameters are generally provisioned when the system/optical span is integrated into a network and should not be changed unless you are reconfiguring the network and have been directed to do so.

Provision the DCC Channel Parameters according to the work instructions and click

Apply

.

Important! The

LAPD Role

parameter is not applicable if

IP Over DCC

is

enabled.

If

OSI Over DCC

is enabled, the

LAPD Role

parameter must be provisioned differently at each end of an optical span. For example, if the

LAPD Role

parameter is provisioned user-side at one end of an optical span, then the

LAPD

Role

parameter must be provisioned network-side at the other end of the optical span.

.................................................................................................................................................................................................

If required, repeat

Step 8

and

Step 9

to provision other DCC ports; otherwise, click

Close

to exit.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-15

System configuration procedures

Procedure 6-5: Network Element synchronization provisioning

.................................................................................................................................................................................................................................

Overview

To configure a network for the flow of valid timing signals between network elements under normal and failure conditions requires a well thought out synchronization plan.

This procedure assumes such a synchronization plan exists and describes how to configure a Metropolis

®

DMX shelf accordingly.

Use this procedure to provision the network element synchronization functions.

Metropolis

®

DMX has the following timing/sync options:

•

Timing Mode: Free Running, External, or Line.

•

Output Timing: Enabled or Disabled. Used to provide derived DS1 references for systems that are capable of accepting a DS1 timing signal.

When Timing Mode is External and Output Timing is Enabled, the sync mode is

External SyncOut.

When Timing Mode is External and Output Timing is Disabled, the sync mode is

External.

When Timing Mode is Line and Output Timing is Enabled, the sync mode is Line

SyncOut.

When Timing Mode is Line and Output Timing is Disabled, the sync mode is Line.

•

Clock Mode Switching: Revertive or Nonrevertive (Line or External).

This determines whether or not the network element automatically exits holdover

(revert) when the fault condition clears. In the nonrevertive mode, the network element remains in holdover.

•

Reference Switching: Revertive-1, Revertive-2, or Nonrevertive (Line or External).

This determines whether or not the system reverts to the provisioned primary reference (Revertive-1 or Revertive-2) when the fault condition clears. If the

Reference Switching parameter is provisioned Revertive-1, Main-1-1 (Line) or

Ref-1 (External) is designated primary. If the Reference Switching parameter is provisioned Revertive-2, Main-2-1 (Line) or Ref-2 (External) is designated primary.

If the Reference Switching parameter is provisioned Nonrevertive, the network element does not revert to the original active reference when the fault condition clears. Does not apply when synchronization mode is Line or Line SyncOut and

Autoreconfiguration is disabled.

When a manual revertive reference switch is performed, the system reports a standing condition indicating a revertive reference switch is active. A Reset is required to switch back to the designated primary reference and clear the standing condition. When a manual nonrevertive reference switch is performed, the system does not report any standing conditions or alarms since both references are designated for service.

.................................................................................................................................................................................................................................

6-16 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures Procedure 6-5: Network Element synchronization provisioning

•

Optical Synchronization Source: Main-1-1 or Main-2-1.

For Line timing, this is the optical line from which system timing is initially derived. If synchronization autoreconfiguration is disabled, this is the only line from which timing is derived.

•

Synchronization Autoreconfiguration: Enable or Disable.

When Synchronization Autoreconfiguration is enabled and the network element is provisioned as Line timed, the network element automatically switches synchronization sources (main-1-1 or main-2-1). An automatic protection switch

(APS) to the standby timing source occurs if the active source fails. The switch is revertive or nonrevertive depending on the provisioned value of the Reference

Switching parameter.

Sync messaging must be enabled on the Main ports prior to enabling

Synchronization Autoreconfiguration.

When the network element is Line timed, it is recommended that Synchronization

Autoreconfiguration be enabled to provide the most reliable network synchronization.

Sync messaging must be enabled on the Main ports prior to enabling

Synchronization Autoreconfiguration.

•

Reference 1 Alarm Severity Assignment Profile (External only): Specifies the

DEFAULT or user-created ASAP to be used when reporting alarms associated with

DS1 timing input 1.

•

Reference 2 Alarm Severity Assignment Profile (External only): Specifies the

DEFAULT or user-created ASAP to be used when reporting alarms associated with

DS1 timing input 2.

Important! Because the initial timing mode is External, the NE enters holdover if no DS1 inputs are available at turnup. If the DS1 signals are applied but the system timing is not provisioned for the proper format, the NE enters holdover and also declares a Minor and a Major LOF alarm on the reference inputs.

Privilege level

You must login as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 6-2)

and

“Required equipment” (p. 6-2)

in this chapter.

2. Obtain the work instructions for this procedure and ensure that a synchronization plan exists for the system.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-17

System configuration procedures

Step

Procedure 6-5: Network Element synchronization provisioning

1

Complete the following steps to provision network synchronization.

.................................................................................................................................................................................................

Determine which system timing mode is to be provisioned and proceed to the appropriate procedure:

If...

Free running

External

Line

External with Output timing

(ext_syncout)

Line with Output timing

(line_syncout)

Then

Proceed to

Procedure 6-5.1: “Free-Running network provisioning” (p. 6-19) .

Proceed to

Procedure 6-5.2: “External timing network provisioning” (p. 6-20) .

Proceed to

Procedure 6-5.3: “Line timing network provisioning” (p. 6-22) .

Proceed to

Procedure 6-5.4: “External timing with output timing network provisioning”

(p. 6-25) .

Proceed to

Procedure 6-5.5: “Line timing with output timing network provisioning” (p. 6-29) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

6-18 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures

Procedure 6-5.1: Free-Running network provisioning

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision the network element Timing Mode to Free Running. In this mode, the network element derives timing from the internal Stratum 3 oscillator.

Step

1

2

3

Complete the following steps to provision a free-running network element.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Timing/Sync

.

Result:

The Configure Timing/Sync window opens.

.................................................................................................................................................................................................

Select the

System Timing

tab.

.................................................................................................................................................................................................

From the

Timing Mode

drop-down menu, select

Free Running

and click

OK

.

Result:

A warning message may appear. Click

Yes

to execute the command.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-19

System configuration procedures

Procedure 6-5.2: External timing network provisioning

.................................................................................................................................................................................................................................

Overview

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 6-5: “Network Element synchronization provisioning”

(p. 6-16) .

Use this procedure to provision the network element Timing Mode to External. In the

External timing mode (initial value), the internal free running clocks of the NE are locked to one of two DS1 timing reference inputs.

Step

1

2

Complete the following steps to provision an externally timed network element.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Timing/Sync

.

Result:

The Configure Timing/Sync window opens.

.................................................................................................................................................................................................

Select the

System Timing

tab.

3

4

.................................................................................................................................................................................................

From the

Timing Mode

drop-down menu, select

External

(initial value).

.................................................................................................................................................................................................

For

Output Timing

, select

Disabled

(initial value).

Result:

With the

Timing Mode

set to

External

, and

Output Timing

set to

Disabled

, the synchronization mode is set to External.

5

.................................................................................................................................................................................................

For

Clock Mode Switching

, select

Revertive

or

Nonrevertive

.

•

Revertive

– Initial value. If the system switches to holdover timing due to a failure of the timing references, it will automatically switch back to the provisioned sync mode after one of the references becomes good.

•

Nonrevertive

– If the system switches to holdover timing due to a failure of the timing references, it will stay in holdover even after a timing reference becomes good. The

Fault

→

Timing/Sync Protection Switch

→

Clock Mode Switch

command from the System View menu must be used to restore the system to normal provisioned mode.

.................................................................................................................................................................................................

6

From the

Reference Switching

drop-down menu box, choose

Revertive-1

,

Revertive-2

, or

Nonrevertive

.

.................................................................................................................................................................................................................................

6-20 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures Procedure 6-5.2: External timing network provisioning

7

8

9

10

This sets the reference switching mode. If revertive, it also sets which reference has priority.

•

Revertive-1

: System selects REF-1 as primary timing reference.

•

Revertive-2

: System selects REF-2 as primary timing reference.

•

Nonrevertive

: Initial value, automatic switching is nonrevertive. Whenever a reference is selected from an automatic switch event, the selected reference remains active even if the event that caused the switch is cleared.

.................................................................................................................................................................................................

Select the required

Reference 1 Alarm Severity Assignment Profile

and

Reference 2

Alarm Severity Assignment Profile

.

.................................................................................................................................................................................................

Click on the

Timing Input Ports

tab.

.................................................................................................................................................................................................

For each of the external timing references (

REF-1

and

REF-2

), set the following parameters:

•

DS1 Input and Output Format

(

SF

[initial value] or

ESF

).

•

DS1 Input Line Code

(

AMI

[initial value] or

B8ZS

).

.................................................................................................................................................................................................

Click

OK

.

Result:

A warning message may appear. Click

Yes

to execute the command.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-21

System configuration procedures

Procedure 6-5.3: Line timing network provisioning

.................................................................................................................................................................................................................................

Overview

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 6-5: “Network Element synchronization provisioning”

(p. 6-16) .

Use this procedure to provision the network element Timing Mode to Line timing. In this mode, the NE derives timing from one incoming high-speed optical line. Timing received from the specified high-speed line times all synchronous outgoing signals.

Important! Line timing does not apply to Metropolis

®

DMX shelves equipped with an LNW80 Switch Pack.

Before you begin

If the Sync Autoreconfiguration parameter is going to be set to Enabled, then Sync

Messaging must also be enabled. If required, select

View

→

Timing/Sync

from the

System View menu, then select the

Sync Message Status

tab to determine if sync messaging is enabled or disabled.

SByte

in the

Type

column for the Main OLIUs indicates that sync messaging is enabled.

If Sync Messaging is to be enabled, use the

Configuration

→

Equipment

command to enable the Sync Messaging parameter for the required Main ports. Refer to

Procedure

4-4: “Provision OLIU circuit packs/ports for service” (p. 4-22) .

Step

1

2

3

4

Complete the following steps to provision a line timed network element.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Timing/Sync

.

Result:

The Configure Timing/Sync window opens.

.................................................................................................................................................................................................

Select the

System Timing

tab.

.................................................................................................................................................................................................

From the

Timing Mode

drop-down menu, select

Line

.

.................................................................................................................................................................................................

For

Output Timing

, select

Disabled

(initial value).

.................................................................................................................................................................................................................................

6-22 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures Procedure 6-5.3: Line timing network provisioning

5

6

7

8

Result:

With the

Timing Mode

set to

Line

, and

Output Timing

set to

Disabled

, the synchronization mode is set to Line timing.

.................................................................................................................................................................................................

For

Clock Mode Switching

, select

Revertive

or

Nonrevertive

.

•

Revertive

– Initial value. If the system switches to holdover timing due to a failure of the timing references, it will automatically switch back to the provisioned sync mode after one of the references becomes good.

•

Nonrevertive

– If the system switches to holdover timing due to a failure of the timing references, it will stay in holdover even after a timing reference becomes good. The

Fault

→

Timing/Sync Protection Switch

→

Clock Mode Switch

command from the System View menu must be used to restore the system to normal provisioned mode.

.................................................................................................................................................................................................

From the

Reference Switching

drop-down menu box, choose

Revertive-1

,

Revertive-2

, or

Nonrevertive

.

This sets the reference switching mode. If revertive, it also sets which reference has priority.

•

Revertive-1

: System selects main-1-1 as primary timing reference.

•

Revertive-2

: System selects main-2-1 as primary timing reference.

•

Nonrevertive

: Initial value, automatic switching is nonrevertive. Whenever a reference is selected from an automatic switch event, the selected reference remains active even if the event that caused the switch is cleared.

.................................................................................................................................................................................................

For

Optical Synchronization Source

, select

main-1-1 (initial value)

or

main-2-1

as the optical line of the sync source.

.................................................................................................................................................................................................

Important! It is recommended that Synchronization Autoreconfiguration be enabled to provide the most reliable network synchronization.

For

Synchronization Autoreconfiguration

, select

Enabled

to enable autoreconfiguration or

Disabled

(initial value) to disable autoreconfiguration.

When autoreconfiguration is enabled, the system automatically reconfigures between line timing sources when the active timing source fails or a higher quality

Sync Status Message is available on the other source. If autoreconfiguration is disabled, the system enters into holdover when the active timing source fails or the

Sync Status Message quality level falls below level 6 (ST3).

Sync messaging must be enabled in order to enable autoreconfiguration.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-23

System configuration procedures Procedure 6-5.3: Line timing network provisioning

9

.................................................................................................................................................................................................

Click

OK

.

Result:

A warning message may appear. Click

Yes

to execute the command.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

6-24 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures

Procedure 6-5.4: External timing with output timing network provisioning

.................................................................................................................................................................................................................................

Overview

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 6-5: “Network Element synchronization provisioning”

(p. 6-16) .

Use this procedure to provision the system synchronization timing to External SyncOut

(

ext_syncout

). In this mode, the free running clocks in the NE are locked to the external reference inputs while the derived DS1 outputs are enabled and timed from the provisioned optical line.

Important! External SyncOut timing does not apply to Metropolis

®

equipped with an LNW80 Switch Pack.

DMX shelves

Before you begin

The

AIS Threshold

parameter for the timing output ports in this procedure will not work unless Sync Messaging is enabled on the Main OLIU circuit packs, although the

NE will allow the user to change the parameter value. The

AIS Threshold

setting is the sync status message quality level which will generate AIS on the output ports.

To prevent AIS from being generated on the output ports, the sync status message level received from the optical interface synchronization source must be a higher quality than that set for the AIS Threshold.

If required, select

View

→

Timing/Sync

from the System View menu, then select the

Sync Message Status

tab to determine if sync messaging is enabled or disabled.

SByte

in the

Type

column for the Main OLIUs indicates that sync messaging is enabled. If sync messaging is enabled, make a note of the Input Message level for main-1-1 and main-2-1.

If Sync Messaging is to be enabled, use the

Configuration

→

Equipment

command to enable the Sync Messaging parameter for both Main ports. Refer to

Procedure 4-4:

“Provision OLIU circuit packs/ports for service” (p. 4-22) .

Select

View

→

Timing/Sync

from the System View menu, then click on the

Sync

Message Status

tab. Make a note of the Input Message level for main-1-1 and main-2-1.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-25

System configuration procedures

Step

Procedure 6-5.4: External timing with output timing network provisioning

1

2

3

4

5

6

Complete the following steps to provision an external timed network element with DS1 synchronization outputs.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Timing/Sync

.

Result:

The Configure Timing/Sync window opens.

.................................................................................................................................................................................................

Select the

System Timing

tab.

.................................................................................................................................................................................................

From the

Timing Mode

drop-down menu, select

External

.

.................................................................................................................................................................................................

For

Output Timing

, select

Enabled

.

With the

Timing Mode

set to

External

, and

Output Timing

set to

Enabled

, the synchronization mode is set to External SyncOut.

.................................................................................................................................................................................................

For

Clock Mode Switching

, select

Revertive

or

Nonrevertive

.

•

Revertive

– Initial value. If the system switches to holdover timing due to a failure of the timing references, it will automatically switch back to the provisioned sync mode after one of the references becomes good.

•

Nonrevertive

– If the system switches to holdover timing due to a failure of the timing references, it will stay in holdover even after a timing reference becomes good. The

Fault

→

Timing/Sync Protection Switch

→

Clock Mode Switch

command from the System View menu must be used to restore the system to normal provisioned mode.

.................................................................................................................................................................................................

From the

Reference Switching

drop-down menu box, choose

Revertive-1

,

Revertive-2

, or

Nonrevertive

.

This sets the reference switching mode. If revertive, it also sets which reference has priority.

•

Revertive-1

: System selects REF-1 as primary timing reference.

•

Revertive-2

: System selects REF-2 as primary timing reference.

•

Nonrevertive

: Initial value, automatic switching is nonrevertive. Whenever a reference is selected from an automatic switch event, the selected reference remains active even if the event that caused the switch is cleared.

.................................................................................................................................................................................................................................

6-26 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures Procedure 6-5.4: External timing with output timing network provisioning

7

8

9

10

11

.................................................................................................................................................................................................

For

Optical Synchronization Source

, select

main-1-1

or

main-2-1

as the optical line from which the DS1 synchronization outputs will be derived.

Important! The sync status message level of the selected line must be higher than the AIS Threshold level setting in

Step 10

to prevent AIS from being generated on the output ports.

.................................................................................................................................................................................................

Select the required

Reference 1 Alarm Severity Assignment Profile

and

Reference 2

Alarm Severity Assignment Profile

.

.................................................................................................................................................................................................

Select the

Timing Output Ports

tab.

.................................................................................................................................................................................................

From the

AIS Threshold

drop-down menu, select one of the following values, if available:

•

SMC

•

ST3

•

ST3E

•

TNC

•

ST2

•

STU

Important! The AIS Threshold function for the timing output ports will not work unless Sync Messaging is enabled on the Main OLIU circuit packs, although the

NE will allow the user to change the AIS threshold value.

.................................................................................................................................................................................................

For each of the external timing references (

REF-1

and

REF-2

), provision the Timing

Output Equalization based on the maximum cable length for 600-type and 1249-type cable.

Timing Output Equalization

•

20

(131 feet [600-type], 90 feet [1249-type]) (initial value)

•

40

(262 feet [600-type], 180 feet [1249-type])

•

60

(393 feet [600-type], 270 feet [1249-type])

•

80

(524 feet [600-type], 360 feet [1249-type])

•

100

(655 feet [600-type], 450 feet [1249-type])

.................................................................................................................................................................................................

Click the

Timing Input Ports

tab.

12

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-27

System configuration procedures Procedure 6-5.4: External timing with output timing network provisioning

13

14

.................................................................................................................................................................................................

For each of the external timing references (

REF-1

and

REF-2

) , set the following parameters:

•

DS1 Input and Output Format

(

SF

[initial value] or

ESF

).

•

DS1 Input Line Code

(

AMI

[initial value] or

B8ZS

).

.................................................................................................................................................................................................

Click

OK

.

Result:

A warning message may appear. Click

Yes

to execute the command.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

6-28 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures

Procedure 6-5.5: Line timing with output timing network provisioning

.................................................................................................................................................................................................................................

Overview

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 6-5: “Network Element synchronization provisioning”

(p. 6-16) .

Use this procedure to provision the system synchronization source to Line SyncOut

(

line_syncout

). In this mode, the NE derives timing from Main optical lines and provides DS1 synchronization reference outputs that are derived from Main optical lines.

Important! Line SyncOut timing does not apply to Metropolis

®

equipped with an LNW80 Switch Pack.

DMX shelves

Before you begin

The

AIS Threshold

parameter for the timing output ports in this procedure will not work unless Sync Messaging is enabled on the Main OLIU circuit packs, although the

NE will allow the user to change the parameter value. The

AIS Threshold

setting is the sync status message quality level which will generate AIS on the output ports.

To prevent AIS from being generated on the output ports, the sync status message level received from the optical interface synchronization source must be a higher quality than that set for the AIS Threshold.

If required, select

View

→

Timing/Sync

from the System View menu, then select the

Sync Message Status

tab to determine if sync messaging is enabled or disabled.

SByte

in the

Type

column for the Main OLIUs indicates that sync messaging is enabled. If sync messaging is enabled, make a note of the Input Message level for main-1-1 and main-2-1.

If Sync Messaging is to be enabled, use the

Configuration

→

Equipment

command to enable the Sync Messaging parameter for both Main ports. Refer to

Procedure 4-4:

“Provision OLIU circuit packs/ports for service” (p. 4-22) .

Select

View

→

Timing/Sync

from the System View menu, then click on the

Sync

Message Status

tab. Make a note of the Input Message level for main-1-1 and main-2-1.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-29

System configuration procedures

Step

Procedure 6-5.5: Line timing with output timing network provisioning

1

2

3

4

5

6

Complete the following steps to provision a line timed network element with DS1 synchronization outputs.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Timing/Sync

.

Result:

The Configure Timing/Sync window opens.

.................................................................................................................................................................................................

Select the

System Timing

tab.

.................................................................................................................................................................................................

From the

Timing Mode

drop-down menu, select

Line

.

.................................................................................................................................................................................................

For

Output Timing

, select

Enabled

.

With the

Timing Mode

set to

Line

, and

Output Timing

set to

Enabled

, the synchronization mode is set to Line SyncOut.

.................................................................................................................................................................................................

For

Clock Mode Switching

, select

Revertive

or

Nonrevertive

.

•

Revertive

– Initial value. If the system switches to holdover timing due to a failure of the timing references, it will automatically switch back to the provisioned sync mode after one of the references becomes good.

•

Nonrevertive

– If the system switches to holdover timing due to a failure of the timing references, it will stay in holdover even after a timing reference becomes good. The

Fault

→

Timing/Sync Protection Switch

→

Clock Mode Switch

command from the System View menu must be used to restore the system to normal provisioned mode.

.................................................................................................................................................................................................

From the

Reference Switching

drop-down menu box, choose

Revertive-1

,

Revertive-2

, or

Nonrevertive

.

This parameter sets the reference switching mode. If revertive, it also sets which reference has priority. This parameter only applies if synchronization autoreconfiguration is enabled below.

•

Revertive-1

: System selects main-1-1 as primary timing reference.

•

Revertive-2

: System selects main-2-1 as primary timing reference.

•

Nonrevertive

: Initial value, automatic switching is nonrevertive. Whenever a reference is selected from an automatic switch event, the selected reference remains active even if the event that caused the switch is cleared.

.................................................................................................................................................................................................................................

6-30 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures Procedure 6-5.5: Line timing with output timing network provisioning

7

8

9

10

11

.................................................................................................................................................................................................

For

Optical Synchronization Source

, select

main-1-1

or

main-2-1

as the optical line from which shelf timing and DS1 synchronization outputs will be derived.

Important! The sync status message level of the selected line must be higher than the AIS Threshold level setting in

Step 10

to prevent AIS from being generated on the output ports.

.................................................................................................................................................................................................

Important! It is recommended that Synchronization Autoreconfiguration be enabled to provide the most reliable network synchronization.

For

Synchronization Autoreconfiguration

, select

Enabled

or

Disabled

.

If sync auto is disabled, the system goes into holdover when the active timing source fails. If sync auto is enabled, the system automatically switches between timing sources as specified by the setting of the

Reference Switching

parameter.

.................................................................................................................................................................................................

Select the

Timing Output Ports

tab.

.................................................................................................................................................................................................

From the

AIS Threshold

drop-down menu, select one of the following values, if available:

•

SMC

•

ST3

•

ST3E

•

TNC

•

ST2

•

STU

Important! The AIS Threshold function for the timing output ports will not work unless Sync Messaging is enabled on the Main OLIU circuit packs, although the

NE will allow the user to change the AIS threshold value.

.................................................................................................................................................................................................

For each of the DS1 timing references (

REF-1

and

REF-2

) , set the following parameters:

•

DS1 Input and Output Format

(

SF

[initial value] or

ESF

).

•

Timing Output Equalization:

Sets the maximum cable length for 600-type and 1249-type cable.

–

20

(131 feet [600-type], 90 feet [1249-type]) (initial value)

–

40

(262 feet [600-type], 180 feet [1249-type])

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-31

System configuration procedures Procedure 6-5.5: Line timing with output timing network provisioning

12

–

60

(393 feet [600-type], 270 feet [1249-type])

–

80

(524 feet [600-type], 360 feet [1249-type])

–

100

(655 feet [600-type], 450 feet [1249-type])

.................................................................................................................................................................................................

Click

OK

.

Result:

A warning message may appear. Click

Yes

to execute the command.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

6-32 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures

Procedure 6-6: Provision system alarm configuration

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision the following system alarm configuration parameters:

•

Alarm-Clear Delay

Sets the time in seconds that the system waits before reporting that an alarm condition is cleared. Alarm-Clear Delay only applies to equipment alarms, not to signal failures. Signal failures have a fixed 10-second delay.

•

Alarm-Generate Delay

Sets the time in seconds that the system waits before reporting an incoming signal alarm condition.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 6-2)

and

“Required equipment” (p. 6-2)

in this chapter.

2. Obtain the work instructions for this procedure.

Step

1

2

Perform the following steps to provision system alarm parameters.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Alarms

→

Alarm

Configuration

.

Result:

The Configure Alarms window opens.

.................................................................................................................................................................................................

Provision the

Alarm-Clear Delay

and/or

Alarm-Generate Delay

parameters according to the work instructions and Click

OK

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-33

System configuration procedures

Procedure 6-7: Provision new alarm severity assignment profile

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision a new alarm severity assignment profile (ASAP).

To change an existing ASAP, refer to

Procedure 6-8: “Change existing alarm severity assignment profile” (p. 6-36) .

Important! The system supports up to 127 user-created ASAPs. (This does not include DEFAULT ASAPs.) Attempts to create more than 127 user-created ASAPs will be denied. To create another ASAP, delete an existing ASAP and then create the new ASAP. To delete an existing ASAP, refer to

Procedure 6-9: “Delete alarm severity assignment profile” (p. 6-39) .

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 6-2)

and

“Required equipment” (p. 6-2)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions identify the required ASAP type, the new ASAP name, and the alarm severity levels to be provisioned.

Step

1

2

Perform the following steps to provision a new alarm severity assignment profile

(ASAP).

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Alarms

→

Alarm Severity

Assignment Profile

.

Result:

The Provision Alarm Severity Profile window opens.

.................................................................................................................................................................................................

Select the

New ASAP

Operation and the ASAP type to be created from the list. Then click

New ASAP

at the bottom of the window.

.................................................................................................................................................................................................................................

6-34 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures Procedure 6-7: Provision new alarm severity assignment profile

3

4

5

6

7

8

Result:

The ASAP information appears.

.................................................................................................................................................................................................

Provision the ASAP Name and Alarm Severity Levels according to the work instructions and click

Apply

.

Result:

A warning appears asking you to confirm executing this command. Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 2

and

Step 3

to provision another new ASAP. Otherwise, click

Close

.

.................................................................................................................................................................................................

From the System View menu, select

View

→

View Alarms

→

View Alarm Severity

Assignment Profile

.

Result:

The View Alarm Severity Profile window opens.

.................................................................................................................................................................................................

Select the required new ASAP and click

View ASAP

.

Result:

The ASAP details appear.

.................................................................................................................................................................................................

Using the work instructions, verify that the Alarm Severity Levels were provisioned correctly for the new ASAP.

.................................................................................................................................................................................................

If required, repeat

Step 6

and

Step 7

to view another ASAP. Otherwise, click

Close

.

The ASAP is now ready to be assigned to the appropriate entities. To assign an

ASAP to an entity, refer to the appropriate provisioning procedure for the specific entity or

Procedure 6-10: “Assign alarm severity assignment profile” (p. 6-41) .

The provisioned ASAP and alarm severity levels are retained until the ASAP is changed/deleted or a system reset is performed using

Fault

→

Reset

→

Initialize

System

. A system reset removes all user-created ASAPs and changes the alarm severity levels of the DEFAULT ASAPs to the default values.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-35

System configuration procedures

Procedure 6-8: Change existing alarm severity assignment profile

.................................................................................................................................................................................................................................

Overview

Use this procedure to perform the following:

• change the name of a user-created alarm severity assignment profile (ASAP). The name of DEFAULT ASAPs is not user-provisionable.

• change the alarm severity levels of an ASAP.

• restore the default alarm severity levels of a DEFAULT ASAP

To provision a new ASAP, refer to

Procedure 6-7: “Provision new alarm severity assignment profile” (p. 6-34) .

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 6-2)

and

“Required equipment” (p. 6-2)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions identify the required ASAP and the changes to be provisioned.

Step

1

Perform the following steps to change an existing alarm severity assignment profile

(ASAP).

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Alarms

→

Alarm Severity

Assignment Profile

.

.................................................................................................................................................................................................................................

6-36 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures Procedure 6-8: Change existing alarm severity assignment profile

Result:

The Provision Alarm Severity Profile window opens.

.................................................................................................................................................................................................

2 If...

changing the name of a user-created

ASAP, changing the alarm severity levels of a user-created or DEFAULT ASAP, restoring the default alarm severity levels of a DEFAULT ASAP,

Then...

Perform the following:

1. Select the

Provision ASAP

Operation and the ASAP to be changed from the list. Then click

Provision

at the bottom of the window.

2. Provision the New Name and/or Alarm

Severity Levels according to the work instructions and click

Apply

.

A warning appears asking you to confirm executing this command. Click

Yes

.

Perform the following:

1. Select the

Initialize ASAP

Operation and the DEFAULT ASAP to be initialized from the list. Then click

Initialize

at the bottom of the window.

2. Verify the DEFAULT ASAP information and click

Apply

.

A warning appears asking you to confirm executing this command. Click

Yes

.

3

4

5

6

.................................................................................................................................................................................................

If required, repeat

Step 2

to change another ASAP. Otherwise, click

Close

.

.................................................................................................................................................................................................

From the System View menu, select

View

→

View Alarms

→

View Alarm Severity

Assignment Profile

.

Result:

The View Alarm Severity Profile window opens.

.................................................................................................................................................................................................

Select the changed ASAP and click

View ASAP

.

Result:

The ASAP details appear.

.................................................................................................................................................................................................

Using the work instructions, verify that the ASAP Name and/or Alarm Severity Levels were provisioned correctly for the ASAP.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-37

System configuration procedures Procedure 6-8: Change existing alarm severity assignment profile

7

.................................................................................................................................................................................................

If required, repeat

Step 5

and

Step 6

to view another ASAP. Otherwise, click

Close

.

If the ASAP is active, then the changes are applied to the next alarm reported for the entity that the ASAP is assigned to.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

6-38 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures

Procedure 6-9: Delete alarm severity assignment profile

.................................................................................................................................................................................................................................

Overview

Use this procedure to delete a user-created alarm severity assignment profile (ASAP) that is not currently active. DEFAULT ASAPs cannot be deleted.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 6-2)

and

“Required equipment” (p. 6-2)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions identify the user-created ASAP to be deleted.

Step

1

2

3

4

Perform the following steps to delete a user-created alarm severity assignment profile

(ASAP) that is not currently active.

.................................................................................................................................................................................................

Important! The system will not delete an ASAP that is assigned to an entity.

From the System View menu, select

Reports

→

Alarm Severity Assignment Profile

User List

.

Result:

The View Alarm Severity Profile User List window opens.

.................................................................................................................................................................................................

Select the required ASAP to be deleted and click

ASAP User List

.

Result:

The ASAP user list appears.

.................................................................................................................................................................................................

Using the ASAP user list, determine if the ASAP to be deleted is currently assigned to an entity (active). Record any entities that are listed.

.................................................................................................................................................................................................

If required, repeat

Step 2

and

Step 3

to view the user list for another ASAP. Otherwise, click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-39

System configuration procedures Procedure 6-9: Delete alarm severity assignment profile

5

6

7

8

9

10

.................................................................................................................................................................................................

If the ASAP to be deleted is currently assigned to an entity, assign another ASAP to the entity.

Reference:

Procedure 6-10: “Assign alarm severity assignment profile” (p. 6-41)

.................................................................................................................................................................................................

Select

Configuration

→

Alarms

→

Alarm Severity Assignment Profile

.

Result:

The Provision Alarm Severity Profile window opens.

.................................................................................................................................................................................................

Select the

Delete ASAP

Operation and the ASAP to be deleted from the list. Then click

Delete

at the bottom of the window.

Result:

The ASAP information appears.

.................................................................................................................................................................................................

Verify the ASAP information and click

Apply

.

Result:

A warning appears asking you to confirm executing this command. Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 7

and

Step 8

to delete another ASAP. Otherwise, click

Close

.

.................................................................................................................................................................................................

Select

View

→

View Alarms

→

View Alarm Severity Assignment Profile

and verify that the ASAP was deleted.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

6-40 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures

Procedure 6-10: Assign alarm severity assignment profile

.................................................................................................................................................................................................................................

Overview

Use this procedure to assign a DEFAULT or user-created alarm severity assignment profile (ASAP) to an entity within the system (for example, system, circuit pack, or port).

ASAPs cannot be preassigned to an entity before the entity is created in the system.

When an entity is created in the system (for example, a slot is equipped with a circuit pack), the system assigns the associated DEFAULT ASAP to the entity.

Different ASAPs within an ASAP type may be assigned to different entities within the system; however, only one ASAP may be assigned to an entity at a time. Assigning a different ASAP to an entity will override the previous assignment. The specified ASAP must agree with the allowed ASAP type for that entity in order to be assigned to the entity.

To create a new ASAP, refer to

Procedure 6-7: “Provision new alarm severity assignment profile” (p. 6-34) .

To change an existing ASAP, refer to

Procedure 6-8: “Change existing alarm severity assignment profile” (p. 6-36) .

ASAP types

The system supports the following ASAP types:

•

1+1 Bidirectional Protection Group

•

1+1 Optimized Protection Group

•

BLSR Protection Group

•

Data Port

•

DS1 Port

•

DS3 Port

•

E1 Port

•

EC1 Port

•

Circuit Pack

•

Fast Ethernet Port

•

Gigabit Ethernet Port

•

Non-Volatile Memory Module

•

OCn Port

•

Pluggable Transmission Module

•

STS Ring Channel

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-41

System configuration procedures Procedure 6-10: Assign alarm severity assignment profile

•

System

•

System Timing

•

VC12 Ring Channel

•

VCG Port

•

VCG STS Tributary

•

VCG VT1.5 Tributary

•

VT1.5 Ring Channel

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 6-2)

and

“Required equipment” (p. 6-2)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions identify the entity (for example, system, circuit pack or port) and the ASAP to be assigned.

Step

1

2

3

4

Perform the following steps to assign a DEFAULT or user-created alarm severity assignment profile (ASAP) to an entity within the system (for example, system, circuit pack, or port).

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Equipment

.

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Select the required entity according to the work instructions and click

Select

.

Result:

The provisionable parameters appear.

.................................................................................................................................................................................................

If required, click

View Details

to view the DEFAULT ASAP and the user-created

ASAPs (if provisioned) for the associated ASAP type. Click

Close

.

.................................................................................................................................................................................................

Select the required ASAP according to the work instructions and click

Apply

.

.................................................................................................................................................................................................................................

6-42 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures Procedure 6-10: Assign alarm severity assignment profile

5

6

7

Result:

A warning may appear asking you to confirm executing this command.

Click

Yes

. Click

Close

to exit.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Equipment

.

Result:

The View Equipment window opens.

.................................................................................................................................................................................................

Select the required entity according to the work instructions and click

Select

.

Result:

The entity details appear.

.................................................................................................................................................................................................

Using the work instructions, verify that the correct ASAP was assigned to the entity.

Click

Close

to exit.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-43

System configuration procedures

Procedure 6-11: Evaluate bandwidth utilization

.................................................................................................................................................................................................................................

Overview

Use this procedure to view backplane and VT fabric utilization and evaluate whether to manually optimize backplane bandwidth between the main packs and specified LS group(s).

For more information on the impact of optimization, see Procedure 6-12: “Optimize backplane bandwidth” (p. 6-46) .

Important! Optimization will only change the internal cross-connection routing; it will not change the endpoints of any cross-connections.

Excessive fragmentation warnings

You can determine if excessive fragmentation exists in the following ways:

•

If you provision a new cross-connection and the backplane bandwidth necessary to support the cross-connection is not available, the command will be denied with a

SARB (Status All Resources Busy) error response.

•

You can check the backplane utilization for each transmission pack and the VT fabric utilization for the main pack in the shelf. You can use the CIT to display the information or view the raw utilization data in the output of the RTRV-ST-EQPT command.

Privilege level

You must login as a Privileged or General user to complete this procedure.

Before you begin

Refer to

“Before you begin” (p. 6-2)

and

“Required equipment” (p. 6-2)

in this chapter.

Step

1

Important! For Ethernet packs that support VT cross-connections, only the backplane utilization parameters are reported; VT utilization is not reported on the

LNW74 pack.

Use the following procedure to evaluate whether you need to optimize backplane bandwidth.

.................................................................................................................................................................................................

Login to the shelf you want to evaluate.

.................................................................................................................................................................................................................................

6-44 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures Procedure 6-11: Evaluate bandwidth utilization

2

.................................................................................................................................................................................................

Choose from the following reports that may help you evaluate the current bandwidth usage on your shelf or system.

If you want to...

View backplane utilization for all function packs on the system. Use to determine when manual defragmentation is necessary.

View STS fabric utilization and VT fabric utilization

(when available) on a per slot basis

View XC fabric utilization for main and function packs to see when you are reaching the limits of capacity and need to plan for more shelves.

Then choose this report..

View backplane bandwidth utilization

View backplane bandwidth utilization

XC fabric utilization

Using this Invocation...

Reports

→

Backplane

Bandwidth Utilization

View

→

Backplane

Bandwidth Utilization

Reports

→

VT XC Fabric

Utilization

3

4

.................................................................................................................................................................................................

View the information presented. For more information on the details provided in these reports, click the help button in the reports screen.

.................................................................................................................................................................................................

If you decide to perform the backplane bandwidth optimization operation, see

Procedure 6-12: “Optimize backplane bandwidth” (p. 6-46)

for details about this operation.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-45

System configuration procedures

Procedure 6-12: Optimize backplane bandwidth

.................................................................................................................................................................................................................................

Overview

Use this procedure to manually optimize the backplane bandwidth between the main packs and the specified LS group(s).

To determine if you need to optimize bandwidth for a particular circuit pack, see

Procedure 6-11: “Evaluate bandwidth utilization” (p. 6-44)

Defragmentation behaviors

Important! For Ethernet packs that support VT cross-connections, only the backplane utilization parameters are reported; VT utilization is not reported on the

LNW74 pack.

The following behaviors apply when you perform the defragmentation operation:

•

Rearrangements do not interrupt traffic on cross-connections that are not being rearranged.

•

No misconnections are caused by rearrangement.

•

For the LNW70 in STS1 mode, rearrangements are not necessary since higher rate cross-connections are not supported.

•

For the LNW74, the VT vs. STS backplane partitioning is preserved during defragmentation of the backplane bandwidth. When enabled, the first 12 backplane

STS1s are reserved for VT-cross connections only. The remaining 36 STS1s are reserved for STS cross-connections only. VT cross-connections are rearranged only within the first 12 STS1s and STS cross-connections will be arranged only within the last 36 STS1s.

•

Backplane optimization will only affect packs on which the backplane bandwidth is dynamically assigned. During cross-connection provisioning, the NE dynamically assigns the I/O tributaries to the backplane tributaries on the following circuit packs:

– LNW45 and LNW49 that support the VT grooming on the tributary fabrics

– LNW63, LNW70, LNW73/LNW73C, and LNW74 where the number of VCG tributaries exceeds the available backplane bandwidth.

•

The optimize backplane bandwidth operation removes the fragmentation at the

STS1, STS3c and STS12c levels and minimizes the number of STS1s required to transport cross-connected VTs to the main packs. Interruptions will vary from 1 second (OCn) to 3 seconds (Ethernet) in duration on VT1, STS1 and STS3c cross-connections each time they are rearranged.

.................................................................................................................................................................................................................................

6-46 365-372-301 R6.0

Issue 15, January 2006

System configuration procedures Procedure 6-12: Optimize backplane bandwidth

Excessive fragmentation

You can determine if excessive fragmentation exists in the following ways:

•

When you provision a new cross-connection and the backplane bandwidth necessary to support the cross-connection is not available, the command will be denied with a SARB (Status All Resources Busy) error response.

•

You can check the backplane utilization for each transmission pack and the VT fabric utilization for the main pack in the shelf. You can use the CIT to display the information or by view the raw utilization data in the output of the RTRV-ST-EQPT command.

Privilege level

You must login as a Privileged or General user to complete this procedure.

Before you begin

Refer to

“Before you begin” (p. 6-2)

and

“Required equipment” (p. 6-2)

in this chapter.

Step

CAUTION

Service disruption hazard

The following conditions apply to traffic interruptions on a rearranged cross-connection:

•

Protection switching requests may be suspended for up to 25 seconds during rearrangement.

•

Traffic interruptions due to rearrangement will vary from 1 second (OCn) to 3 seconds (Ethernet with LCAS disabled). A given cross-connection is not be rearranged more than once in response to a single optimization.

•

Rearrangement of traffic to or from an individual function group completes within 85 seconds. Rearrangement of all function groups completes within

200 seconds.

•

When LCAS is enabled on an Ethernet pack, the duration of the traffic interruption increases to a maximum of 30 seconds.

Disable LCAS prior to performing a rearrangement operation on an

Ethernet/Data interface.

Complete the following steps to optimize backplane bandwidth.

1

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Optimize Backplane

Bandwidth

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

6-47

System configuration procedures Procedure 6-12: Optimize backplane bandwidth

2

3

4

Result:

The

Equipment Selection

screen opens.

The Equipment Selection screen will not open under the following conditions:

•

If there are any existing test access sessions in the NE, you will see the following error message: “Optimize Backplane Bandwidth is not allowed when there are test access sessions existing in the NE.”

•

If the NE is in Ring Upgrade mode, you will see the following error message:

“Optimize Backplane Bandwidth is not allowed when the NE is in Ring

Upgrade mode.”

•

If there is no applicable function pack in the system, you will see the following message: “There are no applicable function packs for Optimizing Backplane

Bandwidth in the system.”

.................................................................................................................................................................................................

From the

Equipment Selection

screen, highlight the required functional pack or the system.

Only the system and function slots equipped with LNW63, LNW45, LNW49, LNW70,

LNW73/LNW73C, or LNW74 circuit packs will be displayed in the equipment selection screen.

.................................................................................................................................................................................................

Click

Select

.

Important! Defragmentation will not be initiated if one of the following conditions exist:

•

If any test access sessions exist on the NE.

•

If the system is in ring upgrade mode.

.................................................................................................................................................................................................

Important! Optimizing backplane bandwidth for the System (All) may take up to four minutes, and protection switching may be disabled for up to 25 seconds during optimization.

A confirmation window opens warning you that execution of this command may affect

NE service. Choose one of the following:

•

Yes

- to initiate optimization.

•

No

- to close the message box, then click

Close

to return to the NE view.

Result:

A confirmation message will appear in the Most Recent Command status bar of the CIT System View.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

6-48 365-372-301 R6.0

Issue 15, January 2006

7

7

procedures

Overview

.................................................................................................................................................................................................................................

Purpose

Use the procedures in this chapter as reference for provisioning optional system administration parameters from the System View

Administration

menu.

This chapter includes procedures used to:

•

Change your own password (Change Password)

•

Provision User and Network Element Security

•

Provision Data Communications

•

Set TL1 Message Map

•

Change NE Login Banner

•

Set Date and Time

•

Set TID (system name)

•

Set NE defaults (FTP, AGNE, remote NE status)

•

Provision Network Time Protocol

Depending on local procedures, types of configurations, and shelf equipage, some of the optional parameters may need to be set. It is assumed that local system administration is responsible for determining these parameter settings. Some of the parameter values may be set during the initial shelf turn-up. Other parameter values may be set after the system is integrated into the network configuration.

Contents

Before you begin

Procedure 7-1: Provision system administration parameters

Procedure 7-2: Change your own password

Procedure 7-3: Edit, delete, or enter a user’s login

7-3

7-4

7-10

7-12

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-1

System administration procedures

Procedure 7-4: Enable/disable lockout security state

Procedure 7-5: Provision system SNMP management features

Procedure 7-6: Edit, delete, or enter SNMP users

Procedure 7-7: Allow/inhibit autonomous message reporting

Procedure 7-8: Create or edit login banner

Procedure 7-9: Set NE defaults — alarm gateway, alarm group, remote

NE status, FTP/FTTD, security and history log thresholds

Procedure 7-10: Set date and time

Procedure 7-11: Set/change system TID

Procedure 7-12: Enable/disable OSI on an IAO LAN port

Procedure 7-13: Provision network layer 3 parameters

Procedure 7-14: Set TARP parameters

Procedure 7-15: Provision TCP/IP and Proxy ARP on an IAO LAN port

Procedure 7-16: Provision/enable/disable the NE as a TL1 TCP/IP GNE

Procedure 7-17: Provision static IP routes on DCC links

Procedure 7-18: Provision RS232 CIT (CIT-1) and/or MODEM (CIT-2) serial port parameters

Procedure 7-19: Map TL1 message types to OS applications

Procedure 7-20: Enable/disable user ID(s)

Procedure 7-21: Provision network element security

Procedure 7-22: Log out user(s)

Overview

7-33

7-38

7-39

7-40

7-43

7-46

7-49

7-52

7-54

7-57

7-59

7-61

7-63

7-16

7-17

7-20

7-24

7-26

7-28

.................................................................................................................................................................................................................................

7-2 365-372-301 R6.0

Issue 15, January 2006

System administration procedures

Before you begin

.................................................................................................................................................................................................................................

Before you begin

Prior to performing all procedures in this chapter,

1. If not previously completed, install generic and WaveStar

®

CIT software on the PC.

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

2. Connect PC and establish a WaveStar

®

CIT session.

Refer to

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24) .

Required equipment

All procedures in this chapter require that the following equipment is available:

•

Personal Computer (PC) with WaveStar

®

CIT software installed

•

Wrist strap

Important! If additional equipment is required to perform a specific procedures, that additional equipment is listed in that procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-3

System administration procedures

Procedure 7-1: Provision system administration parameters

.................................................................................................................................................................................................................................

Overview

Use this procedure as reference for provisioning optional system administration parameters from the System View

Administration

menu.

Administration parameters allow you to:

•

Change your own password (Change Password)

•

Provision User and Network Element Security

•

Provision Data Communications

•

Set TL1 Message Map

•

Change NE Login Banner

•

Set Date and Time

•

Set TID (system name)

•

Set NE defaults (FTP, AGNE, remote NE status)

•

Provision Network Time Protocol.

Depending on local procedures, types of configurations, and shelf equipage, some of the optional parameters may need to be set. It is assumed that local system administration is responsible for determining these parameter settings.

Some of the parameter values may be set during the initial shelf turn-up. Other parameter values may be set after the system is integrated into the network configuration.

Step

1

Use the sections in this procedure as reference for setting system administration parameters.

.................................................................................................................................................................................................

Reference the sections in this procedure to provision the required Administration parameters from your work instructions.

Important! Some of the parameters may have already been provisioned from earlier procedures.

E

N D O F

S

T E P S

Change Password

This command allows any user to change his/her own password.

Administration

→

Change Password

.................................................................................................................................................................................................................................

7-4 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-1: Provision system administration parameters

Procedure 7-2: “Change your own password” (p. 7-10)

Security

This command allows privileged users and in some cases also administration users to perform the following:

•

User Security Provisioning

Administration

→

Security

→

Provision User Logins

Procedure 7-3: “Edit, delete, or enter a user’s login” (p. 7-12)

Creates or modifies another user’s security data (for example, user IDs and passwords).

•

Enable/Disable Lockout Security State (privileged users only)

Administration

→

Security

→

Enable Lockout Security

State Administration

→

Security

→

Disable Lockout Security State

Procedure 7-4: “Enable/disable lockout security state” (p. 7-16)

Enables or locks out non-privileged user ID access to the NE.

•

Enable/Disable User IDs

Administration

→

Security

→

Enable User Login Administration

→

Security

→

Disable User Login

Procedure 7-20: “Enable/disable user ID(s)” (p. 7-59)

Enables/disables one or all non-default user logins.

•

Log Out Other Network Element Users

Administration

→

Security

→

Logout NE User

Procedure 7-22: “Log out user(s)” (p. 7-63)

Terminates the login session of the user executing this command in addition to either one user, or all non-privileged, or all non-administration users. Privileged or administration users must be terminated one user at a time.

•

Network Element Security Provisioning

Administration

→

Security

→

Provision NE Security

Procedure 7-21: “Provision network element security” (p. 7-61)

Provisions network element level security parameters (for example, User ID

Lockout Threshold).

•

SNMP User Provisioning (privileged users only)

Administration

→

Security

→

Provision SNMP Users

Procedure 7-6: “Edit, delete, or enter SNMP users” (p. 7-20)

Related SNMP provisioning may require LAN port provisioning, IP Routing,

TCP/IP access.

Allow/Inhibit Autonomous Message Reporting

This command allows any user to enable or disable autonomous messages for their login session.

Administration

→

Allow/Inhibit Autonomous Message Reporting

→

Current

Session

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-5

System administration procedures Procedure 7-1: Provision system administration parameters

Procedure 7-7: “Allow/inhibit autonomous message reporting” (p. 7-24)

Allows/Inhibits reporting of autonomous alarm and status messages on a user basis per login session. Select Enabled or Disabled as required.

Change NE Login Banner

This command allows a privileged user to add a user-defined proprietary notice at login to enhance system security.

Administration

→

Change NE Login Banner

Procedure 7-8: “Create or edit login banner” (p. 7-26)

Set NE

This command allows a privileged user to provision the NE defaults for the following:

•

Enable/Disable remote NE status

•

Enable/Disable the NE as an Alarm Gateway Network Element (AGNE) and assign alarm group numbers

•

Enable/Disable File Transfer Protocol (FTP)

•

Enable/Disable FTAM-FTP Gateway

•

Provision the security and history log warning threshold.

Administration

→

Set NE

Procedure 7-9: “Set NE defaults — alarm gateway, alarm group, remote NE status,

FTP/FTTD, security and history log thresholds” (p. 7-28)

Set Date and Time

This command allows a privileged user to manually set the Date and Time for this NE.

Administration

→

Set Date and Time

Procedure 7-10: “Set date and time” (p. 7-33)

Note that this command is used to manually set the Date and Time for the NE. If you are using Network Time Protocol, refer to

Administration

→

Set Network Time

Protocol

Procedure 7-10: “Set date and time” (p. 7-33)

Set TID

This command allows a privileged user to set the Target Identifier (TID) for this NE.

The more common time to change a TID is prior to placing the system in-service.

However, this procedure can also be used to change the TID of an in-service system.

Administration

→

Set TID

.................................................................................................................................................................................................................................

7-6 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-1: Provision system administration parameters

Procedure 7-11: “Set/change system TID” (p. 7-38)

The TID is a character string from 1 to 20 characters and must be unique for each NE in the network.

Data Communications

This command allows a privileged user to provision data communications functions.

Administration

→

Data Communications

Selecting one of the following tabs allows a privileged user to provision Data

Communications parameters:

•

IP Routing

Use this procedure to provision IP Routing functionality to utilize DCC Channels for IP communications.

Procedure 9-10: “Add IP route(s) through network” (p. 9-113)

Use this procedure to provision static IP routes over DCC links.

Procedure 7-17: “Provision static IP routes on DCC links” (p. 7-52)

•

TCP/IP Gateway

Use this procedure to enable or disable the Metropolis

®

DMX as a TL1 TCP/IP

GNE and provision authorized IP calling OS host addresses.

Note that TCP/IP functionality must also be enabled and the required TCP/IP parameters provisioned for at least one of the NE’s IAO LAN ports.

Procedure 7-16: “Provision/enable/disable the NE as a TL1 TCP/IP GNE” (p. 7-49)

•

Serial Port

Use this procedure to provision the selected CIT-1 and/or CIT-2 serial port parameters. The user of a serial port may adjust the echo and baudrate parameters of the port. Only a privileged user may modify the parameters without using the serial port.

Procedure 7-18: “Provision RS232 CIT (CIT-1) and/or MODEM (CIT-2) serial port parameters” (p. 7-54)

•

SNMP Management

Use this procedure to provision system SNMP management features.

Related SNMP provisioning may require LAN port provisioning, IP Routing, and

TCP/IP access.

Procedure 7-5: “Provision system SNMP management features” (p. 7-17)

•

OSI LAN Management

Use this procedure to enable or disable the OSI-LAN port status for LAN ports lan-1 and/or lan-2.

Procedure 7-12: “Enable/disable OSI on an IAO LAN port” (p. 7-39)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-7

System administration procedures Procedure 7-1: Provision system administration parameters

•

Network Layer

Use this procedure to modify the NSAP address and provision the node as a Level

1 or Level 1&2 router.

Values should not be changed from default values except by users who intend to provision the SONET subnetwork and partition DCC communications.

Procedure 7-13: “Provision network layer 3 parameters” (p. 7-40)

•

NSAP Threshold Alarming

Use this procedure to provision the NSAP count threshold level for monitoring the number of NSAPs in the level 1 area.

Procedure 7-13: “Provision network layer 3 parameters” (p. 7-40)

•

TARP

,

TARP Data Cache

, and

TARP Manual Adj.

Use this procedure to provision user settable fields and functions relating to TARP

Propagation and Origination parameters, TARP Data Cache entries, and TARP

Manual Adjacencies.

Procedure 7-14: “Set TARP parameters” (p. 7-43)

•

TCP/IP

Use this procedure to provision, enable, or disable TCP/IP on an IAO LAN Port.

This is also used to enable or disable proxy Address Resolution Protocol (ARP) on an IAO LAN port.

Procedure 7-15: “Provision TCP/IP and Proxy ARP on an IAO LAN port” (p. 7-46)

Set TL1 Message Map

This command allows you to map TL1 autonomous message types to an OS type application context ID (ACID). TL1 autonomous messages are not reported unless they are assigned to an OS type. This command allows a user to assign specific TL1 autonomous message types, or none at all.

Administration

→

Set TL1 Message Map

Procedure 7-19: “Map TL1 message types to OS applications” (p. 7-57)

Set Network Time Protocol

This command allows you to provision the Network Time Protocol (NTP) Server properties for this NE.

Administration

→

Set Network Time Protocol

Procedure 7-10: “Set date and time” (p. 7-33)

Note that this command is used to provision the Network Time Protocol server for this

NE. If you are not using NTP, manually set the Date and Time for this NE using the following:

Administration

→

Set Date and Time

Procedure 7-10: “Set date and time” (p. 7-33)

.................................................................................................................................................................................................................................

7-8 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-1: Provision system administration parameters

If you are using NTP, it is assumed that either IP Routing has already been established or each node has its own IP address.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-9

System administration procedures

Procedure 7-2: Change your own password

.................................................................................................................................................................................................................................

Overview

Use this procedure to change your own network element password.

Privilege level

You may login as a either a privileged, administration, general, maintenance, or reports only user to complete this procedure.

Important! Only users with a privileged or administration access code may change other user’s passwords. See

Procedure 7-3: “Edit, delete, or enter a user’s login”

(p. 7-12) .

Password guidelines

Passwords must adhere to the following guidelines:

•

Passwords must be six to ten characters in length.

•

Passwords must contain at least one alphabetic character and at least three non-alphabetic characters (numbers and symbols).

Of the three non-alphabetic characters, at least one must be a symbol and at least one must be a number. The third non-alphabetic character may be either a symbol or number.

The remaining characters in the password may be any combination of alphabetic and non-alphabetic characters.

Symbols may not include space ( ), at (

@

), comma (

,

), colon (

:

), equals sign (

=

), quotation mark (

″

), semicolon (

;

), asterisk (*), exclamation mark (

!

), question mark

(

?

), or back slash (

\

).

•

Passwords are case-sensitive.

•

When passwords are changed, the old and new passwords must be different in at least 3 character positions. The original password, or a significant substring of it, must not be part of the new password.

If the current and new passwords are the same length, then the characters in at least

3 character positions must be different.

If the current and new passwords are different lengths, then for each possible contiguous sub-string of the length of the shorter password within the longer password, the characters in at least 3 character positions must be different between the shorter password and the character sub-string within the longer password.

The network element does not allow reuse of the five most recently used passwords.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

.................................................................................................................................................................................................................................

7-10 365-372-301 R6.0

Issue 15, January 2006

System administration procedures

Step

Procedure 7-2: Change your own password

1

2

Complete the following steps to change your own network element password.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Change Password

to change your own password on an individual NE basis.

Result:

The Change Password window opens.

.................................................................................................................................................................................................

Enter your old password, enter your new password, and then re-enter your new password for confirmation. Click

OK

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-11

System administration procedures

Procedure 7-3: Edit, delete, or enter a user’s login

.................................................................................................................................................................................................................................

Overview

Use this procedure to:

•

Edit an existing user’s network element login parameters

•

Delete an existing user’s network element login parameters

•

Enter a new user’s network element login parameters.

Privilege level

You must log in as a Privileged or Administration user to complete this procedure.

User ID guidelines

User IDs must adhere to the following guidelines:

•

User IDs must be five to ten alphanumeric characters in length.

•

User IDs may not include any symbols.

•

User IDs are case sensitive.

Password guidelines

Passwords must adhere to the following guidelines:

•

Passwords must be six to ten characters in length.

•

Passwords must contain at least one alphabetic character and at least three non-alphabetic characters (numbers and symbols).

Of the three non-alphabetic characters, at least one must be a symbol and at least one must be a number. The third non-alphabetic character may be either a symbol or number.

The remaining characters in the password may be any combination of alphabetic and non-alphabetic characters.

Symbols may not include space ( ), at (

@

), comma (

,

), colon (

:

), equals sign (

=

), quotation mark (

″

), semicolon (

;

), asterisk (*), exclamation mark (

!

), question mark

(

?

), or back slash (

\

).

•

Passwords are case sensitive.

•

When passwords are changed, the old and new passwords must be different in at least 3 character positions. The original password, or a significant substring of it, must not be part of the new password.

If the current and new passwords are the same length, then the characters in at least

3 character positions must be different.

If the current and new passwords are different lengths, then for each possible

.................................................................................................................................................................................................................................

7-12 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-3: Edit, delete, or enter a user’s login contiguous sub-string of the length of the shorter password within the longer password, the characters in at least 3 character positions must be different between the shorter password and the character sub-string within the longer password.

The network element does not allow reuse of the five most recently used passwords.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

Step

Complete the following steps to edit, delete, or enter a user’s login parameters. For additional information about provisionable entries required in this procedure, refer to

Appendix A, “Provisionable parameters” .

.................................................................................................................................................................................................

1

If...

Entering a new user’s login,

Editing an existing user’s login,

Delete an existing user’s login,

Then...

Continue with

Proceed to

Proceed to

Step 2

Step 3

Step 4

.

.

.

2

.................................................................................................................................................................................................

Important! Refer to

“User ID guidelines” (p. 7-12)

and

“Password guidelines”

(p. 7-12) .

ENTER A NEW USER LOGIN:

1. From the System View menu select

Administration

→

Security

→

Provision User

Logins

.

2. From the

User ID Panel

, select

New User

and enter a new user ID in the adjacent field.

3. From the

User Type

panel, select a Security Level for the new user from the pull-down menu.

4. From the

User Password

panel, enter a password for the new user in the

Enter

Password:

and Confirm Password: fields.

5. From the

Password Aging Period

panel, select Disable to disable the password aging function, or enter the number of days (from

7

-

999

) before the new user has to change his/her password.

6. From the

Inactivity Timeout Interval

panel, select Disable to disable the timeout function, or enter the number of minutes (from

1

-

999

) before the new user session is logged off because of inactivity.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-13

System administration procedures Procedure 7-3: Edit, delete, or enter a user’s login

3

4

7. From the

Login ID Status

panel, select Enable or Disable to enable/disable the user ID.

8. From the buttons at the bottom of the screen, click

Add

.

9. Proceed to

Step 5 .

.................................................................................................................................................................................................

Important! Refer to

“User ID guidelines” (p. 7-12)

and

“Password guidelines”

(p. 7-12) .

EDIT EXISTING USER LOGIN:

1. From the System View, menu select

Administration

→

Security

→

Provision

User Logins

.

2. From the

User ID Panel

, select

Existing User

and an existing user ID from the pull-down menu.

The remaining items in this step may be completed as required. Items not changed will retain existing settings.

3. From the

User Type

panel, select a Security Level for the user from the pull-down menu.

4. From the

User Password

panel, enter a password for the user in the

Enter

Password

and Confirm Password fields.

5. From the

New User ID

panel, enter the new ID for the existing user in the

Enter

New User ID

field.

6. From the

Password Aging Interval

panel, select Disable to disable the password aging function, or enter the number of days (from

7

-

999

) before the user has to change his/her password.

7. From the

Inactivity Timeout Period

panel, select Disable to disable the timeout function, or enter the number of minutes (from

1

-

999

) before the user session is logged off because of inactivity.

8. From the

Login ID Status

panel, select Enable or Disable to enable/disable the user ID.

9. From the

Lockout Status

panel, select ENABLE_LOGIN to enable a user ID that has been locked out.

10. From the buttons at the bottom of the screen, click

Modify

.

11. Proceed to

Step 5 .

.................................................................................................................................................................................................

Important! Default privileged users cannot be deleted. Non-default Privileged users may be deleted.

.................................................................................................................................................................................................................................

7-14 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-3: Edit, delete, or enter a user’s login

5

DELETE A USER LOGIN:

1. From the System View, menu select

Administration

→

Security

→

Provision

User Logins

.

2. From the

User ID Panel

, select

Existing User

and an existing user ID from the pull-down menu.

3. From the buttons at the bottom of the screen, click

Delete

.

4. Proceed to

Step 5 .

.................................................................................................................................................................................................

Do you want to continue provisioning?

If...

Yes,

No,

Then...

Return to

Step 1 .

STOP! End of Procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-15

System administration procedures

Procedure 7-4: Enable/disable lockout security state

.................................................................................................................................................................................................................................

Overview

Use this procedure to:

•

Enable all nonprivileged user IDs to access to a network element

•

Lockout all nonprivileged user IDs from the network element.

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

Step

Complete the following steps to enable or disable the lockout security state.

1

.................................................................................................................................................................................................

If...

Enabling all nonprivileged user IDs to access the network element,

Locking out all nonprivileged user IDs from the network element,

Then...

From the System View menu, select

Administration

→

Security

→

Disable Lockout Security State

.

A dialog box appears asking you to confirm executing this command. Click

Yes

.

From the System View menu, select

Administration

→

Security

→

Enable Lockout Security State

.

A dialog box appears asking you to confirm executing this command. Click

Yes

.

2

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Data Communications

.

•

From the

Serial Port

tab, verify the

Access State

information for the CIT Port (

In

Service

or

Lockout

).

•

From the

OSI LAN Management

tab, verify the

Access State

information for the

LAN Port (

In Service

or

Lockout

).

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

7-16 365-372-301 R6.0

Issue 15, January 2006

System administration procedures

Procedure 7-5: Provision system SNMP management features

.................................................................................................................................................................................................................................

Overview

Use this procedure to:

•

Provision SNMP contact and location information

•

Enable or disable SNMP authentication failure traps.

To provision SNMP access to the network element from an SNMP manager, refer to

Procedure 7-6: “Edit, delete, or enter SNMP users” (p. 7-20) .

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. If you want to view, print, or save a file of current SNMP users, select

Administration

→

Security

→

View SNMP Users

from the System View menu.

Step

1

2

Perform the following steps to provision the SNMP management feature.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Data Communications

.

Result:

The Data Communications window opens.

.................................................................................................................................................................................................

Click on the

SNMP Management

tab to view parameters.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-17

System administration procedures Procedure 7-5: Provision system SNMP management features

3

4

5

.................................................................................................................................................................................................

Enter the following parameters according to the work instructions and click

Apply

:

•

NE Contact

Contact Name

: an alphanumeric string of up to 255 characters consisting of the name of the contact person for this NE and how to contact the person.

•

NE Location

Location Name:

an alphanumeric string of up to 255 characters describing the physical location of this NE.

•

SNMP Authentication Failure Trap

SNMP Trap Control:

Select Enable or Disable.

Traps are the SNMP equivalent of SONET alarm and event autonomous messages.

Enabling this feature results in the network element sending an Authentication

Failure trap to all registered SNMP users if an SNMP request is received from an unauthorized user. An unauthorized user is a user whose IP address/community ID pair do not match an entry in the NE’s SNMP User list. To add a user to the

SNMP User list, refer to

Procedure 7-6: “Edit, delete, or enter SNMP users”

(p. 7-20) .

Disabling this feature prevents traps from being sent if there is an authentication failure.

Result:

A dialog box may appear asking you to confirm executing this command.

.................................................................................................................................................................................................

Click

Yes

.

Result:

A warning message appears stating that a reset is required before any

SNMP provisioning changes take effect and that a reset causes all active login sessions to be logged out.

Continue with

Step 5 .

.................................................................................................................................................................................................

Do you wish to perform SNMP User provisioning?

If...

Yes

No

Then...

Click

No

on the warning window. Then click

Close

and refer to

Procedure 7-6: “Edit, delete, or enter SNMP users” (p. 7-20) .

If you select to NOT reset in this procedure, you must perform a Phase 3 reset (

Fault

→

Reset

→

System Controller

) before your changes take place.

Continue with

Step 6 .

.................................................................................................................................................................................................................................

7-18 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-5: Provision system SNMP management features

6

7

8

.................................................................................................................................................................................................

Click

Yes

in the warning window to complete SNMP provisioning.

Result:

The following warning message appears The network element is resetting

due to System Reset.

.................................................................................................................................................................................................

Click

OK

.

Result:

The System View closes, the network element resets, and all active users are disconnected.

A flashing

b

in the

IND

display on the SYSCTL indicates that a boot is in progress.

During the boot, the

b

may extinguish for up to 20 seconds and then resume flashing.

.................................................................................................................................................................................................

If you want to view, print, or save a file of current SNMP users, then log back into the network element and select

Administration

→

Security

→

View SNMP Users

from the System View menu.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-19

System administration procedures

Procedure 7-6: Edit, delete, or enter SNMP users

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision SNMP management access to the system.

To provision SNMP contact/location information and enable/disable SNMP authentication failure traps, refer to

Procedure 7-5: “Provision system SNMP management features” (p. 7-17) .

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. If you want to view, print, or save a file of current SNMP users, select

Administration

→

Security

→

View SNMP Users

from the System View menu.

Step

1

Perform the following steps to edit, delete, or enter SNMP users.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Security

→

Provision SNMP

Users.

Result:

The Provision SNMP Users window opens to allow you to add, modify, or delete an SNMP user.

Any specific value of either SNMP User Community ID or source IP address can be used to create more than one SNMP User, as long as the specific values of the pair of parameters are not duplicated.

This command can be used to create up to 20 SNMP Users. There can be a maximum of 10 SNMP Users enabled for request functionality (for example,

GetRequest, GetNextRequest, GetBulkRequest) and a maximum of up to 10 SNMP

Users enabled for receiving traps.

.................................................................................................................................................................................................................................

7-20 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-6: Edit, delete, or enter SNMP users

2

.................................................................................................................................................................................................

Determine the required provisioning.

If...

add a new SNMP user, modify an existing SNMP user, delete an existing SNMP user,

Then...

Continue with

Step 3 .

Proceed to

Step 4 .

Proceed to

Step 5 .

3

4

.................................................................................................................................................................................................

Perform the following to ADD A NEW USER:

1. Select

New User

in the SNMP User Community ID Panel.

2. Enter the User Community Identifier as a case-sensitive alphanumeric string of 6 to

20 characters in the box provided.

Note that spaces are not allowed in the string of characters.

3. Click on the

Modify

button under SNMP User IP Address Panel.

The Provision SNMP User IP Address window opens.

4. Enter the 32-bit IP address consisting of four dot-separated decimal numbers from

0-255. Click

OK

.

5. Under Request Functionality Control, select

Enable

or

Disable

to enable or disable request functionality (i.e., GetRequest, GetNextRequest, GetBulkRequest). Default is

Enabled

.

6. Under Trap Functionality Control, select

Enable

or

Disable

to enable or disable the SNMP User for receiving traps. Default is

Enabled

.

7. Click

Add

at the bottom of the window.

Result:

A warning message appears stating that a reset is required before any

SNMP provisioning changes take effect and that a reset causes all active login sessions to be logged out.

Proceed to

Step 6 .

.................................................................................................................................................................................................

Perform the following to MODIFY AN EXISTING USER:

1. Select

Existing User

in the SNMP User Community ID Panel.

2. In the drop-down box, select (highlight) the user to be modified.

3. Under Request Functionality Control, select

Enable

or

Disable

to enable or disable request functionality (GetRequest, GetNextRequest, GetBulkRequest). Default is

Enabled

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-21

System administration procedures Procedure 7-6: Edit, delete, or enter SNMP users

5

6

4. Under Trap Functionality Control, select

Enable

or

Disable

to enable or disable the SNMP User for receiving traps. Default is

Enabled

.

5. Click

Modify

at the bottom of the window.

Result:

A warning message appears stating that a reset is required before any

SNMP provisioning changes take effect and that a reset causes all active login sessions to be logged out.

Proceed to

Step 6 .

.................................................................................................................................................................................................

Perform the following to DELETE AN EXISTING USER:

1. Select

Existing User

in the SNMP User Community ID Panel.

2. In the drop-down box, select (highlight) the user to be deleted.

3. Click

Delete

at the bottom of the window.

Result:

A warning message appears stating that a reset is required before any

SNMP provisioning changes take effect and that a reset causes all active login sessions to be logged out.

Continue with

Step 6 .

.................................................................................................................................................................................................

Do you wish to perform additional SNMP User provisioning?

If...

Yes

No

Then...

Click

No

on the warning window and then return to

Step 1 . Note: If you select to NOT reset in

this procedure, you must perform a Phase 3 reset

(

Fault

→

Reset

→

System Controller

) before your changes take place.

Continue with

Step 7 .

7

8

.................................................................................................................................................................................................

Click

Yes

in the warning window to complete your SNMP provisioning.

Result:

The following warning message appears: The network element is resetting

due to System Reset.

.................................................................................................................................................................................................

Click

OK

.

.................................................................................................................................................................................................................................

7-22 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-6: Edit, delete, or enter SNMP users

9

Result:

The System View closes, the network element resets, and all active users are disconnected.

A flashing

b

in the

IND

display on the SYSCTL indicates that a boot is in progress.

During the boot, the

b

may extinguish for up to 20 seconds and then resume flashing.

.................................................................................................................................................................................................

If you want to view, print, or save a file of current SNMP users, then log back into the network element and select

Administration

→

Security

→

View SNMP Users

from the System View menu.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-23

System administration procedures

Procedure 7-7: Allow/inhibit autonomous message reporting

.................................................................................................................................................................................................................................

Overview

Use this procedure to allow or inhibit autonomous message reporting for the current login session.

Allowing autonomous messages enables you to receive all active alarm and status conditions from the NE through autonomous messages for the current login session.

Inhibiting this feature disables the reporting of all autonomous messages for the current login session.

Autonomous message reporting is allowed/inhibited on an individual user basis for the current login session. Every login session begins with the autonomous messages enabled.

Privilege level

You must log in as a Privileged, Administration, General, Maintenance, or Reports

Only user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the work instructions for this procedure.

Step

1

Perform the following steps to enable/disable autonomous message reporting for this user for the current login session.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Allow/Inhibit Autonomous

Message Reporting

→

Current Session

.

Result:

The Allow/Inhibit Autonomous Messages window opens. The current state of autonomous message reporting is displayed, Allow or Inhibit. Every login session begins with autonomous message reporting allowed.

.................................................................................................................................................................................................

2

Important! Autonomous message reporting is enabled (Allow) or disabled (Inhibit) on an individual user basis for the current login session.

Select

Allow

to enable autonomous message reporting for this session, or select

Inhibit

to disable reporting for this session, as required.

.................................................................................................................................................................................................................................

7-24 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-7: Allow/inhibit autonomous message reporting

3

.................................................................................................................................................................................................

Did you change the autonomous message reporting state?

If...

Yes

No

Then...

Click

OK

at bottom of the window, read the caution message, then click

Yes

to execute the command.

Click

Cancel

to exit.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-25

System administration procedures

Procedure 7-8: Create or edit login banner

.................................................................................................................................................................................................................................

Overview

Use this procedure to create or edit a user defined login banner for a Metropolis

®

DMX shelf.

Privilege level

You must log in as a Privileged or Administration user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Determine the text you wish to appear on the login banner (you have a maximum of 11 lines with 62 characters per line).

Step

1

2

3

Complete the following steps to create a user defined login banner.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Change NE Login Banner

.

Result:

Change Login Banner window opens.

.................................................................................................................................................................................................

In the

Change Login Banner

panel, enter the text that you wish to appear on the login screen in the 11 lines provided.

Important! The following rules must be adhered to when populating the login banner:

•

The banner may contain up to 360 characters.

•

Each line may contain up to 62 characters.

•

The banner may begin on Line 1 or Line 2.

•

Only one blank line may exist between each two populated rows.

.................................................................................................................................................................................................

Click

OK

.

.................................................................................................................................................................................................................................

7-26 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-8: Create or edit login banner

4

.................................................................................................................................................................................................

Log out and back in to the NE to verify the changes to the Login Banner.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-27

System administration procedures

Procedure 7-9: Set NE defaults — alarm gateway, alarm group, remote NE status, FTP/FTTD, security and history log thresholds

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision the following:

•

Remote NE Status

•

Alarm Gateway and Alarm Groups

•

FTP and/or FTAM-FTP Gateway

•

Security and History Log warning thresholds.

Privilege level

You must log in as a Privileged user to complete this procedure and its supporting elements.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the work instructions for this procedure.

Step

1

2

Perform the following steps to provision NE defaults.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Set NE

.

Result:

The Set NE window opens.

.................................................................................................................................................................................................

Reference the following, as required, to provision NE defaults:

•

Procedure 7-9.1: “Provision alarm gateway, alarm groups, and remote NE status”

(p. 7-29)

•

Procedure 7-9.2: “Enable/disable FTP and/or FTAM-FTP (FTTD) gateway functions” (p. 7-31)

•

Procedure 7-9.3: “Set security and/or history log thresholds” (p. 7-32)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

7-28 365-372-301 R6.0

Issue 15, January 2006

System administration procedures

Procedure 7-9.1: Provision alarm gateway, alarm groups, and remote NE status

.................................................................................................................................................................................................................................

Overview

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 7-9: “Set NE defaults — alarm gateway, alarm group, remote

NE status, FTP/FTTD, security and history log thresholds” (p. 7-28) .

Use this procedure to provision alarm groups, alarm gateways, and remote NE status, as required. This procedure might best be performed after all network elements have been equipped, tested, and integrated into the network. See below.

AGNE

The Alarm Gateway parameter may have a value of

Enabled

or

Disabled

(default).

Setting the value to

Enabled

designates the NE as an AGNE for its alarm group. One

AGNE is needed for each alarm group to support the message communications for

Remote NE Status feature. One other NE in the same alarm group may be provisioned as a backup AGNE, if required.

Any NE in an alarm group can be an AGNE. It is recommended that you do NOT provision an NE as both an AGNE and a TCP/IP GNE or TL1 GNE.

Remote NE Status must be

Enabled

in order to provision the NE as an AGNE. An NE with Remote NE Status (rnestat)

Enabled

but no AGNE in its alarm group reports an

AGNE Communications failure alarm.

Alarm Groups

Alarm group has a numeric value of 1 through 255. The default is 255. All NEs with

DCC connectivity, whether nearby or not, that have the same Alarm Group number are members of the same alarm group. All members of an alarm group share Remote NE

Status information with each other but not with NEs in different alarm groups. All NEs in an alarm group must be in the same OSI area.

Remote NE Status must be

Enabled

in order to assign an alarm group number to the

NE.

Remote NE Status

Remote NE status may be

Enabled

,

Enable Far-End

, or

Disabled

(default). When provisioned

Enabled

, the system activates support for the far-end activity LED, remote office alarms, and remote alarm/status reports.

When provisioned

Enable Far-End

, the SYSCTL LEDs and the office alarms only illuminate the FE LED; not the LEDs indicating the severity of the alarm. The

SYSCTL LEDs and office panel LEDs that indicate the severity of alarms (CR, MJ,

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-29

System administration procedures Procedure 7-9.1: Provision alarm gateway, alarm groups, and remote NE status

MN) only illuminate for local alarms. Except for the illumination of LEDs, selecting

Enable Far-End

behaves the same as selecting

Enabled

.

When provisioned

Disabled

(default), the system supports only local office alarms and local alarm/status reports. The far-end activity LED is not supported.

Step

1

2

3

4

5

Perform the following steps to provision the alarm group functions.

.................................................................................................................................................................................................

For Remote NE Status, select

Enabled

or

Enable Far-End

to enable Remote NE

Status.

Important! Remote NE Status must be provisioned

Enabled

or

Enable Far-End

in order to provision the alarm group functions.

.................................................................................................................................................................................................

If this NE will serve as an Alarm Gateway, select

Enabled

to provision this NE as an alarm gateway (AGNE). Otherwise, select

Disabled

.

An NE serving as a backup AGNE should have this parameter set to

Enabled

. In this configuration both NEs will actively serve as AGNEs to provide redundant alarm monitoring and distribution. The system does not assign one as primary and the other as secondary.

.................................................................................................................................................................................................

Enter the Alarm Group number (1-255) being assigned to this NE.

.................................................................................................................................................................................................

Ensure the other parameters in the window have not been changed, unless you are provisioning them also. Click

OK

at the bottom of the window.

.................................................................................................................................................................................................

Read the warning message, then click

Yes

to execute the command.

Important! An AGNE Communications failure alarm may occur if no AGNE has been selected for the alarm group. If you need to clear the alarm, select

Administration

→

Set NE

, then select

Disabled

to disable the Remote NE Status.

You will have to enable the remote NE status again when the AGNE has been established in order for this NE to be part of the alarm group.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

7-30 365-372-301 R6.0

Issue 15, January 2006

System administration procedures

Procedure 7-9.2: Enable/disable FTP and/or FTAM-FTP

(FTTD) gateway functions

.................................................................................................................................................................................................................................

Overview

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 7-9: “Set NE defaults — alarm gateway, alarm group, remote

NE status, FTP/FTTD, security and history log thresholds” (p. 7-28) .

This procedure allows you to:

•

Enable/Disable the NE for FTP file transfers to and from the NE. File transfers may be directly to and from an FTP-GNE, or through an FTP-GNE to/from an FTP enabled remote NE using IP Routing. Software downloads and provisionable database backup and restore are supported using FTP file transfers.

•

Enable/Disable the NE as an FTAM-FTP Gateway (GNE). Enabling the NE as an

FTAM-FTP Gateway allows the NE to act as a File Transfer Translation Device

(FTTD) to perform file transfer translation between an FTP server and a remote NE using the FTAM protocol for file transfers.

Important! Other provisioning may be necessary to use this function. Depending on your requirements, provisioning may include TCP/IP addressing and gateways,

IP Routing, NSAP addresses, LAN port provision, and area routing.

Step

1

2

3

Perform the following steps to Enable/Disable FTP and/or FTAM-FTP gateway functions.

.................................................................................................................................................................................................

If FTP will be used on this NE, under File Transfer Protocol, select

Enabled

to enable

FTP on this NE. Otherwise, select

Disabled

to disable FTP.

Important! If this NE is also being provisioned as an FTAM-FTP Gateway, then

File Transfer Protocol must also be

Enabled

.

.................................................................................................................................................................................................

If this NE will be used as an FTAM-FTP Gateway, under FTAM-FTP (FTTD) Gateway

Control, select

Enabled

to enable this NE as an FTAM-FTP Gateway. Otherwise, select

Disabled

.

.................................................................................................................................................................................................

Click

OK

at bottom of the window.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-31

System administration procedures

Procedure 7-9.3: Set security and/or history log thresholds

.................................................................................................................................................................................................................................

Overview

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 7-9: “Set NE defaults — alarm gateway, alarm group, remote

NE status, FTP/FTTD, security and history log thresholds” (p. 7-28) .

Use this procedure to set the Security Log Warning Threshold and/or the History Log

Warning Threshold. The Threshold is the percentage of entries entered since the last

Security/History Log Overflow event message was issued. When this threshold is reached another Security/History Log Overflow event message is issued and the threshold counter is reset to zero.

Step

1

2

Perform the following steps to set the security/history log warning threshold.

.................................................................................................................................................................................................

Under Log Warning Threshold, select the parameter values required for the

Security

Log Warning Threshold

and/or

History Log Warning Threshold

.

The Threshold may be disabled or set as a percentage of entries entered since the last

Security/History Log Overflow event message was issued. Values may be entered from

10% to 100% in increments of 10%. The default is 90%.

Selecting

0%-Disabled

inhibits the issuing of the Security/History Log Overflow event message.

.................................................................................................................................................................................................

Click

OK

at bottom of the window, read the warning message, then click

Yes

to execute the command.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

7-32 365-372-301 R6.0

Issue 15, January 2006

System administration procedures

Procedure 7-10: Set date and time

.................................................................................................................................................................................................................................

Overview

Use this procedure to set the system date and time.

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

Select a source for your time setting. If you are manually setting the date and time, determine the correct time from an established source. If you are using NTP, identify the NTP server(s) to be used as source.

If you are using NTP, it is assumed that IP Routing has already been established or else each node has its own IP address.

Also, if you are using NTP, you will need to know the UTC Offset (UTCo) for the time zone in which the NTP client is located.

Default (Non-NTP) Method for Time and Date Synchronization

Upon initial system turnup, the date and time revert to January 1, 1970 (70-01-01) at midnight (00:00:00). Determine the correct time from an established source and manually set the date and time.

After initial system turnup if a system reset occurs, the system restores the current time.

NTP Method for Time and Date Synchronization

Upon initial system turnup or following a system reset, the date and time revert to

January 1, 1970 (70-01-01) at midnight (000000). The NE (NTP client) queries for date and time from an NTP server (a list of NTP servers is maintained on the NE).

NTP uses the Coordinated Universal Time (UTC) for synchronization.

For subsequent synchronization, the NTP client monitors all the NTP servers to determine the most reliable clock and compares the time reported with its current time

(reliability is determined by clock selection procedures which include accessibility). If the time differs by more than the allowable amount of drift, it resets the time. The

Metropolis

®

DMX NTP client adjusts its clock in small steps (gradually) or in a single step depending upon the significance of the offset from the system clock.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-33

System administration procedures

Step

Procedure 7-10: Set date and time

1

Complete the following steps to set the system time and date:

.................................................................................................................................................................................................

Do you plan to use the Network Time Protocol?

If...

Yes

No

Then...

Proceed to

Step 7 .

Continue with

Step 2 .

2

3

4

5

6

7

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Set Date and Time

.

Result:

The Set Date and Time window opens.

.................................................................................................................................................................................................

From the

Date

panel, select the

Year

and

Month

from the pull-down menus.

Result:

A calendar is displayed for the month and year selected.

.................................................................................................................................................................................................

Click on the date from the calendar.

.................................................................................................................................................................................................

You can provision the time format display for your WaveStar

®

CIT from the Network

View by selecting

View

→

Preferences

and clicking on the Display tab. This screen allows you to choose your preference for time format, either a 12-hour clock or a

24-hour clock.

•

If your time format preference is a 12-hour clock, from the

Time

panel, select

Hour:

(0-12),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus. You must also specify am or pm by selecting one of the radio buttons.

•

If your time format preference is a 24-hour clock, From the

Time

panel, select the

Hour:

(0-23),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus.

.................................................................................................................................................................................................

Click

OK

.

Result:

The new date and time appear in the lower right hand corner of the

WaveStar

®

CIT System View.

Stop!

End of Procedure.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Set Network Time Protocol

.

.................................................................................................................................................................................................................................

7-34 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-10: Set date and time

8

9

10

11

Result:

The Provision Network Time Protocol Server window opens.

.................................................................................................................................................................................................

From the

Network Time Protocol

panel, select

Disabled

.

Important! Disabling NTP prevents the NE from receiving NTP information from the designated NTP server but allows you to enter provisionable data.

.................................................................................................................................................................................................

From the

Coordinated Universal Time Offset

panel, enter the number of

hours

and

minutes

from the pull-down menus to indicate the time difference from the UTC to the NTP client. Then select

plus (+)

or

minus (-)

to indicate the direction of change.

Important! In regions that observe Daylight Saving’s Time, the Offset will need to be adjusted by one hour each time the time changes.

.................................................................................................................................................................................................

From the

Time Change Threshold

panel, select a number between 1 and 499. The number may be selected by sliding the pointer until the desired number appears in the box to the left, or by simply typing the desired number into the box.

The number entered represents the number of milliseconds of clock adjustment that will generate an autonomous message to the WaveStar

®

CIT and OS.

This message indicates that a significant time change has occurred and usually only appears at startup or system reset.

Important! Do not press Enter/Return on the keyboard if you opt to type in the number.

.................................................................................................................................................................................................

From the

Maximum Adjustment Threshold Milliseconds

panel, select a number between 500 and 10,000 (default is 1000). The number may be selected by sliding the pointer until the desired number appears in the box to the left, or by simply typing the desired number into the box.

The number entered represents the number of milliseconds of clock adjustment that will generate an autonomous message. This message indicates that certain scheduled operations may be effected (e.g., performance monitoring), and usually only occurs at startup or system reset.

Important! Do not press Enter/Return on the keyboard if you opt to type in the number.

12

.................................................................................................................................................................................................

From the

Poll Interval

panel, select a

Minimum Poll Interval (seconds)

and a

Maximum Poll Interval (seconds)

from the pull-down menus. These numbers represent the least and most amount of time between the NTP client’s queries to the

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-35

System administration procedures Procedure 7-10: Set date and time

13

14

15

16

server. Allowable values are between are powers of two between 16 and 16384 seconds, inclusive (16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, 16384) Defaults are 64 and 1024.

Selecting a higher minimum interval reduces the traffic generated by the poll. The poll interval gradually increases towards the maximum interval so long as the changes to the NE clock remain small and infrequent. If the changes to the clock become large and/or frequent, the poll interval shifts towards the minimum interval. NTP determines the interval that best maintains synchronization between the client and the server.

.................................................................................................................................................................................................

From the

Network Element’s NTP Server(s)

panel, enter the IP address(es) of up to three known NTP Servers (It is recommended that a minimum of two servers be entered). NTP ranks these servers based upon availability and dependability. When a query is issued, NTP first attempts to synchronize with the most recently accessed server, and if it is unavailable, the query is issued to the highest ranked available server.

Note: There is no auto-discovery for NTP servers. This list must be entered and changed, manually.

Click the

Add NTP Server

button at the bottom of the screen. Enter the IP address of the server (each segment of the address should be entered in a separate box, sequentially across the screen).

Click

OK

.

Note: To remove an NTP server from the list, click to highlight one of the IP addresses in the NTP Server(s) IP Address(es) list. Click on Delete NTP Server button at the bottom of the screen.

.................................................................................................................................................................................................

Once you have completed the NTP form, click

Apply

.

.................................................................................................................................................................................................

From the

Network Time Protocol

panel, select

Enabled

. You will not be able to enter provisionable data while Enabled is selected.

Important! In order for NTP parameter changes to take effect, the NTP has to be disabled and then re-enabled.

.................................................................................................................................................................................................

Click

Apply

and then

Close

.

.................................................................................................................................................................................................................................

7-36 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-10: Set date and time

17

.................................................................................................................................................................................................

If required, select

Administration

→

View Network Time Protocol

and verify NTP status.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-37

System administration procedures

Procedure 7-11: Set/change system TID

.................................................................................................................................................................................................................................

Overview

Use this procedure to set or change the system Target Identifier (TID). The more common time to change a TID is prior to placing the system in-service. However, this procedure can also be used to change the TID of an in-service system.

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the TID from your work instructions.

Step

1

2

Complete the following steps to change an NE’s TID.

.................................................................................................................................................................................................

From your work instructions, obtain the TID (also known as NE Name).

Important! The TID is a case-insensitive character string from 1 to 20 characters and must be unique for each NE in the ring. The allowed characters are

•

Letters from

″ a

″ to

″ z

″ and

″

A

″ to

″

Z

″

.

•

Numbers from

″

0

″ to

″

9

″

.

•

Special characters

″

-

″

(hyphen) and

″

.

″

(period).

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Set TID

, then:

1. In the

New TID:

box, enter the new TID.

2. Confirm your entry in the

Confirm TID:

box.

3. Click the

OK

button.

4. A warning message appears stating that the execution of this command will terminate all active login sessions. Read the message, then click

Yes

.

Result:

The TID is changed, the system resets, and you are logged off the system.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

7-38 365-372-301 R6.0

Issue 15, January 2006

System administration procedures

Procedure 7-12: Enable/disable OSI on an IAO LAN port

.................................................................................................................................................................................................................................

Overview

Use this procedure to enable or disable OSI communication for IAO LAN ports

LAN-1 and/or LAN-2.

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

Step

1

2

3

4

Perform the following steps to enable or disable OSI communication for IAO LAN ports LAN-1 and/or LAN-2.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Data Communications

.

Result:

The Data Communications window opens.

.................................................................................................................................................................................................

Select the

OSI LAN Management

tab.

Result:

The IAO LAN parameters appear.

.................................................................................................................................................................................................

Enable/Disable the

OSI Function

parameter for IAO LAN ports LAN-1 and/or LAN-2 as required.

Important! OSI Function and TCP/IP Function cannot both be enabled on LAN-2.

Reference:

Procedure 7-15: “Provision TCP/IP and Proxy ARP on an IAO LAN port” (p. 7-46)

.................................................................................................................................................................................................

Click

Apply

at bottom of the screen, read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-39

System administration procedures

Procedure 7-13: Provision network layer 3 parameters

.................................................................................................................................................................................................................................

Overview

This procedure allows you to perform the following:

•

Modify the network service access point (NSAP) address

•

Enable/disable Level 2 routing capabilities

•

Enable/disable the NSAP count threshold level.

Important! Values should not be changed from default values except by users who intend to provision the SONET subnetwork and partition DCC communications.

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the work instructions for this procedure.

Step

1

Perform the following steps to provision the network layer 3 parameters, as required.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Data Communications

.

Result:

The Data Communications window opens.

2

.................................................................................................................................................................................................

If...

modifying the NSAP address and/or enabling/disabling level 2 routing capabilities, enabling/disabling the NSAP count threshold level,

Then...

Continue with

Step 3 .

Proceed to

Step 8 .

3

.................................................................................................................................................................................................

Select the

Network Layer

tab.

.................................................................................................................................................................................................................................

7-40 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-13: Provision network layer 3 parameters

4

5

6

7

8

9

Result:

The Network Layer parameters window opens.

.................................................................................................................................................................................................

NETWORK SERVICE ACCESS POINT

Click on the

Modify

button to the right of the NSAP address if you want to modify the

NSAP address for this NE.

Important! The first eight characters of the NSAPs are always the same and cannot be changed. The remaining 18 characters of the NSAP area address are provisionable but only the Area field should be changed to assign a node to a different area. The remainder of the NSAP includes the System Identifier field, which is unique to each node, and the Selector (SEL) field.

Result:

The NSAP Provisioning window opens.

.................................................................................................................................................................................................

Modify the user settable parameters as required, then click

OK

.

Result:

The Network Layer parameters window opens again.

.................................................................................................................................................................................................

Select the desired Routing Capability for this NE as either

Level 1

or

Level 1&2

.

.................................................................................................................................................................................................

Click

Apply

at bottom of the window, read the warning message, then click

Yes

to execute the command or

No

to abort the command.

.................................................................................................................................................................................................

Select the

Network Threshold Alarming

tab.

Result:

The Network Threshold Alarming parameters appear.

.................................................................................................................................................................................................

Provision the

Threshold Level

according to the work instructions and click

Apply

.

Important! If the threshold level is enabled and provisioned, the threshold level is used to monitor the number of NSAPs (OSI nodes) in the NE’s level 1 area. When the NSAP count equals or exceeds the provisioned threshold, the system reports a minor alarm.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-41

System administration procedures Procedure 7-13: Provision network layer 3 parameters

10

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If you are finished provisioning Data Communications parameters, click

Close

to exit.

Otherwise, continue with another tab.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

7-42 365-372-301 R6.0

Issue 15, January 2006

System administration procedures

Procedure 7-14: Set TARP parameters

.................................................................................................................................................................................................................................

Overview

This procedure allows you to provision user settable fields and functions relating to the following TARP capabilities for this NE:

•

TARP Propagation and Origination parameters

•

TARP Data Cache entries

•

TARP Manual Adjacencies.

Important! Values should not be changed from default values except by users who intend to provision the SONET subnetwork and partition DCC communications. All the Layer 4 parameters that can be provisioned and are needed for NE operation have default values. Therefore, it is not necessary to provision these parameters for the NE to operate in the network.

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the work instructions for this procedure.

Step

1

2

3

Perform the following steps to provision TARP parameters, as required.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Data Communications

.

Result:

The Data Communications window opens.

.................................................................................................................................................................................................

TARP PARAMETERS

Select the

TARP

tab.

Result:

The TARP parameters appear.

.................................................................................................................................................................................................

Select

Enable

to enable TARP Data Cache or

Disable

to disable TARP Data Cache.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-43

System administration procedures Procedure 7-14: Set TARP parameters

4

5

6

7

8

9

10

11

12

13

.................................................................................................................................................................................................

Set the TARP Propagation Flush timer as required.

.................................................................................................................................................................................................

Provision the

TARP Lifetime

and

TARP Timers

, as required.

.................................................................................................................................................................................................

Click

Apply

, read the warning message, then click

Yes

to execute the command.

.................................................................................................................................................................................................

TARP DATA CACHE

Click on the

TARP Data Cache

tab.

Result:

The TARP Data Cache Entry List appears.

.................................................................................................................................................................................................

Click on the sunglasses icon to add, modify, or delete entries. Follow the directions in the subsequent windows to edit the TARP Data Cache Entry

NE Name

and

NSAP

.

.................................................................................................................................................................................................

Click

Apply

.

.................................................................................................................................................................................................

TARP MANUAL ADJACENCIES

Click on the

TARP Manual Adj.

tab.

Result:

The TARP Manual Adjacency parameters appear.

.................................................................................................................................................................................................

Up to two Manual Adjacencies may be provisioned. Select one to provision by clicking on the

Modify

button next to MAJ1: or MAJ2:.

Result:

The NSAP Provisioning window opens.

.................................................................................................................................................................................................

Modify the NSAP as required, then click

OK

.

.................................................................................................................................................................................................

Click

Apply

at bottom of the window, read the warning message, then click

Yes

to execute the command or

No

to abort the command.

.................................................................................................................................................................................................................................

7-44 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-14: Set TARP parameters

14

.................................................................................................................................................................................................

If you are finished provisioning Data Communications parameters, click

Close

to exit.

Otherwise, continue with another tab.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-45

System administration procedures

Procedure 7-15: Provision TCP/IP and Proxy ARP on an IAO

LAN port

.................................................................................................................................................................................................................................

Overview

Use this procedure to perform the following:

•

Enable/Disable TCP/IP on an IAO LAN port

•

Enable/Disable Proxy Address Resolution Protocol (Proxy ARP) on an IAO LAN port

•

Provision the IP address and IP Subnet Mask of an IAO LAN port

•

Provision IP Default Router Address if connecting to a default router (LAN-2 only).

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions specify the LAN port(s) to be provisioned.

4. Verify that the work instructions specify the IP Address and IP Subnet Mask of the desired LAN port and the IP Default Router Address if it is connecting to a default router (LAN-2 only).

Step

1

Perform the following steps to complete this procedure.

.................................................................................................................................................................................................

Determine which IAO LAN port(s) you want to use (front or rear).

Important! If you are using the rear IAO LAN port, use lan-2 as your AID. If you are using the front IAO LAN port, use lan-1 as your AID.

2

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Data Communications

.

Result:

The Data Communications window opens.

.................................................................................................................................................................................................

3

Click on the

TCP/IP

tab at the top of the window.

.................................................................................................................................................................................................................................

7-46 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-15: Provision TCP/IP and Proxy ARP on an

IAO LAN port

4

5

Result:

The TCP/IP parameters display.

.................................................................................................................................................................................................

Select and/or modify the following parameters:

1. Select the

Port Aid:

(

LAN-1

[front] or

LAN-2

[rear]) being provisioned.

2. One at a time, click the

Modify

button to set the

IP Address

and

IP Subnet Mask

of the desired LAN port and the

IP Default Router Address

, if it is connecting to a default router (lan-2 only).

When the provisioning window opens for the IP address being provisioned, enter the IP address as four dot-separated decimal numbers ranging from 0 to 255. Click

OK

to make your changes or

Cancel

to quit.

3. Select

Enable

to enable the

TCP/IP Function

, or

Disable

to disable the

TCP/IP

Function

. Disabling the TCP/IP function on an IAO LAN port also causes enabled

Proxy ARP to be disabled for the IAO LAN port.

OSI Function and TCP/IP Function cannot both be enabled on LAN-2.

4. Select

Enable

to enable the

Proxy ARP

, or

Disable

to disable the

Proxy ARP

. To enable Proxy ARP on an IAO LAN port, the TCP/IP Function must also be enabled.

For applications that require IP connectivity between IP-based operations systems and remote network elements (for example, SNMP and Network Time Protocol), enabling Proxy ARP on the Gateway Network Element (GNE) eliminates the need for static routes on the external router or OS host that is connected to the GNE via the IAO LAN interface.

Important! If you enter duplicate IP addresses and/or IP subnet addresses, a warning appears:

Input, Data Not Valid, each IAO LAN port must have a unique

IP subnet address

. Scroll through the Port AID drop-down menu and identify the duplication, then assign correct addresses as necessary.

If you select

Enable

and click

Apply

to apply any changes, then execute the command when requested, the system will reset and you will be logged off the system. Selecting

Disable

allows you to stay logged on to the system to perform more provisioning. You can then come back to this window and enable the TCP/IP function.

Reference:

For an OS to establish a TCP/IP connection to or through a TL1

TCP/IP Gateway Network Element (GNE), the IP address must be entered at the

TL1 TCP/IP GNE to authorize access. Refer to

Procedure 7-16:

“Provision/enable/disable the NE as a TL1 TCP/IP GNE” (p. 7-49) .

.................................................................................................................................................................................................

Click

Apply

at the bottom of the window to make your changes.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-47

System administration procedures Procedure 7-15: Provision TCP/IP and Proxy ARP on an

IAO LAN port

6

7

8

Result:

A warning window opens and asks if you want to execute this command.

.................................................................................................................................................................................................

Click

Yes

to execute the command.

Result:

If you made changes that enabled the TCP/IP function, the changes are applied, the system resets, and you are logged off the system. If you made changes and disabled the TCP/IP function, the changes are applied and you are still logged off the system.

A flashing

b

in the

IND

display on the SYSCTL indicates that a boot is in progress.

During the boot, the

b

may extinguish for up to 20 seconds and then resume flashing.

.................................................................................................................................................................................................

If you wish to enable the second port, return to

Step 2 .

.................................................................................................................................................................................................

Click

Close

when you want to exit window, if you are still logged into the system.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

7-48 365-372-301 R6.0

Issue 15, January 2006

System administration procedures

Procedure 7-16: Provision/enable/disable the NE as a TL1

TCP/IP GNE

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision, enable, or disable the Metropolis

®

DMX as a TL1

TCP/IP GNE.

Privilege level

You must login as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure,

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. If the GNE is connected to the IP WAN via an IAO LAN interface, complete

Procedure 7-15: “Provision TCP/IP and Proxy ARP on an IAO LAN port” (p. 7-46)

to provision and enable TCP/IP for the selected LAN port. If the GNE is connected to the IP WAN through another vendor’s network element using an IP over DCC link, complete

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

and

Procedure 7-17: “Provision static IP routes on DCC links” (p. 7-52)

to enable IP over DCC and specify the static IP routes on the selected DCC port.

4. Verify that the work instructions specify the LAN port to be provisioned.

5. Verify that the work instructions specify the IP calling addresses, host names

(optional), and host types for the OS hosts which will be allowed access to the

Metropolis

®

DMX TL1 TCP/IP GNE.

Step

1

2

Perform the following steps to complete this procedure.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Data Communications

.

Result:

The Data Communications window opens.

.................................................................................................................................................................................................

In the Data Communications window, click on the

TCP/IP

tab.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-49

System administration procedures Procedure 7-16: Provision/enable/disable the NE as a

TL1 TCP/IP GNE

3

4

5

6

7

Result:

The TCP/IP parameters display.

.................................................................................................................................................................................................

Verify that TCP/IP is properly provisioned and enabled for the required LAN port or

DCC port. If TCP/IP is enabled for a DCC port, verify that the IP static route is provisioned on the selected DCC port.

Reference:

•

Procedure 7-15: “Provision TCP/IP and Proxy ARP on an IAO LAN port”

(p. 7-46)

•

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

•

Procedure 7-17: “Provision static IP routes on DCC links” (p. 7-52)

.................................................................................................................................................................................................

In the Data Communications window, click on the

TCP/IP Gateway

tab.

Result:

The TCP/IP Gateway parameters display.

.................................................................................................................................................................................................

Enable or Disable the

TCP/IP Gateway Function

as required.

.................................................................................................................................................................................................

From your work instructions, determine which IP calling addresses will be allowed to access the Metropolis

®

DMX TL1 TCP/IP GNE.

.................................................................................................................................................................................................

Important! Changes to an existing IP map entry (OS Host IP address, OS Host

Name or OS Type) will not impact any existing connections to the corresponding

OS. For example, if an OS Host IP address is removed from the table, and a connection to that OS is currently present, that connection is maintained until the user manually terminates the connection.

Use the instructions on the screen to add, modify, or delete a gateway host from the

TCP/IP Gateway Host List

.

The following parameters apply:

•

The OS Host IP address: four dot-separated decimal numbers, each ranging from 0 to 255.

•

The OS Host Name: may consist of 1 to 24 alpha-numeric characters.

•

The OS Type: may consist of standard types or listed as other.

Repeat this step for each of the Host IP addresses you want to authorize for access to the Metropolis

®

DMX TL1 TCP/IP GNE. There may be up to 20 provisioned entries in the list.

.................................................................................................................................................................................................................................

7-50 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-16: Provision/enable/disable the NE as a

TL1 TCP/IP GNE

8

9

10

.................................................................................................................................................................................................

Click

Apply

at the bottom of the window.

Result:

A warning window opens and asks if you want to execute this command.

.................................................................................................................................................................................................

Click

Yes

to execute the command, then click

Close

to exit window, if desired.

.................................................................................................................................................................................................

Repeat this procedure for each TL1 TCP/IP GNE to be modified, enabled, or disabled.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-51

System administration procedures

Procedure 7-17: Provision static IP routes on DCC links

.................................................................................................................................................................................................................................

Overview

Use this procedure to add/modify/delete static IP routes on DCC links. The static routes are added into the routing table and used to forward IP packets through the provisioned outgoing DCC interfaces to reach the destination IP addresses.

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions specify the required DCC port AID, Destination

IP, Destination IP Subnet Mask, and the required provisioning.

4. If adding a static route, verify that IP over DCC is enabled for the required DCC port using the

View

→

DCC Terminations

command to access the View DCC

Terminations window. If required, refer to

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

to provision the required DCC port.

Step

1

2

3

Perform the following steps to add/modify/delete static IP routes on DCC links.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Data Communications

.

Result:

The Data Communications window opens.

.................................................................................................................................................................................................

Click on the

IP Routing

tab at the top of the window.

Result:

The IP Routing parameters display.

.................................................................................................................................................................................................

In the Manual Routes panel, click on the edit icon (glasses) to add/modify/delete an entry.

.................................................................................................................................................................................................................................

7-52 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-17: Provision static IP routes on DCC links

4

5

6

Result:

The Add/Modify/Delete a Manual Route window opens

.................................................................................................................................................................................................

Select the required DCC port from the

AID:

drop-down list. Enter the

Destination IP

and

Destination IP Subnet Mask

parameters according to the work instructions, and click

Add

/

Modify

/

Delete

, as required.

Result:

The Add/Modify/Delete a Manual Route window closes

.................................................................................................................................................................................................

Click

Apply

to execute the command.

.................................................................................................................................................................................................

Repeat

Step 3

through

Step 5

to provision other static routes on DCC links; otherwise, click

Close

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-53

System administration procedures

Procedure 7-18: Provision RS232 CIT (CIT-1) and/or MODEM

(CIT-2) serial port parameters

.................................................................................................................................................................................................................................

Overview

Use this procedure to:

•

Set or change the baud rate for the serial ports.

•

Enable or disable command echo mode.

•

Assign OS type application context IDs (ACIDs) to the serial ports.

Assigning an acid to a serial port determines the TL1 autonomous message types to be output by the local network element (NE), and any TL1-RNEs (remote NEs) accessed through that serial port.

Important! Changing the serial port parameters may affect access to the serial port.

Changing settings for the front RS232 CIT (cit-1) port may affect WaveStar

®

CIT local access. Changing settings for the MODEM (cit-2) port may affect modem communications, if applicable.

Privilege level

An Administration, General, Maintenance, or Reports Only user may provision a serial port only if they are logged in to that serial port. A Privileged user may provision a serial port while logged in to that serial port or while not logged in to that serial port.

Important! Changing the baud rate on the serial port requires that you first change the baud rate on the NE before changing the baud rate of the COM port on the PC.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the work instructions for this procedure.

Step

1

Perform the following steps to provision the serial ports.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Data Communications

.

Result:

The Data Communications parameters window opens.

.................................................................................................................................................................................................

Select the

Serial Port

tab.

2

.................................................................................................................................................................................................................................

7-54 365-372-301 R6.0

Issue 15, January 2006

System administration procedures Procedure 7-18: Provision RS232 CIT (CIT-1) and/or

MODEM (CIT-2) serial port parameters

3

4

5

Result:

The Serial Port parameters appear.

.................................................................................................................................................................................................

Select the

CIT Port

(

cit-1

or

cit-2

) you want to provision.

Important! Changing the serial port parameters may affect access to the serial port.

.................................................................................................................................................................................................

Note the

Access State

of the selected CIT Port. If the

Access State

is

In Service

you may continue to provision accessible parameters for the serial port. If the

Access

State

is

Lockout

, only a Privileged user may provision the parameters at this time.

An

Access State

of

Lockout

indicates that login access to all ports has been locked out except for Privileged users.

Administration

→

Security

→

Enable Lockout Security State Administration

→

Security

→

Disable Lockout Security State

Reference:

Procedure 7-3: “Edit, delete, or enter a user’s login” (p. 7-12)

.................................................................................................................................................................................................

Provision the Serial Port Parameters as required.

•

Echo Mode

– Specifies whether or not TL1 messages received on the port are echoed back to the user. Values are

enabled

or

disabled

. The WaveStar

®

CIT temporarily disables the echo when launched and re-enables it when closed.

Enabling the Echo after launching the WaveStar

®

CIT can cause the WaveStar

®

CIT to operate improperly.

•

Baud Rate

– Specifies the baud rate at which TL1 messages are transmitted/received on the port. Values are

1200

,

2400

,

4800

,

9600

(default), or

19200

.

Changing the baud rate terminates any active login sessions on the selected port.

•

OS Type

– Only Privileged users may assign/change ACIDs. Specifies the

Application Context Identifier from the following values:

–

TL1PeerComm

(By default, no autonomous messages).

TL1PeerComm

is the default OS Type for cit-2.

–

TL1Maintenance

(By default, all autonomous messages except for Database changes)

–

TL1MemoryAdministration

(By default, Database Change messages only)

–

TL1Test

(By default, all autonomous messages except for PM reports).

TL1Test

is the default OS Type for cit-1.

–

TL1CR

(By default, no autonomous messages possible)

–

TL1OTHER1

(By default, all autonomous messages except report PM)

–

TL1OTHER2

(By default, no autonomous messages)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-55

System administration procedures Procedure 7-18: Provision RS232 CIT (CIT-1) and/or

MODEM (CIT-2) serial port parameters

6

7

8

9

.................................................................................................................................................................................................

In the

Apply To

box, select

This CIT Port only

if the changes only apply to the selected port. Or, select

Both CIT Ports

to apply the changes to both cit-1 and cit-2.

.................................................................................................................................................................................................

Click

Apply

at bottom of the window, read the warning message, then click

Yes

to execute the command.

Important! If you changed the baud rate setting, you will be logged off the system and the system view will close. Changing the OS Type on a port logs out any active user on the port.

Other serial port provisioning takes effect at the current session only after a command is sent to the NE. Click on the

Alarm List

button from the System View menu to send a command to the NE.

.................................................................................................................................................................................................

If you changed the CIT baud rate setting, you must now change the COM port baud rate setting for the WaveStar

®

CIT. From the WaveStar

®

CIT network view, select

Administration

→

Serial COM Selection

.

.................................................................................................................................................................................................

Select the serial port (

COM-1

or

COM-2

) and Baud Rate setting used for serial communication. Click

OK

to change the setting.

Important! The baud rate setting must be the same as the NE CIT port setting.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

7-56 365-372-301 R6.0

Issue 15, January 2006

System administration procedures

Procedure 7-19: Map TL1 message types to OS applications

.................................................................................................................................................................................................................................

Overview

Use this procedure to map TL1 autonomous message types to an OS type application context ID (ACID). TL1 autonomous messages are not reported unless they are assigned to an OS type. This command allows a user to assign specific TL1 autonomous message types, or none at all.

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure,

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the work instructions for this procedure, particularly all relevant ACID/OS requirements.

Step

1

2

Complete the following steps to map TL1 message types to the OS.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Set TL1 Message Map

.

Result:

The Set TL1 Message Map window opens.

.................................................................................................................................................................................................

From the

TL1 Message Type List

, select one of the following ACIDs from the

OS

Application Type

column

•

TL1MAINTENANCE

— Maintenance To be used by the systems that monitor alarms and performance monitoring. Defaults All autonomous messages except for

Database Changes.

•

TL1MEMORYADMINISTRATION

— Memory Administration To be used by systems that provision cross-connections. Defaults Database Changes autonomous messages ONLY.

•

TL1TEST

— Test (Use with WaveStar

®

CIT) Defaults All autonomous messages except for REPT PM.

•

TL1PEERCOM

— Peer Communications Defaults NO autonomous messages.

•

TL1OTHER1

— All autonomous messages except for REPT PM.

•

TL1OTHER2

— NO autonomous messages.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-57

System administration procedures Procedure 7-19: Map TL1 message types to OS applications

3

4

5

6

.................................................................................................................................................................................................

For the selected OS type, verify the desired status (

ENABLED

or

DISABLED

) for each of the following Message Types

•

Alarm (ALM)

— Reports the occurrence of alarms.

•

Environment (ENV)

— Reports the occurrence of environmental alarms.

•

Conditions (CON)

— Periodically reports the active status conditions (every six hours beginning at midnight).

•

Database Changes (DB)

— Reports the occurrence of provisioning changes.

•

Events (EVT)

— Reports the occurrence of status conditions (events).

•

Performance Monitoring (PM)

— Reports performance monitoring data on a scheduled basis.

•

Protection Switch (SW)

— Reports automatic equipment protection switches.

.................................................................................................................................................................................................

To change an

ENABLED

/

DISABLED

status, double-left-click on the status cell and select the correct status from the drop-down menu.

.................................................................................................................................................................................................

Continue from

Step 2

until all types have been correctly defined.

.................................................................................................................................................................................................

Click

OK

at bottom of the window, read the warning message, then click

Yes

to execute the command or

No

to abort the command.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

7-58 365-372-301 R6.0

Issue 15, January 2006

System administration procedures

Procedure 7-20: Enable/disable user ID(s)

.................................................................................................................................................................................................................................

Overview

Use this procedure to:

•

Disable a non-default user’s ID

•

Disable all non-default user IDs

•

Enable a user’s ID that was previously disabled

•

Enable all user IDs.

Privilege level

You must log in as a Privileged or Administration user to complete this procedure.

Before you begin

Prior to performing this procedure,

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the User ID(s) to be enabled or disabled.

Step

Complete the following steps to enable/disable a non-default user ID(s).

.................................................................................................................................................................................................

1

If the non-default user ID(s) is to be...

enabled, disabled,

Then...

Continue with

Proceed to

Step 2

Step 4 .

.

2

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Security

→

Enable User

Login

.

Result:

The Enable User Login window opens.

.................................................................................................................................................................................................

3 If enabling...

one non-default user ID,

Then...

Select the user ID and click This Login. Then click

OK

.

STOP! End of Procedure

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-59

System administration procedures Procedure 7-20: Enable/disable user ID(s)

If enabling...

all user IDs,

Then...

Click All Logins. Then click

OK

.

STOP! End of Procedure

.

4

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Security

→

Disable User

Login

.

Result:

The Disable User Login window opens.

.................................................................................................................................................................................................

5

If disabling...

one non-default user ID, all non-default user IDs,

Then...

Select the user ID and click This Login. Then click

OK

.

STOP! End of Procedure

.

Click All Logins. Then click

OK

.

STOP! End of Procedure

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

7-60 365-372-301 R6.0

Issue 15, January 2006

System administration procedures

Procedure 7-21: Provision network element security

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision the following network element level security parameters:

•

User ID Lockout Threshold

•

User ID Aging Period

•

Minimum Waiting Period Before Password Changes

•

User ID Lockout Interval

•

User ID Lockout Aging Period

•

Change Password Status.

Privilege level

You must log in as a Privileged or Administration user to complete this procedure.

Before you begin

Prior to performing this procedure,

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions identify the network element security parameters to be provisioned and the new values.

Step

1

Complete the following steps to provision the network element level security parameters.

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Security

→

Provision NE

Security

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-61

System administration procedures Procedure 7-21: Provision network element security

2

Result:

The Provision NE Security window opens.

.................................................................................................................................................................................................

Provision the network element security parameters according to your work instructions and click

OK

.

•

User ID Lockout Threshold: The maximum number of consecutive invalid login attempts that are allowed by a User ID. When the number of invalid login attempts reaches the provisioned threshold, the User ID is locked out for the provisioned period of time. After a successful login attempt, the count of invalid login attempts by that User is reset to zero. The value is 2-99 days; default is 5. A value of 0 or selecting

Disable

disables the lockout threshold.

•

User ID Aging Period: If a User ID is not used during the provisioned time interval, it is disabled. User ID aging does not apply to the three default logins.

The value is 0-999 days; default is 60. A value of 0 or selecting

Disable

disables user ID aging.

•

Minimum Waiting Period Before Password Changes: If the Password Aging

Interval (number days before a user has to change his/her password) is enabled

(7-999 days), the Minimum Waiting Period before Password Changes value MUST be less than the Password Aging Interval. The value is 0-30 days; default is 20. A value of 0 or selecting

Disable

disables the minimum waiting period.

•

User ID Lockout Interval: When the number of invalid login attempts reaches the provisioned threshold, the User ID is locked out for this provisioned period of time.

After the provisioned period expires, login attempts are allowed from that User ID.

The value is 0-99 minutes; default is 10. A value of 0 or selecting

Disable

disables the lockout interval.

•

User ID Lockout Aging Period: The time period during which the number of invalid login attempts are counted. When the Lockout Aging Period expires, the counter of invalid login attempts by that User ID is reset to zero. The value is

1-999 minutes; default is 60.

•

Change Password Status: Enables or disables the requirement to change a password when the password is first used in a new login ID or after the password is changed by a System Administrator. The default is

Disable

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

7-62 365-372-301 R6.0

Issue 15, January 2006

System administration procedures

Procedure 7-22: Log out user(s)

.................................................................................................................................................................................................................................

Overview

Use this procedure to log out an active user (including another privileged user) or all active users (excluding privileged and administration users) from the network element.

Privilege level

You must log in as a Privileged or Administration user to complete this procedure.

Before you begin

Prior to performing this procedure,

1. Refer to

“Before you begin” (p. 7-3)

and

“Required equipment” (p. 7-3)

in this chapter.

2. Obtain the user ID(s) of the user(s) to be logged out.

Step

1

Complete the following steps to log out another user(s).

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Security

→

Logout NE User

.

Result:

The Logout NE User window opens.

.................................................................................................................................................................................................

2 If logging out...

one user, all non-privileged and non-administration users and the executing user’s login session,

Then...

Select the user ID and click This login. Then click

OK

.

A dialog box appears asking you to confirm logging out the user. Click

Yes

.

Select All logins and click

OK

.

A dialog box appears asking you to confirm logging out all applicable users. Click

Yes

.

3

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Security

→

View Logged-In

Users

to obtain a list of logged-in users and verify that the desired user(s) have been logged out. Click

Close

to exit.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

7-63

8

8

procedures

Overview

.................................................................................................................................................................................................................................

Purpose

Use the procedures in this chapter to view or provision performance monitoring parameters from the System View

Performance

menu.

Depending on local procedures, types of configurations, and shelf equipage, some or none of the optional parameters may need to be provisioned. It is assumed that local system administration is responsible for determining these parameter values.

Some of the parameter values may be provisioned during the initial shelf turn-up.

Other parameter values may be provisioned after the system is integrated into the network configuration.

Contents

Before you begin

Procedure 8-1: View performance monitoring (PM) thresholds

Procedure 8-2: Provision performance monitoring (PM) thresholds

Procedure 8-3: Initialize performance monitoring (PM) registers

Procedure 8-4: View performance monitoring (PM) settings

Procedure 8-5: Provision performance monitoring (PM) settings

Procedure 8-6: View performance monitoring (PM) reports

Procedure 8-7: Schedule performance monitoring (PM) reports

Procedure 8-8: Clear threshold crossing alert (TCA) counts

8-8

8-11

8-14

8-17

8-2

8-3

8-4

8-5

8-7

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

8-1

System performance monitoring procedures

Before you begin

.................................................................................................................................................................................................................................

Before you begin

Prior to performing all procedures in this chapter,

1. If not previously completed, install generic and WaveStar

®

CIT software on the PC.

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

2. Connect PC and establish a WaveStar

®

CIT session.

Refer to

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24) .

Required equipment

All procedures in this chapter require that a Personal Computer (PC) with WaveStar

®

CIT software installed is available.

.................................................................................................................................................................................................................................

8-2 365-372-301 R6.0

Issue 15, January 2006

System performance monitoring procedures

Procedure 8-1: View performance monitoring (PM) thresholds

.................................................................................................................................................................................................................................

Overview

Use this procedure to view performance monitoring (PM) thresholds for ports or tributaries.

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to view

PM thresholds.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 8-2)

and

“Required equipment” (p. 8-2)

in this chapter.

Step

1

2

Perform the following steps to view PM thresholds.

.................................................................................................................................................................................................

From the System View menu, select either

Performance

→

View Near-End PM

Threshold

or

Performance

→

View Far-End PM Threshold

, as required, then select the desired port rate or tributary rate.

Result:

The View ( ) Near-End PM Threshold or View ( ) PM Far-End Threshold window opens for the port or tributary rate selected.

.................................................................................................................................................................................................

View the parameters and threshold values, then at the bottom of the window, click the appropriate button as required:

Save As

,

Print

,

Refresh

,

Close

, or

Help

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

8-3

System performance monitoring procedures

Procedure 8-2: Provision performance monitoring (PM) thresholds

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision performance monitoring (PM) thresholds for ports or tributaries.

Privilege level

You must log in as a Privileged, General, or Maintenance user to provision PM thresholds.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 8-2)

and

“Required equipment” (p. 8-2)

in this chapter.

Step

1

2

3

Perform the following steps to provision PM thresholds.

.................................................................................................................................................................................................

From the System View menu, select either

Performance

→

Prov Near-End PM

Threshold

or

Performance

→

Prov Far-End PM Threshold

, as required, then select the desired port rate or tributary rate.

Result:

The Provision ( ) Near-End PM Threshold or Provision ( ) PM Far-End

Threshold window opens for the port or tributary rate selected.

.................................................................................................................................................................................................

In the table, find the required PM parameter and double-click inside the table cell for the desired threshold being provisioned. Enter or edit the required threshold values.

Repeat for each threshold being provisioned.

.................................................................................................................................................................................................

After all required threshold values are entered, click

OK

at the bottom of the window.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

8-4 365-372-301 R6.0

Issue 15, January 2006

System performance monitoring procedures

Procedure 8-3: Initialize performance monitoring (PM) registers

.................................................................................................................................................................................................................................

Overview

Important! Executing this procedure will reset and clear the PM register(s) selected. Ensure you want to execute this procedure before continuing.

Use this procedure to initialize all current 15-minute and/or current 1-day PM registers.

PM registers for the previous 15-minute and previous 1-day time periods are not affected.

Privilege level

You may log in as a Privileged, General, or Maintenance user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 8-2)

and

“Required equipment” (p. 8-2)

in this chapter.

Step

1

Perform the following steps to initialize (clear) the current 15-minute and/or current

1-day PM registers.

.................................................................................................................................................................................................

Which register do you wish to initialize?

If ...

current 15-minute registers current 1-day registers current 15-minute and current

1-day registers

Then...

Continue with

Step 2 .

Proceed to

Step 5 .

Proceed to

Step 8 .

2

.................................................................................................................................................................................................

From the System View menu, select

Performance

→

Initialize PM Registers

→

15-Min

.

Result:

A dialog box appears asking you to confirm executing this command.

3

.................................................................................................................................................................................................

Click

Yes

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

8-5

System performance monitoring procedures Procedure 8-3: Initialize performance monitoring (PM) registers

4

5

6

7

8

9

Result:

All current 15-minute PM registers are cleared. PM registers for the

previous 15-minute time periods are not affected.

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

From the System View menu, select

Performance

→

Initialize PM Registers

→

1-Day

.

Result:

A dialog box appears asking you to confirm executing this command.

.................................................................................................................................................................................................

Click

Yes

.

Result:

All current 1-day PM registers are cleared. PM registers for the previous

1-day time periods are not affected.

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

From the System View menu, select

Performance

→

Initialize PM Registers

→

Both

.

Result:

A dialog box appears asking you to confirm executing this command.

.................................................................................................................................................................................................

Click

Yes

.

Result:

All current 15-minute and current 1-day PM registers are cleared. PM registers for the previous 15-minute and previous 1-day time periods are not affected.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

8-6 365-372-301 R6.0

Issue 15, January 2006

System performance monitoring procedures

Procedure 8-4: View performance monitoring (PM) settings

.................................................................................................................................................................................................................................

Overview

Use this procedure to view the provisioned performance monitoring and TCA reporting parameters for a port, tributary, or VCG.

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to view performance monitoring and TCA reporting parameters.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 8-2)

and

“Required equipment” (p. 8-2)

in this chapter.

Step

1

2

3

Perform the following steps to view performance monitoring and TCA reporting parameters.

.................................................................................................................................................................................................

From the System View menu, select

Performance

→

View PM Settings

.

Result:

The View PM window opens.

.................................................................................................................................................................................................

Expand the details for the required Function group or main circuit pack with the ports, tributaries, or VCGs being viewed. Click on the required port, tributary, or VCG you want to view, then click

Select

.

.................................................................................................................................................................................................

View the desired parameters, then at the bottom of the window, click the appropriate button as required:

Refresh

,

Close

, or

Help

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

8-7

System performance monitoring procedures

Procedure 8-5: Provision performance monitoring (PM) settings

.................................................................................................................................................................................................................................

Overview

Use this procedure to perform the following:

•

Enable/disable performance monitoring on a TDM port, TDM tributary, Ethernet port, Data port, or VCG.

•

Enable/disable threshold crossing alert (TCA) reporting on a TDM port, TDM tributary, Ethernet port, Data port, or VCG.

Privilege level

You must log in as a Privileged, General, or Maintenance user to provision performance monitoring and TCA reporting parameters.

TDM alarm, performance monitoring, and threshold crossing alert reporting

The following table shows the port/tributary provisionable parameters that affect TDM alarm, performance monitoring, and threshold crossing alert reporting.

TCA

Monitoring

Mode

Parameter

Enable

Port/Tributary Monitoring Mode (Primary State) Parameter

IS AUTO (Note) NMON (Note)

Disable

Yes Alarm Reporting

Yes PM Reporting

Yes TCA Reporting

Yes Alarm Reporting

Yes PM Reporting

No TCA Reporting

No Alarm Reporting

No PM Reporting

No TCA Reporting

No Alarm Reporting

No PM Reporting

No TCA Reporting

No Alarm Reporting

No PM Reporting

No TCA Reporting

No Alarm Reporting

No PM Reporting

No TCA Reporting

Note: The AUTO and NMON primary states do not apply to high-speed OC-n lines.

Ethernet alarm, performance monitoring, and threshold crossing alert reporting

The following table shows the Ethernet port/VCG provisionable parameters that affect

Ethernet alarm, performance monitoring, and threshold crossing alert reporting.

.................................................................................................................................................................................................................................

8-8 365-372-301 R6.0

Issue 15, January 2006

System performance monitoring procedures Procedure 8-5: Provision performance monitoring (PM) settings

Ethernet

Port/VCG PM

Enable

TCA Monitoring Mode = Enable (Note)

Port/VCG Monitoring Mode

IS AUTO NMON

Enable

Disable

Yes Alarm Reporting

Yes PM Reporting

Yes TCA Reporting

Yes Alarm Reporting

No PM Reporting

No TCA Reporting

No Alarm Reporting

No PM Reporting

No TCA Reporting

No Alarm Reporting

No PM Reporting

No TCA Reporting

No Alarm Reporting

No PM Reporting

No TCA Reporting

No Alarm Reporting

No PM Reporting

No TCA Reporting

Note: If the TCA monitoring mode parameter is disable, TCA reporting is disabled.

Data alarm, performance monitoring, and threshold crossing alert reporting

The following table shows the Data port provisionable parameters that affect Data alarm, performance monitoring, and threshold crossing alert reporting.

Data Port PM

Enable

TCA Monitoring Mode = Enable (Note)

Port Monitoring Mode

IS AUTO NMON

Enable Yes Alarm Reporting

Yes PM Reporting

Yes TCA Reporting

No Alarm Reporting

No PM Reporting

No TCA Reporting

No Alarm Reporting

No PM Reporting

No TCA Reporting

Disable Yes Alarm Reporting

No PM Reporting

No TCA Reporting

No Alarm Reporting

No PM Reporting

No TCA Reporting

No Alarm Reporting

No PM Reporting

No TCA Reporting

Note: If the TCA monitoring mode parameter is disable, TCA reporting is disabled.

The following table shows the Data VCG provisionable parameters that affect Data alarm and performance monitoring reporting.

Data VCG PM

Enable

Enable

VCG Monitoring Mode

IS

Yes Alarm Reporting

Yes PM Reporting

AUTO

No Alarm Reporting

No PM Reporting

NMON

No Alarm Reporting

No PM Reporting

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

8-9

System performance monitoring procedures Procedure 8-5: Provision performance monitoring (PM) settings

Data VCG PM

Enable

Disable

VCG Monitoring Mode

IS

Yes Alarm Reporting

No PM Reporting

AUTO

No Alarm Reporting

No PM Reporting

NMON

No Alarm Reporting

No PM Reporting

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 8-2)

and

“Required equipment” (p. 8-2)

in this chapter.

Step

1

2

3

4

Perform the following steps to provision performance monitoring and TCA reporting.

.................................................................................................................................................................................................

From the System View menu, select

Performance

→

Prov PM Settings

.

Result:

The Provision PM window opens.

.................................................................................................................................................................................................

Expand the details for the required Function group or circuit pack with the ports, tributaries, or VCGs being provisioned. Click on the required port, tributary, or VCG you want to provision, then click

Select

.

.................................................................................................................................................................................................

Provision parameters as required and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

.................................................................................................................................................................................................

Read the warning message and click

Yes

to execute the command. Click

Close

to exit.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

8-10 365-372-301 R6.0

Issue 15, January 2006

System performance monitoring procedures

Procedure 8-6: View performance monitoring (PM) reports

.................................................................................................................................................................................................................................

Overview

Use this procedure to view performance monitoring (PM) reports.

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to view performance monitoring reports.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 8-2)

and

“Required equipment” (p. 8-2)

in this chapter.

Step

1

2

3

4

Perform the following steps to view PM reports.

.................................................................................................................................................................................................

From the System View menu, select

Performance

→

View PM Reports

then select the entity you want to report.

Result:

The ( ) PM Report window opens for the selected entity;

or, if

Performance

→

View PM Reports

→

TCA Report

was selected, the TCA report is displayed automatically. Proceed to

Step 6 .

.................................................................................................................................................................................................

Expand the details for the required group/circuit pack and port (if necessary). Highlight the entity from which you want to report and then click

Select

.

Result:

A parameter selection details window opens.

.................................................................................................................................................................................................

Select the

Time Period

(1 Day or 15 Min).

.................................................................................................................................................................................................

Which

Time Period

did you select?

If ...

1 Day

Then...

Select values for the following parameters:

•

Monitored Date

(Current Date, Previous Date or Both)

•

Monitor Level

(1-UP or 0-UP)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

8-11

System performance monitoring procedures Procedure 8-6: View performance monitoring (PM) reports

If ...

15 Min

Then...

Select values for the following parameters:

•

Number of Bins

(All or Single)

If the

Number of Bins

selected is Single, you must also select a time period from the

Monitored Time

drop-down list.

•

Monitor Level

(1-UP or 0-UP)

.................................................................................................................................................................................................

5

Important! The following menu selections do not display Near End and Far End tabs because far-end performance monitoring is not supported. The parameters that are available for selection are near-end PM parameters.

•

DS1 Line (if the signal format of the selected port is Super Frame, Super

Frame - Near-End Only, or Unframed).

If the signal format of the selected port is Ext. Super Frame - Near and Far

End, the Near End and Far End tabs are available.

•

DS1 Path (if the signal format of the selected port is Super Frame, Super

Frame - Near-End Only).

If the signal format of the selected port is Ext. Super Frame - Near and Far

End, the Near End and Far End tabs are available. DS1 ports with a provisioned signal format of Unframed do not support DS1 Path PM and are not available for selection from this menu.

•

E1 Line

•

DS3 Line

•

DS3 Path (if the signal format of the selected port is Framed)

If the signal format of the selected port is C-Bit, the Near End and Far End tabs are available. DS3 ports with a provisioned signal format of Clear Channel do not support DS3 Path PM and are not available for selection from this menu.

•

OCN Section

•

Ethernet

•

Ethernet QoS

•

Data

Select the Near End and/or Far End Tab as required and select the parameters to report for each tab. Click

Apply

.

Result:

The ( ) PM Report is displayed. If you selected parameters on both tabs, the resulting report includes parameters designated as NEND (Near End) and

FEND (Far End).

Performance monitoring for cross-connections is done at the incoming signal rates, not at the cross-connection rate. For example, an STS-12c cross-connection could

.................................................................................................................................................................................................................................

8-12 365-372-301 R6.0

Issue 15, January 2006

System performance monitoring procedures Procedure 8-6: View performance monitoring (PM) reports

6

7

consist of 1 STS-12c signal, 4 STS-3c signals, 12 STS-1 signals, or a mix of

STS-3c and STS-1 signals. Therefore, a single request could return a report for several entities.

.................................................................................................................................................................................................

At the bottom of the window, click the appropriate button as required:

Save As

,

Print

,

Refresh

,

Close

,

Reset

, or

Help

.

.................................................................................................................................................................................................

If required, click

Close

on the ( ) PM Report window.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

8-13

System performance monitoring procedures

Procedure 8-7: Schedule performance monitoring (PM) reports

.................................................................................................................................................................................................................................

Overview

This procedure allows a user to schedule Performance Monitoring reports on

Metropolis

®

DMX. Performance monitoring can be scheduled to provide quarter hour and daily reports beginning at different time intervals.

In order to schedule PM reports, PM messaging must be enabled and you must use the

WaveStar

®

CIT TL1 cut-through mode or the TL1 Command Builder.

Important! The WaveStar

®

time, support this command.

CIT Graphical User Interface (GUI) does not, at this

If you are unfamiliar with the parameters in this procedure, refer to

SCHED-PMREPT

in the Metropolis

®

DMX Access Multiplexer TL1 Message Details, 365-372-306.

Privilege level

You must log in as a Privileged, General, or Maintenance user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 8-2)

and

“Required equipment” (p. 8-2)

in this chapter.

Step

1

Complete the following steps to schedule PM. The NE supports up to a maximum of

100 active scheduled PM reports, counting every aid as many times as it is scheduled

(aid values that include ALL are counted multiple times). The NE accepts each

SCHED-PMREPT

as a request for a different scheduled PM report unless two requests are exact duplicates. The

SCHED-PMREPT

command does not generate a

REPT DBCHG

message.

.................................................................................................................................................................................................

Important! The port/tributary/VCG monitoring mode (primary state) parameter must be IS (in-service) to enable performance monitoring.

Verify that performance monitoring is enabled (port/tributary/VCG monitoring mode is

IS) for the required port, tributaries, and/or VCGs.

.................................................................................................................................................................................................................................

8-14 365-372-301 R6.0

Issue 15, January 2006

System performance monitoring procedures Procedure 8-7: Schedule performance monitoring (PM) reports

2

3

4

Reference:

Procedure 8-4: “View performance monitoring (PM) settings” (p. 8-7)

.................................................................................................................................................................................................

From the WaveStar

®

CIT System View menu, verify that the Performance Monitoring

(PM) message type has been enabled for the OS Application Type being used by selecting

Administration

→

Set TL1 Message Map

.

Reference:

(p. 7-57)

Procedure 7-19: “Map TL1 message types to OS applications”

.................................................................................................................................................................................................

From the WaveStar

®

CIT System View menu, select

File

→

NE Disconnect

and click

Yes

in the resulting confirmation window.

.................................................................................................................................................................................................

From the Network View, log back into the NE but this time click

TL1

, not Graphical.

Result:

The following appears:

5

6

7

.................................................................................................................................................................................................

Click on

Command Builder

.

Result:

The Login window opens.

.................................................................................................................................................................................................

Enter your user ID and password. Defaults are

LUC01

and

DMX2.5G10G

, respectively.

.................................................................................................................................................................................................

Schedule the required PM report using the

sched-pmrept

TL1 command.

Reference:

365-372-306

Metropolis

®

DMX Access Multiplexer TL1 Message Details,

Performance monitoring for cross-connections is done at the incoming signal rates, not at the cross-connection rate. For example, an STS-12c cross-connection could consist of 1 STS-12c signal, 4 STS-3c signals, 12 STS-1 signals, or a mix of

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

8-15

System performance monitoring procedures Procedure 8-7: Schedule performance monitoring (PM) reports

STS-3c and STS-1 signals. Therefore, a single request could return a report for several entities.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

8-16 365-372-301 R6.0

Issue 15, January 2006

System performance monitoring procedures

Procedure 8-8: Clear threshold crossing alert (TCA) counts

.................................................................................................................................................................................................................................

Overview

Important! Executing the command in this procedure will reset and clear the threshold crossing alert (TCA) counts. Ensure you want to execute this procedure before continuing.

Use this procedure to clear threshold crossing alert (TCA) counts.

Privilege level

You may log in as either a Privileged, General, Maintenance user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 8-2)

and

“Required equipment” (p. 8-2)

in this chapter.

Step

1

2

Perform the following steps to clear TCA counts.

.................................................................................................................................................................................................

From the System View menu, select

Fault

→

Clear TCA Count

.

Result:

A dialog box appears asking you to confirm executing this command.

.................................................................................................................................................................................................

Click

Yes

.

Result:

The TCA counts are cleared.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

8-17

9

9

procedures

Overview

.................................................................................................................................................................................................................................

Purpose

This chapter includes procedures necessary to configure a Metropolis

®

DMX network.

Contents

Before you begin

Procedure 9-1: Establish high-speed end-to-end Metropolis

®

DMX system

Procedure 9-2: Add new Metropolis

®

DMX node to network

Procedure 9-3: Discontinue Metropolis

®

DMX node from network

Procedure 9-4: Provision manual ring map

Procedure 9-5: Establish low-speed 1+1 linear optical extension

Procedure 9-6: Establish single-homed network configurations

Procedure 9-7: Establish dual-homed network configurations

Procedure 9-8: Establish OC-48 0x1 unprotected extensions

Procedure 9-9: Establish subtending low-speed UPSR/BLSR

Procedure 9-10: Add IP route(s) through network

Procedure 9-11: Establish low-speed 1+1 unprotected linear optical extension

9-2

9-3

9-84

9-93

9-98

9-113

9-132

9-29

9-48

9-63

9-69

9-76

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-1

Network configuration procedures

Before you begin

.................................................................................................................................................................................................................................

Before you begin

Prior to performing all procedures in this chapter,

1. If not previously completed, install generic and WaveStar

®

CIT software on the PC.

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

2. Connect PC and establish a WaveStar

®

CIT session.

Refer to

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24) .

Required equipment

All procedures in this chapter require that the following equipment is available:

•

Personal Computer (PC) with WaveStar

®

CIT software installed

•

Wrist strap

Important! If additional equipment is required to perform a specific procedures, that additional equipment is listed in that procedure.

.................................................................................................................................................................................................................................

9-2 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

Procedure 9-1: Establish high-speed end-to-end Metropolis

®

DMX system

.................................................................................................................................................................................................................................

Overview

Use this procedure to establish an end-to-end Metropolis

®

DMX high-speed:

•

OC-12/OC-48/OC-192 UPSR

•

OC-48/OC-192 BLSR (Release 3.0 and later)

•

OC-12/OC-48/OC-192 1+1 linear (Main-to-Main)

•

OC-12/OC-48 1+1 linear (Main-to-Function/Growth) (Release 3.0 and later)

Important! This procedure assumes that the Metropolis

®

DMX shelves have been equipped with the required circuit packs/pluggable transmission modules, software has been installed, and the shelf has passed the looped transmission tests. If not, refer to

Chapter 5, “Node turnup procedures” .

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 9-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

Step

1

Complete the following steps to establish an end-to-end Metropolis

®

DMX system.

.................................................................................................................................................................................................

Important! The network element TID (target identifier) must be unique in the network.

From the System View at the starting node,

1. Select

Administration

→

View NE Administration

.

2. Verify that the NE Parameters and NSAP are provisioned correctly using the work instruction and/or office records.

3. Click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-3

Network configuration procedures Procedure 9-1: Establish high-speed end-to-end

Metropolis

®

DMX system

4. If provisioning changes are required, refer to the appropriate procedure(s) in

Chapter 7, “System administration procedures” .

5. Repeat this step at each node in the network.

.................................................................................................................................................................................................

2

If establishing a high-speed...

UPSR network,

BLSR network,

1+1 linear extension (Main-to-Main) network,

1+1 linear extension (Main-to-Function/

Growth) network,

Then...

Proceed to

Procedure 9-1.1: “Establish high-speed UPSR network” (p. 9-5) .

Proceed to

Procedure 9-1.2: “Establish high-speed BLSR network” (p. 9-11) .

Proceed to

Procedure 9-1.3: “Establish high-speed 1+1 linear (Main-to-Main) network” (p. 9-18) .

Proceed to

Procedure 9-1.4: “Establish high-speed 1+1 linear (Main-to-Function/

Growth) network” (p. 9-23) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

9-4 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

Procedure 9-1.1: Establish high-speed UPSR network

.................................................................................................................................................................................................................................

Important! This is not a standalone procedure. Perform this procedure only as directed by

Procedure 9-1: “Establish high-speed end-to-end Metropolis

®

DMX system” (p. 9-3) .

Step

1

Important! This procedure assumes that the UPSR is established by interconnecting Metropolis

®

DMX nodes using the OC-12/OC-48/OC-192 Main slot pair. However, the Main slot pair of the Metropolis

®

DMX may also be connected in a UPSR with the following:

•

Metropolis

®

DMXtend using OC-12/OC-48 Main slot pair or OC-12/OC-48

Function/Growth slot pair. If connecting to a Metropolis

®

DMXtend, refer to the Metropolis

®

DMXtend Access Multiplexer User Operations Guide,

365-372-325, as required, when performing this procedure.

•

Metropolis

®

DMXplore using OC-12 Main slot pair. If connecting to a

Metropolis

®

DMXplore, refer to the Metropolis

®

DMXplore Access Multiplexer

User Operations Guide, 365-372-332, as required, when performing this procedure.

•

Metropolis

®

DMX using OC-12/OC-48 Function/Growth slot pair. If connecting to the Function/Growth slot pair of another Metropolis

®

DMX, refer to

Procedure 9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98) , as

required, when performing this procedure.

Nodes are provisioned and optical spans are established individually around the

UPSR starting with a Metropolis

®

DMX shelf designated as the starting node.

Continue around the UPSR in the same direction until all nodes are provisioned.

This procedure assumes that all Metropolis

®

DMX shelves have been equipped with the required circuit packs/pluggable transmission modules, software has been installed, and the shelf has passed the looped transmission tests. If not, refer to

Chapter 5, “Node turnup procedures” .

Ignore all alarms until the procedure is complete.

Complete the following steps to establish a high-speed UPSR network.

.................................................................................................................................................................................................

Important! For UPSR applications, the port Application parameter must be provisioned UPSR.

From the System View menu at the starting node, use the

Configuration

→

Equipment

command to access the Main 1 and 2 ports and provision the port parameters according to the work instructions.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-5

Network configuration procedures Procedure 9-1.1: Establish high-speed UPSR network

2

3

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

Use the

View

→

Equipment

command to access the Main 1 and 2 ports and verify that the ports were provisioned correctly.

.................................................................................................................................................................................................

At each node in the UPSR, provision the port parameters according to the work instructions.

If the node is a...

Metropolis

®

DMX and the Main ports are used,

Metropolis

®

DMX and the

Function/Growth ports are used,

Metropolis

®

Metropolis

®

DMXtend or

DMXplore,

Then...

Repeat

Step 1

and

Step 2

to provision and verify the required OC-n ports.

Refer to

Procedure 9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98)

to provision and verify the required OC-n ports.

Refer to the other product’s documentation to provision and verify the required OC-n ports.

.................................................................................................................................................................................................

4

Important! The LAPD Role parameter must be provisioned differently at each end of an optical span. For example, if the LAPD Role parameter is provisioned user-side at one end of an optical span, then the LAPD Role parameter must be provisioned network-side at the other end of the optical span.

From the System View menu at the starting node,

1. Select

Configuration

→

DCC Terminations

2. Select the required DCC Port dcc-m1-1, provision

OSI Over DCC

as enabled, and the

LAPD Role

as user-side.

3. Click

Apply

to make changes.

4. Select the required companion DCC Port dcc-m2-1, provision

OSI Over DCC

as

enabled, and the

LAPD Role

as network-side.

5. Click

Apply

to make changes.

6. Click

Close

.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

5

From the System View menu, select

View

→

DCC Terminations

, verify that the DCC terminations were provisioned correctly for DCC ports dcc-m1-1 and dcc-m2-1, and click

Close

.

.................................................................................................................................................................................................................................

9-6 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-1.1: Establish high-speed UPSR network

6

.................................................................................................................................................................................................

At each node in the UPSR, provision the DCC terminations according to the work instructions.

If the node is a...

Metropolis

®

DMX and the Main ports are used,

Metropolis

®

DMX and the

Function/Growth ports are used,

Metropolis

®

Metropolis

®

DMXtend or

DMXplore,

Then...

Repeat

Step 4

and

Step 5

to provision and verify the required DCC terminations.

Refer to

Procedure 9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98)

to provision and verify the required DCC terminations.

Refer to the other product’s documentation to provision and verify the required DCC terminations.

7

8

.................................................................................................................................................................................................

Important! Synchronization Autoreconfiguration is only provisionable if the system

Timing Mode parameter is Line and the Sync Messaging parameter of all ports is

enabled. If the Sync Messaging parameter is enabled at any port in the network, it must be enabled at all ports in the network.

At the starting node, provision the synchronization functions (for example, timing mode) according to work instructions.

Reference:

(p. 6-16)

Procedure 6-5: “Network Element synchronization provisioning”

.................................................................................................................................................................................................

At each node in the UPSR, provision synchronization functions according to the work instructions.

If the node is a...

Metropolis

®

DMX and the Main ports are used,

Metropolis

®

DMX and the

Function/Growth ports are used,

Metropolis

®

DMXtend or

Metropolis

®

DMXplore,

Then...

Repeat

Step 7

to provision the required synchronization functions.

Refer to

Procedure 9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98)

to provision the required synchronization functions.

Refer to the other product’s documentation to provision the required synchronization functions.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-7

Network configuration procedures Procedure 9-1.1: Establish high-speed UPSR network

9

10

.................................................................................................................................................................................................

Important! If Remote NE Status is to be used, at least one network element must be provisioned as the Alarm Gateway Network Element (AGNE) in the network. If the network element is designated as the Alarm Gateway Network Element

(AGNE), the Alarm Gateway parameter must be provisioned Enabled.

From the System View menu at the starting node, select

Administration

→

Set NE

, provision the Remote NE Status, Alarm Group, and Alarm Gateway parameters according to the work instructions, and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command. Click

Yes

.

Reference:

Procedure 7-9: “Set NE defaults — alarm gateway, alarm group, remote NE status, FTP/FTTD, security and history log thresholds” (p. 7-28)

.................................................................................................................................................................................................

At each node in the UPSR, provision Remote NE Status functions according to the work instructions.

If the node is a...

Metropolis

®

DMX and the Main ports are used,

Metropolis

®

DMX and the

Function/Growth ports are used,

Metropolis

®

Metropolis

®

DMXtend or

DMXplore,

Then...

Repeat

Step 9

to provision the required Remote

NE Status functions.

Refer to

Procedure 9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98)

to provision the required Remote NE Status functions.

Refer to the other product’s documentation to provision the required Remote NE Status functions.

11

.................................................................................................................................................................................................

Beginning with the starting optical span, connect the fibers between the Main-1 circuit pack at the starting node and the adjacent node and verify the integrity of the optical span being established.

If the adjacent node is a...

Metropolis

®

DMX, Metropolis

®

DMXtend, or Metropolis

®

DMXplore and the Main slots are used,

Then connect to the...

Main-2 circuit pack.

Refer to the other product’s documentation, as required, to connect the fibers and verify the integrity of the optical span.

.................................................................................................................................................................................................................................

9-8 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-1.1: Establish high-speed UPSR network

If the adjacent node is a...

Metropolis

®

DMX or Metropolis

®

DMXtend and the Function/Growth slots are used,

Then connect to the...

Function/Growth circuit pack in Slot 1.

Refer to the other product’s documentation, as required, connect and test the optical span.

12

13

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Perform end-to-end optical line test.

Reference:

(p. 14-61)

Procedure 14-7: “Perform end-to-end optical line test on Main OLIUs”

.................................................................................................................................................................................................

Continue around the UPSR in the same direction until all nodes are connected.

If the node is a...

Metropolis

®

DMX and the Main ports are used,

Metropolis

®

DMX and the

Function/Growth ports are used,

Metropolis

®

DMXtend or

Metropolis

®

DMXplore,

Then...

Repeat

Step 11

and

Step 12

to connect and test the optical span.

Refer to

Procedure 9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98)

to connect and test the optical span.

Refer to the other product’s documentation to connect and test the optical span.

14

.................................................................................................................................................................................................

At each node in the UPSR, click the

Alarm List

button or select

Fault

→

NE Alarm

List

from the System View menu and verify that no alarms are present.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

15

.................................................................................................................................................................................................

The UPSR is now ready for initial service to be established.

Important! Establishing service requires that the proper slots in each terminating node be properly equipped with the correct circuit pack(s) for the type of service being established. It also requires numerous cross-connections in each of the nodes representing the path of the required service. Additionally, transmission tests should be performed to verify the continuity and quality of the established circuit.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-9

Network configuration procedures Procedure 9-1.1: Establish high-speed UPSR network

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

9-10 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

Procedure 9-1.2: Establish high-speed BLSR network

.................................................................................................................................................................................................................................

Important! This is not a standalone procedure. Perform this procedure only as directed by

Procedure 9-1: “Establish high-speed end-to-end Metropolis

®

DMX system” (p. 9-3) .

Step

1

2

Important! This procedure assumes that the BLSR is established by interconnecting Metropolis

®

DMX nodes using the OC-12/OC-48/OC-192 Main slot pair. However, the Main slot pair of the Metropolis

®

DMX may also be connected in a BLSR with the Function/Growth slot pair of another Metropolis

®

DMX. If connecting to the Function/Growth slot pair of another Metropolis

®

DMX, refer to

Procedure 9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98) , as

required, when performing this procedure.

Nodes are provisioned and optical spans are established individually around the

BLSR starting with a Metropolis

®

DMX shelf designated as the starting node.

Continue around the BLSR in the same direction until all nodes are provisioned.

(Refer to the 2-fiber bidirectional line switched ring worksheet at the end of this procedure when performing this procedure.)

This procedure assumes that all Metropolis

®

DMX shelves have been equipped with the required circuit packs, software has been installed, and the shelf has passed the looped transmission tests. If not, refer to

Chapter 5, “Node turnup procedures” .

Ignore all alarms until the procedure is complete.

Complete the following steps to establish a high-speed OC-48/OC-192 BLSR.

.................................................................................................................................................................................................

Important! For BLSR applications, the port Application parameter must be provisioned 2F BLSR.

From the System View menu at the starting node, use the

Configuration

→

Equipment

command to access the Main 1 and 2 ports and provision the port parameters according to the work instructions.

Result:

The system reports a default K-bytes alarm.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

Use the

View

→

Equipment

command to access the Main 1 and 2 ports and verify that the ports were provisioned correctly.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-11

Network configuration procedures Procedure 9-1.2: Establish high-speed BLSR network

3

4

5

6

7

.................................................................................................................................................................................................

At each node in the 2-fiber BLSR (refer to the 2-fiber BLSR worksheet at the end of the procedure), repeat

Step 1

and

Step 2

to provision and verify the required main

OC-n ports.

If a Metropolis

®

DMX is using a Function/Growth slot pair, refer to

Procedure 9-9:

“Establish subtending low-speed UPSR/BLSR” (p. 9-98)

to provision and verify the required OC-n ports.

.................................................................................................................................................................................................

From the system view at the starting node,

1. Select

Configuration

→

Equipment

.

2. Select the

Ring ID

tab and expand the required ring by clicking on the plus sign

(+).

3. Click on the 2F BLSR main-1-1 protection group and

Select

.

4. Provision the required protection group parameters according to the work instructions, then click

Apply

and

Close

. If no changes were made, click

Close

and go to the next step.

.................................................................................................................................................................................................

From the System View menu,

1. Select

View

→

Protection

.

2. Select 2F BLSR main-1-1 and click

Select

.

3. Click on the Provisionable Parameters tab and verify that the protection group parameters were provisioned correctly. Then click

Close

.

.................................................................................................................................................................................................

At each node in the 2-fiber BLSR (refer to the 2-fiber BLSR worksheet at the end of the procedure), repeat

Step 4

and

Step 5

to provision and verify the main 2-fiber BLSR protection group.

If a Metropolis

®

DMX is using a Function/Growth slot pair, refer to

Procedure 9-9:

“Establish subtending low-speed UPSR/BLSR” (p. 9-98)

to provision and verify the required 2-fiber BLSR protection group.

.................................................................................................................................................................................................

Determine the status of Automatic Ring Discovery.

If automatic ring discovery was...

enabled at each node, (Release 3.0 and later releases),

Then...

Continue with

Step 8 .

.................................................................................................................................................................................................................................

9-12 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-1.2: Establish high-speed BLSR network

If automatic ring discovery was...

disabled at each node (manual ring discovery),

Then...

At the starting node, establish a new manual ring map.

Repeat this step at each node in the 2-fiber

BLSR.

Procedure 9-4: “Provision manual ring map”

(p. 9-63)

8

9

10

.................................................................................................................................................................................................

Important! The LAPD Role parameter must be provisioned differently at each end of an optical span. For example, if the LAPD Role parameter is provisioned user-side at one end of an optical span, then the LAPD Role parameter must be provisioned network-side at the other end of the optical span.

From the System View menu at the starting node,

1. Select

Configuration

→

DCC Terminations

2. Select DCC Port dcc-m1-1, provision

OSI Over DCC

as enabled, and the

LAPD

Role

as user-side.

3. Click

Apply

to make changes.

4. Select DCC Port dcc-m2-1, provision

OSI Over DCC

as enabled, and the

LAPD

Role

as network-side.

5. Click

Apply

to make changes.

6. Click

Close

.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

From the System View menu, select

View

→

DCC Terminations

, verify that the DCC terminations were provisioned correctly for DCC ports dcc-m1-1 and dcc-m2-1, and click

Close

.

.................................................................................................................................................................................................

At each node in the 2-fiber BLSR (refer to the 2-fiber BLSR worksheet at the end of the procedure), repeat

Step 8

and

Step 9

to provision and verify the DCC terminations for the Main ports.

If a Metropolis

®

DMX is using a Function/Growth slot pair, refer to

Procedure 9-9:

“Establish subtending low-speed UPSR/BLSR” (p. 9-98)

to provision and verify the required DCC terminations.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-13

Network configuration procedures Procedure 9-1.2: Establish high-speed BLSR network

11

12

13

14

.................................................................................................................................................................................................

Important! Synchronization Autoreconfiguration is only provisionable if the system timing mode is Line and the Sync Messaging parameter of all ports is enabled. If the Sync Messaging parameter is enabled at any port in the network, it must be enabled at all ports in the network.

At the starting node, provision synchronization functions according to work instructions.

Repeat this step at each node in the 2-fiber BLSR (refer to the 2-fiber BLSR worksheet at the end of the procedure).

Reference:

(p. 6-16)

Procedure 6-5: “Network Element synchronization provisioning”

.................................................................................................................................................................................................

Important! If Remote NE Status is to be used, at least one network element must be provisioned as the Alarm Gateway Network Element (AGNE) in the network. If the network element is designated as the Alarm Gateway Network Element

(AGNE), the Alarm Gateway parameter must be provisioned Enabled.

From the System View menu at the starting node, select

Administration

→

Set NE

, provision the Remote NE Status, Alarm Group, and Alarm Gateway parameters according to the work instructions, and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command. Click

Yes

.

Reference:

Procedure 7-9: “Set NE defaults — alarm gateway, alarm group, remote NE status, FTP/FTTD, security and history log thresholds” (p. 7-28)

Repeat this step at each node in the 2-fiber BLSR (refer to the 2-fiber BLSR worksheet at the end of the procedure).

.................................................................................................................................................................................................

Beginning with the starting optical span (refer to the 2-fiber BLSR worksheet at the end of the procedure), connect the fibers between the Main-2 circuit pack at the starting node and the Main-1 circuit pack at the adjacent East node and verify the integrity of the optical span being established.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Perform end-to-end optical line test.

.................................................................................................................................................................................................................................

9-14 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-1.2: Establish high-speed BLSR network

15

Reference:

(p. 14-61)

Procedure 14-7: “Perform end-to-end optical line test on Main OLIUs”

.................................................................................................................................................................................................

Repeat

Step 13

and

Step 14

for each optical span in the 2-fiber BLSR (refer to the

2-fiber BLSR example and worksheet at the end of the procedure).

If connecting to a Function/Growth slot pair at a Metropolis

®

DMX, refer to

Procedure

9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98)

to connect and test the optical span.

.................................................................................................................................................................................................

16

If automatic ring discovery was...

enabled at each node (in

Step

4 ),

disabled at each node (in

Step 4 ),

Then...

Important! As the ring is connected, nodes automatically communicate with each other using the data communications channel (DCC) and build a ring map. If successful, automatic ring discovery builds a ring map at each node and the

Ring Discovery in Progress condition clears. If unsuccessful, the ring map is not complete and alarms are reported.

At the host node, select

View

→

Ring Map

→

Ring Map

.

Then click on the appropriate ring and

Select

.

The ring map information appears. If the ring is incomplete and alarms are present, refer to Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302.

Continue with

Step 17 .

17

.................................................................................................................................................................................................

At the starting node, verify 2-fiber BLSR protection switching:

1. Select

Fault

→

Protection Switch

. Select 2F BLSR main-1-1 and click

Select

.

Choose the

East

or

West

direction with switch type

Manual to Protection, Ring

.

Click

Apply

.

2. Select

View

→

Protection

. Select 2F BLSR main-1-1 and click

Select

. Observe the

Ring Node APS (Automatic Protection Switch) State, East Switch Request State,

West Switch Request State, East Channel Status, and West Channel Status parameters. Verify the 2-fiber BLSR protection switch was performed.

3. Select

Fault

→

Protection Switch

. Select 2F BLSR main-1-1 and click

Select

.

Choose the required direction with switch type

Clear

. Click

Apply

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-15

Network configuration procedures Procedure 9-1.2: Establish high-speed BLSR network

18

19

Repeat this step at each node in the 2-fiber BLSR (refer to the 2-fiber BLSR worksheet at the end of the procedure) to verify protection switching.

.................................................................................................................................................................................................

At each node in the 2-fiber BLSR, click the

Alarm List

button or select

Fault

→

NE

Alarm List

from the System View menu and verify that no alarms are present.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

The 2-fiber BLSR is now ready for initial service to be established.

Important! Establishing service requires that the proper slots in each terminating node be properly equipped with the correct circuit pack(s) for the type of service being established. It also requires numerous cross-connections in each of the nodes representing the path of the required service. Additionally, transmission tests should be performed to verify the continuity and quality of the established circuit.

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

9-16 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-1.2: Establish high-speed BLSR network

2-Fiber Bidirectional Line Switched Ring Worksheet

Ending

Span

Direction

Starting

Span

Direction

West

Port

West (W)

OUT

East (E)

M1

IN

N

(Starting Node)

OUT

M2

IN

User

Side

Network

Side

East Port

West Port

West (W)

M1

IN

OUT

User

Side

N+1

East (E)

M2

OUT

IN

Network

Side

East

Port

East (E)

M2

N+2 and other Nodes

Network

Side

User

Side

West (W)

M1 nc-usm-368

2-FIBER RING WORKSHEET

N

TID=

Ring ID:

Node ID:

Protection Group AID

OUT Fiber Color/ID

IN Color/ID

Received Power Level

Required LBO

SPAN NAME/ID

N+1

TID=

Node ID:

Protection Group AID

IN Fiber Color/ID

Received Power Level

Required IN PAD

OUT Fiber Color

NC-USM-216

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-17

Network configuration procedures

Procedure 9-1.3: Establish high-speed 1+1 linear

(Main-to-Main) network

.................................................................................................................................................................................................................................

Important! This is not a standalone procedure. Perform this procedure only as directed by

Procedure 9-1: “Establish high-speed end-to-end Metropolis

®

DMX system” (p. 9-3) .

Step

1

Important! This procedure assumes that the 1+1 linear network is established by interconnecting two Metropolis

®

DMX nodes using the OC-12/OC-48/OC-192

Main slot pair. However, the Main slot pair of the Metropolis

®

DMX may also be connected in a high-speed 1+1 linear network with either of the following:

•

Metropolis

®

DMXtend using OC-12/OC-48 Main slot pair. If connecting to a

Metropolis

®

DMXtend, refer to the Metropolis

®

DMXtend Access Multiplexer

User Operations Guide, 365-372-325, as required, when performing this procedure.

•

Metropolis

®

DMXplore using OC-12 Main slot pair. If connecting to a

Metropolis

®

DMXplore, refer to the Metropolis

®

DMXplore Access Multiplexer

User Operations Guide, 365-372-332, as required, when performing this procedure.

This procedure assumes that the near-end node is a Metropolis

®

DMX and the far-end node is either a Metropolis

®

DMX, Metropolis

®

DMXtend, or Metropolis

®

DMXplore. Refer to the 1+1 linear worksheet at the end of this procedure when performing this procedure.

This procedure assumes that all Metropolis

®

DMX shelves have been equipped with the required circuit packs, software has been installed, and the shelf has passed the looped transmission tests. If not, refer to

Chapter 5, “Node turnup procedures” .

Ignore all alarms until the procedure is complete.

Complete the following steps to establish a high-speed 1+1 linear (main-to-main) network.

.................................................................................................................................................................................................

Important! The port Application parameter must be provisioned 1+1 at both ends of the system, Optimized 1+1 at both ends of the system, or Bidirectional 1+1 at both ends of the system. Bidirectional 1+1 is only required when interworking with other vendor’s equipment that does not bridge DCC traffic on the active and standby lines. (Metropolis

®

DMX supports bridging DCC traffic on the active and standby lines.)

Metropolis

®

DMXtend does not support Optimized 1+1.

.................................................................................................................................................................................................................................

9-18 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

2

3

4

5

Procedure 9-1.3: Establish high-speed 1+1 linear

(Main-to-Main) network

Metropolis

®

DMXplore does not support Optimized 1+1 or Bidirectional 1+1.

From the System View menu at the near-end node, use the

Configuration

→

Equipment

command to access the Main 1 and 2 ports and provision the port parameters according to the work instructions.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

Use the

View

→

Equipment

command to access the Main 1 and 2 ports and verify that the ports were provisioned correctly.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Equipment

. Select the system

(AID=system), then click

Select

at the bottom of the window.

If required, provision the 1+1 Protection Priority (1+1 applications only) and Wait To

Rename (Optimized 1+1 applications only) parameters. Click

Apply

if changes were made, then click

Yes

to the warning message to make your changes. Click

Close

to exit.

.................................................................................................................................................................................................

Important! The protection group Revertive Mode and Wait to Restore parameters apply to 1+1 applications and Bidirectional 1+1 applications only.

If the Revertive Mode parameter is disabled, the Wait to Restore parameter is not provisionable.

If required, from the System View menu,

1. Select

Configuration

→

Equipment

.

2. Select the

Ptn Grp

tab.

3. Click on the required 1+1 protection group and

Select

.

4. Provision the required protection group parameters according to the work instructions, then click

Apply

and

Close

. If no changes were made, click

Close

and go to the next step.

.................................................................................................................................................................................................

If required, from the System View menu,

1. Select

View

→

Protection

.

2. Select the required 1+1 protection group and click

Select

.

3. Verify that the protection group parameters were provisioned correctly. Then click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-19

Network configuration procedures Procedure 9-1.3: Establish high-speed 1+1 linear

(Main-to-Main) network

6

7

8

9

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled, the LAPD Role parameter must be provisioned differently at each end of an optical span. For example, if the LAPD

Role parameter is provisioned user-side at one end of an optical span, then the

LAPD Role parameter must be provisioned network-side at the other end of the optical span.

From the System View menu, select

Configuration

→

DCC Terminations

and provision the DCC terminations for DCC port dcc-m-1 according to the work instructions.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

From the System View menu, select

View

→

DCC Terminations

, verify that the DCC terminations were provisioned correctly for DCC port dcc-m-1 and click

Close

.

.................................................................................................................................................................................................

Important! Synchronization Autoreconfiguration is only provisionable if the system

Timing Mode parameter is Line and the Sync Messaging parameter of all ports is

enabled. If the Sync Messaging parameter is enabled at any port in the network, it must be enabled at all ports in the network.

Provision synchronization functions (for example, timing mode) according to work instructions.

Reference:

(p. 6-16)

Procedure 6-5: “Network Element synchronization provisioning”

.................................................................................................................................................................................................

Important! If Remote NE Status is to be used, at least one network element must be provisioned as the Alarm Gateway Network Element (AGNE) in the network. If the network element is designated as the Alarm Gateway Network Element

(AGNE), the Alarm Gateway parameter must be provisioned Enabled.

From the System View menu, select

Administration

→

Set NE

, provision the Remote

NE Status, Alarm Group, and Alarm Gateway parameters according to the work instructions, and click

OK

.

.................................................................................................................................................................................................................................

9-20 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-1.3: Establish high-speed 1+1 linear

(Main-to-Main) network

10

Result:

A dialog box appears asking you to confirm executing this command. Click

Yes

.

Reference:

Procedure 7-9: “Set NE defaults — alarm gateway, alarm group, remote NE status, FTP/FTTD, security and history log thresholds” (p. 7-28)

.................................................................................................................................................................................................

At the far-end node, provision the Main ports, DCC terminations, synchronization, and

Remote NE Status functions according to the work instructions.

If the far-end node is a...

Metropolis

®

DMX,

Metropolis

®

Metropolis

®

DMXtend or

DMXplore,

Then...

Repeat

Step 1

through

Step 9 .

Refer to the other product’s documentation to provision the required Main ports, DCC terminations, synchronization, and remote NE status functions.

11

.................................................................................................................................................................................................

Important! The near-end circuit pack in the Main 1 slot must be connected to the far-end circuit pack in the Main 1 slot, and the near-end circuit pack in the Main 2 slot must be connected to the far-end circuit pack in the Main 2 slot. Refer to the

1+1 linear worksheet.

Connect the optical fibers and verify the integrity of the optical span being established.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

12

.................................................................................................................................................................................................

Perform end-to-end optical line test.

Reference:

(p. 14-61)

Procedure 14-7: “Perform end-to-end optical line test on Main OLIUs”

13

.................................................................................................................................................................................................

At each node in the 1+1 linear network, click the

Alarm List

button or select

Fault

→

NE Alarm List

from the System View menu and verify that no alarms are present.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

14

Important! Establishing service requires that the proper slots in each terminating node be properly equipped with the correct circuit pack(s) for the type of service being established. It also requires numerous cross-connections in each of the nodes

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-21

Network configuration procedures Procedure 9-1.3: Establish high-speed 1+1 linear

(Main-to-Main) network representing the path of the required service. Additionally, transmission tests should be performed to verify the continuity and quality of the established circuit.

The 1+1 linear network is now ready for initial service to be established.

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

E

N D O F

S

T E P S

1+1 Linear Worksheet (Main-to-Main)

Near End

M1

OUT

IN

IN

OUT

M1

Far End

M2

OUT

IN

TID=

Protection Group AID

M1

OUT Fiber Color/ID

IN Fiber Color/ID

Received Power Level

Required LBO

M2

OUT Fiber Color/ID

IN Fiber Color/ID

Received Power Level

Required LBO

IN

OUT

M2 nc-dmx-252

TID=

Protection Group AID

Port

IN Fiber Color/ID

Received Power Level

Required LBO

OUT Fiber Color/ID

Port

IN Fiber Color/ID

Received Power Level

Required LBO

OUT Fiber Color/ID nc-dmx-251

.................................................................................................................................................................................................................................

9-22 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

Procedure 9-1.4: Establish high-speed 1+1 linear

(Main-to-Function/Growth) network

.................................................................................................................................................................................................................................

Important! This is not a standalone procedure. Perform this procedure only as directed by

Procedure 9-1: “Establish high-speed end-to-end Metropolis

®

DMX system” (p. 9-3) .

Step

1

Important! This procedure assumes that the high-speed 1+1 linear network is established by interconnecting the OC-12/OC-48 Main slot pair of the Metropolis

®

DMX to an OC-12/OC-48 Function/Growth slot pair of another Metropolis

®

DMX.

However, the OC-12/OC-48 Main slot pair of the Metropolis

®

DMX may also be connected to an OC-12/OC-48 Function/Growth slot pair of a Metropolis

®

DMXtend. If connecting to a Metropolis

®

DMXtend, refer to the Metropolis

®

DMXtend Access Multiplexer User Operations Guide, 365-372-325, as required, when performing this procedure.

This procedure assumes that the near-end node is the Main slot pair of a

Metropolis

®

DMX and the far-end node is the Function/Growth slot pair of a

Metropolis

®

DMX or Metropolis

®

DMXtend. Refer to the 1+1 linear worksheet at the end of this procedure when performing this procedure.

This procedure assumes that all Metropolis

®

DMX shelves have been equipped with the required circuit packs/pluggable transmission modules, software has been installed, and the shelf has passed the looped transmission tests. If not, refer to

Chapter 5, “Node turnup procedures” .

Ignore all alarms until the procedure is complete.

Complete the following steps to establish a high-speed 1+1 linear (main-tofunction/growth) network.

.................................................................................................................................................................................................

Important! The port Application parameter must be provisioned 1+1 at both ends of the system, Optimized 1+1 at both ends of the system, or Bidirectional 1+1 at both ends of the system. Bidirectional 1+1 is only required when interworking with other vendor’s equipment that does not bridge DCC traffic on the active and standby lines. (Metropolis

®

DMX supports bridging DCC traffic on the active and standby lines.)

Metropolis

®

DMXtend does not support Optimized 1+1.

From the System View menu at the near-end node, use the

Configuration

→

Equipment

command to access the Main 1 and 2 ports and provision the port parameters according to the work instructions.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-23

Network configuration procedures Procedure 9-1.4: Establish high-speed 1+1 linear

(Main-to-Function/Growth) network

2

3

4

5

6

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

Use the

View

→

Equipment

command to access the Main 1 and 2 ports and verify that the ports were provisioned correctly.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Equipment

. Select the system

(AID=system), then click

Select

at the bottom of the window.

If required, provision the 1+1 Protection Priority (1+1 applications only) and Wait To

Rename (Optimized 1+1 applications only) parameters. Click

Apply

if changes were made, then click

Yes

to the warning message to make your changes. Click

Close

to exit.

.................................................................................................................................................................................................

Important! The protection group Revertive Mode and Wait to Restore parameters apply to 1+1 applications and Bidirectional 1+1 applications only.

If the Revertive Mode parameter is disabled, the Wait to Restore parameter is not provisionable.

If required, from the System View menu,

1. Select

Configuration

→

Equipment

.

2. Select the

Ptn Grp

tab.

3. Click on the required 1+1 protection group and

Select

.

4. Provision the required protection group parameters according to the work instructions, then click

Apply

and

Close

. If no changes were made, click

Close

and go to the next step.

.................................................................................................................................................................................................

If required, from the System View menu,

1. Select

View

→

Protection

.

2. Select the required 1+1 protection group and click

Select

.

3. Verify that the protection group parameters were provisioned correctly. Then click

Close

.

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled, the LAPD Role parameter must be provisioned differently at each end of an optical span. For example, if the LAPD

Role parameter is provisioned user-side at one end of an optical span, then the

LAPD Role parameter must be provisioned network-side at the other end of the optical span.

.................................................................................................................................................................................................................................

9-24 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

7

8

9

Procedure 9-1.4: Establish high-speed 1+1 linear

(Main-to-Function/Growth) network

From the System View menu, select

Configuration

→

DCC Terminations

and provision the DCC terminations for DCC port dcc-m-1 according to the work instructions.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

From the System View menu, select

View

→

DCC Terminations

, verify that the DCC terminations were provisioned correctly for DCC port dcc-m-1, and click

Close

.

.................................................................................................................................................................................................

Important! Synchronization Autoreconfiguration is only provisionable if the system

Timing Mode parameter is Line and the Sync Messaging parameter of all ports is

enabled. If the Sync Messaging parameter is enabled at any port in the network, it must be enabled at all ports in the network.

Provision synchronization functions (for example, timing mode) according to work instructions.

Reference:

(p. 6-16)

Procedure 6-5: “Network Element synchronization provisioning”

.................................................................................................................................................................................................

Important! If Remote NE Status is to be used, at least one network element must be provisioned as the Alarm Gateway Network Element (AGNE) in the network. If the network element is designated as the Alarm Gateway Network Element

(AGNE), the Alarm Gateway parameter must be provisioned Enabled.

From the System View menu, select

Administration

→

Set NE

, provision the Remote

NE Status, Alarm Group, and Alarm Gateway parameters according to the work instructions, and click

OK

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-25

Network configuration procedures Procedure 9-1.4: Establish high-speed 1+1 linear

(Main-to-Function/Growth) network

10

Result:

A dialog box appears asking you to confirm executing this command. Click

Yes

.

Reference:

Procedure 7-9: “Set NE defaults — alarm gateway, alarm group, remote NE status, FTP/FTTD, security and history log thresholds” (p. 7-28)

.................................................................................................................................................................................................

At the far-end node, provision the required Function/Growth ports and DCC terminations according to the work instructions.

If the far-end node is a...

Metropolis

®

DMX,

Metropolis

®

DMXtend,

Then...

Refer to

Procedure 9-5: “Establish low-speed 1+1 linear optical extension” (p. 9-69)

to provision the required Function/Growth ports and DCC terminations.

Refer to the other product’s documentation to provision the required Function/Growth ports and

DCC terminations.

11

12

.................................................................................................................................................................................................

Important! The near-end circuit pack in the Main 1 slot must be connected to the far-end circuit pack in the Metropolis

®

DMX Function/Growth slot A1, B1, C1,

D1, G1, or the Metropolis

®

DMXtend Function slot D1 or G1.

The near-end circuit pack in the Main 2 slot must be connected to the far-end circuit pack in the Metropolis

®

DMX Function/Growth slot A2, B2, C2, D2, G2, or the Metropolis

®

DMXtend Function slot D2 or G2.

Refer to the 1+1 linear worksheet at the end of this procedure when connecting fibers.

Connect the optical fibers and verify the integrity of the optical span being established.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Perform end-to-end optical line test.

Reference:

•

Procedure 14-7: “Perform end-to-end optical line test on Main OLIUs”

(p. 14-61)

•

Procedure 14-8: “Perform end-to-end optical line test on Function OLIUs”

(p. 14-64)

.................................................................................................................................................................................................................................

9-26 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-1.4: Establish high-speed 1+1 linear

(Main-to-Function/Growth) network

13

14

.................................................................................................................................................................................................

At each node in the 1+1 linear network, click the

Alarm List

button or select

Fault

→

NE Alarm List

from the System View menu and verify that no alarms are present.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! Establishing service requires that the proper slots in each terminating node be properly equipped with the correct circuit pack(s) for the type of service being established. It also requires numerous cross-connections in each of the nodes representing the path of the required service. Additionally, transmission tests should be performed to verify the continuity and quality of the established circuit.

The 1+1 linear network is now ready for initial service to be established.

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-27

Network configuration procedures Procedure 9-1.4: Establish high-speed 1+1 linear

(Main-to-Function/Growth) network

1+1 Linear Worksheet (Main-to-Function/Growth)

Important! A, B, C, D, and G (Growth) are valid Function slot pairs for

Metropolis

®

DMX. D and G (Growth) are valid Function slot pairs for Metropolis

®

DMXtend.

Near End

M1

OUT

IN

Far End

IN

OUT

(A,B,C,D,G) 1

Line Timed

M2

OUT

IN

TID=

Protection Group AID

M1

OUT Fiber Color/ID

IN Fiber Color/ID

Received Power Level

Required LBO

M2

OUT Fiber Color/ID

IN Fiber Color/ID

Received Power Level

Required LBO

IN

OUT

(A,B,C,D,G) 2

Line or External Timed nc-dmx-253

TID=

Protection Group AID

Port

IN Fiber Color/ID

Received Power Level

Required LBO

OUT Fiber Color/ID

Port

IN Fiber Color/ID

Received Power Level

Required LBO

OUT Fiber Color/ID nc-dmx-251

.................................................................................................................................................................................................................................

9-28 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

Procedure 9-2: Add new Metropolis

®

DMX node to network

.................................................................................................................................................................................................................................

Overview

Use this procedure to add a new Metropolis

®

DMX node to a unidirectional path switched ring (UPSR)/bidirectional line switched ring (BLSR) using the following:

•

OC-3 UPSR (Function/Growth slot pair only)

•

OC-12 UPSR (Main slot pair or a Function/Growth slot pair)

•

OC-48 UPSR (Main slot pair or a Function/Growth slot pair)

•

OC-192 UPSR (Main slot pair only)

•

OC-48 BLSR (Main slot pair or a Function/Growth slot pair)

•

OC-192 BLSR (Main slot pair only).

Important! This procedure assumes that the new Metropolis

®

DMX shelf has been equipped with the required circuit packs/pluggable transmission modules, software has been installed, and the shelf has passed the looped transmission tests. If not, refer to

Chapter 5, “Node turnup procedures” .

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 9-2) , the following

equipment is also required at the new Metropolis

®

DMX node and the two adjacent network elements:

•

Optical power meter

•

Note pad

•

Technicians at each network element must be able to communicate with each other.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 9-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Verify that the work instructions specify the following for the new node:

•

System-level parameter settings (for example, TID, alarm gateway function, and alarm group)

•

Automatic ring discovery parameter settings (BLSRs only)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-29

Network configuration procedures Procedure 9-2: Add new Metropolis

®

DMX node to network

•

System synchronization parameter settings

•

Port AIDs and parameter settings

•

DCC port AIDs and parameter settings

•

Nodes that are to be adjacent to the new node

Step

1

2

3

4

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to add a new Metropolis

®

DMX node to a network.

.................................................................................................................................................................................................

To verify that no alarms are present at the new node, click

Alarm List

in the top right corner of the System View or select

Fault

→

NE Alarm List

.

To verify that no loopbacks, protection switch lockouts, or protection switches are present at the new node, from the System View menu, select

View

→

Rolling Events

.

Under the line beginning with

RTRV-COND-ALL

, any loopbacks, protection switch lockouts, or protection switches are displayed. Click

Close

.

Important! If the Metropolis

®

DMX fails to respond in the indicated manner, refer to the Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble Clearing

Guide, 365-372-302.

.................................................................................................................................................................................................

Notify maintenance center that alarms will be generated.

.................................................................................................................................................................................................

Important! Two or more shelves in the same network cannot have the same TID.

Determine from either the Network Operations Center (NOC) or work instructions, all the other nodes in the existing ring. Verify that no duplicate TID settings exist between the ring and the new node. If duplicate TID settings exist, determine new settings and at each of the sites with duplicate TID settings, select

Administration

→

Set TID

from the System View menu, and enter new TID settings.

Reference:

Procedure 7-11: “Set/change system TID” (p. 7-38)

.................................................................................................................................................................................................

If required, modify the network service access point (NSAP) address and/or enable

Level 2 routing capabilities at the new node to be compatible with the network.

.................................................................................................................................................................................................................................

9-30 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-2: Add new Metropolis

®

DMX node to network

5

Reference:

Procedure 7-13: “Provision network layer 3 parameters” (p. 7-40)

.................................................................................................................................................................................................

To designate the alarm gateway function and alarm group numbers, select

Administration

→

Set NE

from the System View at the new node. If required, provision the Remote NE Status, Alarm Group, and Alarm Gateway parameters according to the work instructions.

Reference:

Procedure 7-9: “Set NE defaults — alarm gateway, alarm group, remote NE status, FTP/FTTD, security and history log thresholds” (p. 7-28)

6

.................................................................................................................................................................................................

At the adjacent nodes, verify and record the DCC termination settings using the

View

→

DCC Terminations

command.

.................................................................................................................................................................................................

7

If adding a new node (shelf) to a...

UPSR,

Then...

BLSR,

Proceed to

Procedure 9-2.1: “Add new

Metropolis

®

DMX node to UPSR” (p. 9-32) .

Proceed to

Procedure 9-2.2: “Add new

Metropolis

®

DMX node to BLSR” (p. 9-38) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-31

Network configuration procedures

Procedure 9-2.1: Add new Metropolis

®

DMX node to UPSR

.................................................................................................................................................................................................................................

Important! This is not a standalone procedure. Perform this procedure only as directed by

Procedure 9-2: “Add new Metropolis

®

DMX node to network”

(p. 9-29) .

Step

1

2

3

Important! This procedure assumes that the new Metropolis

®

DMX shelf has been equipped with the required circuit packs/pluggable transmission modules, software has been installed, and the shelf has passed the looped transmission tests. If not, refer to

Chapter 5, “Node turnup procedures” .

A new Metropolis

®

DMX node may be added to a unidirectional path switched ring (UPSR) using the following:

•

OC-3 UPSR (Function/Growth slot pair only)

•

OC-12 UPSR (Main slot pair or a Function/Growth slot pair)

•

OC-48 UPSR (Main slot pair or a Function/Growth slot pair)

•

OC-192 UPSR (Main slot pair only).

Complete the following steps to add a new Metropolis

®

DMX node to an existing

UPSR.

.................................................................................................................................................................................................

Important! For UPSR applications, the port Application parameter must be provisioned UPSR.

From the System View menu at the new node, use the

Configuration

→

Equipment

command to access the Main 1 and 2 ports and provision the port parameters according to the work instructions.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

Use the

View

→

Equipment

command to access the Main 1 and 2 ports and verify that the ports were provisioned correctly.

.................................................................................................................................................................................................

Important! The LAPD Role parameter must be provisioned differently at each end of an optical span. For example, if the LAPD Role parameter is provisioned user-side at one end of an optical span, then the LAPD Role parameter must be provisioned network-side at the other end of the optical span.

.................................................................................................................................................................................................................................

9-32 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-2.1: Add new Metropolis

®

DMX node to

UPSR

4

5

6

From the System View menu at the new node,

1. Select

Configuration

→

DCC Terminations

2. Select the required DCC Port dcc-m1-1 or dcc-{a,b,c,d,g}1-{n}, and provision the

DCC terminations according to the work instructions.

3. Click

Apply

to make changes.

4. Select the required DCC Port dcc-m2-1 or dcc-{a,b,c,d,g}2-{n}, and provision the

DCC terminations according to the work instructions.

5. Click

Apply

to make changes.

6. Click

Close

.

Result:

The system reports inconsistent DCC values and section DCC channel failed alarms. These alarms clear when the new node is connected to

UPSR.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

From the System View menu at the new node, select

View

→

DCC Terminations

, verify that the DCC terminations were provisioned correctly and click

Close

.

.................................................................................................................................................................................................

If the new node is added to the UPSR using the Main OLIU circuit packs, determine from either the Network Operations Center (NOC) or the work instructions the synchronization for the new node. If DS1 external timing references are not available, view the synchronization of the adjacent nodes to determine the direction of the line timing. Configure the new node the same way. From the System View menu, select

Configuration

→

Timing/Sync

and provision the synchronization parameters according to the work instructions or office records.

Reference:

(p. 6-16)

Procedure 6-5: “Network Element synchronization provisioning”

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

If pass-through cross-connections are not provisioned service interruptions can occur.

Pass-through cross-connections must be provisioned to support existing traffic on the ring through the new node.

Determine from either the Network Operations Center (NOC) or work instructions all the other nodes in the existing ring. Verify through the NOC all existing cross-connections that exist on the adjacent nodes to where the new node will be located. Also, note the cross-connection rate (for example, STS1, STS3C). These will

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-33

Network configuration procedures Procedure 9-2.1: Add new Metropolis

®

DMX node to

UPSR

7

8

be pass-through cross-connections at the new node. Enter the required pass-through cross-connections into the new node by selecting

Configuration

→

Cross-

Connections

→

Create a New Cross-Connection

.

Important! It may be helpful to make a sketch of the network to visualize the cross-connections required.

.................................................................................................................................................................................................

Important! Refer to the example in

Figure 9-1, “Adding a node example” (p. 9-35)

when performing this step. The example assumes that the UPSR network is established using the Main slot pairs of Metropolis

®

DMX nodes. However, the

Main/Function/Growth slots pairs at a Metropolis

®

DMX may also be connected in a UPSR with another Metropolis

®

DMX (Function/Growth slot pair), a Metropolis

®

DMXtend (Main/Function/Growth slot pair) and/or a Metropolis

®

DMXplore (Main slot pair).

At each node in the UPSR, select

Reports

→

Path Protection List

to verify that no

Forced or Lockout path protection switches exist.

If required, clear any existing Forced or Lockout path protection switches using the

Fault

→

Protection Switch

→

Path Protection

→

Switch Type Clear

command.

(Refer to

Figure 9-1, “Adding a node example” (p. 9-35)

Figure A.)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Removal of wrong fiber connections will result in a service interruption.

Using the work instructions, identify the nodes adjacent to the new node and ensure that you remove only the fiber connections for the optical span being discontinued.

Important! When the optical fibers are disconnected, the system performs automatic protection switches and subsequent transmission hits (less than 60 ms) will occur.

Perform the following: (Refer to

Figure 9-1, “Adding a node example” (p. 9-35)

Figure

B for example.)

•

At the West adjacent node (NE1), disconnect the optical fibers connected to the

East adjacent node (NE2).

•

At the East adjacent node (NE2), disconnect the optical fibers connected to the

West adjacent node (NE1).

.................................................................................................................................................................................................................................

9-34 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-2.1: Add new Metropolis

®

DMX node to

UPSR

Result:

Automatic path protection switching may occur at nodes in the ring.

Transmission hits (less than 60 ms) occur as active traffic switches.

Figure 9-1 Adding a node example

Figure A Figure B m2 NE5 m1 m2 NE5 m1 m1 m2

NE1 m2 m1

UPSR

NE4 m2 m1

NE3

NE2 m1 m2

NE1 m2 m1 m1 m2

UPSR

NE2 m1 m2

NE4 m2 m1

NE3

Figure C m2

NE5 m1 m1 m2

NE1 m2 m1

NE4 m2

UPSR m1

NE3

NE2 m1 m2

MA-DMXplore-024

Figure A shows the new node (NE5) to be added to the UPSR.

Figure B shows the UPSR after path switches are performed on designated paths and fibers are disconnected between the West and East adjacent nodes (NE1 and NE2).

Figure C shows the new node (NE5) connected to the UPSR.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-35

Network configuration procedures Procedure 9-2.1: Add new Metropolis

®

DMX node to

UPSR

9

10

11

12

.................................................................................................................................................................................................

Perform the following: (Refer to

Figure 9-1, “Adding a node example” (p. 9-35)

Figure

C for example.)

•

At the West adjacent node (NE1), New node (NE5), and East adjacent node (NE2), connect all transmit fibers.

•

At the West adjacent node (NE1), New node (NE5), and East adjacent node (NE2), measure the optical power level in the receive direction and attenuate if necessary.

•

At the West adjacent node (NE1), New node (NE5), and East adjacent node (NE2), connect all receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

From the System View menu at the new node, select

Administration

→

OSI Neighbor

Map

and verify that the new node is connected to the required adjacent nodes.

Important! If the report indicates wrong (or no) fiber connections and DCC-related alarms are reported, select

View

→

DCC Terminations

to obtain the View DCC

Termination report and verify that the DCC terminations are provisioned correctly.

If required, check fiber integrity and verify the node NSAP address is correct using the

Administration

→

View NE Administration

command.

.................................................................................................................................................................................................

From the System View menu at the new node, select

View

→

Timing/Sync

and verify the operational synchronization mode of the new node.

If the

Timing Mode

is holdover, check that the incoming timing references are connected. Also check

Mode Switching

(NA, revertive, or nonrevertive). If DS1 timing inputs are used, click the

Timing Input Ports

tab and check the

DS1 Input

Format

.

.................................................................................................................................................................................................

At the new node and the adjacent nodes, click the

Alarm List

button or select

Fault

→

NE Alarm List

from the System View menu and verify that no alarms are present.

Important! If inc. VT AIS

, inc. VT unequipped

, inc. STSN AIS

, inc. STSN unequipped alarm is present with no inc. OCn LOS alarm at the nodes adjacent to the new node, check that all pass-through cross-connections at the new node have been properly made. From the System View menu, select

View

→

Cross-Connections

.

.................................................................................................................................................................................................................................

9-36 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

13

Procedure 9-2.1: Add new Metropolis

®

DMX node to

UPSR

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! Establishing service requires that the proper slots in each terminating node be properly equipped with the correct circuit pack(s) for the type of service being established. It also requires numerous cross-connections in each of the nodes representing the path of the required service. Additionally, transmission tests should be performed to verify the continuity and quality of the established circuit.

The new node is now ready for initial service to be established.

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-37

Network configuration procedures

Procedure 9-2.2: Add new Metropolis

®

DMX node to BLSR

.................................................................................................................................................................................................................................

Important! This is not a standalone procedure. Perform this procedure only as directed by

Procedure 9-2: “Add new Metropolis

®

DMX node to network”

(p. 9-29) .

Step

Important! This procedure assumes that the new Metropolis

®

DMX shelf has been equipped with the required circuit packs, software has been installed, and the shelf has passed the looped transmission tests. If not, refer to

Chapter 5, “Node turnup procedures” .

A new Metropolis

®

DMX node may be added to a bidirectional line switched ring

(BLSR) using the following:

•

OC-48 BLSR (Main slot pair or a Function/Growth slot pair)

•

OC-192 BLSR (Main slot pair only).

A BLSR supports up to 16 nodes.

Complete the following steps to add a new Metropolis

®

OC-48/OC-192 BLSR.

DMX node to an

1

.................................................................................................................................................................................................

From the System View menu at a node in the OC-48/OC-192 BLSR,

1. Select

View

→

Protection

.

2. Select the required 2F BLSR protection group and click

Select

.

3. Click on the Provisionable Parameters tab and observe the provisioned value of the

Automatic Ring Discovery parameter. Determine whether Automatic Ring

Discovery is enabled or disabled and click

Close

.

.................................................................................................................................................................................................

2

Important! For BLSR applications, the port Application parameter must be provisioned 2F BLSR.

From the System View menu at the new node, use the

Configuration

→

Equipment

command to access the Main 1 and 2 ports and provision the port parameters according to the work instructions.

Result:

The system reports a default K-bytes alarm.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

3

Use the

View

→

Equipment

command to access the Main 1 and 2 ports and verify that the ports were provisioned correctly.

.................................................................................................................................................................................................................................

9-38 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-2.2: Add new Metropolis

®

DMX node to

BLSR

4

5

6

7

.................................................................................................................................................................................................

From the system view at the new node,

1. Select

Configuration

→

Equipment

.

2. Select the

Ring ID

tab and expand the required ring by clicking on the plus sign

(+).

3. Select the required 2F BLSR protection group and click

Select

.

4. Provision the required protection group parameters according to the work instructions, then click

Apply

to make the changes.

5. Click

Close

.

.................................................................................................................................................................................................

From the System View menu,

1. Select

View

→

Protection

.

2. Select the required 2F BLSR protection group and click

Select

.

3. Click on the Provisionable Parameters tab and verify that the protection group parameters were provisioned correctly. Then click

Close

.

.................................................................................................................................................................................................

Important! The LAPD Role parameter must be provisioned differently at each end of an optical span. For example, if the LAPD Role parameter is provisioned user-side at one end of an optical span, then the LAPD Role parameter must be provisioned network-side at the other end of the optical span.

From the System View menu at the new node,

1. Select

Configuration

→

DCC Terminations

.

2. Select the required DCC Port dcc-m1-1 or dcc-{a,b,c,d,g}1-{n}, and provision the

DCC terminations according to the work instructions.

3. Click

Apply

to make changes.

4. Select the required DCC Port dcc-m2-1 or dcc-{a,b,c,d,g}2-{n}, and provision the

DCC terminations according to the work instructions.

5. Click

Apply

to make changes.

6. Click

Close

.

Result:

The system reports inconsistent DCC values and section DCC channel failed alarms. These alarms clear when the new node is connected to

BLSR.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

From the System View menu at the new node, select

View

→

DCC Terminations

, verify that the DCC terminations were provisioned correctly and click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-39

Network configuration procedures Procedure 9-2.2: Add new Metropolis

®

DMX node to

BLSR

8

9

10

11

.................................................................................................................................................................................................

If the new node is added to the BLSR using the Main OLIU circuit packs, determine from either the Network Operations Center (NOC) or the work instructions the synchronization for the new node. If DS1 external timing references are not available, view the synchronization of the adjacent nodes to determine the direction of the line timing. Configure the new node the same way. From the System View menu, select

Configuration

→

Timing/Sync

and provision the synchronization parameters according to the work instructions or office records.

Reference:

(p. 6-16)

Procedure 6-5: “Network Element synchronization provisioning”

.................................................................................................................................................................................................

Determine from either the Network Operations Center (NOC) or the work instructions all the other nodes in the existing ring. Verify through the NOC all existing cross-connections that exist on the adjacent nodes to where the new node will be located. Also, note the source or destination, cross-connection type (for example, 2F

BLSR add/drop, 1-way), and cross-connection rate (for example, STS1, STS3c). These will be pass-through cross-connections at the new node.

Important! It may be helpful to make a sketch of the network to visualize the required pass-through cross-connections at the new node.

To verify the cross-connections, at the adjacent West node select

View

→

Cross-Connections

. On the left side of the screen, select the required circuit pack and click

Select

. Record the Src (source tributary AID), Src NE Name (source network element name) Type, Rate, Dest (destination tributary AID), Dest NE Name

(destination network element name), and CKT ID (circuit ID) of the cross-connections that result in traffic directly to and/or from the other adjacent node. These will be pass-through cross-connections at the new node.

.................................................................................................................................................................................................

At each node in the BLSR, verify that no BLSR protection switches are present, select

View

→

Rolling Events

. Under the line reading

RTRV-COND-ALL determine if any protection switches are displayed.

Remove all BLSR protection switches before continuing with this procedure.

Reference:

Metropolis

®

DMXplore Access Multiplexer Alarm Messages and

Trouble Clearing Guide, 365-372-333

.................................................................................................................................................................................................

Important! The Force to Protection, Ring switch may cause transmission hits (less than 60 ms).

.................................................................................................................................................................................................................................

9-40 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-2.2: Add new Metropolis

®

DMX node to

BLSR

Perform the following: (Refer to the following figure.)

•

At the West Node, from the System View menu select

Fault

→

Protection Switch

.

Select the required 2F BLSR protection group (according to the work instructions) and perform a protection switch in the

East

direction with switch type

Force to

Protection, Ring

. Click

Apply

. A dialog box appears asking you to confirm executing this command. Click

Yes

. After the protection switch completes, click

Close

.

•

At the East Node, from the System View menu select

Fault

→

Protection Switch

.

Select the required 2F BLSR protection group (according to the work instructions) and perform a protection switch in the

West

direction with switch type

Force to

Protection, Ring

. Click

Apply

. A dialog box appears asking you to confirm executing this command. Click

Yes

. After the protection switch completes, click

Close

.

Line

1W

Line

1E

Line

1W

Line

1E

Line

1W

Line

1E

West

Node

New

Node

East

Node

Line

1E

Other

Node(s)

Line

1W

Line

1E

Other

Node(s)

Line

1W

NC-USM-219

12

Legend

:

Line 1W: Line 1W (West port) is the port in slot 1 of the 2F BLSR protection group

(for example, Main-1 or FN-A-1).

Line 1E: Line 1E (East port) is the port in slot 2 of the 2F BLSR protection group (for example, Main-2 or FN-A-2).

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Removal of wrong fiber connections will result in a service interruption.

Ensure that you remove only the fiber connections for the optical span being discontinued.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-41

Network configuration procedures Procedure 9-2.2: Add new Metropolis

®

DMX node to

BLSR

Perform the following: (Refer to the following figure.)

•

At the West Node, disconnect the optical fibers connected to the East Node.

•

At the East Node, disconnect the optical fibers connected to the West Node.

Line

1W

Line

1E

Line

1W

Line

1E

Line

1W

Line

1E

West

Node

New

Node

East

Node

Line

1E

Other

Node(s)

Line

1W

Line

1E

Other

Node(s)

Line

1W

NC-USM-220

13

Legend

:

Line 1W: Line 1W (West port) is the port in slot 1 of the 2F BLSR protection group

(for example, Main-1 or FN-A-1).

Line 1E: Line 1E (East port) is the port in slot 2 of the 2F BLSR protection group (for example, Main-2 or FN-A-2).

.................................................................................................................................................................................................

Perform the following: (Refer to the following figure.)

•

At the West, New, and East nodes, connect all transmit fibers.

•

At the West, New, and East nodes, measure the optical power level in the receive direction and attenuate if necessary.

•

At the West, New, and East nodes, connect all receive fiber.

.................................................................................................................................................................................................................................

9-42 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-2.2: Add new Metropolis

®

DMX node to

BLSR

Refer to

Procedure 14-4: “Perform connection and verification of optical facility”

(p. 14-44) .

Line

1W

Line

1E

Line

1W

Line

1E

Line

1W

Line

1E

West

Node

New

Node

East

Node

Line

1E

Other

Node(s)

Line

1W

Line

1E

Other

Node(s)

Line

1W

NC-USM-221

Legend

:

Line 1W: Line 1W (West port) is the port in slot 1 of the 2F BLSR protection group

(for example, Main-1 or FN-A-1).

Line 1E: Line 1E (East port) is the port in slot 2 of the 2F BLSR protection group (for example, Main-2 or FN-A-2).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-43

Network configuration procedures Procedure 9-2.2: Add new Metropolis

®

DMX node to

BLSR

.................................................................................................................................................................................................

14

If...

automatic ring discovery (Release 3.0

and later releases), manual ring discovery (Release 2.1),

Then...

Important! As the ring is connected, nodes automatically communicate with each other using the data communications channel (DCC) and build a ring map. If successful, automatic ring discovery builds a ring map at each node and the

Ring

Discovery in Progress condition clears. If unsuccessful, the ring map is not complete and alarms are reported.

Perform the following:

1. Wait until the

Ring Discovery in

Progress condition clears.

If other alarms/conditions are reported, refer to the Metropolis

®

DMX Access

Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302 and clear the alarms/conditions.

2. Continue with

Step 15 .

Important! The manual ring map must be updated manually at each node in the ring.

Perform the following:

1. At the new node, edit and activate the manual ring map.

2. At the existing nodes, edit the manual ring map to add the new node, but do

NOT activate the updated manual ring maps.

3. Continue with

Step 15 .

Procedure 9-4: “Provision manual ring map”

(p. 9-63)

15

.................................................................................................................................................................................................

From the System View menu at the new node, select

Administration

→

OSI Neighbor

Map

and verify that the new node is connected to the required adjacent nodes.

Important! If the report indicates wrong (or no) fiber connections and DCC-related alarms are reported, select

View

→

DCC Terminations

to obtain the View DCC

.................................................................................................................................................................................................................................

9-44 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-2.2: Add new Metropolis

®

DMX node to

BLSR

16

17

Termination report and verify that the DCC terminations are provisioned correctly.

If required, check fiber integrity and verify the node NSAP address is correct using the

Administration

→

View NE Administration

command.

.................................................................................................................................................................................................

From the System View menu at the new node, select

View

→

Timing/Sync

and verify the operational synchronization mode of the new node.

If the

Timing Mode

is holdover, check that the incoming timing references are connected. Also check

Mode Switching

(NA, revertive, or nonrevertive). If DS1 timing inputs are used, click the

Timing Input Ports

tab and check the

DS1 Input

Format

.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

If pass-through cross-connections are not provisioned service interruptions can occur.

Pass-through cross-connections must be provisioned to support existing traffic on the ring through the new node.

18

At the new node, enter the required pass-through cross-connections (based on the cross-connection information retrieved in

Step 9 ) by selecting

Configuration

→

Cross-Connections

→

Create a New Cross-Connection

.

.................................................................................................................................................................................................

If Automatic Ring Discovery is disabled (that is, manual ring discovery), activate the manual ring maps at the existing nodes in the network. Otherwise, continue with the next step.

Select

Configuration

→

Activate Manual Ring Map

. Select the required Ring ID and click

Select

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-45

Network configuration procedures Procedure 9-2.2: Add new Metropolis

®

DMX node to

BLSR

19

20

21

22

Result:

A dialog box appears asking you to confirm activating the manual ring map. Click

OK

. The inactive manual ring map is now activated.

.................................................................................................................................................................................................

Perform the following:

•

At the West Node, from the System View menu select

Fault

→

Protection Switch

.

Select the required 2F BLSR protection group and clear the protection switch in the

East

direction with switch type

Clear

. Click

Apply

. A dialog box appears asking you to confirm executing this command. Click

Yes

. After the protection switch clears, click

Close

.

•

At the East Node, from the System View menu select

Fault

→

Protection Switch

.

Select the required 2F BLSR protection group and clear the protection switch in the

West

direction with switch type

Clear

. Click

Apply

. A dialog box appears asking you to confirm executing this command. Click

Yes

. After the protection switch clears, click

Close

.

Important! The Clear switch may cause transmission hits (less than 60 ms). Wait for alarms to clear.

.................................................................................................................................................................................................

From the System View menu at the East and West nodes,

1. Select

View

→

Protection

.

2. Select the required 2F BLSR protection group and click

Select

.

3. Observe the Ring Node APS (Automatic Protection Switch) State, East Switch

Request State, West Switch Request State, East Channel State, and West Channel

State parameters. Verify that the protection switches have cleared and click

Close

.

.................................................................................................................................................................................................

At the new node and the adjacent nodes, click the

Alarm List

button or select

Fault

→

NE Alarm List

from the System View menu and verify that no alarms are present.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! Establishing service requires that the proper slots in each terminating node be properly equipped with the correct circuit pack(s) for the type of service being established. It also requires numerous cross-connections in each of the nodes representing the path of the required service. Additionally, transmission tests should be performed to verify the continuity and quality of the established circuit.

The new node is now ready for initial service to be established.

.................................................................................................................................................................................................................................

9-46 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-2.2: Add new Metropolis

®

DMX node to

BLSR

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-47

Network configuration procedures

Procedure 9-3: Discontinue Metropolis

®

DMX node from network

.................................................................................................................................................................................................................................

Overview

Use this procedure to discontinue a Metropolis

®

DMX node from a unidirectional path switched ring (UPSR) or bidirectional line switched ring (BLSR).

The Metropolis

®

DMX node may interface with a UPSR/BLSR using the OLIU circuit packs in the Main slot pair or a Function/Growth slot pair.

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 9-2)

in this chapter

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

Step

1

2

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to discontinue a Metropolis

®

DMX node from a UPSR or BLSR.

.................................................................................................................................................................................................

To verify that no alarms are present, select

Fault

→

NE Alarm List

from the System

View menu at each node.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! To retrieve a map of the SONET network, select

Administration

→

OSI Routing Map

and

Administration

→

OSI Neighbor Map

. To retrieve a map of the BLSR use

View

→

Rings

→

Ring Map

.

Determine which Metropolis

®

DMX node is being discontinued.

.................................................................................................................................................................................................................................

9-48 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-3: Discontinue Metropolis

®

DMX node from network

3

4

5

.................................................................................................................................................................................................

Verify that the optical loss budget will not be exceeded by removing this node. (Refer to the Metropolis

®

DMX Access Multiplexer Applications and Planning Guide,

365-372-300 for the SONET optical specifications of the OLIU circuit packs.)

.................................................................................................................................................................................................

Verify the system timing at each node using the

View

→

Timing/Sync

command. If required, reconfigure the timing of the network using the

Configuration

→

Timing/Sync

command.

Important! Reconfiguring network timing may cause nodes to temporarily go into the holdover timing mode.

Reference:

(p. 6-16)

Procedure 6-5: “Network Element synchronization provisioning”

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Discontinuing a node with active add/drop traffic will result in a service interruption.

Ensure that ALL service to/from the UPSR/BLSR is removed from the node before continuing.

6

7

At the node being discontinued, verify that all service to/from the UPSR/BLSR has been removed. From the System View menu, use

View

→

Cross-Connections

to verify that there are no add/drop cross-connections to the UPSR/BLSR. If required, delete any existing add/drop cross-connections to the UPSR/BLSR using

Configuration

→

Cross-Connections

.

.................................................................................................................................................................................................

If the node being discontinued is an AGNE, establish another node in the network as an AGNE (if required). If required, disable the AGNE at the node being discontinued.

Important! At the new AGNE, the Remote NE Status parameter must be enabled prior to designating the AGNE(s).

Reference:

Procedure 7-9: “Set NE defaults — alarm gateway, alarm group, remote NE status, FTP/FTTD, security and history log thresholds” (p. 7-28)

.................................................................................................................................................................................................

If the node being discontinued is the gateway host node, establish another gateway host node with an IP address for the network element and the required IP addresses in the gateway host file.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-49

Network configuration procedures Procedure 9-3: Discontinue Metropolis

®

DMX node from network

Reference:

Procedure 7-16: “Provision/enable/disable the NE as a TL1 TCP/IP

GNE” (p. 7-49)

.................................................................................................................................................................................................

8

If discontinuing a node from a...

Then...

UPSR, Proceed to

Metropolis

®

Procedure 9-3.1: “Discontinue

DMX node from UPSR” (p. 9-51) .

BLSR, Proceed to

Procedure 9-3.2: “Discontinue

Metropolis

®

DMX node from BLSR” (p. 9-56) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

9-50 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

Procedure 9-3.1: Discontinue Metropolis

®

DMX node from

UPSR

.................................................................................................................................................................................................................................

Important! This is not a standalone procedure. Perform this procedure only as directed by

Procedure 9-3: “Discontinue Metropolis

®

DMX node from network”

(p. 9-48) .

Step

1

2

Important! The Metropolis

®

DMX node may be using the OLIU circuit packs in the Main slot pair or a Function/Growth slot pair to interface with a UPSR.

Complete the following steps to discontinue a Metropolis

®

DMX node from a UPSR.

.................................................................................................................................................................................................

Important! Refer to the example in

Figure 9-2, “Discontinuing a node example”

(p. 9-52)

when performing this step. The example assumes that the UPSR network is established using the Main slot pairs of Metropolis

®

DMX nodes. However, the

Main/Function/Growth slots pairs at a Metropolis

®

DMX may also be connected in a UPSR with another Metropolis

®

DMX (Function/Growth slot pair), a Metropolis

®

DMXtend (Main/Function/Growth slot pair) and/or a Metropolis

®

DMXplore (Main slot pair).

At each node in the UPSR, select

Reports

→

Path Protection List

to verify that no

Forced or Lockout path protection switches exist.

If required, clear any existing Forced or Lockout path protection switches using the

Fault

→

Protection Switch

→

Path Protection

→

Switch Type Clear

command. (See example in

Figure 9-2, “Discontinuing a node example” (p. 9-52)

Figure A.)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Removal of wrong fiber connections will result in a service interruption.

Ensure that you remove only the fiber connections for the optical span being discontinued.

Important! When the optical fibers are disconnected, the system performs an automatic protection switch and subsequent transmission hits (less than 60 ms) will occur.

Remove the optical fiber from NE1 M1 transmit to NE5 M2 receive and the optical

fiber from NE5 M1 transmit to NE2 M2 receive (only) ( Figure 9-2, “Discontinuing a node example” (p. 9-52)

Figure A). These optical fibers are associated with Ring (Path)

2.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-51

Network configuration procedures Procedure 9-3.1: Discontinue Metropolis

®

DMX node from

UPSR

Result:

Automatic path protection switching will occur. Ring (Path) 1 is active.

Figure 9-2 Discontinuing a node example

Figure A Figure B m2

NE5 m1 m2

NE5 m1 m1

NE1 m2 m1

NE4 m2 m1

NE3

NE2 m2 m1 m2 m1

NE1 m2 m1

NE2 m2 m1 m2

NE4 m2 m1

NE3

Figure C m2

NE5 m1 m1

NE1 m2 m1

NE2 m2 m1 m2

NE4 m2 m1

NE3

Ring (Path) 1

Ring (Path) 2

NC-Xpress-078

Figure A shows the node to be discontinued (NE5) from the UPSR.

Figure B shows the removal of the optical fibers associated with Ring (Path) 2 and the connection of optical fiber associated with Ring (Path) 2 fiber from NE1 to NE2.

Figure C shows the removal of the optical fibers associated with Ring (Path) 1 and the connection of optical fiber associated with Ring (Path) 1 fiber from NE2 to NE1.

.................................................................................................................................................................................................................................

9-52 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-3.1: Discontinue Metropolis

®

DMX node from

UPSR

3

4

.................................................................................................................................................................................................

Connect the fiber to NE1 M1 transmit ( Figure 9-2, “Discontinuing a node example”

(p. 9-52) B). At NE2 M2 receive, measure the optical power level in the receive

direction, attenuate if necessary, and connect the fiber.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Removal of wrong fiber connections will result in a service interruption.

Ensure that you remove only the fiber connections for the optical span being discontinued.

5

6

Important! When the optical fibers are disconnected, the system performs an automatic protection switch and subsequent transmission hits (less than 60 ms) will occur.

Remove the optical fiber from NE2 M2 transmit to NE5 M1 receive and the optical

fiber from NE5 M2 transmit to NE1 M1 receive. ( Figure 9-2, “Discontinuing a node example” (p. 9-52)

Figure B).

Result:

Automatic path protection switching will occur.

.................................................................................................................................................................................................

Connect the fiber to NE2 M2 transmit ( Figure 9-2, “Discontinuing a node example”

(p. 9-52)

Figure C). At NE1 M1 receive, measure the optical power level in the receive direction, attenuate if necessary, and connect the fiber.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

To verify that no alarms are present in the network, select

Fault

→

NE Alarm List

from the System View menu at each node.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-53

Network configuration procedures

7

Procedure 9-3.1: Discontinue Metropolis

®

DMX node from

UPSR

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Is the removed shelf to be powered down?

If...

Yes

No

Then...

Power down the shelf per local procedures and remove circuit packs (if required), then proceed to

Step 14 .

Continue with

Step 8 .

8

9

10

11

12

13

.................................................................................................................................................................................................

If required to prevent alarms, provision the system Timing Mode parameter as Free

Running using

Configuration

→

Timing/Sync

.

Reference:

(p. 6-16)

Procedure 6-5: “Network Element synchronization provisioning”

.................................................................................................................................................................................................

If required to prevent alarms, disable the DCC terminations on the ports removed from service using

Configuration

→

DCC Terminations

.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

If the Main ports are being removed from service, loop back the Main OC-n ports.

Reference:

Procedure 14-6: “Connect OLIU optical loopbacks” (p. 14-56)

.................................................................................................................................................................................................

If the shelf is being removed from service, use

View

→

Cross-Connections

to verify that there are no cross-connections on the shelf. If required, delete any existing cross-connections using

Configuration

→

Cross-Connections

.

.................................................................................................................................................................................................

Update the internal equipment list by either pressing the

UPD/INIT

push-button on the

SYSCTL circuit pack or using

Configuration

→

Update System

→

Update All

.

.................................................................................................................................................................................................

To verify that no alarms are present, click the

Alarm List

button or select

Fault

→

NE

Alarm List

.

.................................................................................................................................................................................................................................

9-54 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-3.1: Discontinue Metropolis

®

DMX node from

UPSR

14

.................................................................................................................................................................................................

The Metropolis

®

ring (UPSR).

DMX node is now removed from the unidirectional path switched

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-55

Network configuration procedures

Procedure 9-3.2: Discontinue Metropolis

®

DMX node from

BLSR

.................................................................................................................................................................................................................................

Important! This is not a standalone procedure. Perform this procedure only as directed by

Procedure 9-3: “Discontinue Metropolis

®

DMX node from network”

(p. 9-48) .

Step

1

Important! Verify that the work instructions specify whether automatic ring discovery is enabled or disabled on the existing ring.

The Metropolis

®

DMX node (shelf) may be using the OLIU circuit packs in the

Main slot pair or a Function/Growth slot pair to interface with a BLSR.

Complete the following steps to discontinue a Metropolis

®

DMX node from a BLSR.

.................................................................................................................................................................................................

Important! The example assumes that the BLSR network is established using the

Main slot pairs of Metropolis

®

DMX nodes. However, a Function/Growth slots pair may also be used to interface with an OC-48 BLSR.

Identify the node to be discontinued, the adjacent West node, and the adjacent East node. (Refer to the following figure.)

Line

1W

West

Node

Line

1E

Line

1W

Node

To Be

Discontinued

Line

1E

Line

1W

East

Node

Line

1E

Line

1E

Other

Node(s)

Line

1W

Line

1E

Other

Node(s)

Line

1W

MA-DMX-387

Legend

:

Line 1W: Line 1W (West port) is the port in slot 1 of the 2F BLSR protection group

(for example, Main-1 or FN-A-1).

Line 1E: Line 1E (East port) is the port in slot 2 of the 2F BLSR protection group (for example, Main-2 or FN-A-2).

.................................................................................................................................................................................................................................

9-56 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-3.2: Discontinue Metropolis

®

DMX node from

BLSR

2

.................................................................................................................................................................................................

Important! The Force to Protection, Ring switch may cause transmission hits (less than 60 ms).

Perform the following: (Refer to the following figure.)

•

At the West Node, from the System View menu select

Fault

→

Protection Switch

.

Select the required 2F BLSR protection group (according to the work instructions) and perform a protection switch in the

East

direction with switch type

Force to

Protection, Ring

. Click

Apply

. A dialog box appears asking you to confirm executing this command. Click

Yes

. After the protection switch completes, click

Close

.

•

At the East Node, from the System View menu select

Fault

→

Protection Switch

.

Select the required 2F BLSR protection group (according to the work instructions) and perform a protection switch in the

West

direction with switch type

Force to

Protection, Ring

. Click

Apply

. A dialog box appears asking you to confirm executing this command. Click

Yes

. After the protection switch completes, click

Close

.

1W

1E

1W

1E

1W

1E

West

Node

Node

To Be

Discontinued

East

Node

Line

1E

Other

Node(s)

Line

1W

Line

1E

Other

Node(s)

Line

1W

MA-DMX-388

Legend

:

Line 1W: Line 1W (West port) is the port in slot 1 of the 2F BLSR protection group

(for example, Main-1 or FN-A-1).

Line 1E: Line 1E (East port) is the port in slot 2 of the 2F BLSR protection group (for example, Main-2 or FN-A-2).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-57

Network configuration procedures Procedure 9-3.2: Discontinue Metropolis

®

DMX node from

BLSR

3

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Removal of wrong fiber connections will result in a service interruption.

Ensure that you remove only the fiber connections for the optical span being discontinued.

Perform the following: (Refer to the following figure.)

•

At the adjacent West Node, disconnect the optical fibers connected to the node to be discontinued.

•

At the node to be discontinued, disconnect the optical fibers connected to the adjacent East Node and West Node.

•

At the adjacent East Node disconnect the optical fibers connected to the node to be discontinued.

Line

1W

West

Node

Line

1E

Line

1W

Node

To Be

Discontinued

Line

1E

Line

1W

East

Node

Line

1E

Line

1E

Other

Node(s)

Line

1W

Line

1E

Other

Node(s)

Line

1W

MA-DMX-389

Legend

:

Line 1W: Line 1W (West port) is the port in slot 1 of the 2F BLSR protection group

(for example, Main-1 or FN-A-1).

Line 1E: Line 1E (East port) is the port in slot 2 of the 2F BLSR protection group (for example, Main-2 or FN-A-2).

4

.................................................................................................................................................................................................

Perform the following: (Refer to the following figure.)

•

At the West and East nodes, connect the transmit fiber.

•

At the West and East nodes, measure the optical power level in the receive direction and attenuate if necessary.

•

At the West and East nodes, connect the receive fiber.

.................................................................................................................................................................................................................................

9-58 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-3.2: Discontinue Metropolis

®

DMX node from

BLSR

Refer to

Procedure 14-4: “Perform connection and verification of optical facility”

(p. 14-44) .

Line

1W

West

Node

Line

1E

Line

1W

Node

To Be

Discontinued

Line

1E

Line

1W

East

Node

Line

1E

Line

1E

Other

Node(s)

Line

1W

Line

1E

Other

Node(s)

Line

1W

MA-DMX-390

Legend

:

Line 1W: Line 1W (West port) is the port in slot 1 of the 2F BLSR protection group

(for example, Main-1 or FN-A-1).

Line 1E: Line 1E (East port) is the port in slot 2 of the 2F BLSR protection group (for example, Main-2 or FN-A-2).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-59

Network configuration procedures Procedure 9-3.2: Discontinue Metropolis

®

DMX node from

BLSR

.................................................................................................................................................................................................

5

If automatic ring discovery is...

enabled, disabled (manual ring discovery),

Then...

Important! As the ring is connected, nodes automatically communicate with each other using the data communications channel (DCC) and build a ring map. If successful, automatic ring discovery builds a ring map at each node and the

Ring

Discovery in Progress condition clears. If unsuccessful, the ring map is not complete and alarms are reported.

Perform the following:

1. Wait until the

Ring Discovery in

Progress condition clears.

If other alarms/conditions are reported, refer to the Metropolis

®

DMX Access Multiplexer

Alarm Messages and Trouble Clearing

Guide, 365-372-302 and clear the alarms/conditions.

2. Proceed to

Step 7 .

Important! The manual ring map must be updated manually at each node in the ring.

At each of the remaining nodes in the ring, edit the manual ring map to remove the discontinued node, but do NOT activate the updated manual ring maps. Then continue with

Step 6

Refer to

Procedure 9-4: “Provision manual ring map” (p. 9-63) .

6

.................................................................................................................................................................................................

If Automatic Ring Discovery is disabled at the remaining nodes in the ring, activate the manual ring maps.

Select

Configuration

→

Activate Manual Ring Map

. Select the required Ring ID and click

Select

.

.................................................................................................................................................................................................................................

9-60 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-3.2: Discontinue Metropolis

®

DMX node from

BLSR

7

8

9

10

Result:

A dialog box appears asking you to confirm activating the manual ring map. Click

OK

. The inactive manual ring map is now activated.

.................................................................................................................................................................................................

Perform the following:

•

At the West Node, from the System View menu select

Fault

→

Protection Switch

.

Select the required 2F BLSR protection group (according to the work instructions) and clear the protection switch in the

East

direction with switch type

Clear

. Click

Apply

. A dialog box appears asking you to confirm executing this command. Click

Yes

. After the protection switch completes, click

Close

.

•

At the East Node, from the System View menu select

Fault

→

Protection Switch

.

Select the required 2F BLSR protection group (according to the work instructions) and clear the protection switch in the

West

direction with switch type

Clear

. Click

Apply

. A dialog box appears asking you to confirm executing this command. Click

Yes

. After the protection switch completes, click

Close

.

Important! The Clear switch may cause transmission hits (less than 60 ms). Wait for alarms to clear.

Result:

The node to be discontinued is now removed from the ring.

.................................................................................................................................................................................................

From the System View menu at the East and West nodes,

1. Select

View

→

Protection

.

2. Select the required 2F BLSR protection group and click

Select

.

3. Observe the Ring Node APS (Automatic Protection Switch) State, East Switch

Request State, West Switch Request State, East Channel State, and West Channel

State parameters. Verify that the protection switches have cleared and click

Close

.

.................................................................................................................................................................................................

To verify that no alarms are present in the network, select

Fault

→

NE Alarm List

from the System View menu at each node.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Is the removed shelf to be powered down?

If...

Yes,

No,

Then...

Power down the shelf per local procedures then proceed to

Step 17 .

Continue with

Step 11 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-61

Network configuration procedures Procedure 9-3.2: Discontinue Metropolis

®

DMX node from

BLSR

11

12

13

14

15

16

17

.................................................................................................................................................................................................

If required to prevent alarms, provision the system Timing Mode parameter as Free

Running using

Configuration

→

Timing/Sync

.

Reference:

(p. 6-16)

Procedure 6-5: “Network Element synchronization provisioning”

.................................................................................................................................................................................................

If required to prevent alarms, disable the DCC terminations on the ports removed from service using

Configuration

→

DCC Terminations

.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

If the Main ports are being removed from service, loop back the Main OC-n ports.

Reference:

Procedure 14-6: “Connect OLIU optical loopbacks” (p. 14-56)

.................................................................................................................................................................................................

If the shelf is being removed from service, use

View

→

Cross-Connections

to verify that there are no cross-connections on the shelf. If required, remove any existing cross-connection using

Configuration

→

Cross-Connections

.

.................................................................................................................................................................................................

Update the internal equipment list by either pressing the

UPD/INIT

push-button on the

SYSCTL circuit pack or using

Configuration

→

Update System

→

Update All

.

.................................................................................................................................................................................................

To verify that no alarms are present, click the

Alarm List

button or select

Fault

→

NE

Alarm List

.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

The Metropolis

®

DMX node is now removed from the bidirectional line switched ring

(BLSR).

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

9-62 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

Procedure 9-4: Provision manual ring map

.................................................................................................................................................................................................................................

Overview

Use this procedure to perform the following at a node in a 2-fiber bidirectional line switched ring (BLSR):

•

Establish a new manual ring map

•

Add a node(s) to an existing manual ring map

•

Delete a node(s) from an existing manual ring map.

Important! If deleting a node(s) from an existing ring map, then the circuits that add/drop to the deleted node(s) must be deleted. Refer to

Chapter 10, “TDM service provisioning procedures”

and

Chapter 11, “Ethernet/Data network provisioning procedures” .

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 9-2)

in this chapter

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Verify that the work instructions specify the 2F BLSR protection group (port

Application parameter must be provisioned 2F BLSR), Ring ID, and node ID(s).

Step

Complete the following steps to provision the manual ring map at a node(s) in a

2-fiber bidirectional line switched ring (BLSR).

1

.................................................................................................................................................................................................

If the network element is equipped with...

Release 3.0 or later software,

Then...

verify that Automatic Ring Discovery is disabled by selecting

View

→

Protection

. Click on the required 2F BLSR protection groupand

Select

.

Then click on the Provisionable Parameters tab and observe the Automatic Ring Discovery parameter. Continue with

Step 2 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-63

Network configuration procedures Procedure 9-4: Provision manual ring map

If the network element is equipped with...

Release 2.1 or earlier software,

Then...

Proceed to

Step 3 .

2

.................................................................................................................................................................................................

Is the Automatic Ring Discovery parameter Enabled or Disabled?

If Automatic Ring Discovery is...

Disabled,

Enabled,

Then...

Click

Close

and continue with

Step 3 .

Click

Close

and perform the following:

1. Select

Configuration

→

Equipment

.

2. Select the

Ptn Grp

tab and the required 2F BLSR protection group. Then click

Select

.

3. Provision the Automatic Ring Discovery parameter to Disabled, then click

Apply

and

Close

.

3

.................................................................................................................................................................................................

Select

Configuration

→

Configure Manual Ring Map

.

Result:

The Configure Manual Ring Map window opens.

.................................................................................................................................................................................................

4 If...

Then...

Establishing a new manual ring map, Continue with

Step 5 .

Adding a node(s) to an existing manual ring map, Proceed to

Step 10 .

Deleting a node(s) from an existing manual ring map,

Proceed to

Step 13 .

5

.................................................................................................................................................................................................

Click on the required Ring ID and

Select

.

.................................................................................................................................................................................................................................

9-64 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-4: Provision manual ring map

Result:

A dialog box appears stating that there is no existing manual ring map, you will be configuring a new manual ring map. Click

OK

. The Configure Manual

Ring window opens showing the local node and an unnamed node. (Refer to following figure.)

6

.................................................................................................................................................................................................

Important! The local node appears on the right side of the Configure Manual

Ring screen. This shows the NE Name (DMX) and Node ID (0). The Node ID of the local node may need to be changed to comply with the work instructions.

If required, right click on the local node and change the Node ID according to the work instructions. Click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

, and the modified node information appears on the Configure Manual

Ring screen.

7

.................................................................................................................................................................................................

Important! The NE Name and Node ID of the unnamed node must be modified to the NE Name and node ID of the node that is connected to the East port (for example, Main-2) of the Local node per the work instructions.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-65

Network configuration procedures Procedure 9-4: Provision manual ring map

8

9

Right click on the unnamed node (UNNAMED 1) and change the NE Name and Node

ID according to the work instructions. Click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

, and the modified node information appears on the Configure Manual

Ring screen.

.................................................................................................................................................................................................

Important! In the manual ring map, nodes are added in the clockwise (East) direction only from the node that is selected.

To add another node, click on the required node and click

Add Node

. Enter the NE

Name and Node ID of the next node in the East direction (clockwise) according to the work instructions. Click

OK

.

Result:

A dialog box appears asking you to confirm adding a new node to the manual ring map. Click

Yes

, and the new node appears on the Configure Manual

Ring screen.

.................................................................................................................................................................................................

Are additional nodes to be added?

If...

Yes,

No,

Then...

Important! A maximum of 16 nodes can be added to the manual ring map.

As required per the work instructions, repeat

Step

8

to add additional nodes to the manual ring map.

Then proceed to

Step 16 .

Proceed to

Step 16 .

10

11

.................................................................................................................................................................................................

Click on the required Ring ID and

Select

.

Result:

The Configure Manual Ring window opens.

.................................................................................................................................................................................................

Important! The local node appears at the top of the Configure Manual Ring screen. In the manual ring map, nodes are added in the clockwise (East) direction only from the node that is selected.

Select the required node and then click

Add Node

. Enter the NE Name and Node ID of the new node according to the work instructions. Click

OK

.

.................................................................................................................................................................................................................................

9-66 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-4: Provision manual ring map

12

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

, and the new node appears on the Configure Manual Ring screen.

.................................................................................................................................................................................................

Are additional nodes to be added?

If...

Yes,

No,

Then...

Important! A maximum of 16 nodes can be added to the manual ring map.

As required per the work instructions, repeat

Step

11

to add additional nodes to the manual ring map. Then proceed to

Step 16 .

Proceed to

Step 16 .

13

14

15

.................................................................................................................................................................................................

Click on the required Ring ID and

Select

.

Result:

The Configure Manual Ring window opens.

.................................................................................................................................................................................................

Important! The local node appears at the top of the Configure Manual Ring screen.

Click on the node to be deleted and then click

Remove Node

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and the node is removed from the Configure Manual Ring screen.

.................................................................................................................................................................................................

Are additional nodes to be deleted?

If...

Yes,

No,

Then...

As required per the work instructions, repeat

Step

14

to delete additional nodes from the manual ring map. Then proceed to

Step 16 .

Proceed to

Step 16 .

16

.................................................................................................................................................................................................

Click

Apply

.

17

.................................................................................................................................................................................................

Select

Configuration

→

Activate Manual Ring Map

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-67

Network configuration procedures Procedure 9-4: Provision manual ring map

18

19

Result:

The Activate Manual Ring Map window opens.

.................................................................................................................................................................................................

Select the required Ring ID and click

Select

.

Result:

A dialog box appears asking you to confirm activating the manual ring map. Click

OK

. The inactive manual ring map is now activated.

.................................................................................................................................................................................................

Select

View

→

Rings

→

Ring Map

. Select the required Ring ID and click

Select

.

Verify that the manual ring map was provisioned correctly and click

Close

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

9-68 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

Procedure 9-5: Establish low-speed 1+1 linear optical extension

.................................................................................................................................................................................................................................

Overview

Use this procedure to establish a low-speed 1+1 linear OC-3/12/48 optical extension.

Important! This procedure assumes that the low-speed 1+1 optical linear extension is established by interconnecting a OC-3/12/48 Function/Growth slot pair at the host Metropolis

®

DMX to one of the following:

•

Metropolis

®

DMX using OC-12/48 Main slot pair.

Figure 9-3, “1+1 extension example 1” (p. 9-74)

shows a Metropolis

®

DMX at Node 1 with low-speed

OC-12/48 OLIUs in Function slot pair D1/D2 connected to Node 2 Main slot pair. If connecting to the Main slot pair of another Metropolis

®

DMX, refer to

Procedure 9-1: “Establish high-speed end-to-end Metropolis

®

DMX system”

(p. 9-3) , as required, when performing this procedure.

•

Metropolis

®

DMX using OC-3/12/48 Function/Growth slot pair.

Figure 9-4,

“1+1 extension example 2” (p. 9-74)

shows a Metropolis

®

DMX at Node 6 with low-speed OC-3/12/48 OLIUs in Function slot pair D1/D2 connected to

Node 5 low-speed D1/D2 Function slot pair.

The Function/Growth slot pair at the host Metropolis

®

connected to the following:

DMX may also be

•

Metropolis

®

DMXtend using OC-3/12/48 Main slot pair or an OC-3/12/48

Function/Growth slot pair. If connecting to a Metropolis

®

DMXtend, refer to the Metropolis

®

DMXtend Access Multiplexer User Operations Guide,

365-372-325, as required, when performing this procedure.

•

Metropolis

®

DMXplore using OC-3/OC-12 Main slot pair. If connecting to a

Metropolis

®

DMXplore, refer to the Metropolis

®

DMXplore Access Multiplexer

User Operations Guide, 365-372-332, as required, when performing this procedure.

Ignore all alarms until the procedure is complete.

Privilege level

You must log in as either a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 9-2)

and

“Required equipment” (p. 9-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-69

Network configuration procedures Procedure 9-5: Establish low-speed 1+1 linear optical extension

3. Verify that you have the necessary work instructions detailing the slots, circuit packs, ports, and network element parameters to be used for this procedure.

4. Verify that the network containing the host Metropolis

®

and operating properly.

DMX node is established

5. Verify that the far-end node being connected to the host Metropolis

®

DMX node has been equipped and is operating properly.

Step

1

2

3

4

Complete the following steps to establish a low-speed 1+1 optical extension.

.................................................................................................................................................................................................

Determine the network configuration using the work instructions and office records.

Refer to the examples in

Figure 9-3, “1+1 extension example 1” (p. 9-74)

and

Figure

9-4, “1+1 extension example 2” (p. 9-74) .

.................................................................................................................................................................................................

Important! Two or more shelves in the same network cannot have the same TID.

Using the work instructions and office records, verify that no duplicate TID settings exist between the host Metropolis

®

DMX and the far-end node. If duplicate TID settings exist, determine new settings and at each site with duplicate TID settings, select

Administration

→

Set TID

from the System View menu, and enter new TID settings.

Reference:

Procedure 7-11: “Set/change system TID” (p. 7-38)

.................................................................................................................................................................................................

If required, modify the network service access point (NSAP) address and/or enable

Level 2 routing capabilities at the host Metropolis

®

DMX and the far-end node.

Reference:

Procedure 7-13: “Provision network layer 3 parameters” (p. 7-40)

.................................................................................................................................................................................................

At the host Metropolis

®

DMX node, verify/install OLIU circuit packs and/or pluggable transmission modules in the Function Group slot pair (A, B, C, D, or G) being used for access according to the work instructions.

Important! If the work instructions or office records do not specify OLIU types, refer to the Metropolis

®

DMX Access Multiplexer Applications and Planning Guide,

365-372-300, for a description of OLIU circuit packs/pluggable transmission modules and applications. Optical line power measurements and/or office records must be used to verify that the span length can be supported.

The connections to the Metropolis

®

DMX shelf must be in two slots in the same

Function/Growth group (for example: A1 and A2).

.................................................................................................................................................................................................................................

9-70 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-5: Establish low-speed 1+1 linear optical extension

5

6

7

Reference:

•

Procedure 4-3: “Install OLIU circuit packs in Function slots” (p. 4-14)

•

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62)

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled for ports, an inconsistent DCC values alarm is reported when the ports are looped back.

If required at the host Metropolis

®

DMX node, clear the inconsistent DCC values alarm by disabling OSI over DCC for the required ports. From the System View menu, select

Configuration

→

DCC Terminations

and disable

OSI Over DCC

for the required DCC ports.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

Important! The port Application parameter must be provisioned 1+1 at both ends of the system, Optimized 1+1 at both ends of the system, or Bidirectional 1+1 at both ends of the system. Bidirectional 1+1 is only required when interworking with other vendor’s equipment that does not bridge DCC traffic on the active and standby lines. (Metropolis

®

DMX supports bridging DCC traffic on the active and standby lines.)

Metropolis

®

DMXtend does not support Optimized 1+1.

Metropolis

®

DMXplore does not support Optimized 1+1 or Bidirectional 1+1.

From the System View menu at the host Metropolis

®

DMX node, select

Configuration

→

Equipment

. One at a time, select the required ports, and provision the required port parameters according to the work instructions.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

From the System View menu at the host Metropolis

®

DMX node, select

Configuration

→

Equipment

, if not already open. Select the system (AID=system), then click

Select

at the bottom of the window.

If required, provision the 1+1 Protection Priority (1+1 applications only) and Wait To

Rename (Optimized 1+1 applications only) parameters. Click

Apply

if changes were made, then click

Yes

to the warning message to make your changes. Click

Close

to exit.

8

.................................................................................................................................................................................................

At the host Metropolis

®

DMX node, verify that the low-speed OC-n ports were provisioned correctly using the

View

→

Equipment

command.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-71

Network configuration procedures Procedure 9-5: Establish low-speed 1+1 linear optical extension

9

10

11

12

.................................................................................................................................................................................................

Important! The protection group Revertive Mode and Wait to Restore parameters apply to 1+1 applications and Bidirectional 1+1 applications only.

If the Revertive Mode parameter is disabled, the Wait to Restore parameter is not provisionable.

If required, from the System View menu,

1. Select

Configuration

→

Equipment

.

2. Select the

Ptn Grp

tab.

3. Click on the required 1+1 protection group and

Select

.

4. Provision the required protection group parameters according to the work instructions, then click

Apply

and

Close

. If no changes were made, click

Close

and go to the next step.

.................................................................................................................................................................................................

If required, from the System View menu,

1. Select

View

→

Protection

.

2. Select the required 1+1 protection group and click

Select

.

3. Verify that the protection group parameters were provisioned correctly. Then click

Close

.

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled, the LAPD Role parameter must be provisioned differently at each end of an optical span. For example, if the LAPD

Role parameter is provisioned user-side at one end of an optical span, then the

LAPD Role parameter must be provisioned network-side at the other end of the optical span.

From the System View menu, select

Configuration

→

DCC Terminations

and provision the DCC terminations for the required DCC ports according to the work instructions.

Result:

If OSI over DCC is enabled, an inconsistent DCC values alarm will occur if the OC-n ports are looped back.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

From the System View menu at the host Metropolis

®

DMX node, select

View

→

DCC

Terminations

and verify that the DCC terminations were provisioned correctly.

.................................................................................................................................................................................................................................

9-72 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-5: Establish low-speed 1+1 linear optical extension

13

.................................................................................................................................................................................................

At the far-end node that is connecting to the host Metropolis

®

DMX node, provision the required Main/Function/Growth ports, DCC terminations, synchronization, and remote NE status functions according to the work instructions.

If the far-end node is a...

Metropolis

®

DMX

Function/Growth Slot pair,

Then...

Repeat

Step 4

through

Step 12

to provision the required Function/Growth ports and DCC terminations.

Metropolis

®

DMX Main Slot pair, Refer to

Procedure 9-1: “Establish high-speed end-to-end Metropolis

®

DMX system” (p. 9-3)

to provision the required Main ports, DCC terminations, synchronization, and remote NE status functions.

Metropolis

®

DMXtend or

Metropolis

®

DMXplore,

Refer to the other product’s documentation to provision the required Main/Function/Growth ports, DCC terminations, synchronization, and remote NE status functions.

14

.................................................................................................................................................................................................

Important! The circuit pack in Function/Growth slot 1 of the host Metropolis

®

DMX node must be connected to the far-end circuit pack in Main/Function/Growth slot 1, and the circuit pack in Function/Growth slot 2 of the host Metropolis

®

DMX node must be connected to the far-end circuit pack in Main/Function/Growth slot 2.

Connect the optical fibers and verify the integrity of the optical span being installed.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

15

.................................................................................................................................................................................................

Perform end-to-end optical line test.

Reference:

•

Procedure 14-7: “Perform end-to-end optical line test on Main OLIUs”

(p. 14-61)

•

Procedure 14-8: “Perform end-to-end optical line test on Function OLIUs”

(p. 14-64)

16

.................................................................................................................................................................................................

At each node in the 1+1 linear network, click the

Alarm List

button or select

Fault

→

NE Alarm List

from the System View menu and verify that no alarms are present.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-73

Network configuration procedures

17

Procedure 9-5: Establish low-speed 1+1 linear optical extension

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! Establishing service requires that the proper slots in each terminating node be properly equipped with the correct circuit pack(s) for the type of service being established. It also requires numerous cross-connections in each of the nodes representing the path of the required service. Additionally, transmission tests should be performed to verify the continuity and quality of the established circuit.

The optical linear extension is now ready for initial service to be established.

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

E

N D O F

S

T E P S

Figure 9-3 1+1 extension example 1

Node 1

DMX

M 1 M 2

A/B/C D1 D2

Port Application = 1+1

LAPD Role = NS

G

Low Speed 1+1 optical extension

M 1

Node 2

M 2

Port Application = 1+1

LAPD Role = US

High Speed 1+1 optical extension

MA-DMX-377

.................................................................................................................................................................................................................................

9-74 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-5: Establish low-speed 1+1 linear optical extension

Figure 9-4 1+1 extension example 2

IN

OUT

M 2

Node 5

M 1

OUT

IN

IN

OUT

M 2

Node 4

M 1

OUT

IN

A B

C

D1 D2

G

Low Speed 1+1 optical extension

Port Application = 1+1

LAPD Role = NS

A B

C

D1 D2

G

M 2

Node 7

DMX

M 1

A/B/C

D1 D2

G

M 1

Node 6

DMX

M 2

A/B/C

D1 D2

G

Low Speed 1+1 optical extension

Port Application = 1+1

LAPD Role = US

MA-DMX-378

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-75

Network configuration procedures

Procedure 9-6: Establish single-homed network configurations

.................................................................................................................................................................................................................................

Overview

Use this procedure to establish single-homed OC-3/12/48 access to host Metropolis

®

DMX nodes in a UPSR backbone ring.

Figure 9-5, “Single-homed configuration example” (p. 9-83)

shows an example network configuration with single-homed access to a UPSR backbone ring. This allows the single-homed ring to be completed through the UPSR backbone ring. The UPSR backbone ring transports/drops traffic from the single-homed ring. The end-of-path network elements that drop the traffic perform path protection switching.

This procedure assumes that single-homed access is established by interconnecting

Metropolis

®

DMX nodes using a Function/Growth slot pair at the host Metropolis

®

DMX node and the OC-12/OC-48 Main slot pair of the Metropolis

®

DMX nodes in the single-homed ring. However, the Function/Growth slot pair of the host Metropolis

®

DMX node may also be connected in a single-homed ring with the following:

•

Metropolis

®

DMXtend using OC-3/12 Main slot pair or OC-3/12/48

Function/Growth slot pair. If connecting to a Metropolis

®

DMXtend Access

Multiplexer User Operations Guide, 365-372-325, as required, when performing this procedure.

•

Metropolis

®

DMXplore using OC-3/OC-12 Main slot pair. If connecting to a

Metropolis

®

DMXplore, refer to the Metropolis

®

DMXplore Access Multiplexer

User Operations Guide, 365-372-332, as required, when performing this procedure.

•

Metropolis

®

DMX using OC-3/12/48 Function/Growth slot pair. If connecting to the Function/Growth slots of another Metropolis

®

DMX, refer to

Procedure 9-9:

“Establish subtending low-speed UPSR/BLSR” (p. 9-98) , as required, when

performing this procedure.

Important! Single-homed access is supported at the host Metropolis

®

DMX nodes using UPSR port applications and UNSWITCHED cross-connection channel applications. This configuration is essentially the same as establishing a subtending

UPSR ring ( Procedure 9-9: “Establish subtending low-speed UPSR/BLSR”

(p. 9-98) ), except for the cross-connection applications.

Ignore all alarms until procedure is complete.

Privilege level

You must log in as either a Privileged user to complete this procedure.

.................................................................................................................................................................................................................................

9-76 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-6: Establish single-homed network configurations

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 9-2) , the following

equipment is also required:

•

Optical power meter

•

Lightguide jumpers

•

Lightguide BuildOuts (LBOs)

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 9-2)

and

“Required equipment” (p. 9-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

3. Verify that you have the necessary work instructions detailing the slots, circuit packs, ports, and network element parameters to be used for this procedure.

4. Verify that the UPSR backbone ring containing the host Metropolis

®

DMX nodes is established and operating properly using the procedures in this manual.

5. Verify that all systems being connected to the host Metropolis

®

been equipped and operating properly.

DMX nodes have

Step

1

Complete the following steps to establish single-homed OC-3/12/48 access to host

Metropolis

®

DMX nodes in a UPSR backbone ring.

.................................................................................................................................................................................................

From your work instructions, determine the network configuration. Refer to

Figure 9-5,

“Single-homed configuration example” (p. 9-83)

for an example. If possible, make a sketch of the existing UPSR backbone ring and the required single-homed connections.

If required, select the

Administration

→

OSI Neighbor Map

command at the host

Metropolis

®

DMX node and note the NEs connected to Main 1 and Main 2.

Access each NE identified, select the

Administration

→

OSI Neighbor Map

command, and note the NEs connected to Main 1 and Main 2.

Repeat this step until the UPSR backbone ring can be sketched.

.................................................................................................................................................................................................

2

Important! Two or more shelves in the same network cannot have the same TID.

Using the work instructions and office records, verify that no duplicate TID settings exist between the nodes in the existing UPSR backbone ring and the single-homed ring. If duplicate TID settings exist, determine new settings and at each site with

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-77

Network configuration procedures

3

4

5

6

Procedure 9-6: Establish single-homed network configurations duplicate TID settings, select

Administration

→

Set TID

from the System View menu, and enter new TID settings.

Reference:

Procedure 7-11: “Set/change system TID” (p. 7-38)

.................................................................................................................................................................................................

If required, modify the network service access point (NSAP) address and/or enable

Level 2 routing capabilities at the host Metropolis

®

DMX node and the nodes in the single-homed ring.

Reference:

Procedure 7-13: “Provision network layer 3 parameters” (p. 7-40)

.................................................................................................................................................................................................

At the host Metropolis

®

DMX node (Nodes 2 and 5 in

Figure 9-5, “Single-homed configuration example” (p. 9-83) ), verify/install OLIU circuit packs and/or pluggable

transmission modules in the Function/Growth Group slot pair (A1 and A2, B1 and B2,

C1 and C2, D1 and D2, or G1 and G2) being used for access according to the work instructions.

Important! If the work instructions or office records do not specify OLIU types, refer to Metropolis

®

DMX Access Multiplexer Applications and Planning Guide,

365-372-300, for a description of OLIU circuit packs, pluggable transmission modules, and applications. Optical line power measurements and/or office records must be used to verify that the span length can be supported.

The single-homed ring connections to the host Metropolis

®

DMX node must be in two slots in the same Function/Growth group (for example: D1 and D2).

Reference:

•

Procedure 4-3: “Install OLIU circuit packs in Function slots” (p. 4-14)

•

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62)

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled for ports, an inconsistent DCC values alarm is reported when the ports are looped back.

If required at the host Metropolis

®

DMX node, clear the inconsistent DCC values alarm by disabling OSI over DCC for the required ports. From the System View menu, select

Configuration

→

DCC Terminations

and disable

OSI Over DCC

for the required DCC ports.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

Important! For single-homed access, provision the Application parameter to UPSR for the low-speed OC-n port pairs being connected.

.................................................................................................................................................................................................................................

9-78 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

7

8

9

10

Procedure 9-6: Establish single-homed network configurations

From the System View menu at the Metropolis

®

DMX host node, select

Configuration

→

Equipment

, select the required low-speed OC-n ports, and provision the port parameters as required from your work instruction.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

At the host Metropolis

®

DMX node, verify that the low-speed OC-n ports were provisioned correctly using the

View

→

Equipment

command.

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled, the LAPD Role parameter must be provisioned differently at each end of an optical span. For example, if the LAPD

Role parameter is provisioned user-side at one end of an optical span, then the

LAPD Role parameter must be provisioned network-side at the other end of the optical span.

From the System View menu, select

Configuration

→

DCC Terminations

and provision the DCC terminations for the required DCC ports according to the work instructions.

Result:

If OSI over DCC is enabled, an inconsistent DCC values alarm will occur if the OC-n ports are looped back.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

From the System View menu at the host Metropolis

®

DMX node, select

View

→

DCC

Terminations

and verify that the DCC terminations were provisioned correctly.

.................................................................................................................................................................................................

At each node in the single-homed ring, provision the required Main/Function/Growth ports, DCC terminations, synchronization, and remote NE status functions according to the work instructions.

If the node is a...

Metropolis

®

DMX and the Main ports are used,

Then...

Refer to

Procedure 9-1: “Establish high-speed end-to-end Metropolis

®

DMX system” (p. 9-3)

to provision and verify the required Main ports,

DCC terminations, synchronization, and remote

NE status functions.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-79

Network configuration procedures

If the node is a...

Metropolis

®

DMX and the

Function/Growth ports are used,

Metropolis

Metropolis

®

®

DMXtend or

DMXplore,

Procedure 9-6: Establish single-homed network configurations

Then...

Refer to

Procedure 9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98)

to provision and verify the required Function/Growth ports and DCC terminations.

Refer to the other product’s documentation to provision and verify the required ports, DCC terminations, synchronization, and remote NE status functions.

11

.................................................................................................................................................................................................

Beginning at the host Metropolis

®

DMX node, connect the fibers between the required low-speed OC-n port in Function/Growth slot 1 and the required OC-n port in

Main/Function/Growth slot 1 at the adjacent node and verify the integrity of the optical span being established.

Reference:

Figure 9-5, “Single-homed configuration example” (p. 9-83)

shows the following single-homed connections at the host Metropolis

®

DMX node:

Metropolis

®

DMX

Function/Growth slot

(A,B,C,D,G)1 (Node 2 and Node 5)

Metropolis

®

DMX

Function/Growth slot

(A,B,C,D,G)2 (Node 2 and Node 5)

Connects to the M1 OLIU at the adjacent node (Node 7 and

Node 8)

Connects to the M2 OLIU at the adjacent node (Node 7 and

Node 8)

12

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Perform end-to-end optical line test on the span being established.

Reference:

•

Procedure 14-7: “Perform end-to-end optical line test on Main OLIUs”

(p. 14-61)

•

Procedure 14-8: “Perform end-to-end optical line test on Function OLIUs”

(p. 14-64)

.................................................................................................................................................................................................................................

9-80 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-6: Establish single-homed network configurations

13

.................................................................................................................................................................................................

Continue around the single-homed ring in the same direction until all nodes are connected.

If the node is a...

Metropolis

®

DMX and the Main ports are used,

Metropolis

®

DMX and the

Function/Growth ports are used,

Metropolis

®

Metropolis

®

DMXtend or

DMXplore,

Then...

Refer to

Procedure 9-1: “Establish high-speed end-to-end Metropolis

®

DMX system” (p. 9-3)

to connect and test the optical span.

Refer to

Procedure 9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98)

to connect and test the optical span.

Refer to the other product’s documentation to connect and test the optical span.

14

15

16

.................................................................................................................................................................................................

At each node in the single-homed ring, click the

Alarm List

button or select

Fault

→

NE Alarm List

from the System View menu and verify that no alarms are present.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

If required, repeat this procedure from

Step 1

to establish single-homed access at another host Metropolis

®

DMX node in the UPSR backbone ring.

.................................................................................................................................................................................................

Important! Establishing service requires that the proper slots in each terminating node be properly equipped with the correct circuit pack(s) for the type of service being established. It also requires numerous cross-connections in each of the nodes representing the path of the required service. Additionally, transmission tests should be performed to verify the continuity and quality of the established circuit.

The single-homed access network is now ready for initial service to be established.

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-81

Network configuration procedures Procedure 9-6: Establish single-homed network configurations

Configuration

The example in

Figure 9-5, “Single-homed configuration example” (p. 9-83)

shows a

Metropolis

®

DMX UPSR backbone ring consisting of Nodes 1, 2, 3, 4, 5, and 6 with single-homed Nodes 7 and 8.

The host Metropolis

®

DMX nodes support OC-3/12/48 single-homed access in

Function/Growth slots A, B, C, D, and G.

The single-homed nodes could be one or more Metropolis

®

DMX, Metropolis

®

DMXtend, Metropolis

®

DMXplore, and/or any system supporting OC-3/12/48 configurations.

Traffic Flow

In the following figure, if Node 7 is the source and Node 8 is the destination, traffic will flow as follows when the proper cross-connections are made:

•

From Node 7 MAIN 1 to Node 5 A1, then clockwise around the ring from Node 5

MAIN 1 to Node 2 MAIN 2. From Node 2 A2 to Node 8 MAIN 2.

•

From Node 7 MAIN 2 to Node 5 A2, then counter-clockwise around the ring from

Node 5 MAIN 2 to Node 2 MAIN 1. From Node 2 A1 to Node 8 MAIN 1.

Protection

At the host Metropolis

®

DMX nodes, the port Application parameter for the low-speed

OC-n ports that connect to the single-homed nodes (Node 5:A1/A2, Node 2:A1/A2) must be provisioned UPSR and the cross-connection channel application must be

Unswitched.

The single-homed configuration transports traffic through the UPSR backbone ring without any protection switching by the host nodes (Node 5 and Node 2) or

.................................................................................................................................................................................................................................

9-82 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-6: Establish single-homed network configurations pass-through nodes on the UPSR backbone ring. The UPSR terminating nodes (Node 7 and Node 8) perform path protection switching.

Figure 9-5 Single-homed configuration example

C

2

C

1

B

2

B

1

A

2

A

1

NS TSI US

MAIN 2 MAIN 1

Node 8

A 1

A 2

B 1

B 2

C 1

C 2

D 1

D 2

G 1

G 2

G

2

G

1

D

2

NS

D

1

MAIN 2

MAIN 1

US

Node 1

C

2

TSI

C

1

Node 5

B

2

B

1

US

MAIN 1

TSI

MAIN 2

NS

A

2

A

1

NS

Port application = UPSR

A

1

A

2

B

1

US

B

2

C

1

C

2

D

1

D

2

G

1

G

2

NS - Network Side

US - User Side

OUT

IN

Node 7

MAIN 1

US TSI

MAIN 2

NS

IN

OUT

A

1

A

2

B

1

B

2

C

1

C

2

IN

G

2

G

1

D

2

D

1

Node 2

C

2

C

1

B

2

US

B

1

A

2

Port application = UPSR

A

1

NS

OUT

NS

MAIN 2

TSI

US

MAIN 1

G 2

G 1

D 2

D 1

C 2

C 1

B 2

B 1

A 2

A 1

IN

OUT

Node 4

MAIN 1

US

TSI

MAIN 2

NS

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2 nc-dmx-117A

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-83

Network configuration procedures

Procedure 9-7: Establish dual-homed network configurations

.................................................................................................................................................................................................................................

Overview

Use this procedure to establish dual-homed OC-3/12/48 access to host Metropolis

®

DMX nodes in a UPSR backbone ring.

Figure 9-6, “Dual-Homed network configuration example 1” (p. 9-91)

and

Figure 9-7,

“Dual-Homed network configuration example 2” (p. 9-91)

show example network configurations with dual-homed access to a UPSR backbone ring. This allows the dual-homed ring to be completed through the UPSR backbone ring. The UPSR backbone ring transports/drops traffic from the dual-homed ring. The end-of-path network elements that drop the traffic perform path protection switching.

This procedure assumes that dual-homed access is established by interconnecting

Metropolis

®

DMX nodes using a Function/Growth slot at two host Metropolis

®

DMX nodes and the OC-12/OC-48 Main slot pair of the Metropolis

®

DMX nodes in the dual-homed ring. However, the Function/Growth slots of the two host Metropolis

®

DMX nodes may also be connected in a dual-homed ring with the following:

•

Metropolis

®

DMXtend using OC-3/12/48 Main slot pair or OC-3/12/48

Function/Growth slot pair. If connecting to a Metropolis

®

DMXtend, refer to the

Metropolis

®

DMXtend Access Multiplexer User Operations Guide, 365-372-325, as required, when performing this procedure.

•

Metropolis

®

DMXplore OC-3/OC-12 Main slot pair. If connecting to a Metropolis

®

DMXplore, refer to the Metropolis

®

DMXplore Access Multiplexer User Operations

Guide, 365-372-332, as required, when performing this procedure.

•

Metropolis

®

DMX (OC-3/12/48 Function/Growth slot pair): If connecting to the

Function/Growth slots of another Metropolis

®

DMX, refer to

Procedure 9-9:

“Establish subtending low-speed UPSR/BLSR” (p. 9-98) , as required, when

performing this procedure.

Important! Dual-homed access is supported at the host Metropolis

®

using the 0x1S1 and 0x1S2 or UPSR port applications.

DMX nodes

If the port application is UPSR, then the cross-connection channel application must be UNSWITCHED. This configuration is essentially the same as establishing a

subtending UPSR ring [ Procedure 9-9: “Establish subtending low-speed

UPSR/BLSR” (p. 9-98) ], except for the cross-connection applications.

Ignore all alarms until procedure is complete.

Privilege level

You must log in as either a Privileged user to complete this procedure.

.................................................................................................................................................................................................................................

9-84 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-7: Establish dual-homed network configurations

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 9-2) , the following

equipment is also required:

•

Optical power meter

•

Lightguide jumpers

•

Lightguide BuildOuts (LBOs)

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 9-2)

and

“Required equipment” (p. 9-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

3. Verify that you have the necessary work instructions detailing the slots, circuit packs, ports, and network element parameters to be used for this procedure.

4. Verify that the UPSR backbone ring containing the host Metropolis

®

established and operating properly.

DMX nodes is

5. Verify that all systems being connected to the host Metropolis

®

been equipped and are operating properly.

DMX nodes have

Step

1

2

Complete the following steps to establish dual-homed OC-3/12/48 access to host

Metropolis

®

DMX nodes in a UPSR backbone ring.

.................................................................................................................................................................................................

From your work instructions, determine the network configuration. Refer to

Figure 9-6,

“Dual-Homed network configuration example 1” (p. 9-91)

and

Figure 9-7,

“Dual-Homed network configuration example 2” (p. 9-91)

for examples. If possible, make a sketch of the existing UPSR backbone ring and the required dual-homed connections.

If required, select the

Administration

→

OSI Neighbor Map

command at the host

Metropolis

®

DMX node and note the NEs connected to Main 1 and Main 2.

Access each NE identified, select the

Administration

→

OSI Neighbor Map

command, and note the NEs connected to Main 1 and Main 2.

Repeat this step until the UPSR backbone ring can be sketched.

.................................................................................................................................................................................................

Important! Two or more shelves in the same network cannot have the same TID.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-85

Network configuration procedures Procedure 9-7: Establish dual-homed network configurations

3

4

Using the work instructions and office records, verify that no duplicate TID settings exist between the nodes in the existing UPSR backbone ring and the dual-homed ring.

If duplicate TID settings exist, determine new settings and at each site with duplicate

TID settings, select

Administration

→

Set TID

from the System View menu, and enter new TID settings.

Reference:

Procedure 7-11: “Set/change system TID” (p. 7-38)

.................................................................................................................................................................................................

If required, modify the network service access point (NSAP) address and/or enable

Level 2 routing capabilities at the host Metropolis

®

DMX nodes and the nodes in the dual-homed ring.

Reference:

Procedure 7-13: “Provision network layer 3 parameters” (p. 7-40)

.................................................................................................................................................................................................

At the host Metropolis

®

DMX nodes (for example, Nodes 4 and 5 in

Figure 9-6,

“Dual-Homed network configuration example 1” (p. 9-91)

and

Figure 9-7,

“Dual-Homed network configuration example 2” (p. 9-91) ), verify/install OLIU circuit

packs and/or pluggable transmission modules in the Function/Growth slot (A1 or A2,

B1 or B2, C1 or C2, D1 or D2, or G1 or G2) being used for access according to the work instructions.

Important! If the work instructions or office records do not specify OLIU types, refer to Metropolis

®

DMX Access Multiplexer Applications and Planning Guide,

365-372-300, for a description of OLIU circuit packs, pluggable transmission modules, and applications. Optical line power measurements and/or office records must be used to verify that the span length can be supported.

To establish dual-homed access using UPSR interfaces, Function/Growth slot 1 must be used at one host Metropolis

®

DMX node, and Function/Growth slot 2 must be used at the other host Metropolis

®

DMX node.

The companion Function/Growth slot at the host Metropolis

®

DMX nodes may be:

• unequipped (no protection OLIU circuit pack installed)

• equipped with a protection OLIU circuit pack and the companion port in the

AUTO or NMON state (no cable connected to port)

• equipped with a protection OLIU circuit pack and the companion socket is unequipped.

Reference:

•

Procedure 4-3: “Install OLIU circuit packs in Function slots” (p. 4-14)

•

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62)

.................................................................................................................................................................................................................................

9-86 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-7: Establish dual-homed network configurations

5

6

7

8

9

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled for ports, an inconsistent DCC values alarm is reported when the ports are looped back.

If required at the host Metropolis

®

DMX node, clear the inconsistent DCC values alarm by disabling OSI over DCC for the required ports. From the System View menu, select

Configuration

→

DCC Terminations

and disable

OSI Over DCC

for the required DCC ports.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

Important! For dual-homed access, provision the Application parameter to UPSR for all ports being connected, or provision the Application parameter of the port in

Function/Growth slot 1 to 0x1S1 and the Application parameter of the port in

Function/Growth slot 2 to 0x1S2.

From the System View menu at the host Metropolis

®

DMX nodes, select

Configuration

→

Equipment

, select the required low-speed OC-n port, and provision the port parameters according to the work instructions.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

At the host Metropolis

®

DMX nodes, verify that the low-speed OC-n ports were provisioned correctly using the

View

→

Equipment

command.

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled, the LAPD Role parameter must be provisioned differently at each end of an optical span. For example, if the LAPD

Role parameter is provisioned user-side at one end of an optical span, then the

LAPD Role parameter must be provisioned network-side at the other end of the optical span.

From the System View menu, select

Configuration

→

DCC Terminations

and provision the DCC terminations for the required DCC ports according to the work instructions.

Result:

If OSI over DCC is enabled, an inconsistent DCC values alarm will occur if the OC-n ports are looped back.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

From the System View menu at the host Metropolis

®

DMX nodes, select

View

→

DCC

Terminations

and verify that the DCC terminations were provisioned correctly.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-87

Network configuration procedures Procedure 9-7: Establish dual-homed network configurations

10

.................................................................................................................................................................................................

At each node in the dual-homed ring, provision the required Main/Function/Growth ports, DCC terminations, synchronization, and remote NE status functions according to the work instructions.

If the node is a...

Metropolis

®

DMX and the Main ports are used,

Metropolis

®

DMX and the

Function/Growth ports are used,

Metropolis

®

DMXtend or

Metropolis

®

DMXplore,

Then...

Refer to

Procedure 9-1: “Establish high-speed end-to-end Metropolis

®

DMX system” (p. 9-3)

to provision and verify the required Main ports,

DCC terminations, synchronization, and remote

NE status functions.

Refer to

Procedure 9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98)

to provision and verify the required Function/Growth ports and DCC terminations.

Refer to the other product’s documentation to provision and verify the required ports, DCC terminations, synchronization, and remote NE status functions.

11

.................................................................................................................................................................................................

Beginning at the host Metropolis

®

DMX node using Function/Growth slot 1, connect the fibers between the required low-speed OC-n port in Function/Growth slot 1 and the required OC-n port in Main/Function/Growth slot 1 at the adjacent node and verify the integrity of the optical span being established.

Reference:

Figure 9-6, “Dual-Homed network configuration example 1” (p. 9-91)

shows the following dual-homed connections at the host Metropolis

®

DMX nodes:

Metropolis

®

DMX

Function/Growth slot

A1 (Node 5)

Metropolis

®

DMX

Function/Growth slot

A2 (Node 4)

Connects to the M1 OLIU at the adjacent node (Node 7)

Connects to the M2 OLIU at the adjacent node (Node 8)

In

Figure 9-7, “Dual-Homed network configuration example 2” (p. 9-91) , note the

difference between the Function slot connections for the direction of traffic flow.

.................................................................................................................................................................................................................................

9-88 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-7: Establish dual-homed network configurations

12

13

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Perform end-to-end optical line test.

Reference:

•

Procedure 14-7: “Perform end-to-end optical line test on Main OLIUs”

(p. 14-61)

•

Procedure 14-8: “Perform end-to-end optical line test on Function OLIUs”

(p. 14-64)

.................................................................................................................................................................................................

Continue around the dual-homed ring in the same direction until all nodes are connected.

If the node is a...

Metropolis

®

DMX and the Main ports are used,

Metropolis

®

DMX and the

Function/Growth ports are used,

Metropolis

®

DMXtend or

Metropolis

®

DMXplore,

Then...

Refer to

Procedure 9-1: “Establish high-speed end-to-end Metropolis

®

DMX system” (p. 9-3)

to connect and test the optical span.

Refer to

Procedure 9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98)

to connect and test the optical span.

Refer to the other product’s documentation to connect and test the optical span.

14

.................................................................................................................................................................................................

At each node in the dual-homed ring, click the

Alarm List

button or select

Fault

→

NE

Alarm List

from the System View menu and verify that no alarms are present.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

15

.................................................................................................................................................................................................

If required, repeat this procedure from

Step 1

to establish dual-homed access at other host Metropolis

®

DMX nodes in the UPSR backbone ring.

.................................................................................................................................................................................................

16

Important! Establishing service requires that the proper slots in each terminating node be properly equipped with the correct circuit pack(s) for the type of service being established. It also requires numerous cross-connections in each of the nodes representing the path of the required service. Additionally, transmission tests should be performed to verify the continuity and quality of the established circuit.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-89

Network configuration procedures Procedure 9-7: Establish dual-homed network configurations

The dual-homed access network is now complete and ready for service to be established.

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

E

N D O F

S

T E P S

Configuration

The example in

Figure 9-6, “Dual-Homed network configuration example 1” (p. 9-91)

shows a Metropolis

®

DMX UPSR backbone ring consisting of Nodes 1, 2, 3, 4, 5, and

6 with dual-homed Nodes 7 and 8 at Node 4 and Node 5. The example in

Figure 9-6,

“Dual-Homed network configuration example 1” (p. 9-91)

also shows dual-homed

Node 9 at Node 1 and Node 2.

The host Metropolis

®

DMX nodes support OC-3/12/48 dual-homed access in

Function/Growth slots A, B, C, D, and G.

The dual-homed nodes could be a Metropolis

®

DMX, Metropolis

®

DMXtend,

Metropolis

®

DMXplore, or any system supporting OC-3/12/48 configurations.

The example in

Figure 9-7, “Dual-Homed network configuration example 2” (p. 9-91)

shows dual-homed Nodes 7 and 8.

Traffic Flow Example

In

Figure 9-6, “Dual-Homed network configuration example 1” (p. 9-91) , if Node 7 is

the source and Node 9 is the destination, traffic will flow as follows when the proper cross-connections are made:

•

From Node 7 MAIN 1 to Node 5 A1, then clockwise around the ring from Node 5

MAIN 1 to Node 1 MAIN 2. From Node 1 A2 to Node 9 MAIN 2.

•

From Node 7 MAIN 2 through Node 8 to Node 4 A2, then counter-clockwise around the ring from Node 4 MAIN 2 to Node 2 MAIN 1. From Node 2 A1 to

Node 9 MAIN 1.

Protection

At the host Metropolis

®

DMX nodes, the port Application parameter for the low-speed

OC-n ports that connect to the dual-homed nodes (Node 5 A1 and Node 4 A2 in

.................................................................................................................................................................................................................................

9-90 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-7: Establish dual-homed network configurations

Figure 9-6, “Dual-Homed network configuration example 1” (p. 9-91) ) must be

provisioned using one of the following methods:

•

The Application parameter of both low-speed OC-n ports must be provisioned

UPSR and the cross-connection channel application must be Unswitched.

•

The Application parameter of the low-speed OC-n port must be provisioned 0x1S1 if dual-homed ring is cabled to the port in Function/Growth slot 1, and the

Application parameter of the low-speed OC-n port must be provisioned 0x1S2 if dual-homed ring is cabled to the port in Function/Growth slot 2 .

The dual-homed configuration transports traffic through the network backbone ring without any protection switching by the host nodes or pass-through nodes on the network backbone ring. The UPSR terminating nodes perform the path protection switching.

Figure 9-6 Dual-Homed network configuration example 1

Node 9

MAIN 2 MAIN 1

NS

TSI

US

G

2

G

1

D

2

D

1

Node 1

C

2

C

1

B

2

US

B

1

A

2

A

1

Port application=UPSR or 0x1S2

NS US

MAIN 2

TSI

MAIN 1

A

1

A

2

B

1

B

2

C

1

C

2

IN

OUT

Port application=UPSR or 0x1S1

G

2

G

1

D

2

D

1

Node 2

C

2

C

1

B

2

B

1

A

2

A

1

NS

NS US

MAIN 2

TSI

MAIN 1

A 1

A 2

B 1

B 2

C 1

C 2

D 1

D 2

G 1

G 2

Traffic flow

MAIN 1

US

Node 5

TSI

MAIN 2

NS

NS

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Port application=UPSR or 0x1S1

Node 7

MAIN 1

US

TSI

MAIN 2

NS

Node 8

MAIN 1

US

TSI

MAIN 2

NS

IN

OUT

A

1

A

2

Node 4

MAIN 1

US

TSI

MAIN 2

NS

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Traffic flow

Port application=UPSR or 0x1S2

NS - Network Side

US - User Side

A

1

A

2

B

1

B

2

C

1

C

2

A

1

A

2

B

1

B

2

C

1

C

2 nc-dmx-201A

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-91

Network configuration procedures Procedure 9-7: Establish dual-homed network configurations

IN

OUT

Figure 9-7 Dual-Homed network configuration example 2

Node 5

MAIN 1

TSI

US

MAIN 2

NS

IN

OUT

Node 3

MAIN 1

TSI

US

MAIN 2

NS

IN

OUT

Node 4

MAIN 1

US

TSI

MAIN 2

NS

OUT

IN

A

1

A

2

US

B

1

B

2

C

1

C

2

D

1

D

2

G

1

Port application=UPSR or 0x1S2

Traffic flow

G

2

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Port application=UPSR or 0x1S1

Traffic flow

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

NS

NS - Network Side

US - User Side

Node 7

MAIN 2

NS

TSI

MAIN 1

US

A

1

A

2

B

1

B

2

C

1

C

2

Node 8

MAIN 2

NS

TSI

MAIN 1

US

A

1

A

2

B

1

B

2

C

1

C

2 nc-dmx-202

.................................................................................................................................................................................................................................

9-92 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

Procedure 9-8: Establish OC-48 0x1 unprotected extensions

.................................................................................................................................................................................................................................

Overview

Use this procedure to establish OC-48 0x1 unprotected extensions where the

Metropolis

®

DMX is the host and the Metropolis

®

DMXpress is the non-switching extension.

Privilege level

You must log in as either a Privileged user to complete this procedure.

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 9-2) , the following

equipment is also required:

•

Optical power meter

•

Lightguide jumpers

•

Lightguide BuildOuts (LBOs).

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 9-2)

and

“Required equipment” (p. 9-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

3. Verify that you have the necessary work instructions detailing the slots, circuit packs, ports, and network element parameters to be used for this procedure.

4. Verify that the network ring containing the host Metropolis

®

DMX node is established and operating properly using the procedures in this manual.

5. Verify that the application option plug (p5) on the OC48/1.3I2 Main circuit pack of the Metropolis

®

DMXpress was set to 0x1 in the unswitched extension.

Refer to the Metropolis

®

DMXpress Access Multiplexer User Operations Guide,

365-372-314.

Step

1

Complete the following steps to establish the configuration.

.................................................................................................................................................................................................

Connect a PC to the host Metropolis

®

establish a WaveStar

®

CIT session.

DMX node and Metropolis

®

DMXpress and

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-93

Network configuration procedures Procedure 9-8: Establish OC-48 0x1 unprotected extensions

2

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Determine the network configuration.

Reference:

The following figure shows an example where Node 1 is the host

Metropolis

®

DMX and Node 2 is the unprotected extension.

Figure 9-8 OC-48 0x1 unprotected extension

Node 1

DMX OC-48

MAIN 1

TSI

MAIN 2

NS

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

OC-48

OUT

Node 2

DMX

press

OC-48

IN

MAIN 1

US

A

1

A

2

B

1

B

2

C

1

C

2

NC-Xpress-081

3

4

.................................................................................................................................................................................................

Determine the optical loss of each optical span from office records or by making the required measurements.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

At the host Metropolis

®

DMX node, verify/install the required OC-48 LS OLIU circuit packs in Function Group or Growth slots (A1, B1, C1, D1, or G1) being used for access.

At the extension, verify Main 1 is being used for access (Main 2 is unavailable in this application).

Important! If you plan to use STS-1 tributaries 25-48 on slots A1, B1, or C1 of the host Metropolis

®

DMX node, then the LNW27, LNW29, LNW76,

LNW221-259 OC-48 or OC-192 circuit packs must be used in the MAIN slots. If

.................................................................................................................................................................................................................................

9-94 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-8: Establish OC-48 0x1 unprotected extensions

5

6

the work instructions or office records do not specify OLIU types, refer to

Metropolis

®

DMX Access Multiplexer Applications and Planning Guide,

365-372-300, for a description of OLIU circuit packs, pluggable transmission modules, and applications. Optical line power measurements and/or office records must be used to verify that the span length can be supported.

The companion Function/Growth slot at the host Metropolis

®

DMX nodes may be:

• unequipped (no protection OLIU circuit pack installed)

• equipped with a protection OLIU circuit pack and the companion port in the

AUTO or NMON state (no cable connected to port)

• equipped with a protection OLIU circuit pack and the companion socket is unequipped.

Reference:

•

Procedure 4-3: “Install OLIU circuit packs in Function slots” (p. 4-14)

•

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62)

.................................................................................................................................................................................................

Important! For this application, ensure the Application port parameter is set to

UPSR or 0x1S1 at the host node.

From the System View menu at the host Metropolis

®

DMX node, select

Configuration

→

Equipment

, select the required port, and provision port parameters as required from your work instruction.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled, the LAPD Role parameter must be provisioned differently at each end of an optical span. For example, if the LAPD

Role parameter is provisioned user-side at one end of an optical span, then the

LAPD Role parameter must be provisioned network-side at the other end of the optical span.

From the System View menu, select

Configuration

→

DCC Terminations

and provision the DCC terminations for the required DCC ports according to the work instructions.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-95

Network configuration procedures

7

8

9

10

11

Procedure 9-8: Establish OC-48 0x1 unprotected extensions

Result:

If OSI over DCC is enabled, an inconsistent DCC values alarm will occur if the OC-n ports are looped back.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

Set the timing at the Metropolis

®

DMXpress NE. From the System View menu select

Configuration

→

Timing/Sync

. In the

Provision Timing/Sync

window set the following:

•

Timing Source:

to Line

•

Mode Switching

to Revertive

•

Synchronization Source

to main-1-1

•

Synchronization Autoreconfiguration

to Enabled

.................................................................................................................................................................................................

Determine from either the Network Operations Center (NOC) or work instructions, all the nodes in the existing network. At the Metropolis

®

DMX NE verify the NEs in the ring or network by selecting

Administration

→

OSI Routing Map

.

Important! Note the NEs. Verify that no NE on the ring or network has the same

TID name as the NE being added. If a duplicate TID exists request a new TID name from the NOC. At the Metropolis

®

DMXpress NE being added, select

Administration

→

Set TID

and enter the new TID Name.

.................................................................................................................................................................................................

If required at the Metropolis

®

DMX NE, remove the optical loop from the OLIU in the Function or Growth port in position 1. If required at the Metropolis

®

DMXpress

NE, remove the optical loop from Main-1.

Result:

A loss of signal (LOS) alarm will occur if the port is being monitored.

.................................................................................................................................................................................................

At the Metropolis

®

OUT.

DMX NE, connect the fiber drop to Function 1 or Growth 1 OLIU

.................................................................................................................................................................................................

At the Metropolis

®

DMXpress NE, measure the power on the fiber drop to Main-1 IN.

If required insert an LBO in Main-1 IN and connect the Fiber drop to the LBO. Verify that the flashing red LED on the main circuit pack stops flashing. Connect the fiber drop to Main-1 OUT.

.................................................................................................................................................................................................................................

9-96 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-8: Establish OC-48 0x1 unprotected extensions

12

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

At the Metropolis

®

DMX NE, measure the power on the fiber drop to Function 1 or

Growth 1 OLIU IN. If required insert an LBO in Function 1 or Growth 1 IN and connect the Fiber drop to the LBO. Verify that the flashing red LED on the circuit pack stops flashing.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-97

Network configuration procedures

Procedure 9-9: Establish subtending low-speed UPSR/BLSR

.................................................................................................................................................................................................................................

Overview

Use this procedure to establish the following subtending low-speed rings:

•

OC-3/12/48 UPSR

•

OC-48 BLSR (Release 3.0 and later)

Privilege level

You must log in as a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 9-2)

and

“Required equipment” (p. 9-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

3. Verify that you have the necessary work instructions detailing the slots, circuit packs, ports, and network element parameters to be used for this procedure.

4. Verify that the network containing the host Metropolis

®

DMX node is established and operating properly.

5. Verify that all systems being connected to the host Metropolis

®

DMX have been equipped and operating properly.

Step

Complete the following steps to establish a subtending low-speed UPSR/BLSR.

1

.................................................................................................................................................................................................

If establishing a subtending low-speed...

UPSR,

Then...

BLSR,

Proceed to

Procedure 9-9.1: “Establish subtending low-speed UPSR” (p. 9-99) .

Proceed to

Procedure 9-9.2: “Establish subtending low-speed BLSR” (p. 9-105) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

9-98 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

Procedure 9-9.1: Establish subtending low-speed UPSR

.................................................................................................................................................................................................................................

Important! This is not a standalone procedure. Perform this procedure only as directed by

Procedure 9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98)

.

Step

1

2

Important! This procedure establishes a subtending low-speed OC-3/12/48 UPSR.

Note that this configuration differs from a single-homed application in that it supports ring closure by providing path protection switching, and by allowing low-speed pass-through cross-connections.

This procedure assumes that the subtending ring is established by interconnecting

Metropolis

®

DMX nodes using a Function/Growth slot at the host Metropolis

®

DMX node and the OC-12/OC-48 Main/Function/Growth slot pair of the

Metropolis

®

DMX nodes in the subtending ring. However, the Function/Growth slots of the host Metropolis

®

DMX node may also be connected in a subtending ring with the following:

•

Metropolis

®

DMXtend using OC-3/12/48 Main slot pair or OC-3/12/48

Function/Growth slot pair. If connecting to a Metropolis

®

DMXtend, refer to the Metropolis

®

DMXtend Access Multiplexer User Operations Guide,

365-372-325, as required, when performing this procedure.

•

Metropolis

®

DMXplore using OC-3/OC-12 Main slot pair. If connecting to a

Metropolis

®

DMXplore, refer to the Metropolis

®

DMXplore Access Multiplexer

User Operations Guide, 365-372-332 as required, when performing this procedure.

Ignore all alarms until procedure is complete.

Complete the following steps to establish a subtending low-speed UPSR.

.................................................................................................................................................................................................

From your work instructions, determine the network configuration. Refer to

Figure 9-9,

“Subtending UPSR configuration example” (p. 9-104)

for an example. If possible, make a sketch of the existing network and the required subtending ring connections.

If required, select the

Administration

→

OSI Neighbor Map

command at the host

Metropolis

®

DMX node and note the NEs connected to Main 1 and Main 2.

Access each NE identified, select the

Administration

→

OSI Neighbor Map

command, and note the NEs connected to Main 1 and Main 2.

Repeat this step until the network can be sketched.

.................................................................................................................................................................................................

Important! Two or more shelves in the same network cannot have the same TID.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-99

Network configuration procedures Procedure 9-9.1: Establish subtending low-speed UPSR

3

4

5

Using the work instructions and office records, verify that no duplicate TID settings exist between the nodes in the existing network and the subtending ring. If duplicate

TID settings exist, determine new settings and at each site with duplicate TID settings, select

Administration

→

Set TID

from the System View menu, and enter new TID settings.

Reference:

Procedure 7-11: “Set/change system TID” (p. 7-38)

.................................................................................................................................................................................................

If required, modify the network service access point (NSAP) address and/or enable

Level 2 routing capabilities at the host Metropolis

®

DMX node and the nodes in the subtending ring.

Reference:

Procedure 7-13: “Provision network layer 3 parameters” (p. 7-40)

.................................................................................................................................................................................................

At the host Metropolis

®

DMX node (Node 5 in

Figure 9-9, “Subtending UPSR configuration example” (p. 9-104) ) install OLIU circuit packs and/or pluggable

transmission modules in Function Group or Growth slot pair (A1 and A2, B1 and B2,

C1 and C2, D1 and D2, or G1 and G2) being used for access according to the work instructions.

Important! If the work instructions or office records do not specify OLIU types, refer to Metropolis

®

DMX Access Multiplexer Applications and Planning Guide,

365-372-300, for a description of OLIU circuit packs, pluggable transmission modules, and applications. Optical line power measurements and/or office records must be used to verify that the span length can be supported.

The subtending ring connections to the host Metropolis

®

DMX node must be in two slots in the same Function/Growth group (for example: A1 and A2.)

Reference:

•

Procedure 4-3: “Install OLIU circuit packs in Function slots” (p. 4-14)

•

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62)

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled for ports, an inconsistent DCC values alarm is reported when the ports are looped back.

If required at the host Metropolis

®

DMX node, clear the inconsistent DCC values alarm by disabling OSI over DCC for the required ports. From the System View menu, select

Configuration

→

DCC Terminations

and disable

OSI Over DCC

for the required DCC ports.

.................................................................................................................................................................................................................................

9-100 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-9.1: Establish subtending low-speed UPSR

6

7

8

9

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

Important! The Application parameter of the low-speed OC-n port pairs being connected must be provisioned UPSR.

From the System View menu at the host Metropolis

®

DMX node, select

Configuration

→

Equipment

, select the required low-speed OC-n ports, and provision the port parameters according to the work instructions.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

At the host Metropolis

®

DMX node, verify that the low-speed OC-n ports were provisioned correctly using the

View

→

Equipment

command.

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled, the LAPD Role parameter must be provisioned differently at each end of an optical span. For example, if the LAPD

Role parameter is provisioned user-side at one end of an optical span, then the

LAPD Role parameter must be provisioned network-side at the other end of the optical span.

From the System View menu, select

Configuration

→

DCC Terminations

and provision the DCC terminations for the required DCC ports according to the work instructions.

Result:

If OSI over DCC is enabled, an inconsistent DCC values alarm will occur if the OC-n ports are looped back.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

From the System View menu at the host Metropolis

Terminations

®

DMX node, select

View

→

DCC

and verify that the DCC terminations were provisioned correctly.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-101

Network configuration procedures Procedure 9-9.1: Establish subtending low-speed UPSR

10

.................................................................................................................................................................................................

At each node in the subtending ring, provision the required Main/Function/Growth ports, DCC terminations, synchronization, and remote NE status functions according to the work instructions.

If the node is a...

Metropolis

®

DMX and the Main ports are used,

Metropolis

®

DMX and the

Function/Growth ports are used,

Metropolis

®

DMXtend or

Metropolis

®

DMXplore,

Then...

Refer to

Procedure 9-1: “Establish high-speed end-to-end Metropolis

®

DMX system” (p. 9-3)

to provision and verify the required Main ports,

DCC terminations, synchronization, and remote

NE status functions.

Repeat

Step 4

through

Step 9

to provision and verify the required Function/Growth ports and

DCC terminations.

Refer to the other product’s documentation to provision and verify the required ports, DCC terminations, synchronization, and remote NE status functions.

11

.................................................................................................................................................................................................

Beginning at the host Metropolis

®

DMX node, connect the fibers between the required low-speed OC-n port in Function/Growth slot 1 and the required OC-n port in Main slot 1 or Function/Growth slot 2 at the adjacent node and verify the integrity of the optical span being established.

Refer to

Figure 9-9, “Subtending UPSR configuration example” (p. 9-104)

when connecting fibers. The following connections are required at the host Metropolis

®

DMX node:

Metropolis

®

DMX

Function/Growth slot

A1, B1, C1, D1, or G1

(Node 5)

Metropolis

®

DMX

Function/Growth slot

A2, B2, C2, D2, or G2

(Node 5)

Connects to the M1 OLIU or Function/Growth slot 2 OLIU

(A2, B2, C2, D2, or G2) of the subtending shelf

Connects to the M2 OLIU or Function/Growth slot 1 OLIU

(A1, B1, C1, D1, or G1) of the subtending shelf

.................................................................................................................................................................................................................................

9-102 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-9.1: Establish subtending low-speed UPSR

12

13

14

15

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Perform end-to-end optical line test.

Reference:

•

Procedure 14-7: “Perform end-to-end optical line test on Main OLIUs”

(p. 14-61)

•

Procedure 14-8: “Perform end-to-end optical line test on Function OLIUs”

(p. 14-64)

.................................................................................................................................................................................................

Repeat

Step 11

and

Step 12

for each optical span in the subtending UPSR. Continue around the subtending ring in the same direction until all nodes are connected. Refer to the example at the end of the procedure.

.................................................................................................................................................................................................

At each node in the subtending ring, click the

Alarm List

button or select

Fault

→

NE

Alarm List

from the System View menu and verify that no alarms are present.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! Establishing service requires that the proper slots in each terminating node be properly equipped with the correct circuit pack(s) for the type of service being established. It also requires numerous cross-connections in each of the nodes representing the path of the required service. Additionally, transmission tests should be performed to verify the continuity and quality of the established circuit.

The subtending ring is now ready for initial service to be established.

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-103

Network configuration procedures Procedure 9-9.1: Establish subtending low-speed UPSR

Figure 9-9 Subtending UPSR configuration example

Node 1 Node 2

MAIN 2

MAIN 1

MAIN 2

MAIN 1

TSI TSI

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

C 1

B 2

B 1

A 2

A 1

G 2

G 1

D 2

D 1

C 2

Node 5

MAIN 1

US

TSI

MAIN 2

NS

UPSR ring closure

(application=upsr)

NS

A

1

A

2

B

1

US

B

2

C

1

C

2

D

1

D

2

G

1

G

2

IN

OUT

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Node 4

MAIN 1

US

TSI

MAIN 2

NS

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Subtending UPSR

Node 7

MAIN 1 MAIN 2

US

TSI

NS

Node 8

MAIN 1

MAIN 2

TSI

US NS

NS - Network Side

US - User Side

NC-DMX-204

.................................................................................................................................................................................................................................

9-104 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

Procedure 9-9.2: Establish subtending low-speed BLSR

.................................................................................................................................................................................................................................

Important! This is not a standalone procedure. Perform this procedure only as directed by

Procedure 9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98)

.

Step

1

2

3

Important! This procedure assumes that the subtending ring is established by interconnecting Metropolis

®

DMX nodes using a Function/Growth slot at the host

Metropolis

®

DMX node and the OC-48 Main/Function/Growth slot pair of the

Metropolis

®

DMX nodes in the subtending ring.

Ignore all alarms until procedure is complete.

Complete the following steps to establish a subtending low-speed OC-48 2-fiber BLSR.

(Refer to the example in

Figure 9-10, “Subtending 2-fiber BLSR example” (p. 9-111)

and 2-fiber bidirectional line switched ring worksheet at the end of this procedure when performing this procedure.)

.................................................................................................................................................................................................

From your work instructions, determine the network configuration. Refer to

Figure

9-10, “Subtending 2-fiber BLSR example” (p. 9-111)

for an example. If possible, make a sketch of the existing network and the required subtending ring connections.

If required, select the

Administration

→

OSI Neighbor Map

command at the host

Metropolis

®

DMX node and note the NEs connected to Main 1 and Main 2.

Access each NE identified, select the

Administration

→

OSI Neighbor Map

command, and note the NEs connected to Main 1 and Main 2.

Repeat this step until the network can be sketched.

.................................................................................................................................................................................................

Important! Two or more shelves in the same network cannot have the same TID.

Using the work instructions and office records, verify that no duplicate TID settings exist between the nodes in the existing network and the subtending ring. If duplicate

TID settings exist, determine new settings and at each site with duplicate TID settings, select

Administration

→

Set TID

from the System View menu, and enter new TID settings.

Reference:

Procedure 7-11: “Set/change system TID” (p. 7-38)

.................................................................................................................................................................................................

If required, modify the network service access point (NSAP) address and/or enable

Level 2 routing capabilities at the host Metropolis

®

DMX node and the nodes in the subtending ring.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-105

Network configuration procedures Procedure 9-9.2: Establish subtending low-speed BLSR

4

5

Reference:

Procedure 7-13: “Provision network layer 3 parameters” (p. 7-40)

.................................................................................................................................................................................................

Important! When the Main slot pair is equipped with LNW26B OC-48 OLIU circuit packs, low-speed OC-48 BLSRs are only supported in slot pair D1 and D2 or G1 and G2 only. Metropolis

®

DMX supports up to two subtending BLSRs.

At the host Metropolis

®

DMX node (DMX Node 5 in

Figure 9-10, “Subtending 2-fiber

BLSR example” (p. 9-111) ) install the OLIU circuit packs in the appropriate

Function/Growth slot pair (A1 and A2, B1 and B2, C1 and C2, D1 and D2, or G1 and

G2).

Important! If the work instructions or office records do not specify OLIU types, refer to Metropolis

®

DMX Access Multiplexer Applications and Planning Guide,

365-372-300, for a description of OLIU circuit packs and applications. Optical line power measurements and/or office records must be used to verify that the span length can be supported.

The subtending ring connections to the host Metropolis

®

DMX node must be in two slots in the same Function/Growth group (for example: A1 and A2.)

Reference:

Procedure 4-3: “Install OLIU circuit packs in Function slots” (p. 4-14)

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled for ports, an inconsistent DCC values alarm is reported when the ports are looped back.

If required at the host Metropolis

®

DMX node, clear the inconsistent DCC values alarm by disabling OSI over DCC for the required ports. From the System View menu, select

Configuration

→

DCC Terminations

and disable

OSI Over DCC

for the required DCC ports.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

6

.................................................................................................................................................................................................

Important! The Application parameter of the low-speed OC-n port pairs being connected must be provisioned 2F BLSR.

From the System View menu at the host Metropolis

®

DMX node, select

Configuration

→

Equipment

, select the required low-speed OC-n ports, and provision the port parameters according to the work instructions.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

7

.................................................................................................................................................................................................

At the host Metropolis

®

DMX node, verify that the low-speed OC-n ports were provisioned correctly using the

View

→

Equipment

command.

.................................................................................................................................................................................................................................

9-106 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-9.2: Establish subtending low-speed BLSR

8

9

.................................................................................................................................................................................................

From the system view at the host Metropolis

®

DMX node,

1. Select

Configuration

→

Equipment

.

2. Select the

Ring ID

tab and expand the required ring by clicking on the plus sign

(+).

3. Click on the required 2F BLSR protection group and

Select

.

4. Provision the required protection group parameters according to the work instructions, then click

Apply

and

Close

. If no changes were made, click

Close

and go to the next step.

.................................................................................................................................................................................................

From the System View menu,

1. Select

View

→

Protection

.

2. Select the required 2F BLSR protection group and click

Select

.

3. Click on the Provisionable Parameters tab and verify that the protection group parameters were provisioned correctly. Then click

Close

.

10

.................................................................................................................................................................................................

If...

automatic ring discovery was provisioned at each node, manual ring discovery was provisioned at each node,

Then...

Continue with

Step 11 .

At the host node, establish a new manual ring map.

Refer to

Procedure 9-4: “Provision manual ring map” (p. 9-63) .

11

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled, the LAPD Role parameter must be provisioned differently at each end of an optical span. For example, if the LAPD

Role parameter is provisioned user-side at one end of an optical span, then the

LAPD Role parameter must be provisioned network-side at the other end of the optical span.

From the System View menu, select

Configuration

→

DCC Terminations

and provision the DCC terminations for the required DCC ports according to the work instructions.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-107

Network configuration procedures Procedure 9-9.2: Establish subtending low-speed BLSR

12

13

Result:

If OSI over DCC is enabled, an inconsistent DCC values alarm will occur if the OC-n ports are looped back.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

From the System View menu at the host Metropolis

®

DMX node, select

View

→

DCC

Terminations

and verify that the DCC terminations were provisioned correctly.

.................................................................................................................................................................................................

At each node in the subtending ring, provision the required Main/Function/Growth ports, 2-fiber BLSR protection group, DCC terminations, synchronization, and remote

NE status functions according to the work instructions.

If the node is a...

Metropolis

®

DMX and the Main ports are used,

Metropolis

®

DMX and the

Function/Growth ports are used,

Then...

Refer to

Procedure 9-1: “Establish high-speed end-to-end Metropolis

®

DMX system” (p. 9-3)

to provision and verify the required Main ports,

DCC terminations, synchronization, and remote

NE status functions.

Repeat

Step 4

through

Step 12

to provision and verify the required Function/Growth ports, 2-fiber

BLSR protection group, and DCC terminations.

14

.................................................................................................................................................................................................

Beginning at the host Metropolis

®

DMX node, connect the fibers between the required low-speed OC-n port in Function/Growth slot 1 and the required OC-n port in

Main/Function/Growth slot 2 at the adjacent node and verify the integrity of the optical span being established.

Reference:

Refer to

Figure 9-10, “Subtending 2-fiber BLSR example” (p. 9-111)

when connecting fibers. The following connections are required at the host

Metropolis

®

DMX node:

Function/Growth slot

A1, B1, C1, D1, or G1 at (Node 5)

Function/Growth slot

A2, B2, C2, D2, or G2

(Node 5) connects to the M2 OLIU or Function/Growth slot 2 OLIU

(A2, B2, C2, D2, or G2) of the subtending shelf connects to the M1 OLIU or Function/Growth slot 1 OLIU

(A1, B1, C1, D1, or G1) of the subtending shelf

.................................................................................................................................................................................................................................

9-108 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-9.2: Establish subtending low-speed BLSR

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

15

16

.................................................................................................................................................................................................

Perform end-to-end optical line test.

Reference:

•

Procedure 14-7: “Perform end-to-end optical line test on Main OLIUs”

(p. 14-61)

•

Procedure 14-8: “Perform end-to-end optical line test on Function OLIUs”

(p. 14-64)

.................................................................................................................................................................................................

Repeat

Step 14

and

Step 15

for each optical span in the subtending 2-fiber BLSR.

Continue around the subtending ring in the same direction until all nodes are connected. Refer to the example at the end of the procedure.

.................................................................................................................................................................................................

17

If automatic ring discovery was provisioned...

enabled at each node,

Then...

disabled at each node,

Important! As the ring is connected, nodes automatically communicate with each other using the data communications channel (DCC) and build a ring map. If successful, automatic ring discovery builds a ring map at each node and the

Ring Discovery in Progress condition clears. If unsuccessful, the ring map is not complete and alarms are reported.

At the host node, select

View

→

Ring Map

→

Ring Map

.

Then click on the appropriate ring and

Select

.

The ring map information appears. If the ring is incomplete and alarms are present, refer to Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302.

go to the next step.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-109

Network configuration procedures Procedure 9-9.2: Establish subtending low-speed BLSR

18

19

20

.................................................................................................................................................................................................

At the host Metropolis

®

DMX node, verify 2-fiber BLSR protection switching:

1. Select

Fault

→

Protection Switch

. Select the required protection group and click

Select

. Choose the

East

or

West

direction with switch type

Manual to Protection,

Ring

. Click

Apply

.

2. Select

View

→

Protection

. Select the required protection group and click

Select

.

Observe the Ring Node APS (Automatic Protection Switch) State, East Switch

Request State, West Switch Request State, East Channel State, and West Channel

State parameters. Verify the 2-fiber BLSR protection switch was performed.

3. Select

Fault

→

Protection Switch

. Select the required protection group and click

Select

. Choose the required direction with switch type

Clear

. Click

Apply

.

Repeat this step at each node in the subtending 2-fiber BLSR (refer to the 2-fiber

BLSR worksheet at the end of the procedure) to verify protection switching.

.................................................................................................................................................................................................

At each node in the subtending ring, click the

Alarm List

button or select

Fault

→

NE

Alarm List

from the System View menu and verify that no alarms are present.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! Establishing service requires that the proper slots in each terminating node be properly equipped with the correct circuit pack(s) for the type of service being established. It also requires numerous cross-connections in each of the nodes representing the path of the required service. Additionally, transmission tests should be performed to verify the continuity and quality of the established circuit.

The subtending ring is now ready for initial service to be established.

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

9-110 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-9.2: Establish subtending low-speed BLSR

Figure 9-10 Subtending 2-fiber BLSR example

Node 1

MAIN 2

MAIN 1

TSI

MAIN 2

Node 2

TSI

MAIN 1

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

D 1

C 2

C 1

B 2

B 1

A 2

A 1

G 2

G 1

D 2

Node 5

MAIN 1

US

TSI

MAIN 2

NS

BLSR

(application= 2F BLSR)

NS

A

1

A

2

B

1

US

B

2

C

1

C

2

D

1

D

2

G

1

G

2

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

IN

OUT

Node 4

MAIN 1

US

TSI

MAIN 2

NS

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Node 7

MAIN 1

MAIN 2

US

TSI

NS

Subtending BLSR

Node 8

MAIN 1

MAIN 2

TSI

US NS

NS - Network Side

US - User Side

NC-DMX-254

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-111

Network configuration procedures

2-Fiber BLSR Worksheet

2-FIBER RING WORKSHEET

N

TID=

Ring ID:

Node ID:

Protection Group AID

OUT Fiber Color/ID

IN Color/ID

Received Power Level

Required LBO

Procedure 9-9.2: Establish subtending low-speed BLSR

SPAN NAME/ID

N+1

TID=

Node ID:

Protection Group AID

IN Fiber Color/ID

Received Power Level

Required IN PAD

OUT Fiber Color

NC-USM-216

.................................................................................................................................................................................................................................

9-112 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

Procedure 9-10: Add IP route(s) through network

.................................................................................................................................................................................................................................

Overview

Use this procedure to add IP Routes (IP Tunnels) through the data communications channel (DCC) OSI-based network.

Privilege level

You must log in as a Privileged user to complete this procedure.

IP routing examples

The following examples illustrate different methods of establishing IP routes through a network.

Each example is followed by the necessary instructions to program that example. In addition, tables are provided that list the required provisioning for the WaveStar

®

CIT,

NEs, OMS, Router, and AnyMedia OS for each scenario.

Example 1: Local access over LAN

In this example ( Figure 9-11, “Local access over LAN” (p. 9-113) ), the PC-CIT is both

the OS and FTP Server and is connected on the same subnet as GNE i.e. local access over the Local Area Network (LAN).

Figure 9-11 Local access over LAN

220.20.3.1/32

RNE B

PC-CIT

220.20.2.1

IP

Subnet

220.20.2.0/24

220.20.2.2

GNE A

OSI

Network

220.20.3.2/32

RNE C

GNE: Gateway NE

RNE: Remote NE

RNE D

220.20.3.3/32 nc-dmx-270

No manual route for the OS needs to be added in GNE as it would appear in GNE’s routing table as a local entry.

ALL NEs are connected over a ring (over OSI-based DCC) and communicate using

OSI, identifying each other through the NSAP addresses. They all support IP stack and thus have IP addresses and subnet masks assigned. Here, they are DMX Product

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-113

Network configuration procedures Procedure 9-10: Add IP route(s) through network

Family IP NEs but could also be connected to IP-only NEs (e.g. a case of IP Fringe discussed later).

How to Provision Example 1

Use the following information along with the Step instructions for this procedure to provision the route illustrated in Example 1:

At ...

Provision ...

PC-CIT Provision its own IP address (220.20.2.1) and subnet mask (24 or 255.255.255.0).

Provision GNE with IP address 220.20.2.2 as default router

GNE Provision its own IP address (220.20.2.2) and subnet mask (24 or 255.255.255.0) for the rear LAN port.

Enable TCP/IP Function on the rear LAN port.

No need to provision manual route to PC-CIT since GNE would advertise it as local entry within its own area.

Ensure that TAP Advertise and TAP Learn are enabled.

RNE B Provision its own IP address (220.20.3.1) and subnet mask (32 or 255.255.255.255) for

DCC port.

Enable TCP/IP Function on the DCC port.

Enable Advertising of its own local entry.

Ensure that TAP Advertise and TAP Learn are enabled.

Use the following routing information at the PC-CIT to provision the route illustrated in Example 1:

Destination Gateway Interface Comments

PC-CIT

220.20.2.1/24 default

-

220.20.2.2

lan lan populated by stack populated by stack

Use the following routing information at the GNE/RNE to provision the route illustrated in Example 1:

Destination Next Hop

Port

Next Hop

Address

Owner TAP Cost

Advertisement

GNE

.................................................................................................................................................................................................................................

9-114 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-10: Add IP route(s) through network

RNE B

Destination Next Hop

Port

220.20.2.2/24 LAN

220.20.2.1/24 LAN

220.20.3.1/32 CLNP_

TUNNEL

220.20.3.2/32 CLNP_

TUNNEL

220.20.3.3/32 CLNP_

TUNNEL

Next Hop

Address

-

220.20.2.1

<NSAP-B>

<NSAP-C>

<NSAP-D>

Owner

local local

TAP

TAP

TAP

TAP Cost

Advertisement

no yes yes

20

20

20 yes yes

20

20

220.20.3.1/32 LAN

220.20.2.1/24 CLNP_

TUNNEL

220.20.3.2/32 CLNP_

TUNNEL

220.20.3.3/32 CLNP_

TUNNEL

-

<NSAP-A>

<NSAP-C>

<NSAP-D> local

TAP

TAP

TAP yes yes yes yes

20

20

20

20

Example 2: Access over IP WAN

In this example ( Figure 9-12, “Access over IP WAN” (p. 9-115) ), the GNE is accessed

over the Internet Protocol Wide Area Network (IP WAN). The Optical Management

System (OMS) (Navis

®

Optical Element Management System) and the GNE are connected over a private internet/intranet via routers, R1 and R2.

Figure 9-12 Access over IP WAN

220.20.3.1/32

RNE B

SNMS

220.20.1.1

IP

Subnet

220.20.1.0/24

220.20.1.2

R1

Intranet

IP

Subnet

220.20.2.0/24

220.20.2.1

R2

220.20.2.2

GNE A

OSI

Network

220.20.3.2/32

RNE C

GNE: Gateway NE

RNE: Remote NE

R: Router

RNE D

220.20.3.3/32 nc-dmx-271

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-115

Network configuration procedures Procedure 9-10: Add IP route(s) through network

At ...

OMS

Router R1

Router R2

GNE

OMS and router R1 are on the same subnet 220.20.1.0/24 and router R2 and GNE are on another subnet 220.20.2.0/24. ALL NEs are connected over a ring (over OSI-based

DCC) and communicate using OSI and identify each other through the NSAP addresses. Here, they are standalone IP NEs but could also be connected to IP-only

NEs (e.g. a case of IP Fringe discussed later).

How to Provision Example 2

Use the following information along with the Step instructions for this procedure to provision the route illustrated in Example 2:

Provision ...

Provision its own IP address (220.20.1.1) and subnet mask (24 or 255.255.255.0)

Provision router, R1 with IP address 220.20.1.2 as default router

Provision IP addresses for its all interfaces

- IP address (220.20.1.2) and subnet mask (24 or 255.255.255.0)

- IP address for the interface connecting to intranet and the subnet mask of the directly attached subnet

- If routers don’t autoshare static routes, then

Provision a static route to a subnet address which can cover maximum number of

RNEs e.g. 220.20.3.0/24 as destination and GNE’s IP address 220.20.2.2 as next-hop-address

Provision IP addresses for its all interfaces

- IP address (220.20.2.1) and subnet mask (24 or 255.255.255.0)

- IP address for the interface connecting to intranet and the subnet mask of the directly attached subnet

Provision a static route to a subnet address which can cover maximum number of

RNEs e.g. 220.20.3.0/24 as destination and GNE’s IP address 220.20.2.2 as next-hop-address

Provision its own IP address (220.20.2.2) and subnet mask (24 or 255.255.255.0) for the rear LAN port.

Enable TCP/IP Function on the rear LAN port.

Provision R2 as default router with IP address 220.20.2.1

Provision manual route to OMS which it would advertise within its own OSI Level

1 area.

The manual route would have OMS IP address 220.20.1.1/32 as destination and router R2’s IP address 220.20.2.1 as next-hop-address.

Ensure that TAP Advertise and TAP Learn are enabled.

.................................................................................................................................................................................................................................

9-116 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-10: Add IP route(s) through network

At ...

RNE B

OMS

220.20.1.1/24 default

-

220.20.1.2

lan lan populated by stack populated by stack

Router

R1

R2

220.20.1.2/24

220.20.3.0/24

220.20.2.1/24

220.20.3.0/24

-

220.20.2.2

-

220.20.2.2

lan lan lan lan populated by stack

1. populated by

OSPF (if static routes autoshare)

2. manual (if static routes not autoshare e.g. in Cajun 550) populated by stack manual

Use the following routing information at the GNE/RNE to provision the route illustrated in Example 2:

Destination Next Hop Port Next Hop

Address

Owner TAP

Advertisement

Cost

GNE

Provision ...

Provision its own IP address (220.20.3.1) and subnet mask (32 or 255.255.255.255) for DCC port.

Enable TCP/IP Function on the DCC port.

Enable Advertising of its own local entry.

Ensure that TAP Advertise and TAP Learn are enabled.

Use the following routing information at the OMS and Router to provision the route illustrated in Example 2:

Destination Gateway Interface Comments

220.20.2.2/24 default

220.20.1.1/32

220.20.3.1/32

220.20.3.2/32

LAN

LAN

-

220.20.2.1

LAN 220.20.2.1

CLNP_TUNNEL <NSAP-B>

CLNP_TUNNEL <NSAP-C> local local manual

TAP

TAP no no yes yes yes

20

20

20

20

20

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-117

Network configuration procedures Procedure 9-10: Add IP route(s) through network

Destination

220.20.3.3/32

RNE B

220.20.3.1/32

220.20.1.1/32

220.20.3.2/32

220.20.3.3/32

Next Hop Port Next Hop

Address

CLNP_TUNNEL <NSAP-D>

LAN -

CLNP_TUNNEL <NSAP-A>

CLNP_TUNNEL <NSAP-C>

CLNP_TUNNEL <NSAP-D>

Owner

TAP local

TAP

TAP

TAP

TAP

Advertisement

Cost

yes 20 yes yes yes yes

20

20

20

20

Example 3: Multi-Area operations

In this example ( Figure 9-13, “Multi-Area operations” (p. 9-118) ), an extension to

Example 2, we have added other NEs that are deployed in different areas (1, 2, and 3).

RNE C, P, and X are level-2 routers which enable communications across areas. But the manual route to OMS provisioned at GNE wouldn’t be advertised by RNE C to other areas. This requires establishing manual routes across areas which are then advertised by Level 2 routers within their areas. Each area can be represented by a single subnet. This also requires adding static entries to each subnet in Router R2.

Figure 9-13 Multi-Area operations

SNMS

220.20.1.1

IP

Subnet

220.20.1.0/24

220.20.1.2

R1

IP

Subnet

220.20.2.0/24

220.20.2.1

Intranet

R2

GNE: Gateway NE

RNE: Remote NE

R: Router

RNE B

220.20.3.1/32

220.20.3.66/32

RNE Q

Area 2

RNE P

220.20.3.65/32

RNE R

220.20.3.67/32

220.20.2.2

GNE A

220.20.3.2/32

OSI

Network

RNE C

Area 1

220.20.3.3/32

RNE D

220.20.3.129/32

RNE X

Area 3

220.20.3.130/32

RNE Y

RNE Z

220.20.3.132/32 nc-dmx-272

Careful planning and design of subnet addresses for these areas could reduce the number of static entries required at Router R2.

How to Provision Example 3

Use the following information along with the Step instructions for this procedure to provision the route illustrated in Example 3:

.................................................................................................................................................................................................................................

9-118 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

At ...

OMS

Router R1

Router R2

GNE

Procedure 9-10: Add IP route(s) through network

Provision ...

Provision its own IP address (220.20.1.1) and subnet mask (24 or 255.255.255.0)

Provision router, R1 with IP address 220.20.1.2 as default router

Provision IP addresses for its all interfaces

- IP address (220.20.1.2) and subnet mask (24 or 255.255.255.0)

- IP address for the interface connecting to intranet and the subnet mask of the directly attached subnet

- If routers don’t autoshare static routes, then

Provision a static route to a subnet address which can cover maximum number of

RNEs e.g. 220.20.3.0/24 as destination covers subnets 220.20.3.0/26,

220.20.3.64/26 and 220.20.3.128/26. The GNE’s IP address 220.20.2.2 as next-hop-address.

Provision IP addresses for its all interfaces

- IP address (220.20.2.1) and subnet mask (24 or 255.255.255.0)

- IP address for the interface connecting to intranet and the subnet mask of the directly attached subnet

Provision a static route to a subnet address which can cover maximum number of

RNEs e.g. 220.20.3.0/24 as destination covers subnets 220.20.3.0/26,

220.20.3.64/26 and 220.20.3.128/26. The GNE’s IP address 220.20.2.2 as next-hop-address.

Provision its own IP address (220.20.2.2) and subnet mask (24 or 255.255.255.0) for the rear LAN port.

Enable TCP/IP Function on the rear LAN port.

Provision R2 as default router with IP address 220.20.2.1

Provision manual route to OMS which it would advertise within its own area. The manual route would have OMS IP address 220.20.1.1/32 as destination and router

R2’s IP address 220.20.2.1 as next-hop-address.

Ensure that TAP Advertise and TAP Learn are enabled.

Provision manual route for two areas with RNE P’s and RNE X’s IP addresses

(220.20.3.65/26 and 220.20.3.129/26) as destination and their respective NSAP addresses as the next hop address.

No need to advertise this entry.

(In case, any area can’t be covered with one subnet, more than one route might have to be added)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-119

Network configuration procedures Procedure 9-10: Add IP route(s) through network

At ...

RNE C

RNE P

RNE X

RNE R

Provision ...

Provision its own IP address (220.20.3.2) and subnet mask (32 or

255.255.255.255) for DCC port.

Enable TCP/IP Function on the DCC port.

Enable Advertising of its own local entry.

Ensure that TAP Advertise and TAP Learn are enabled.

Provision its own IP address (220.20.3.65) and subnet mask (32 or

255.255.255.255) for DCC port.

Enable TCP/IP Function on the DCC port.

Enable Advertising of its own local entry.

Ensure that TAP Advertise and TAP Learn are enabled.

Provision manual route to GNE which it would advertise within its own area. The manual route would have OMS IP address 220.20.1.1/32 as destination and GNE’s

NSAP address as the next-hop address. Set advertise enable for this entry.

Provision its own IP address (220.20.3.129) and subnet mask (32 or

255.255.255.255) for DCC port.

Enable TCP/IP Function on the DCC port.

Enable Advertising of its own local entry.

Ensure that TAP Advertise and TAP Learn are enabled.

Provision manual route to GNE which it would advertise within its own area. The manual route would have OMS IP address 220.20.1.1/32 as destination and GNE’s

NSAP address as the next-hop address. Set advertise enable for this entry.

Provision its own IP address (220.20.3.67) and subnet mask (32 or

255.255.255.255) for DCC port.

Enable TCP/IP Function on the DCC port.

Enable Advertising of its own local entry.

Ensure that TAP Advertise and TAP Learn are enabled.

Use the following routing information at the OMS and NE (GNE/RNE) to provision the route illustrated in Example 3:

Destination Gateway Interface Comments

OMS

220.20.1.1/24 default

-

220.20.1.2

lan lan populated by stack populated by stack

Router

R1 220.20.1.2/24 lan populated by stack

.................................................................................................................................................................................................................................

9-120 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-10: Add IP route(s) through network

R2

Destination

220.20.3.0/24

220.20.2.1/24

220.20.3.0/24

Gateway

220.20.2.2

-

220.20.2.2

Interface

lan lan lan

Comments

1. populated by

OSPF (if static routes autoshare)

2. manual (if static routes not autoshare e.g. in

Cajun 550) populated by stack manual

Use the following routing information at the GNE/RNE to provision the route illustrated in Example 3:

Destination Next Hop

Port

Next Hop

Address

Owner TAP

Advertisement

Cost

GNE

220.20.2.2/24 default

LAN

LAN

220.20.1.1/32 LAN

220.20.3.65/26 CLNP_

TUNNEL

220.20.3.129/26 CLNP_

TUNNEL

220.20.3.1/32 CLNP_

TUNNEL

220.20.3.2/32

220.20.3.3/32

CLNP_

TUNNEL

CLNP_

TUNNEL

-

220.20.2.1

220.20.2.1

<NSAP-P>

<NSAP-X>

<NSAP-B>

<NSAP-C>

<NSAP-D> local local manual manual manual

TAP

TAP

TAP no no yes no no yes yes yes

20

20

20

20

20

20

20

20

RNE C

220.20.3.2/32

220.20.1.1/32

220.20.3.1/32

220.20.3.3/32

LAN

CLNP_

TUNNEL

CLNP_

TUNNEL

CLNP_

TUNNEL

-

<NSAP-A>

<NSAP-B>

<NSAP-D> local

TAP

TAP

TAP yes yes yes yes

20

20

20

20

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-121

Network configuration procedures Procedure 9-10: Add IP route(s) through network

Destination

RNE P

RNE X

220.20.3.65/32 LAN

220.20.1.1/32 CLNP_

TUNNEL

220.20.3.66/32 CLNP_

TUNNEL

220.20.3.67/32 CLNP_

TUNNEL

220.20.3.129/32 LAN

220.20.1.1/32 CLNP_

TUNNEL

220.20.3.130/32 CLNP_

TUNNEL

220.20.3.131/32 CLNP_

TUNNEL

RNE R

Next Hop

Port

220.20.3.67/32 LAN

220.20.1.1/32 CLNP_

TUNNEL

220.20.3.65/32 CLNP_

TUNNEL

220.20.3.66/32 CLNP_

TUNNEL

Next Hop

Address

Owner

-

<NSAP-A> local manual

<NSAP-Q> TAP

<NSAP-R> TAP

-

<NSAP-A> local manual

<NSAP-Y> TAP

<NSAP-Z> TAP

-

<NSAP-A> local

TAP

<NSAP-P> TAP

<NSAP-Q> TAP

TAP

Advertisement

Cost

yes yes yes yes yes yes yes yes yes yes yes yes

20

20

20

20

20

20

20

20

20

20

20

20

Example 4: IP NEs on the fringe

In this example ( Figure 9-14, “IP NEs on the fringe” (p. 9-123) ), another extension of

Example 2, IP routing is used to reach the IP-only NEs on the fringe of the OSI

.................................................................................................................................................................................................................................

9-122 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-10: Add IP route(s) through network network, allowing termination of an IP connection at the IP-only host connected to

RNE C on the same IP subnet. It can also be reached via additional routers).

Figure 9-14 IP NEs on the fringe

220.20.3.1/32

RNE B

Any Media

OS

220.20.1.3

SNMS

220.20.1.1

IP

Subnet

220.20.1.0/24

220.20.1.2

R1

Intranet

IP

Subnet

220.20.2.0/24

R2

220.20.2.1

220.20.2.2

GNE A

OSI

Network

220.20.3.17/28

RNE C

IP

Subnet

220.20.3.16/28

RNE D

220.20.3.3/32

GNE: Gateway NE

RNE: Remote NE

R: Router

IP-Only

NE

220.20.3.18/28 nc-dmx-273

At ...

OMS

AnyMedia OS

The RNE C is connected via its LAN port and is given a real IP address 220.20.3.17

(rather 220.20.3.2) which belongs to the subnet 220.20.3.16/28. The RNE C is still reachable via the IP address 220.20.3.0/24 provisioned at Router R1 as destination for the entire OSI subnet.

This also requires manual provisioning of the route to AnyMedia OS at the GNE and

RNE C being provisioned as default router at the IP-only NE.

How to Provision Example 4

Use the following information along with the Step instructions for this procedure to provision the route illustrated in Example 4:

Provision ...

Provision its own IP address (220.20.1.1) and subnet mask (24 or

255.255.255.0)

Provision router, R1 with IP address 220.20.1.2 as default router

Provision its own IP address (220.20.1.3) and subnet mask (24 or

255.255.255.0)

Provision router, R1 with IP address 220.20.1.2 as default router

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-123

Network configuration procedures

At ...

Router R1

Router R2

GNE

RNE C

IP-only NE

Provision ...

Procedure 9-10: Add IP route(s) through network

Provision IP addresses for its all interfaces

- IP address (220.20.1.2) and subnet mask (24 or 255.255.255.0)

- IP address for the interface connecting to intranet and the subnet mask of the directly attached subnet

- If routers don’t autoshare static routes, then

Provision a static route to a subnet address which can cover maximum number of RNEs e.g. 220.20.3.0/24 as destination and GNE’s IP address 220.20.2.2 as next-hop-address.

Provision IP addresses for its all interfaces

- IP address (220.20.2.1) and subnet mask (24 or 255.255.255.0)

- IP address for the interface connecting to intranet and the subnet mask of the directly attached subnet

Provision a static route to a subnet address which can cover maximum number of RNEs e.g. 220.20.3.0/24 as destination and GNE’s IP address 220.20.2.2 as next-hop-address.

Provision its own IP address (220.20.2.2) and subnet mask (24 or

255.255.255.0) for the rear LAN port.

Enable TCP/IP Function on the rear LAN port.

Provision R2 as default router with IP address 220.20.2.1

Provision manual route to OMS which it would advertise within its own area.

The manual route would have OMS IP address 220.20.1.1/32 as destination and router R2’s IP address 220.20.2.1 as next-hop-address

Ensure that TAP Advertise and TAP Learn are enabled.

Provision a manual route to AnyMedia OS similar to OMS and IP address of

AnyMedia OS, 220.20.1.3/24

Provision its own IP address (220.20.3.17) and subnet mask (28 or

255.255.255.240) for the LAN port.

Enable TCP/IP Function on the LAN port.

Enable Advertising of its own local entry.

Ensure that TAP Advertise and TAP Learn are enabled.

Provision its own IP address (220.20.3.18) and subnet mask (28 or

255.255.255.240)

Provision RNE C as its default router with IP address (220.20.3.17)

.................................................................................................................................................................................................................................

9-124 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-10: Add IP route(s) through network

Use the following routing information at the OMS and Router to provision the route illustrated in Example 4:

Destination Gateway Interface Comments

OMS

220.20.1.1/24 default

-

220.20.1.2

lan lan populated by stack populated by stack

Router

R1 220.20.1.2/24 lan

R2

220.20.3.0/24

220.20.2.1/24

220.20.3.0/24

-

220.20.2.2

220.20.2.2

lan lan lan populated by stack

1. populated by

OSPF (if static routes autoshare)

2. manual (if static routes not autoshare e.g. in

Cajun 550) populated by stack manual

Use the following routing information at the AnyMedia OS to provision the route illustrated in Example 4:

Destination Gateway Interface Comments

AnyMedia

OS

220.20.1.3/24 default

-

220.20.1.2

lan lan populated by stack populated by stack

Use the following routing information at the GNE/RNE to provision the route illustrated in Example 4:

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-125

Network configuration procedures Procedure 9-10: Add IP route(s) through network

Destination

GNE

220.20.2.2/24 default

220.20.1.1/32

220.20.1.3/32

220.20.3.1/32

220.20.3.2/32

220.20.3.3/32

RNE C

220.20.3.17/28

220.20.3.18/28

220.20.1.1/32

220.20.3.1/32

220.20.3.3/32

Next Hop

Port

LAN

LAN

LAN

LAN

CLNP_

TUNNEL

CLNP_

TUNNEL

CLNP_

TUNNEL

Next Hop

Address

-

220.20.2.1

220.20.2.1

220.20.2.1

<NSAP-B>

<NSAP-C>

<NSAP-D>

Owner TAP

Advertisement

Cost

local local no no manual yes manual yes

TAP yes

TAP

TAP yes yes

LAN

LAN

CLNP_

TUNNEL

CLNP_

TUNNEL

CLNP_

TUNNEL

-

-

<NSAP-A>

<NSAP-B>

<NSAP-D> local local

TAP

TAP

TAP yes no yes yes yes

20

20

20

20

20

Use the following routing information at the IP-Only NE to provision the route illustrated in Example 4:

Destination Gateway Interface Comments

IP-Only NE

220.20.3.18/28 default

-

220.20.3.17

lan lan populated by stack populated by stack

20

20

20

20

20

20

20

Example 5: Multiple GNEs scenario

In this example ( Figure 9-15, “Multiple GNEs scenario” (p. 9-127) ), a single area has

many NEs and if TCP/IP Function is provisioned, the Tunnel Auto Provisioning (TAP)

.................................................................................................................................................................................................................................

9-126 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-10: Add IP route(s) through network advertisement that would be exchanged would be significantly high and lot of such traffic would pass through GNE.

Figure 9-15 Multiple GNEs scenario

Area

RNE B

T

OS R

GNE 1

TAP Group 1 TAP Group 2

T

GNE 2 T

RNE C

T

NE supporting tunneling

NE not supporting tunneling

Automatic tunnel

Manual tunnel into the area nc-dmx-274

At ...

OS

To avoid the overloading on the network and particularly on GNE, TAP Groups are defined. With this, TAP enabled NEs wouldn’t listen to the advertisements from NEs outside their TAP groups and thus don’t form tunnels with them or through them.

Setting up TAP groups necessitates two GNEs, each with one manual route entry to OS and advertise in their respective TAP groups.

How to Provision Example 5

Use the following information along with the Step instructions for this procedure to provision the route illustrated in Example 5:

Provision ...

Provision its own IP address and subnet mask .

Provision router as default router.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-127

Network configuration procedures

At ...

Router

GNE 1

GNE 2

RNE B

RNE C

Procedure 9-10: Add IP route(s) through network

Provision ...

Provision IP addresses for all interfaces.

Provision 2 static routes (one to GNE 1 and one to GNE 2).

Provision its own IP address and subnet mask for the rear LAN port.

Enable TCP/IP Function on the rear LAN port.

Provision default router .

Provision manual route entry to OS with TAP Group 1.

Ensure that TAP Advertise and TAP Learn are enabled.

Provision its own IP address and subnet mask for the rear LAN port.

Enable TCP/IP Function on the rear LAN port.

Provision default router .

Provision manual route entry to OS with TAP Group 2.

Ensure that TAP Advertise and TAP Learn are enabled.

Provision its own IP address and subnet mask for DCC port.

Enable TCP/IP Function on the DCC port.

Enable Advertising of its own local entry.

Ensure that TAP Advertise and TAP Learn are enabled for TAP Group 1.

Provision its own IP address and subnet mask for DCC port.

Enable TCP/IP Function on the DCC port.

Enable Advertising of its own local entry.

Ensure that TAP Advertise and TAP Learn are enabled for TAP Group 2.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 9-2)

and

“Required equipment” (p. 9-2)

in this chapter.

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions identify the OS/FTP server, gateway network element, and remote network element.

4. Verify that the work instructions specify the required provisioning at each network element (for example, IP addresses and subnet masks).

.................................................................................................................................................................................................................................

9-128 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-10: Add IP route(s) through network

5. If the FTP server is a local PC (WaveStar

®

CIT), verify that the PC’s IP address and Subnet Mask parameters are provisioned and that a static route on the PC connects it to the remote NEs.

6. If the FTP server is a remote OS, verify that the remote OS’ IP address and Subnet

Mask parameters are provisioned and if the remote OS and GNE are in different subnetworks, verify that the Default Router IP address is provisioned.

Step

1

2

3

4

Complete the following steps to add IP routes through the data communications channel (DCC) OSI-based network:

.................................................................................................................................................................................................

If the remote OS is a local PC, a static route on the PC must provide a path to the remote NEs. If packets are intended for the remote NE, then you must route to the gateway NE.

If the remote OS is a remote operations system, the static route must be entered on the router.

Example:

If the OS is a local PC, from the MS-DOS prompt, enter

route add

120.20.20.0 MASK 255.255.255.0 120.20.30.1

. In this example 120.20.20.0 is the subnetwork address of the remote NE and 120.20.30.1 is the IP address of the gateway NE. The Subnet Mask of the OS and the Gateway is 255.255.255.0 while the Subnet Mask of the Remote NEs is 255.255.255.255.

.................................................................................................................................................................................................

If the remote OS and GNE are in different subnetworks, verify that the router in each subnetwork has IP addresses provisioned for all interfaces and that the static route, as described in

Step 1 , has been provisioned on the router.

.................................................................................................................................................................................................

Establish a login session to the GNE.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

At the GNE:

1. From the System View, select

Administration

→

Data Communications

. The

Data Communications window opens.

2. Click on the

TCP/IP

tab.

3. In the Data Communications window, click on the

Port AID:

drop-down menu and select LAN-1 or LAN-2 according to the work instructions.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-129

Network configuration procedures Procedure 9-10: Add IP route(s) through network

5

6

7

8

4. Enable the

TCP/IP Function

, and provision the

IP Address

and

IP Subnet Mask

parameters according to the work instructions.

5. If the remote OS and GNE are in different subnetworks, provision the

IP Default

Router Address

parameter according to the work instructions.

6. Click

Apply

. A dialog box appears stating that executing this command resets the network element. Click

Yes

and the WaveStar

®

CIT disconnects from the network element.

A flashing

b

in the

IND

display on the SYSCTL indicates that a boot is in progress.

During the boot, the

b

may extinguish for up to 20 seconds and then resume flashing.

Important! If automatic synchronization is unsuccessful, the date and time must be reset manually.

Reference:

Procedure 7-10: “Set date and time” (p. 7-33) .

.................................................................................................................................................................................................

Re-establish the log in session to the GNE.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

At the GNE:

1. From System View, select

Administration

→

Data Communications

The Data

Communications window opens.

2. Click on the

IP Routing

tab.

3. In the Data Communications window, enable the

TAP Advertise

and

TAP Learn

parameters. Then provision the

TAP Group

parameter according to the work instructions. Click

Apply

and

Close

.

.................................................................................................................................................................................................

Log out of the GNE and log in to the remote NE.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

At the RNE:

1. From the System View, select

Administration

→

Data Communications

. The

Data Communications window opens.

2. Click on the

TCP/IP

tab.

3. In the Data Communications window, click on the

Port AID:

drop-down menu and select DCC-ALL.

.................................................................................................................................................................................................................................

9-130 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-10: Add IP route(s) through network

9

10

11

4. Enable

TCP/IP Function

parameter.

5. Provision the

IP Address

and

IP Subnet Mask

parameters according to the work instructions and click on

Apply

. A dialog box appears stating that executing this command resets the network element. Click

Yes

and the WaveStar

®

CIT disconnects from the network element.

A flashing

b

in the

IND

display on the SYSCTL indicates that a boot is in progress.

During the boot, the

b

may extinguish for up to 20 seconds and then resume flashing.

Important! If automatic synchronization is unsuccessful, the date and time must be reset manually.

Reference:

Procedure 7-10: “Set date and time” (p. 7-33) .

.................................................................................................................................................................................................

Re-establish the log in session to the RNE.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

At the RNE:

1. From the System View, select

Administration

→

Data Communications

. The

Data Communications window opens.

2. Click on the

IP Routing

tab.

3. In the Data Communications window, enable the

TAP Advertise

and

TAP Learn

parameters. Then provision the

TAP Group

parameter according to the work instructions. Click

Apply

and

Close

.

.................................................................................................................................................................................................

If required, repeat

Step 7

through

Step 10

at other RNEs.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-131

Network configuration procedures

Procedure 9-11: Establish low-speed 1+1 unprotected linear optical extension

.................................................................................................................................................................................................................................

Overview

Use this procedure to establish a low-speed 1+1 unprotected linear OC-3/12/48 optical extension.

Important! This procedure assumes that the low-speed 1+1 unprotected optical linear extension is established by interconnecting a OC-3/12/48 Function/Growth slot at the host Metropolis

®

DMX to a far-end node or a local testhead for test access tributaries.

Ignore all alarms until the procedure is complete.

Privilege level

You must log in as either a Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 9-2)

and

“Required equipment” (p. 9-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

3. Verify that you have the necessary work instructions detailing the slots, circuit packs, ports, and network element parameters to be used for this procedure.

4. Verify that the network containing the host Metropolis

®

and operating properly.

DMX node is established

5. Verify that the far-end node or local testhead being connected to the host

Metropolis

®

DMX node has been equipped and is operating properly.

.................................................................................................................................................................................................................................

9-132 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures

Step

Procedure 9-11: Establish low-speed 1+1 unprotected linear optical extension

1

Complete the following steps to establish a low-speed 1+1 unprotected OC-3/12/48 optical extension.

.................................................................................................................................................................................................

Determine the network configuration using the work instructions and office records.

Refer to the example in

Figure 9-16, “Example of 1+1 unprotected optical linear extension” (p. 9-133) .

Figure 9-16 Example of 1+1 unprotected optical linear extension

Node 1

DMX OC-48

MAIN 1

TSI

MAIN 2

NS

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

OC-48

OUT

Node 2

DMX

press

OC-48

IN

MAIN 1

US

A

1

A

2

B

1

B

2

C

1

C

2

NC-Xpress-081

2

3

.................................................................................................................................................................................................

Important! Two or more shelves in the same network cannot have the same TID.

Using the work instructions and office records, verify that no duplicate TID settings exist between the host Metropolis

®

DMX and the far-end node or local testhead. If duplicate TID settings exist, determine new settings and at each site with duplicate TID settings, select

Administration

→

Set TID

from the System View menu, and enter new

TID settings.

Reference:

Procedure 7-11: “Set/change system TID” (p. 7-38)

.................................................................................................................................................................................................

If required, modify the network service access point (NSAP) address and/or enable

Level 2 routing capabilities at the host Metropolis

®

DMX and the far-end node or local testhead.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-133

Network configuration procedures Procedure 9-11: Establish low-speed 1+1 unprotected linear optical extension

4

5

6

Reference:

Procedure 7-13: “Provision network layer 3 parameters” (p. 7-40)

.................................................................................................................................................................................................

At the host Metropolis

®

DMX node, verify/install the required OLIU circuit packs and/or pluggable transmission modules in the Function Group slot (A1, B1, C1, D1, or

G1) being used for access according to the work instructions.

Important! If the work instructions or office records do not specify OLIU types, refer to the Metropolis

®

DMX Access Multiplexer Applications and Planning Guide,

365-372-300, for a description of OLIU circuit packs/pluggable transmission modules and applications. Optical line power measurements and/or office records must be used to verify that the span length can be supported.

The companion Function/Growth slot at the host Metropolis

®

DMX nodes may be:

• unequipped (no protection OLIU circuit pack installed)

• equipped with a protection OLIU circuit pack and the companion port in the

AUTO or NMON state (no cable connected to port)

• equipped with a protection OLIU circuit pack and the companion socket is unequipped.

Reference:

•

Procedure 4-3: “Install OLIU circuit packs in Function slots” (p. 4-14)

•

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62)

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled for ports, an inconsistent DCC values alarm is reported when the ports are looped back.

If required at the host Metropolis

®

DMX node, clear the inconsistent DCC values alarm by disabling OSI over DCC for the required ports. From the System View menu, select

Configuration

→

DCC Terminations

and disable

OSI Over DCC

for the required DCC ports.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

Important! It is recommended that the port Application parameter be provisioned

1+1 at both ends of the system.

For test access tributaries, the port Application parameter must be provisioned 1+1.

From the System View menu at the host Metropolis

®

DMX node, select

Configuration

→

Equipment

. Select the required ports and provision the required port parameters according to the work instructions.

.................................................................................................................................................................................................................................

9-134 365-372-301 R6.0

Issue 15, January 2006

Network configuration procedures Procedure 9-11: Establish low-speed 1+1 unprotected linear optical extension

7

8

9

10

11

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

From the System View menu at the host Metropolis

®

DMX node, select

Configuration

→

Equipment

, if not already open. Select the system (AID=system), then click

Select

at the bottom of the window.

If required, provision the 1+1 Protection Priority (1+1 applications only) and Wait To

Rename (Optimized 1+1 applications only) parameters. Click

Apply

if changes were made, then click

Yes

to the warning message to make your changes. Click

Close

to exit.

.................................................................................................................................................................................................

At the host Metropolis

®

DMX node, verify that the low-speed OC-n ports were provisioned correctly using the

View

→

Equipment

command.

.................................................................................................................................................................................................

Important! If OSI over DCC is enabled, the LAPD Role parameter must be provisioned differently at each end of an optical span. For example, if the LAPD

Role parameter is provisioned user-side at one end of an optical span, then the

LAPD Role parameter must be provisioned network-side at the other end of the optical span.

For test access tributaries, OSI over DCC and IP over DCC must be disabled.

From the System View menu, select

Configuration

→

DCC Terminations

and provision the DCC terminations for the required DCC ports according to the work instructions.

Result:

If OSI over DCC is enabled, an inconsistent DCC values alarm will occur if the OC-n ports are looped back.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

From the System View menu at the host Metropolis

Terminations

®

DMX node, select

View

→

DCC

and verify that the DCC terminations were provisioned correctly.

.................................................................................................................................................................................................

At the far-end node or local testhead that is connecting to the host Metropolis

®

DMX node, provision the required ports, DCC terminations, synchronization, and remote NE status functions according to the work instructions.

Refer to the other product’s documentation to perform the required provisioning.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

9-135

Network configuration procedures Procedure 9-11: Establish low-speed 1+1 unprotected linear optical extension

12

13

14

15

.................................................................................................................................................................................................

Connect the optical fibers and verify the integrity of the optical span being installed.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Perform end-to-end optical line test.

Reference:

Procedure 14-8: “Perform end-to-end optical line test on Function

OLIUs” (p. 14-64)

.................................................................................................................................................................................................

Click the

Alarm List

button or select

Fault

→

NE Alarm List

from the System View menu and verify that no alarms are present.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! Establishing service requires that the proper slots in each terminating node be properly equipped with the correct circuit pack(s) for the type of service being established. It also requires numerous cross-connections in each of the nodes representing the path of the required service. Additionally, transmission tests should be performed to verify the continuity and quality of the established circuit.

The unprotected linear optical extension is now ready for initial service or a test access session to be established.

Reference:

•

Chapter 10, “TDM service provisioning procedures”

•

Chapter 11, “Ethernet/Data network provisioning procedures”

•

Procedure 14-23: “Establish test access session in the MON(E or EF) mode”

(p. 14-114)

•

Procedure 14-24: “Establish test access session in the SPLT(E or EF) mode”

(p. 14-121)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

9-136 365-372-301 R6.0

Issue 15, January 2006

10

10

procedures

Overview

.................................................................................................................................................................................................................................

Purpose

This chapter includes procedures to provision TDM services.

Contents

Before you begin

Procedure 10-1: Establish DS1 or E1 service

Procedure 10-2: Discontinue DS1 or E1 service

Procedure 10-3: Establish DS3 or EC-1 service

Procedure 10-4: Discontinue DS3 or EC-1 service

Procedure 10-5: Make VT1.5 or STS-n cross-connections, single

OC-3/OC-12 UPSR configuration

Procedure 10-6: Make Function unit UPSR, hairpin, and Main to

Function unit UPSR cross-connections

Procedure 10-7: Make 1+1 (linear extension) cross-connections

Procedure 10-8: Make single-homed cross-connections

Procedure 10-9: Make dual-homed cross-connections

Procedure 10-10: Bridge and roll cross-connections

Procedure 10-11: Establish dual ring interworking (DRI) connections

Procedure 10-12: Provision DS1/DS3 locked cross-connections on a

UPSR

Procedure 10-13: Provision VT1.5 cross-connections on a BLSR

VT cross-connections for BLSR

10-26

10-32

10-39

10-48

10-56

10-64

10-2

10-3

10-7

10-10

10-13

10-16

10-22

10-71

10-76

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-1

TDM service provisioning procedures

Before you begin

.................................................................................................................................................................................................................................

Before you begin

Prior to performing all procedures in this chapter,

1. If not previously completed, install generic and WaveStar

®

CIT software on the PC.

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

2. Connect PC and establish a WaveStar

®

CIT session.

Refer to

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24) .

Required equipment

All procedures in this chapter require that the following equipment is available:

•

Personal Computer (PC) with WaveStar

®

CIT software installed

•

Wrist strap

Important! If additional equipment is required to perform a specific procedures, that additional equipment is listed in that procedure.

.................................................................................................................................................................................................................................

10-2 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures

Procedure 10-1: Establish DS1 or E1 service

.................................................................................................................................................................................................................................

Overview

Use this procedure to establish end-to-end DS1 or E1 service.

Important! This procedure assumes that the Metropolis

®

DMX shelf and network have been properly equipped and tested. If the Metropolis

®

DMX shelf has not been properly equipped, refer to

Chapter 5, “Node turnup procedures” . If the

network has not been properly configured, refer to

Chapter 9, “Network configuration procedures” .

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Verify that the work instructions specify the terminating nodes, pass-through nodes

(UPSRs/BLSRs only), DS1/E1 port addresses, the DS1/E1 port parameters to provision, and the cross-connections to be established.

Step

Complete the following steps to establish end-to-end DS1 or E1 service.

1

2

.................................................................................................................................................................................................

Click the

Alarm List

button or select

Fault

→

NE Alarm List

from the System View menu to obtain an NE Alarm List and verify that no alarms are present. Clear all alarms before continuing this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

From the System View menu at each terminating node, select

View

→

Equipment

to verify that the proper service and protection circuit packs have been installed in the

Function Unit groups (A, B, C, or D) used for this service.

.................................................................................................................................................................................................

3

If circuit packs have not been installed, install circuit packs as required.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-3

TDM service provisioning procedures Procedure 10-1: Establish DS1 or E1 service

4

5

6

7

Reference:

Procedure 4-8: “Install DS1/E1 circuit packs” (p. 4-39)

.................................................................................................................................................................................................

At the terminating nodes of the circuit being established, determine which DS1/E1 ports are to be put into service, and what port parameters to provision using the work instruction.

Important! All the ports on a DS1/E1 circuit pack are provisioned for either DS1 or E1; DS1 and E1 ports cannot be mixed on a single pack.

.................................................................................................................................................................................................

At the terminating nodes, select

Configuration

→

Equipment

. Expand the circuit pack details, then select the DS1/E1 port to provision for the circuit being established.

Provision parameters as required.

The

Bi-Polar Violations

parameter does not apply to the LNW18 12TMUX circuit pack or the LNW8 56DS1/E1 circuit pack.

Bi-Polar Violations

parameter value settings:

•

No - When Bi-Polar Violations is set to

No

(default), incoming BPVs at the

DS1 port are corrected by the port unit circuitry before the DS1 is mapped into the VT1.5 payload and are not translated in the outgoing direction. This value should be used if not connected to a GR-8 compliant DLC.

•

Yes - Bi-Polar Violations should be set to

Yes

for a DS1 port connected to a

GR-8 compliant DLC terminal. This permits the DLC system to detect LOS or

LOF and switch to protection. If linecde=B8ZS, bpv threshold crossings are translated to LOF; if linecde=AMI, they are translated to LOS.

If the

Port Monitoring Mode

is provisioned NMON, the port is not monitored/alarmed and the port will not automatically transition to the IS

(in-service) state when a good signal (not LOS) is detected. If the

Port Monitoring

Mode

is provisioned AUTO, the port automatically transitions to the IS (in-service) state when a good signal (not LOS) is detected, and the port is monitored/alarmed.

Reference:

(p. 4-42)

Procedure 4-9: “Provision DS1/E1 circuit packs/ports for service”

.................................................................................................................................................................................................

Verify that the DS1/E1 cable connections have been made from the terminating nodes to the cross-connect panel or equivalent connection points.

.................................................................................................................................................................................................

Determine the necessary add/drop and pass-through (UPSRs/BLSRs only) cross-connections for each node from the work instructions.

.................................................................................................................................................................................................................................

10-4 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-1: Establish DS1 or E1 service

8

9

10

11

.................................................................................................................................................................................................

At the terminating nodes and pass-through nodes (UPSR/BLSRs only), select

Configuration

→

Cross-Connections

to access the Cross-Connection Wizard and establish the necessary cross-connections. Use the following references as examples.

Reference:

•

Procedure 10-5: “Make VT1.5 or STS-n cross-connections, single OC-3/OC-12

UPSR configuration” (p. 10-16)

•

Procedure 10-6: “Make Function unit UPSR, hairpin, and Main to Function unit

UPSR cross-connections” (p. 10-22)

•

Procedure 10-7: “Make 1+1 (linear extension) cross-connections” (p. 10-26)

•

Procedure 10-8: “Make single-homed cross-connections” (p. 10-32)

•

Procedure 10-9: “Make dual-homed cross-connections” (p. 10-39)

•

Procedure 10-11: “Establish dual ring interworking (DRI) connections”

(p. 10-56)

•

Procedure 10-12: “Provision DS1/DS3 locked cross-connections on a UPSR”

(p. 10-64)

•

Procedure 10-13: “Provision VT1.5 cross-connections on a BLSR” (p. 10-71)

.................................................................................................................................................................................................

Perform the DS1/E1 end-to-end transmission test for each circuit being put into service, as required.

Reference:

Procedure 14-9: “Perform DS1/E1 transmission test” (p. 14-67)

.................................................................................................................................................................................................

Important! If the

Port Monitoring Mode

is provisioned NMON, the port is not monitored/alarmed and the port will not automatically transition to the IS

(in-service) state when a good signal (not LOS) is detected. If the

Port Monitoring

Mode

is provisioned AUTO, the port automatically transitions to the IS (in-service) state when a good signal (not LOS) is detected, and the port is monitored/alarmed.

At the terminating nodes, use

View

→

Equipment

to access the required DS/E1 ports and verify the value of the

Port Monitoring Mode

parameter.

If required, use

Configuration

→

Equipment

to access DS1/E1 ports and change the value of the

Port Monitoring Mode

parameter.

.................................................................................................................................................................................................

Important! If the

Tributary Monitoring Mode

is provisioned NMON, the tributary is not monitored/alarmed and the tributary will not automatically transition to the IS

(in-service) state when a good signal (not UNEQ, AIS, LOP, SF) is detected. If the

Tributary Monitoring Mode

is provisioned AUTO, the tributary automatically

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-5

TDM service provisioning procedures Procedure 10-1: Establish DS1 or E1 service transitions to the IS (in-service) state when a good signal (not UNEQ, AIS, LOP,

SF) is detected, and the tributary is monitored/alarmed.

At the terminating nodes and pass-through nodes (UPSRs/BLSRs only), use

View

→

Equipment

to access the required tributaries and verify the value of the

Tributary

Monitoring Mode

parameter.

If required, use

Configuration

→

Equipment

to access tributaries and change the value of the

Tributary Monitoring Mode

parameter.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

10-6 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures

Procedure 10-2: Discontinue DS1 or E1 service

.................................................................................................................................................................................................................................

Overview

Use this procedure to discontinue end-to-end DS1 or E1 service.

Important! This procedure assumes that the Metropolis

®

DMX is in service and that a DS1/E1 port is being discontinued.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Verify that the work instructions specify the terminating nodes, pass-through nodes

(UPSRs/BLSRs only), DS/E1 port addresses, and cross-connections to be deleted.

Step

1

2

3

Complete the following steps to discontinue end-to-end DS1 or E1 service.

.................................................................................................................................................................................................

Using the work instructions, determine the DS1/E1 port to be discontinued.

.................................................................................................................................................................................................

At the terminating nodes, click the

Alarm List

button or select

Fault

→

NE Alarm List

from the System View menu to obtain an NE Alarm List and verify that no alarms are present. Clear all alarms before continuing this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! This step may activate the office alarms. The audible alarm may be suppressed by pressing the

ACO

push-button.

At the cross-connect panel or equivalent connection point at the terminating nodes, remove the DS1/E1 signal associated with the port being discontinued.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-7

TDM service provisioning procedures Procedure 10-2: Discontinue DS1 or E1 service

4

5

6

7

8

9

10

11

Result:

The

FAULT

LED flashes on the circuit pack with signals removed.

.................................................................................................................................................................................................

At the terminating nodes, click the

Alarm List

button or select

Fault

→

NE Alarm List

to obtain an NE Alarm List and verify that the correct DS1/E1 signal was removed.

.................................................................................................................................................................................................

At the terminating nodes, select

Configuration

→

Update System

→

Update States

to clear the DS1/E1 LOS alarms.

Result:

The flashing

FAULT

LEDs go off.

.................................................................................................................................................................................................

At the terminating nodes, click the

Alarm List

button or select

Fault

→

NE Alarm List

to obtain an NE Alarm List and verify that the DS1/E1 LOS alarm is cleared.

.................................................................................................................................................................................................

At the terminating nodes, use

View

→

Equipment

to access the required DS1/E1 ports and verify that the

Port Monitoring Mode

changed to AUTO.

.................................................................................................................................................................................................

Determine the cross-connections for the circuit being discontinued using the work instructions, or at the terminating nodes and non-terminating nodes (UPSRs/BLSRs only), use

View

→

Cross-Connections

to obtain a current list of cross-connections.

Record the source addresses (

SRC

) of the cross-connections to be deleted.

.................................................................................................................................................................................................

At the terminating nodes, use

Configuration

→

Cross-Connections

to access the

Cross-Connection Wizard and delete the add/drop cross-connections for all DS1/E1 service being removed.

(Refer to the cross-connection source addresses recorded in

Step 8 .)

Important! DS1/E1 slots cannot be unequipped without an alarm until all port cross-connections are removed.

.................................................................................................................................................................................................

If required, at each pass-through node (UPSRs/BLSRs only) use

Configuration

→

Cross-Connections

to access the Cross-Connection Wizard and delete the pass-through cross-connections for all DS1/E1 service being removed.

(Refer to the cross-connection source addresses recorded in

Step 8 .)

.................................................................................................................................................................................................

Important! The LNW6/7 28DS1/DS1PM circuit packs have 28 DS1 ports. The

LNW8 56DS1/E1 circuit pack has 56 DS1/E1 ports.

.................................................................................................................................................................................................................................

10-8 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-2: Discontinue DS1 or E1 service

12

If all ports on the circuit pack are being discontinued, you may remove the circuit pack, if required.

.................................................................................................................................................................................................

Have circuit packs been removed?

If...

Yes,

No,

Then...

Continue with

Step 13 .

Proceed to

Step 15 .

13

14

15

16

.................................................................................................................................................................................................

If circuit packs have been removed, update the internal equipment list. From the

System View menu select

Configuration

→

Update System

→

Update Inventory

.

Click

OK

.

.................................................................................................................................................................................................

Insert 177D application blanks or LNW98 Detectable Blank circuit packs into the empty slots, then go to

Step 16 .

.................................................................................................................................................................................................

If circuit packs have not been removed, provision the

Port Monitoring Mode

of the

DS1/E1 ports to AUTO or NMON, as required.

From the System View menu select

Configuration

→

Equipment

, expand the required circuit pack details, then select the DS1/E1 port.

Under the

Fault Management

section, select NMON (Not Monitored) or AUTO

(Automatic) for the

Port Monitoring Mode

.

Important! If the Port Monitoring Mode is NMON, the port is not monitored/alarmed, and the port will not automatically transition to the in service state if a valid signal is detected. If the Port Monitoring Mode is AUTO, the port automatically transitions to the in service state if a valid signal is detected and the port is monitored/alarmed.

.................................................................................................................................................................................................

At the terminating nodes and non-terminating nodes (UPSRs/BLSRs only), click the

Alarm List

button or select

Fault

→

NE Alarm List

to obtain an NE Alarm List and verify that no alarms are present.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-9

TDM service provisioning procedures

Procedure 10-3: Establish DS3 or EC-1 service

.................................................................................................................................................................................................................................

Overview

Use this procedure to establish end-to-end DS3 or EC-1 service.

Important! This procedure assumes that the Metropolis

®

DMX shelf and network have been properly equipped and tested. If the Metropolis

®

DMX shelf has not been properly equipped, refer to

Chapter 5, “Node turnup procedures” . If the

network has not been properly configured, refer to

Chapter 9, “Network configuration procedures” .

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Verify that the work instructions specify the terminating nodes, pass-through nodes

(UPSRs/BLSRs only), DS3/EC-1 port addresses, the DS3/EC-1 port parameters to provision, and the cross-connections to be established.

Step

Complete the following steps to establish end-to-end DS3 or EC-1 service.

1

2

.................................................................................................................................................................................................

Click the

Alarm List

button or select

Fault

→

NE Alarm List

from the System View menu to obtain an NE Alarm List and verify that no alarms are present. Clear all alarms before continuing this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

At the terminating nodes, select

View

→

Equipment

to verify that the proper service and protection DS3/EC-1 circuit packs have been installed in the Function Unit group

(A, B, C, or D) used for this service.

.................................................................................................................................................................................................

3

If circuit packs have not been installed, install circuit packs as required.

.................................................................................................................................................................................................................................

10-10 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-3: Establish DS3 or EC-1 service

4

5

6

7

8

Reference:

Procedure 4-6: “Install DS3/EC1 circuit packs” (p. 4-32)

.................................................................................................................................................................................................

At the terminating nodes of the circuit being established, determine which DS3/EC-1 ports are to be put into service and what port parameters to provision using the work instructions.

.................................................................................................................................................................................................

At the terminating nodes, select

Configuration

→

Equipment

. Expand the required circuit pack details, then select the DS3/EC-1 port to provision for the circuit being established. Provision parameters as required.

If the

Port Monitoring Mode

is provisioned NMON, the port is not monitored/alarmed and the port will not automatically transition to the IS

(in-service) state when a good signal (not LOS) is detected. If the

Port Monitoring

Mode

is provisioned AUTO, the port automatically transitions to the IS (in-service) state when a good signal (not LOS) is detected, and the port is monitored/alarmed.

Reference:

(p. 4-37)

Procedure 4-7: “Provision DS3/EC1 circuit packs/ports for service”

.................................................................................................................................................................................................

Verify that the DS3/EC-1 cable connections have been made from the terminating nodes to the cross-connect panel or equivalent connection points.

.................................................................................................................................................................................................

Determine the necessary add/drop and pass-through (UPSRs/BLSRs only) cross-connections for each node from the work instructions.

.................................................................................................................................................................................................

At the terminating nodes and pass-through nodes (UPSRs/BLSRs only), select

Configuration

→

Cross-Connections

to access the Cross-Connection Wizard and establish the necessary cross-connections. Use the following references as examples.

Reference:

•

Procedure 10-5: “Make VT1.5 or STS-n cross-connections, single OC-3/OC-12

UPSR configuration” (p. 10-16)

•

Procedure 10-6: “Make Function unit UPSR, hairpin, and Main to Function unit

UPSR cross-connections” (p. 10-22)

•

Procedure 10-7: “Make 1+1 (linear extension) cross-connections” (p. 10-26)

•

Procedure 10-8: “Make single-homed cross-connections” (p. 10-32)

•

Procedure 10-9: “Make dual-homed cross-connections” (p. 10-39)

•

Procedure 10-11: “Establish dual ring interworking (DRI) connections”

(p. 10-56)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-11

TDM service provisioning procedures Procedure 10-3: Establish DS3 or EC-1 service

9

10

11

•

Procedure 10-12: “Provision DS1/DS3 locked cross-connections on a UPSR”

(p. 10-64)

•

Procedure 10-13: “Provision VT1.5 cross-connections on a BLSR” (p. 10-71)

.................................................................................................................................................................................................

Perform the DS3/EC-1 end-to-end transmission test for each circuit being put into service, as required.

Reference:

•

Procedure 14-10: “Perform DS3 transmission test” (p. 14-74)

•

Procedure 14-11: “Perform EC-1 transmission test” (p. 14-80)

.................................................................................................................................................................................................

Important! If the

Port Monitoring Mode

is provisioned NMON, the port is not monitored/alarmed and the port will not automatically transition to the IS

(in-service) state when a good signal (not LOS) is detected. If the

Port Monitoring

Mode

is provisioned AUTO, the port automatically transitions to the IS (in-service) state when a good signal (not LOS) is detected, and the port is monitored/alarmed.

At the terminating nodes, use

View

→

Equipment

to access the required DS3/EC-1 ports and verify the value of the

Port Monitoring Mode

parameter.

If required, use

Configuration

→

Equipment

to access DS3/EC-1 ports and change the value of the

Port Monitoring Mode

parameter.

.................................................................................................................................................................................................

Important! If the

Tributary Monitoring Mode

is provisioned NMON, the tributary is not monitored/alarmed and the tributary will not automatically transition to the IS

(in-service) state when a good signal (not UNEQ, AIS, LOP, SF) is detected. If the

Tributary Monitoring Mode

is provisioned AUTO, the tributary automatically transitions to the IS (in-service) state when a good signal (not UNEQ, AIS, LOP,

SF) is detected, and the tributary is monitored/alarmed.

At the terminating nodes and pass-through nodes (UPSRs/BLSRs only), use

View

→

Equipment

to access the required tributaries and verify the value of the

Tributary

Monitoring Mode

parameter.

If required, use

Configuration

→

Equipment

to access tributaries and change the value of the

Tributary Monitoring Mode

parameter.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

10-12 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures

Procedure 10-4: Discontinue DS3 or EC-1 service

.................................................................................................................................................................................................................................

Overview

Use this procedure to discontinue end-to-end DS3 or EC-1 service.

Important! This procedure assumes that the Metropolis

®

DMX is in service and that a DS3/EC-1 port is being discontinued.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Verify that the work instructions specify the terminating nodes, pass-through nodes

(UPSR/BLSRs only), DS3/EC-1 port addresses, and cross-connections to be deleted.

Step

1

2

3

Complete the following steps to discontinue end-to-end DS3 or EC-1 service.

.................................................................................................................................................................................................

Using the work instructions, determine the DS3/EC-1 port to be discontinued.

.................................................................................................................................................................................................

At the terminating nodes, click the

Alarm List

button or select

Fault

→

NE Alarm List

from the System View menu to obtain an NE Alarm List and verify that no alarms are present. Clear all alarms before continuing this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! This step may activate the office alarms. The audible alarm may be suppressed by pressing the

ACO

push-button.

At the cross-connect panel or equivalent connection point at the terminating nodes, remove the DS3/EC-1 signal associated with the port being discontinued.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-13

TDM service provisioning procedures Procedure 10-4: Discontinue DS3 or EC-1 service

4

5

6

7

8

9

10

11

Result:

The

FAULT

LED flashes on the circuit pack with signals removed.

.................................................................................................................................................................................................

At the terminating nodes, click the

Alarm List

button or select

Fault

→

NE Alarm List

to obtain an NE Alarm List and verify that the correct DS3/EC-1 signal was removed.

.................................................................................................................................................................................................

At the terminating nodes, select

Configuration

→

Update System

→

Update States

to clear the DS3/EC-1 LOS alarms.

Result:

The flashing

FAULT

LEDs go off.

.................................................................................................................................................................................................

At the terminating nodes, click the

Alarm List

button or select

Fault

→

NE Alarm List

to obtain an NE Alarm List and verify that the DS3/EC-1 LOS alarm is cleared.

.................................................................................................................................................................................................

At the terminating nodes, use

View

→

Equipment

to access the required DS3/EC-1 ports and verify that the

Port Monitoring Mode

changed to AUTO.

.................................................................................................................................................................................................

Determine the cross-connections for the circuit being discontinued using the work instructions, or at the terminating nodes and non-terminating nodes (UPSRs/BLSRs only), use

View

→

Cross-Connections

to obtain a current list of cross-connections.

Record the source addresses (

SRC

) of the cross-connections to be deleted.

.................................................................................................................................................................................................

At the terminating nodes, use

Configuration

→

Cross-Connections

to access the

Cross-Connection Wizard and delete the add/drop cross-connections for all DS3/EC-1 service being removed.

(Refer to the cross-connection source addresses recorded in

Step 8 .)

Important! DS3/EC-1 slots cannot be unequipped without an alarm until all port cross-connections are removed.

.................................................................................................................................................................................................

If required, at each pass-through node (UPSRs/BLSRs only) use

Configuration

→

Cross-Connections

to access the Cross-Connection Wizard and delete the pass-through cross-connections for all DS3/EC-1 service being removed.

(Refer to the cross-connection source addresses recorded in

Step 8 .)

.................................................................................................................................................................................................

Important! The LNW16 circuit packs have 12 DS3/EC-1 ports. The LNW19/19B circuit packs have 48 DS3/EC-1 ports.

.................................................................................................................................................................................................................................

10-14 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-4: Discontinue DS3 or EC-1 service

12

13

14

15

If all the DS3/EC-1 ports on the circuit pack are being discontinued, you may remove the circuit pack, if required.

.................................................................................................................................................................................................

If circuit packs have been removed continue with

Step 13 , otherwise proceed to Step

14 .

.................................................................................................................................................................................................

If circuit packs have been removed, update the Metropolis

®

DMX internal equipment list.

From the System View menu select

Configuration

→

Update System

→

Update

Inventory

.

Click

OK

.

Insert 177D application blanks or LNW98 Detectable Blank circuit packs into empty slots, then proceed to

Step 15 .

.................................................................................................................................................................................................

If circuit packs have not been removed, provision the

Port Monitoring Mode

of the

DS3/EC-1 ports to AUTO or NMON, as required.

From the System View menu select

Configuration

→

Equipment

, expand the required circuit pack details, then select the DS3/EC-1 port.

Under the

Fault Management

section, select NMON (Not Monitored) or AUTO

(Automatic) for the

Port Monitoring Mode

.

Important! If the Port Monitoring Mode is NMON, the port is not monitored/alarmed, and the port will not automatically transition to the in service state if a valid signal is detected. If the Port Monitoring Mode is AUTO, the port automatically transitions to the in service state if a valid signal is detected and the port is monitored/alarmed.

.................................................................................................................................................................................................

At the terminating nodes and non-terminating nodes (UPSRs/BLSRs only), click the

Alarm List

button or select

Fault

→

NE Alarm List

to obtain an NE Alarm List and verify that no alarms are present.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-15

TDM service provisioning procedures

Procedure 10-5: Make VT1.5 or STS-n cross-connections, single OC-3/OC-12 UPSR configuration

.................................................................................................................................................................................................................................

Overview

Use this procedure as an example for VT1.5 or STS-n cross-connections.

This procedure uses examples of cross-connections to DS1 and DS3 interfaces to illustrate the steps involved in cross-connections in a single UPSR ring configuration.

This same procedure could also be used to make any allowable VT1.5, STS-1, STS-3c,

STS-12c, or STS-48c cross-connection. This procedure uses the CIT Cross-Connection

Wizard commands to illustrate the provisioning. The same provisioning may be made using the TL1

ent-crs-( )

command. Note that E1 services require an STS-3c cross-connection.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Verify that you have the work instructions for this procedure stating the circuit pack and port options to be set, the pass-through and terminating end nodes, and cross-connections being made.

Step

1

2

Complete the following steps to make the necessary cross-connections.

.................................................................................................................................................................................................

Log in to any node in each ring in the network and retrieve a map of the network which lists all the systems and how they are connected to each other. From the System

View menu select

Administration

→

OSI Routing Map

or

Administration

→

OSI

Neighbor Map

.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on the work order or circuit order.

.................................................................................................................................................................................................................................

10-16 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-5: Make VT1.5 or STS-n cross-connections, single OC-3/OC-12 UPSR configuration

3

4

5

6

.................................................................................................................................................................................................

From work order or circuit order, determine the terminating (drop) nodes and the pass-through nodes for the service being established.

Important! In ring configurations, use the following general rules for establishing cross-connections.

1. All cross-connections to/from the same STS-1 timeslot must be provisioned the same, either all VT1.5 or STS-1.

2. If all 28 VT1.5s (DS1s) in an STS-1 are being passed through at a node in a

VT1.5 path-switched ring, then the cross-connection may be provisioned as either a pass-through STS-1 or VT1.5. However, if you are dropping VT1.5s

from the pass through node in the future, you should provision the pass-throughs as VT1.5 cross-connections.

See Metropolis

®

DMX Access Multiplexer TL1 Message Details, 365-372-306 for more detailed information on types of cross-connections, and restrictions regarding rates, circuit pack types, and VT granularity.

.................................................................................................................................................................................................

Log in to each node in the network and verify that each shelf is properly equipped for the service being established. From the System View menu select

View

→

Equipment

.

.................................................................................................................................................................................................

From work order or circuit order, determine the cross-connections to be made at each node associated with the service to be established. See

Figure 10-1, “Path protected

OC-48 ring network (DS1 to DS1) with VT1.5 cross-connections” (p. 10-20)

and

Figure 10-2, “Path protected OC-48 ring network (DS3 to DS3) with STS-1 cross-connections” (p. 10-20)

for DS1/DS3 cross-connection examples.

Important! Cross-connections supporting DS3 services are STS-1 cross-connections. Cross-connections supporting DS1 services may be either STS-1 or VT1.5 cross-connections. Use VT1.5 cross-connections for DS1 services if you expect to cross connect only some of the VT1.5 signals in the STS-1 channel. If

STS-1 cross-connections are made at a shelf, there is a fixed mapping of all 28

VT1.5 cross-connections to a specific shelf group.

.................................................................................................................................................................................................

Starting at one of the terminating nodes for the circuit being established, at each node in the ring use

View

→

Cross-Connections

from the System View menu to verify that the cross-connections specified on the work order or circuit order may be made. If the cross-connections are already assigned to another service or improperly assigned, refer trouble to the organization responsible for facility design. Improperly assigned cross-connections may have to be deleted.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-17

TDM service provisioning procedures Procedure 10-5: Make VT1.5 or STS-n cross-connections, single OC-3/OC-12 UPSR configuration

7

8

9

10

11

.................................................................................................................................................................................................

At all non-terminating nodes in the network, provision pass-through cross-connections.

From the System View menu select

Configuration

→

Cross-Connections

, then use the Cross-Connection Wizard to make the cross-connections. Select

2-Way

Point-to-Point, Through

for pass through cross-connections.

.................................................................................................................................................................................................

At the terminating (add/drop) nodes of the circuit being established, establish the terminating cross-connections. From the System View menu select

Configuration

→

Cross-Connections

, then use the Cross-Connection Wizard to make the

UPSR Ring

Add/Drop

cross-connections.

Important! The channel mode provisioning feature provides In-Service, Automatic, or Not Monitored states for VT and STS channels similar to the port modes for

DS1 and DS3 ports. At installation, or when a cross connection is made to a point of termination, the channel is in the Automatic mode and alarming is suppressed until a valid signal is received. The channel must receive a good signal from either side of the ring to cause the channel to transition to in-service.

.................................................................................................................................................................................................

After all cross-connections have been made, verify that the channels have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Equipment

.

Result:

The View Equipment window opens.

Alarms are not reported until the channel state transitions to in-service (IS) which happens only when a good signal is received. Cross-connections create connections to both sides of the ring. The channel state will transition once a good signal is received on either side of the ring.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required DS1/DS3 port, then click

Select

at the bottom of the window. Verify the port AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Under

Port Data/Fault

in the parameter display, verify the

Port Monitoring Mode

is

IS (in service). If the

Port Monitoring Mode

is IS, then Stop, you have completed this procedure. Otherwise, perform one of the following:

•

If the

Port Monitoring Mode

is NMON (Not Monitored),

.................................................................................................................................................................................................................................

10-18 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-5: Make VT1.5 or STS-n cross-connections, single OC-3/OC-12 UPSR configuration

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, select the required DS1/DS3 port and then click

Select

at the bottom of the window.

2. Under the

Fault Management

section, select AUTO (Automatic) for the

Port

Monitoring Mode

.

3. Click

Apply

at the bottom of the window.

4. Click

Close

to exit the window, then repeat this procedure from

Step 9 .

•

If the

Port Monitoring Mode

is AUTO:

Check the connections at the local cross-connect panel (or equivalent connection point).

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-19

TDM service provisioning procedures Procedure 10-5: Make VT1.5 or STS-n cross-connections, single OC-3/OC-12 UPSR configuration

Figure 10-1 Path protected OC-48 ring network (DS1 to DS1) with VT1.5

cross-connections

Node 1

DMX OC-48

Node 2

DMX OC-48

M 1 M 2 M 1 M 2

Ring 1

Ring 2

A

DS1

B C D G

Rate: VT1.5

UPSR Ring Add/Drop cross-connection: m1-1-1-1-1,a1-1-1-1

A B

C

D G

2-Way Point-to-Point, Through cross-connections: m1-1-1-1-1, m2-1-1-1-1

M 2

Node 5

DMX OC-48

M 1

IN

OUT

Node 4

DMX OC-48

M 2 M 1

A

DS1

B C D G

Rate: VT1.5

UPSR Ring Add/Drop cross-connection: m1-1-1-1-1,a1-1-1-1

A B C D G

2-Way Point-to-Point, Through cross-connections: m1-1-1-1-1, m2-1-1-1-1

NC-DMX-189-2

.................................................................................................................................................................................................................................

10-20 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-5: Make VT1.5 or STS-n cross-connections, single OC-3/OC-12 UPSR configuration

Figure 10-2 Path protected OC-48 ring network (DS3 to DS3) with STS-1 cross-connections

Node 1

DMX OC-48

Node 2

DMX OC-48

Ring 1

M 1 M 2

M 1 M 2

Ring 2

A

DS3

B C D G

A B C D G

Rate: STS3

UPSR Ring Add/Drop cross-connection: m1-1-1,a1-1

2-Way Point-to-Point, Through cross-connections: m1-1-1, m2-1-1

Node 5

DMX OC-48

M 2 M 1

OUT

IN

IN

OUT

Node 4

DMX OC-48

M 2 M 1

A

DS3

B C D G A B C D G

Rate: STS3

UPSR Ring Add/Drop cross-connection: m1-1-1,a1-1

2-Way Point-to-Point, Through cross-connections: m1-1-1, m2-1-1

NC-DMX-190-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-21

TDM service provisioning procedures

Procedure 10-6: Make Function unit UPSR, hairpin, and Main to Function unit UPSR cross-connections

.................................................................................................................................................................................................................................

Overview

Use this procedure as an example to provision certain types of cross-connections on a single Metropolis

®

DMX Access Multiplexer shelf. See Metropolis

®

DMX Access

Multiplexer TL1 Message Details, 365-372-306 for rates, types, restrictions, and allowable cross-connections. Note that E1 services require an STS-3c cross-connection.

This procedure is intended only to illustrate some of the many types of cross-connections, not to illustrate end-to-end service provisioning.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Verify that the UPSR network configurations have been established using

Procedure

9-9: “Establish subtending low-speed UPSR/BLSR” (p. 9-98) , if required.

4. Determine the slots, circuit packs, ports, cross-connection types and cross-connection rates.

5. Obtain the work instructions for this procedure.

Step

1

Complete the following steps to make the necessary cross-connections.

.................................................................................................................................................................................................

Refer to

Figure 10-3, “Cross-Connection examples” (p. 10-23)

for examples of some of the possible cross-connections. These examples show OC-48 optical rates in the Main slots and OC-3/12 optical rates in the Function/Growth slots. Other configurations with

OC-192 in the Main slots and OC-3/12/48 in the Function/Growth slots are also applicable.

.................................................................................................................................................................................................................................

10-22 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-6: Make Function unit UPSR, hairpin, and

Main to Function unit UPSR cross-connections

These examples are only brief descriptions of possible cross-connections. Refer to

Metropolis

®

DMX Access Multiplexer TL1 Message Details, 365-372-306 for more information about allowable cross-connections.

Figure 10-3 Cross-Connection examples

DMX

OC48 OC48 OC48

M1 M2 M1

DMX

M2

OC48

A1 A2

B C D G

OC3/OC12

UPSR Ring

Completion

OC48

M1

DMX

M2

OC48

OC3/OC12

FN UPSR Ring to FN UPSR Ring

A1

A2

B C

D1

D2

G

OC48

M1

DMX

M2

OC48

A1 A2

B C D G

OC-48 UPSR to

FN OC3/OC12

UPSR Ring

®

DMX = Metropolis DMX Access Multiplexer

FN OC3/OC12

UPSR Ring to DS1/DS3

A1 A2

B C1 C2 D1 D2 G

OC3/OC12

UPSR Ring to OC-n 1 +1 nc-dmx-179

2

3

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Routing Map window opens.

.................................................................................................................................................................................................

Verify that the ring configurations are the same as specified in the work instructions.

Important! All differences between the work instructions and the actual ring configuration must be resolved before continuing.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-23

TDM service provisioning procedures Procedure 10-6: Make Function unit UPSR, hairpin, and

Main to Function unit UPSR cross-connections

4

5

6

7

8

9

10

11

.................................................................................................................................................................................................

From the System View menu of the subject Metropolis

®

Equipment

.

DMX node, select

View

→

Result:

The View Equipment window opens.

.................................................................................................................................................................................................

Find the circuit pack, port, and tributaries being used for this service. Select the entity to view, then click the

Select

button at the bottom of the window. View the provisioning details for the selected entity and verify the entities are properly provisioned.

.................................................................................................................................................................................................

If the entities are not provisioned properly, use the procedures in this section to condition the circuit packs/ports for service.

.................................................................................................................................................................................................

From your work instructions, determine the cross-connections to be made for the service being established.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

to verify that the cross-connections specified on the work instructions may be made. If cross-connections are already assigned or improperly assigned, refer trouble to the provisioning organization. Improperly assigned cross-connections may have to be deleted, or a different timeslot must be selected for the service being selected.

.................................................................................................................................................................................................

Select

Configuration

→

Cross-Connections

from the System View menu to start the

Cross-Connection Wizard.

.................................................................................................................................................................................................

In the Cross-Connection Wizard, select

Create a new cross-connection

, select the type of cross-connection, then follow the wizard directions.

.................................................................................................................................................................................................

After all cross-connections have been made, verify that the channels have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Equipment

.

.................................................................................................................................................................................................................................

10-24 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-6: Make Function unit UPSR, hairpin, and

Main to Function unit UPSR cross-connections

12

13

Result:

The View Equipment window opens.

Alarms are not reported until the channel state transitions to in-service (IS) which happens only when a good signal is received. Cross-connections create connections to both sides of the ring. The channel state will transition once a good signal is received on either side of the ring.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required port, then click

Select

at the bottom of the window. Verify the port AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Under

Port Data/Fault

in the parameter display, verify the

Port Monitoring Mode

is

IS (in service). If the

Port Monitoring Mode

is IS, then Stop, you have completed this procedure. Otherwise, perform one of the following:

•

If the

Port Monitoring Mode

is NMON (Not Monitored),

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, select the required port and then click

Select

at the bottom of the window.

2. Under the

Fault Management

section, select AUTO (Automatic) for the

Port

Monitoring Mode

.

3. Click

Apply

at the bottom of the window.

4. Click

Close

to exit the window, then repeat this procedure from

Step 11 .

•

If the

Port Monitoring Mode

is AUTO:

Check the connections at the local cross-connect panel (or equivalent connection point).

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-25

TDM service provisioning procedures

Procedure 10-7: Make 1+1 (linear extension) cross-connections

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision cross-connections at a Metropolis

®

DMX Access

Multiplexer shelf serving as a terminating node for a 1+1 optical extension. See

Metropolis

®

DMX Access Multiplexer TL1 Message Details, 365-372-306 for rates, types, restrictions, and allowable cross-connections. Note that E1 services require an

STS-3c cross-connection.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Verify that the 1+1 optical extension has been established using the procedures in

Procedure 9-5: “Establish low-speed 1+1 linear optical extension” (p. 9-69) .

4. Determine the cross-connection types, rates, and terminating nodes for the optical extension.

5. Obtain the work instructions for this procedure.

Step

1

2

Complete the following steps to make the necessary cross-connections.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the Metropolis

®

DMX host nodes providing the 1+1 extension.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Refer to

Figure 10-4, “Two Metropolis

®

DMX UPSRs connected in a 1+1 (linear extension)” (p. 10-27)

for an example of two Metropolis

®

DMX UPSRs connected in a

1+1 (linear extension) configuration.

.................................................................................................................................................................................................................................

10-26 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-7: Make 1+1 (linear extension) cross-connections

Note that this example depicts OC-48 optical line rates. Other applications and line rates are also possible.

Figure 10-4 Two Metropolis

®

Node 1

DMX

DMX UPSRs connected in a 1+1 (linear extension)

Node 2

DMX

MAIN 1 MAIN 2 MAIN 1 MAIN 2

OC-48

IN

TSI

TSI

OUT

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

OC-48

OC-48

MAIN 2

1+1 (linear) Extension

Service Drop

Node 4

DMX

MAIN 1

TSI

OC-48

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Node 1

DMX

MAIN 2

TSI

MAIN 1

IN

OUT

MAIN 2

Node 3

DMX

MAIN 1

TSI

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Node 2

DMX

MAIN 2

TSI

MAIN 1

1 +1 (Linear) Extensions

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

OC-48

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

MAIN 1

Node 3

DMX

MAIN 2

TSI

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

OC-48 nc-dmx-185

3

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

to retrieve a node-to-node listing of every node on the Metropolis

®

DMX rings.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-27

TDM service provisioning procedures Procedure 10-7: Make 1+1 (linear extension) cross-connections

4

5

6

7

8

9

10

This command may take several minutes to complete depending on the size of the network.

Result:

The OSI Routing Map window opens.

.................................................................................................................................................................................................

Verify that the network configuration is the same as specified in the work instructions.

Important! All differences between the work instructions and the actual ring configuration must be resolved before continuing.

.................................................................................................................................................................................................

From the work instructions, determine the terminating (add/drop) nodes at each end of the 1+1 optical extension.

.................................................................................................................................................................................................

One at a time, use the WaveStar

®

CIT to log in to each terminating node. From the

System View menu at each node, select

View

→

Equipment

.

Result:

The View Equipment window opens.

.................................................................................................................................................................................................

Find the circuit pack, port, and/or tributaries being used for this service. Select the entity to view, then click the

Select

button at the bottom of the window. View the provisioning details for the selected entity and verify the entities are properly provisioned.

.................................................................................................................................................................................................

If the entities are not provisioned properly, use the procedures in this chapter to condition the circuit packs/ports for service.

.................................................................................................................................................................................................

From your work instructions, determine the type of cross-connections to be made at each node for the service being established.

.................................................................................................................................................................................................

At each of the terminating nodes for the circuit being established, select

View

→

Cross-Connections

from the System View menu to verify that the cross-connections specified on the work instructions may be made. If cross-connections are already assigned or improperly assigned, refer trouble to the provisioning organization.

Improperly assigned cross-connections may have to be deleted, or a different timeslot must be selected for the service being selected.

.................................................................................................................................................................................................................................

10-28 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures

11

Procedure 10-7: Make 1+1 (linear extension) cross-connections

.................................................................................................................................................................................................

Select

Configuration

→

Cross-Connections

from the System View menu to start the

Cross-Connection Wizard. Use the Cross-Connection Wizard to provision the add/drop cross-connections at each terminating node serving the optical extension.

Figure 10-5, “1+1 STS-3c cross-connection examples” (p. 10-29)

illustrates an example network with 1+1 STS-3c cross-connections at Metropolis

®

DMX nodes 1 and 4.

Figure 10-5 1+1 STS-3c cross-connection examples

Node 1

DMX

MAIN 1

TSI

MAIN 2

OC-48

Node 2

DMX

MAIN 1

TSI

MAIN 2

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

OC-48

OC-48

1+1 (linear) Extension

Service Drop

Node 4

DMX

MAIN 2

TSI

MAIN 1

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Node 1

DMX

MAIN 2

TSI

MAIN 1

OC-48

IN

OUT

Node 3

DMX

MAIN 2

TSI

MAIN 1

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Node 2

DMX

MAIN 2

TSI

MAIN 1

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Port application = 1+1

OC-48

1 +1 (Linear) Extensions

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Node 3

DMX

MAIN 1

TSI

MAIN 2

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

AID Structure for OC-3

Function Group Slot Port STS trib VTGroup VT1.5

(a,b,c,d,g) 1,2 (1-x) (1-3) (1-7, all) (1-4, all)

AID Structure for OC-12

Function Group Slot Port STS trib VTGroup VT1.5

(a,b,c,d,g) 1,2 (1-x) (1-12) (1-7, all) (1-4, all)

Example aid for an OC-3 using Port 2, STS3c to Main trib #7: m1-1-7,a1-2-1

NC-DMX-186-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-29

TDM service provisioning procedures Procedure 10-7: Make 1+1 (linear extension) cross-connections

12

13

14

15

16

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connection has been made.

.................................................................................................................................................................................................

If other cross-connections are to be made, for example, from a terminating node in one ring to a terminating node in the other ring, refer to the appropriate procedures in this chapter to establish the particular service.

.................................................................................................................................................................................................

After all cross-connections have been made, verify that the channels have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Equipment

.

Result:

The View Equipment window opens.

The provisioned cross-connections create connections to both sides of the ring. The channel state will transition once a good signal is received on either side of the ring. Note there will be channel states on the tributaries of the 1+1 interface as well.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required port, then click

Select

at the bottom of the window. Verify the port AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Under

Port Data/Fault

in the parameter display, verify the

Port Monitoring Mode

is

IS (in service). If the

Port Monitoring Mode

is IS, then Stop, you have completed this procedure. Otherwise, perform one of the following:

•

If the

Port Monitoring Mode

is NMON (Not Monitored),

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, select the required port and then click

Select

at the bottom of the window.

2. Under the

Fault Management

section, select AUTO (Automatic) for the

Port

Monitoring Mode

.

3. Click

Apply

at the bottom of the window.

4. Click

Close

to exit the window, then repeat this procedure from

Step 14 .

•

If the

Port Monitoring Mode

is AUTO:

Check the connections at the local cross-connect panel (or equivalent connection point).

.................................................................................................................................................................................................................................

10-30 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-7: Make 1+1 (linear extension) cross-connections

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-31

TDM service provisioning procedures

Procedure 10-8: Make single-homed cross-connections

.................................................................................................................................................................................................................................

Overview

Use this procedure as an example for making cross-connections in Metropolis

®

DMX single-homed ring configurations. This procedure uses the CIT Cross-Connection

Wizard commands to illustrate the provisioning of the cross-connections. The TL1

ent-crs-( )

command may be used to perform the same provisioning.

See Metropolis

®

DMX Access Multiplexer TL1 Message Details, 365-372-306 for rates, types, restrictions, and allowable cross-connections. Note that E1 services require an

STS-3c cross-connection.

Although this example illustrates OC-3/12 rings single-homing to a OC-48 UPSR ring, the same procedure applies for OC-3/12/48 subtending rings to an OC-192 UPSR.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Verify that the single-homed network has been established using the procedures in

Procedure 9-6: “Establish single-homed network configurations” (p. 9-76) .

4. Determine the cross-connection types, rates, terminating nodes, host nodes, and pass-through nodes.

5. Obtain the work instructions for this procedure.

Step

1

Complete the following steps to make the necessary cross-connections in single-homed configurations.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to the Metropolis

®

DMX host node being used for single homing.

.................................................................................................................................................................................................................................

10-32 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-8: Make single-homed cross-connections

2

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Refer to

Figure 10-6, “Single-Homed Metropolis

®

DMX ring example” (p. 10-33)

for an example of a simple single-homed Metropolis

®

DMX ring configuration. Note that this example uses an OC-48 ring as a backbone ring and OC-3/12 subtending nodes.

Other applications may be at different optical rates.

Figure 10-6 Single-Homed

Metropolis

®

Node 1

DMX

DMX ring example

Node 2

DMX

MAIN 1 MAIN 2

OC-48

MAIN 1 MAIN 2

TSI TSI

OC-48

OC-48

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Service Drop

OC-48

Node 5

DMX

MAIN 2

TSI

MAIN 1

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

OC-3/12

OC-48

Node 7

DDM-2000

OC-3/12 Shelf

MAIN 1

TSI

MAIN 2

A

1

A

2

B

1

B

2

C

1

C

2

Service Drop

OC-3/12

IN

OUT

Node 4

DMX

MAIN 2

TSI

MAIN 1

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

OC-48 nc-dmx-183

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-33

TDM service provisioning procedures Procedure 10-8: Make single-homed cross-connections

3

4

5

6

7

8

9

10

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

and/or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node on this Metropolis

®

DMX ring.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the ring configuration is the same as specified in the work instructions.

Important! All differences between the work instructions and the actual ring configuration must be resolved before continuing.

.................................................................................................................................................................................................

From the work instructions, determine the terminating (add/drop) nodes and the pass-through nodes for the particular service that is being established.

.................................................................................................................................................................................................

One at a time, use the WaveStar

®

CIT to log in to each node. From the System View menu at each node, select

View

→

Equipment

.

Result:

The View Equipment window opens.

.................................................................................................................................................................................................

Find the circuit pack, port, and/or tributaries being used for this service. Select the entity to view, then click the

Select

button at the bottom of the window. View the provisioning details for the selected entity and verify the entities are properly provisioned.

.................................................................................................................................................................................................

Use product documentation for non Metropolis

®

proper circuit pack/port provisioning details.

DMX nodes in the network to verify

.................................................................................................................................................................................................

If the entities are not provisioned properly, use the procedures in this section to condition the circuit packs/ports for service.

.................................................................................................................................................................................................

From your work instructions, determine the type of cross-connections to be made at each node for the service being established.

.................................................................................................................................................................................................................................

10-34 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-8: Make single-homed cross-connections

Figure 10-7, “Network with single-homed cross-connections example” (p. 10-36)

illustrates an example network with single-homed cross-connections at Metropolis

®

DMX node 5.

For single homed configurations using a port

Application

of UPSR, the cross-connection command at the host node must include the cross-connection channel application (

chappl

) parameter for this example at Node5:

2-Way Point-to-Point,

Add/Drop, Unswitched

(m1-1-1-3-1,a1-2-1-3-1).

Ports that connect the subtending ring to the Metropolis

®

DMX that are provisioned for UPSR protection and the cross-connection channel application of UNSWITCHED transport traffic over the Metropolis

®

DMX UPSR without any protection switching by

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-35

TDM service provisioning procedures Procedure 10-8: Make single-homed cross-connections the Metropolis

®

DMX nodes on the backbone ring. The end-of-path NEs [Node7 and

Node1] do the path protection switching.

Figure 10-7 Network with single-homed cross-connections example

Node 1

DMX

Node 2

DMX

MAIN 1

TSI

MAIN 2

OC-48

MAIN 1

TSI

MAIN 2

OC-48

OC-48

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

G 2

G 1

D 2

D 1

C 2

C 1

B 2

B 1

A 2

A 1

Service Drop

2-Way Point-to-Point, Add/Drop, Unswitched cross-connection at Node 5 to OC-3 Port 2, STS trib 1, VTG 3, VT1.5 #1: m1-1-1-3-1:a1-2-1-3-1

Node 5

DMX

MAIN 2

TSI

MAIN 1

OC-48

IN

OUT

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Node 4

DMX

MAIN 2

TSI

MAIN 1

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Port application = UPSR

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

OC-3/12

Node 7

DDM-2000

OC-3/12 Shelf

MAIN 1

TSI

MAIN 2

OC-3/12

OC-48

OC-48

AID Structure for OC-3

Function Group Slot Port STS trib VTGroup VT1.5

(a,b,c,d,g) 1,2 (1-x) (1-3) (1-7, all) (1-4, all)

AID Structure for OC-12

Function Group Slot Port STS trib VTGroup VT1.5

(a,b,c,d,g) 1,2 (1-x) (1-12) (1-7, all) (1-4, all)

AID structure for OC-48 in Main:

Group Slot Line STS trib VTGroup VT1.5

(m) 1,2 (1-x) (1-48) (1-7, all) (1-4, all)

A

1

A

2

B

1

B

2

C

1

C

2

AID Structure for DS-1 in DDM-2000 OC-3

Function Group Circuit Pack Port

(a,b,c) (1-7) (1-4)

Example: AID for a 1x7 Ds 1 using STS-1,

VTG 3, and VT1.5 1

ENT-CRS-VT1:tid:m-1-3-1,c-3-1:ctag;

NC-DMX-184A-2

Important! Cross-connections supporting DS3 services are STS-1 cross-connections. Cross-connections supporting DS1 services may be either STS-1 or VT1.5 cross-connections. Use VT1.5 cross-connections for DS1 services if you expect to cross connect only a portion of the VT1.5 signals in the STS-1 channel or if the VT1.5s are coming from different places. If STS-1 cross-connections are made at a shelf, there is a fixed mapping of all 28 VT1.5 cross-connections to a specific shelf group.

.................................................................................................................................................................................................................................

10-36 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-8: Make single-homed cross-connections

11

12

13

14

15

.................................................................................................................................................................................................

Starting at the host node for the circuit being established, select

View

→

Cross-Connections

from the System View menu at each node in the ring to verify that the cross-connections specified on the work instructions may be made. If cross-connections are already assigned or improperly assigned, refer trouble to the provisioning organization. Improperly assigned cross-connections may have to be deleted, or a different timeslot must be selected for the service being selected.

.................................................................................................................................................................................................

Select

Configuration

→

Cross-Connections

from the System View menu to start the

Cross-Connection Wizard. Use the Cross-Connection Wizard at all nonterminating nodes in the network to provision pass-through cross-connections.

.................................................................................................................................................................................................

Use the Cross-Connection Wizard at the terminating (add/drop) nodes of the circuit being established to make the terminating cross-connections. (Select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection

Wizard.)

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connection has been made.

.................................................................................................................................................................................................

After all cross-connections have been made, verify that the channels have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Equipment

.

Result:

The View Equipment window opens.

Alarms are not reported until the channel state transitions to in-service (IS) which happens only when a good signal is received. Cross-connections create connections to both sides of the ring. The channel state will transition once a good signal is received on either side of the ring.

16

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required port, then click

Select

at the bottom of the window. Verify the port AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

17

Under

Port Data/Fault

in the parameter display, verify the

Port Monitoring Mode

is

IS (in service). If the

Port Monitoring Mode

is IS, then Stop, you have completed this procedure. Otherwise, perform one of the following:

•

If the

Port Monitoring Mode

is NMON (Not Monitored),

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-37

TDM service provisioning procedures Procedure 10-8: Make single-homed cross-connections

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, select the required port and then click

Select

at the bottom of the window.

2. Under the

Fault Management

section, select AUTO (Automatic) for the

Port

Monitoring Mode

.

3. Click

Apply

at the bottom of the window.

4. Click

Close

to exit the window, then repeat this procedure from

Step 15 .

•

If the

Port Monitoring Mode

is AUTO:

Check the connections at the local cross-connect panel (or equivalent connection point).

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

10-38 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures

Procedure 10-9: Make dual-homed cross-connections

.................................................................................................................................................................................................................................

Overview

Use this procedure as an example for making cross-connections in Metropolis

®

DMX dual-homed ring configurations. This procedure uses the CIT Cross-Connection Wizard commands to illustrate the provisioning of the cross-connections. The TL1

ent-crs-(

)

command may be used to perform the same provisioning.

See Metropolis

®

DMX Access Multiplexer TL1 Message Details, 365-372-306 for rates, types, restrictions, and allowable cross-connections. Note that E1 services require an

STS-3c cross-connection.

Although this example illustrates OC-3/12 rings dual-homing to a OC-48 UPSR ring, the same procedure applies for OC-3/12/48 subtending rings to an OC-192 UPSR.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Verify that the dual-homed network has been established using the procedures in

Procedure 9-7: “Establish dual-homed network configurations” (p. 9-84) .

5. Determine the cross-connection types, rates, terminating nodes, pass-through nodes, and host nodes.

Step

1

Complete the following steps to make the necessary cross-connections in dual-homed ring configurations.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the Metropolis

®

DMX host nodes being used for dual homing.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-39

TDM service provisioning procedures Procedure 10-9: Make dual-homed cross-connections

2

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Refer to

Figure 10-8, “Dual-Homed Metropolis

®

DMX ring example” (p. 10-40)

for an example of a dual-homed Metropolis

®

DMX ring configuration. Note that this example uses an OC-48 ring as a backbone ring and OC-3/12 subtending nodes. Other applications may be at different optical rates.

Figure 10-8 Dual-Homed

Metropolis

®

DMX ring example

Node 9

MAIN 2 MAIN 1

NS

TSI

US

G

2

G

1

D

2

D

1

Node 1

C

2

C

1

B

2

US

B

1

A

2

A

1

Port application=UPSR or 0x1S2

NS US

MAIN 2

TSI

MAIN 1

A

1

A

2

B

1

B

2

C

1

C

2

IN

OUT

Port application=UPSR or 0x1S1

G

2

G

1

D

2

D

1

Node 2

C

2

C

1

B

2

B

1

A

2

A

1

NS

NS US

TSI

MAIN 2

MAIN 1

B 2

C 1

C 2

A 1

A 2

B 1

D 1

D 2

G 1

G 2

Traffic flow

Node 5

MAIN 1

US

TSI

MAIN 2

NS

NS

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Port application=UPSR or 0x1S1

Node 7

MAIN 1

US

TSI

MAIN 2

NS

Node 8

MAIN 1

US

TSI

MAIN 2

NS

IN

OUT

A

1

A

2

Node 4

MAIN 1

TSI

MAIN 2

US NS

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Traffic flow

Port application=UPSR or 0x1S2

NS - Network Side

US - User Side

A

1

A

2

B

1

B

2

C

1

C

2

A

1

A

2

B

1

B

2

C

1

C

2 nc-dmx-201A

3

.................................................................................................................................................................................................

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

.................................................................................................................................................................................................................................

10-40 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-9: Make dual-homed cross-connections

4

5

6

7

8

9

On the System View menu, select

Administration

→

OSI Routing Map

and/or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node on this Metropolis

®

DMX ring.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the ring configuration, Metropolis

®

DMX host nodes, terminating nodes, and pass-through nodes are the same as specified in the work instructions.

Important! All differences between the work instructions and the actual ring configuration must be resolved before continuing.

.................................................................................................................................................................................................

One at a time, use the WaveStar

®

CIT to log in to each Metropolis

®

DMX node. From the System View menu at each node, select

View

→

Equipment

.

Result:

The View Equipment window opens.

.................................................................................................................................................................................................

Find the circuit pack, port, and/or tributaries being used for this service. Select the entity to view, then click the

Select

button at the bottom of the window. View the provisioning details for the selected entity and verify the entities are properly provisioned.

.................................................................................................................................................................................................

Use product documentation for non Metropolis

®

DMX nodes in the network to verify proper circuit pack/port provisioning details.

.................................................................................................................................................................................................

If the entities are not provisioned properly, use the procedures in this document to provision the Metropolis

®

DMX circuit packs/ports for service.

.................................................................................................................................................................................................

Important! Cross-connections supporting DS3 services are STS-1 cross-connections. Cross-connections supporting DS1 services may be either STS-1 or VT1.5 cross-connections. Use VT1.5 cross-connections for DS1 services if you expect to cross connect only a portion of the VT1.5 signals in the STS-1 channel or if the VT1.5s are coming from different places. If STS-1 cross-connections are made at a shelf, there is a fixed mapping of all 28 VT1.5 cross-connections to a specific shelf group.

From your work instructions, determine the type of cross-connections to be made at each node for the service being established.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-41

TDM service provisioning procedures Procedure 10-9: Make dual-homed cross-connections

10

11

12

13

14

15

Refer to

“Dual-homed cross-connections example (UPSR port application)”

(p. 10-44)

and

“Dual-homed cross-connection example (0x1S1 and 0x1S2 port application)” (p. 10-46)

at the end of this procedure.

.................................................................................................................................................................................................

Starting at one of the host nodes for the circuit being established, select

View

→

Cross-Connections

from the System View menu at each node in the ring to verify that the cross-connections specified on the work instructions may be made. If cross-connections are already assigned or improperly assigned, refer trouble to the provisioning organization. Improperly assigned cross-connections may have to be deleted, or a different timeslot must be selected for the service being selected.

.................................................................................................................................................................................................

Select

Configuration

→

Cross-Connections

from the System View menu to start the

Cross-Connection Wizard. Use the Cross-Connection Wizard at all non terminating nodes in the network to provision pass-through cross-connections.

.................................................................................................................................................................................................

Use the Cross-Connection Wizard at the host nodes to make the proper cross-connections. (Select

Configuration

→

Cross-Connections

from the System

View menu to start the Cross-Connection Wizard).

.................................................................................................................................................................................................

Use the Cross-Connection Wizard at the terminating (add/drop) nodes of the circuit being established to make the terminating cross-connections. (Select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection

Wizard).

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connection has been made.

.................................................................................................................................................................................................

After all cross-connections have been made, verify that the channels have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Equipment

.

.................................................................................................................................................................................................................................

10-42 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-9: Make dual-homed cross-connections

16

17

Result:

The View Equipment window opens.

The provisioned cross-connections create connections to both sides of the ring.

However, for unswitched STS cross-connections there are no channel states. For unswitched VT cross-connections there is an STS channel state (for the terminated

STS). The channel state will transition once a good signal is received on either side of the ring. There will be channel states on the tributaries of the 0x1Sn interface.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required port, then click

Select

at the bottom of the window. Verify the port AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Under

Port Data/Fault

in the parameter display, verify the

Port Monitoring Mode

is

IS (in service). If the

Port Monitoring Mode

is IS, then Stop, you have completed this procedure. Otherwise, perform one of the following:

•

If the

Port Monitoring Mode

is NMON (Not Monitored),

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, select the required port and then click

Select

at the bottom of the window.

2. Under the

Fault Management

section, select AUTO (Automatic) for the

Port

Monitoring Mode

.

3. Click

Apply

at the bottom of the window.

4. Click

Close

to exit the window, then repeat this procedure from

Step 15 .

•

If the

Port Monitoring Mode

is AUTO:

Check the connections at the local cross-connect panel (or equivalent connection point).

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-43

TDM service provisioning procedures Procedure 10-9: Make dual-homed cross-connections

Dual-homed cross-connections example (UPSR port application)

The following example network shows dual-homed cross-connections at Metropolis

®

DMX node 4 and node 5.

OC-3/12

Node 9

OC-3/12 Shelf

MAIN 2 MAIN 1

TSI

OC-3/12

G

2

G

1

D

2

D

1

Node 1

DMX

C

2

C

1

B

2

B

1

A

2

Port application = UPSR

A

1

A

1

A

2

OC-48

B

1

B

2

C

1

C

2

G

2

G

1

D

2

D

1

Node 2

DMX

C

2

C

1

B

2

B

1

A

2

A

1

Port application = UPSR

OC-48 OC-48

MAIN 2

TSI

MAIN 1

MAIN 2

TSI

MAIN 1

A 1

A 2

B 1

B 2

C 1

C 2

D 1

D 2

G 1

G 2

OC-48

Traffic flow

2-Way Point-to-Point, Add/Drop, Unswitched cross-connection at Node 5 to OC-3 Port 2, STS trib 1, VTG 3, VT1.5 #1: m1-1-1-3-1:a1-2-1-3-1

2-Way Point-to-Point, Add/Drop, Unswitched cross-connection at Node 4 to OC-3 Port 2, STS trib 1, VTG 3, VT1.5 #1: m2-1-1-3-1:a2-2-1-3-1

Node 5

DMX

MAIN 1

TSI

MAIN 2

NS

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Port application = UPSR

Node 7

OC-3/12 Shelf

OC-3/12

MAIN 1

TSI

MAIN 2

OC-3/12

OC-48

Node 4

DMX

MAIN 1

TSI

MAIN 2

IN

OUT

Node 8

OC-3/12 Shelf

MAIN 1

TSI

MAIN 2

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Port application = UPSR

Traffic flow

OC-3/12

OC-48

A

1

A

2

B

1

B

2

C

1

C

2

Pass through in DDM-2000

ENT-CRS-VT1:tid:m-1-3-1,m-1-3-1

AID structure for OC-3:

Function Group Slot Line STS trib VTGroup VT1.5

(a,b,c,d,g) 1,2 (1-x) (1-3) (1-7, all) (1-4, all)

A

1

A

2

B

1

B

2

C

1

C

2

AID structure for DS-1 in DDM-2000 OC-3

Function Group Circuit Pack Port

{a,b,c} {1-7} {1-4}

Example: m-1-3-1,b-3-1

AID structure for OC-12:

Function Group Slot Line STS trib VTGroup VT1.5

(a,b,c,d,g) 1,2 (1-x) (1-12) (1-7, all) (1-4, all)

AID structure for OC-48 in Main:

Group Slot Line STS trib VTGroup VT1.5

(m) 1,2 (1-x) (1-48) (1-7, all) (1-4, all)

NC-DMX-203A-2

.................................................................................................................................................................................................................................

10-44 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-9: Make dual-homed cross-connections

The Application parameter of the ports used for the dual-homed connections is provisioned UPSR.

For dual homed configurations using a port

Application

of UPSR, the cross-connection command at the host node would include the cross-connection channel application parameter (

chappl

) for this example:

2-Way Point-to-Point, Add/Drop, Unswitched

at Node 5 (m1-1-1-3-1,a1-2-1-3-1)

2-Way Point-to-Point, Add/Drop, Unswitched

at Node 4 (m2-1-1-3-1,a2-2-1-3-1)

Ports that connect the subtending ring to the Metropolis

®

DMX host nodes that are provisioned for UPSR protection, transport unswitched traffic (cross-connection chappl

= UNSWITCHED) over the Metropolis

®

DMX UPSR without any protection switching by the Metropolis

®

DMX nodes on the backbone ring. The end-of-path NEs (Node 8 and Node 9) do the path protection switching.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-45

TDM service provisioning procedures Procedure 10-9: Make dual-homed cross-connections

Dual-homed cross-connection example (0x1S1 and 0x1S2 port application)

The following example network shows dual-homed cross-connections at Metropolis

®

DMX node 4 and node 5.

OC-3/12

Node 9

OC-3/12 Shelf

MAIN 2 MAIN 1

TSI

OC-3/12

G

2

G

1

D

2

D

1

Node 1

DMX

C

2

C

1

B

2

B

1

A

2

Port application = 0x1S2

A

1

A

1

A

2

B

1

B

2

C

1

C

2

OC-48

G

2

G

1

D

2

D

1

Node 2

DMX

C

2

C

1

B

2

B

1

A

2

A

1

Port application = 0x1S1

OC-48 OC-48

MAIN 2

TSI

MAIN 1

MAIN 2

TSI

MAIN 1

A 1

A 2

B 1

B 2

C 1

C 2

D 1

D 2

G 1

G 2

OC-48

Traffic flow

UPSR Dual Home Arc cross-connection at Node 5 to OC-3 Port 2, STS trib 1, VTG 3, VT1.5 #1: m1-1-1-3-1,a1-2-1-3-1

MAIN 1

Node 5

DMX

TSI

MAIN 2

OC-48

UPSR Dual Home Arc cross-connection at Node 4 to OC-3 Port 2, STS trib 1, VTG 3, VT1.5 #1: m2-1-1-3-1,a2-2-1-3-1

Node 4

DMX

IN

MAIN 1

TSI

MAIN 2

OUT

NS

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Node 7

OC-3/12 Shelf

OC-3/12

MAIN 1 MAIN 2

TSI

OC-3/12

Node 8

OC-3/12 Shelf

MAIN 1 MAIN 2

TSI

OC-3/12

A

1

A

2

B

1

B

2

C

1

C

2

D

1

D

2

G

1

G

2

Port application = 0x1S2

Traffic flow

OC-48

A

1

A

2

B

1

B

2

C

1

C

2

Pass through in DDM-2000

ENT-CRS-VT1:tid:m-1-3-1,m-1-3-1

AID Structure for OC-3

Function Group Slot Port STS trib VTGroup VT1.5

(a,b,c,d,g) 1,2 (1-x) (1-3) (1-7, all) (1-4, all)

A

1

A

2

B

1

B

2

C

1

C

2

AID Structure for OC-12

Function Group Slot Port STS trib VTGroup VT1.5

(a,b,c,d,g) 1,2 (1-x) (1-12) (1-7, all) (1-4, all)

AID structure for OC-48 in Main:

Group Slot Line STS trib VTGroup VT1.5

(m) 1,2 (1-x) (1-48) (1-7, all) (1-4, all)

AID structure for DS-1 in DDM-2000 OC-3

Function Group Circuit Pack Port

{a,b,c} {1-7} {1-4}

Example: ENT-CRS-VT1:tid:m-1-3-1,b-3-1:ctag;

10-46

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-9: Make dual-homed cross-connections

The Application parameter of the ports used for the dual-homed connections is provisioned 0x1S1 and 0x1S2. The Application parameter of the low-speed OC-n ports in FNA of node 5 is provisioned 0x1S1. The Application parameter of the low-speed

OC-n ports in FNA of node 4 is provisioned 0x1S2.

Dual homed configurations using a port

Application

of 0X1Sn, use one-way cross-connection commands at the host nodes:

UPSR Dual Home Arc

at Node 5 (m1-1-1-3-1,a1-2-1-3-1)

UPSR Dual Home Arc

at Node 4 (m2-1-1-3-1,a2-2-1-3-1).

Traffic is transported without any protection switching by the Metropolis

®

DMX nodes on the backbone ring. The end-of-path NEs (Node 8 and Node 9) do the path protection switching.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-47

TDM service provisioning procedures

Procedure 10-10: Bridge and roll cross-connections

.................................................................................................................................................................................................................................

Overview

CAUTION

Service disruption hazard

Service interruption of up to 10 ms for STS cross-connections or 25 ms for VT cross-connections may occur when an existing source is rolled to a new source. In cases involving roll procedures from Main 2 cross-connections to function slot ports, the service interruption may be as high as 200 ms.

Use this procedure to move traffic to another circuit path. Traffic can be moved from the existing tributary to another tributary on:

• the same set of interconnecting facilities.

• a different set of interconnecting facilities.

Traffic is moved using a coordinated sequence of bridging and rolling cross-connection legs at the terminating (add/drop) nodes and provisioning new cross-connections at pass-through nodes (UPSRs/BLSRs only).

At the head-end terminating node of a 1-way circuit, the existing add cross-connection leg is bridged to the new destination tributary allowing traffic to be added to the new circuit path.

At the tail-end terminating node of the 1-way circuit, the existing drop cross-connection leg is rolled to the new source tributary allowing traffic to be switched to the new circuit path.

For 2-way circuits, traffic in one direction of transmission is moved to the new circuit path, then the traffic in the opposite direction of transmission is moved to the new circuit path.

Bridging cross-connection legs

Cross-connection legs are bridged at the head-end terminating node of a 1-way circuit to move traffic to the new circuit path. Bridged cross-connection legs allow a single source tributary to be cross-connected to multiple destination tributaries at the same rate.

At the head-end terminating node of a 1-way circuit, the existing add cross-connection leg is bridged using 1-Way Point-to-Point or 1-Way Path Protected Drop from a UPSR

Ring cross-connections.

.................................................................................................................................................................................................................................

10-48 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-10: Bridge and roll cross-connections

Rolling cross-connection legs

Cross-connection legs are rolled at the tail-end terminating node of a 1-way circuit to switch traffic from the existing circuit path to the new circuit path. The source tributary of the existing drop cross-connection is switched to the new source tributary at the same rate.

Guidelines for provisioning the circuit ID parameter

When bridging/rolling cross-connection legs use the following guidelines to provision the circuit ID parameter.

•

If an existing cross-connection has (or does not have) a circuitid value, and you want the new circuit to have a different or new circuitid value

(circuitid=some_other_value), then specify circuitid=some_other_value in the bridge command. Then, specify the same circuitid=some_other_value in the roll command.

•

If an existing cross-connection does not have a circuitid value, and you do not want the new circuit to have a circuitid value, then do not specify a circuitid value in the bridge command. Then, do not specify a circuitid value in the roll command.

•

If an existing cross-connection has a circuitid value and you want the new circuit to have the same circuitid value, then specify the same circuitid value in the bridged cross-connection. Then, do not specify a circuitid value in the roll command.

•

If an existing cross-connection has a circuitid value and you do not want the new circuit to have a circuitid value, then do not specify a circuitid value in the bridge command. Then, specify a null value for the circuitid (circuitid=

″″

) in the roll command.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Before you begin this procedure, you must:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-49

TDM service provisioning procedures Procedure 10-10: Bridge and roll cross-connections

4. Verify that the work instructions specify the existing circuit path including terminating (add/drop) nodes, pass-through nodes (UPSRs/BLSRs only), cross-connections, and port/tributary addresses.

5. Verify that the work instructions specify the new circuit path including port/tributary addresses, cross-connections, and pass-through nodes (UPSRs/BLSRs only).

Step

1

2

3

4

Complete the following steps to move traffic to another circuit path.

.................................................................................................................................................................................................

Important! For 2-way circuits, traffic in one direction of transmission is moved to the new circuit path, then the traffic in the opposite direction of transmission is moved to the new circuit path.

Using the work instructions, determine whether the circuit to be moved is 1-way or

2-way. If the circuit to be moved is 2-way, identify the direction of transmission to be moved first.

.................................................................................................................................................................................................

Identify and log in to the terminating (add/drop) nodes.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Identify and record the existing interconnecting facilities and the new interconnecting facilities (if required). If required, at the terminating (add/drop) nodes select

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the interconnecting facilities is not provided with the work instructions, it is recommended that you draw a simple diagram and list each node’s TID.

.................................................................................................................................................................................................

Important! If the Port Monitoring Mode parameter is AUTO, the port automatically transitions to the in service state if a valid signal is detected and the port is monitored/alarmed. If the Port Monitoring Mode is NMON, the port is not monitored/alarmed, and the port will not automatically transition to the in service state if a valid signal is detected. No alarm reporting creates the possibility of service degradation or service outage if the new circuit path has a defect.

.................................................................................................................................................................................................................................

10-50 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-10: Bridge and roll cross-connections

5

At each terminating (add/drop) and pass-through node (UPSRs/BLSRs only), select

View

→

Equipment

and verify that all circuit packs, pluggable transmission modules, ports, and protection groups have been provisioned at each node.

If required, refer to

Chapter 4, “Install and provision circuit packs/OLIUs procedures”

to perform additional installation and provisioning.

.................................................................................................................................................................................................

Important! Before moving traffic to the new circuit path, new cross-connections must be created at pass-through nodes (UPSRs/BLSRs only).

If moving a...

1-way circuit,

2-way circuit,

Then at each pass-through node

(UPSRs/BLSRs only)...

select

Configuration

→

Cross-Connections

to access the Cross-Connection Wizard and create the required new

1-Way

Point-to-Point, Through

cross-connection.

select

Configuration

→

Cross-Connections

to access the Cross-Connection Wizard and create the required new

2-Way

Point-to-Point, Through

cross-connection.

6

7

8

.................................................................................................................................................................................................

At each pass-through node (UPSRs/BLSRs only), select

View

→

Cross-Connections

to access the cross-connection list and verify that the required pass-through cross-connection was created.

.................................................................................................................................................................................................

Important! If the Tributary Monitoring Mode parameter is AUTO, the tributary automatically transitions to the in service state if a valid signal is detected and the tributary is monitored/alarmed. If the Tributary Monitoring Mode is NMON, the tributary is not monitored/alarmed, and the tributary will not automatically transition to the in service state if a valid signal is detected.

At each pass-through node (UPSRs/BLSRs only), select

View

→

Equipment

and verify the new Tributary parameters.

If required, use

Configuration

→

Equipment

and refer to

Chapter 4, “Install and provision circuit packs/OLIUs procedures”

to perform additional provisioning.

.................................................................................................................................................................................................

Important! At the head-end terminating node of the 1-way circuit, the traffic to be moved must be bridged to the new tributary. In UPSRs, the traffic to be moved

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-51

TDM service provisioning procedures Procedure 10-10: Bridge and roll cross-connections must be bridged to the same new tributary on Main/Function/Growth 1 and

Main/Function/Growth 2.

At the head-end node of the 1-way circuit, select

Configuration

→

Cross-

Connections

to access the Cross-Connection Wizard. Select

Bridge a crossconnection from a source to multiple destinations

and follow the directions to bridge the add cross-connection leg to the required new destination tributary(ies).

The following figure shows an example of an add cross-connection leg bridged to new destination tributaries within a UPSR.

Existing tributary New tributary

Bridge

M2

M1

MA-DMX-309

9

10

11

.................................................................................................................................................................................................

At the head-end node of the 1-way circuit, select

View

→

Cross-Connections

to access the cross-connection list and verify that the required add cross-connection leg was bridged to the new destination tributary(ies).

.................................................................................................................................................................................................

Important! If the Tributary Monitoring Mode parameter is AUTO, the tributary automatically transitions to the in service state if a valid signal is detected and the tributary is monitored/alarmed. If the Tributary Monitoring Mode is NMON, the tributary is not monitored/alarmed, and the tributary will not automatically transition to the in service state if a valid signal is detected.

At the head-end node of the 1-way circuit, select

View

→

Equipment

and verify the new Tributary parameters.

If required, use

Configuration

→

Equipment

and refer to

Chapter 4, “Install and provision circuit packs/OLIUs procedures”

to perform additional provisioning.

.................................................................................................................................................................................................

At each terminating (add/drop) and pass-through node (UPSRs/BLSRs only), click the

Alarm List

button or select

Fault

→

NE Alarm List

from the System View menu to obtain an NE Alarm List and verify that no alarms are present. Clear all alarms before continuing this procedure.

.................................................................................................................................................................................................................................

10-52 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-10: Bridge and roll cross-connections

12

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Service interruption of up to 10 ms for STS cross-connections or 25 ms for VT cross-connections may occur when performing the following roll procedures. In cases involving roll procedures from Main 2 cross-connections to Function slot ports, the service interruption may be as high as 200 ms.

CAUTION

Service disruption hazard

Service outage will occur if all new cross-connections are not properly made before performing the following roll procedures.

Important! It is suggested that you use a Command Mode (cmdmde) of

NORM

when rolling a cross-connection input to a SONET interface. If the new input is being monitored and it is faulty, the command will not complete. A Command

Mode of

FRCD

allows the command to complete even if the new input is faulty.

When rolling a cross-connection input to a non-SONET interface, the new input is not monitored and the Command Mode must be set to

FRCD

.

At the tail-end terminating node of the 1-way circuit, the traffic to be moved must be rolled to the new tributary. In UPSRs, the traffic to be moved must be bridged to the same new tributary on Main/Function/Growth 1 and Main/Function/Growth

2.

At the tail-end node of the 1-way circuit, select

Configuration

→

Cross-Connections

to access the Cross-Connection Wizard. Select

Roll a cross-connection from a source to a new source

and follow the directions to roll the drop cross-connection leg(s) to the required new source tributary(ies).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-53

TDM service provisioning procedures Procedure 10-10: Bridge and roll cross-connections

If a new Circuit Identifier (circuitid) is not specified, then the circuitid parameter value of the resultant cross-connection is inherited from the original cross-connection. If a new Circuit Identifier (circuitid) is null (circuitid=

″″

), then the circuitid parameter value of the resultant cross-connection is cleared.

The following figure shows an example of drop cross-connection legs rolled to new source tributaries within a UPSR.

New tributary Existing tributary

M1

M2

Roll

MA-DMX-313

13

14

15

16

.................................................................................................................................................................................................

At the tail-end node of the 1-way circuit, select

View

→

Cross-Connections

to access the cross-connection list and verify that the required drop cross-connection leg(s) was rolled to the new source tributary(ies).

.................................................................................................................................................................................................

Important! If the Tributary Monitoring Mode parameter is AUTO, the tributary automatically transitions to the in service state if a valid signal is detected and the tributary is monitored/alarmed. If the Tributary Monitoring Mode is NMON, the tributary is not monitored/alarmed, and the tributary will not automatically transition to the in service state if a valid signal is detected.

At the tail-end node of the 1-way circuit, select

View

→

Equipment

and verify the new Tributary parameters.

If required, use

Configuration

→

Equipment

and refer to

Chapter 4, “Install and provision circuit packs/OLIUs procedures”

to perform additional provisioning.

.................................................................................................................................................................................................

If moving a 2-way circuit, repeat

Step 8

through

Step 14

to move the traffic in the opposite direction of transmission to the new circuit path; otherwise, continue with the next step.

.................................................................................................................................................................................................

At each terminating (add) and pass-through node (UPSRs/BLSRs only), select

Configuration

→

Cross-Connections

to access the Cross-Connection Wizard. Select

.................................................................................................................................................................................................................................

10-54 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-10: Bridge and roll cross-connections

Delete leg(s) of an existing cross-connection

and follow the directions to delete the original cross-connections in the original circuit path.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-55

TDM service provisioning procedures

Procedure 10-11: Establish dual ring interworking (DRI) connections

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring basic dual ring interworking connections (DRI). See

Figure 10-9, “Example of final DRI configuration” (p. 10-58)

for an example.

This procedure provides examples of the steps involved in making the proper cross-connections at the DRI interconnecting nodes. It is not intended for establishing complete service from an end node to an end node (for example, from Node 1 to Node

6). Although, once the DRI connections are made at the interconnecting nodes, establishing service from an end node to an end node only requires the proper pass-through cross-connections at intermediate nodes and add/drop cross-connections in the terminating end nodes.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Important! The following procedure is based on a hypothetical example. You can use this example procedure to apply the basic concepts to the procedure you want to perform.

This procedure assumes that the individual rings being connected have been established and are working properly.

Before you begin

Before you begin this procedure, you must:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Identify the nodes in the network and determine which nodes are the interconnecting DRI nodes.

5. Identify which Function slots in the DRI nodes are going to be used to make the connections.

6. Determine the cross-connections to be used.

7. Be able to log in to the NE with the WaveStar

®

CIT and be familiar with the functions of the WaveStar

®

CIT.

.................................................................................................................................................................................................................................

10-56 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures

Step

Procedure 10-11: Establish dual ring interworking (DRI) connections

1

2

Complete the following steps to perform DRI connections.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to the nodes, if not already performed.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu at each node, select Administration

→

OSI Neighbor Map to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

This command may take several minutes to complete depending on the size of the network.

Result:

The OSI Neighbor Map window opens.

See

Figure 10-9, “Example of final DRI configuration” (p. 10-58)

for an example of a final configuration.

In this example, two UPSR rings are being interconnected in a DRI configuration using STS-1 cross-connections between two pairs of interconnecting nodes (Nodes

2 and 3, and Nodes 4 and 5), one pair in each ring. Note that cross-connections in this release are STS cross-connections.

In this figure the main ports are on the UPSR and the low-speed ports are used as the add/drop ports. The add/drop ports may be UPSR, 1+1, 0x1S1 or 0xS2, or

BLSR OC-N ports, or an electrically protected EC-1 port. For this example, we assume the low speed ports are configured as UPSR ports.

This example is only one of many possible configurations. In this example one could reverse the roles of the main OLIUs and the low speed circuit packs at any

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-57

TDM service provisioning procedures Procedure 10-11: Establish dual ring interworking (DRI) connections of the nodes to form another configuration. Also, a low speed UPSR could be used in place of the Main OLIUs at any of the interconnecting nodes.

Figure 10-9 Example of final DRI configuration

Node 1

M2

M1

Low Speed

UPSR Ring 1

M1

Node 3

M2

M1

Node 2

M2

Low Speed

Low Speed

Low Speed

Low Speed

M1

Node 4

M2 M1

Node 5

M2

UPSR Ring 2

M2

Node 6

M1

Low Speed

MA-DMX-335

3

.................................................................................................................................................................................................

From the System View menu, select

View

→

Equipment

and verify that all circuit packs have been installed and ports have been provisioned and connected at each interconnecting DRI node. For example, at nodes 2, 3, 4, and 5 in

Figure 10-9,

“Example of final DRI configuration” (p. 10-58) .

Important! Before performing the DRI cross-connections in this procedure, the optical or electrical interconnection between the DRI nodes must be completed.

.................................................................................................................................................................................................................................

10-58 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-11: Establish dual ring interworking (DRI) connections

4

5

6

7

If circuit packs have not been installed, the ports have not been provisioned, or the proper interconnection application has not been performed, use the procedures in this manual to install, provision, and connect the required circuit pack ports. The add/drop ports may be UPSR, 1+1, or BLSR OC-n ports, or electrically protected

EC-1 ports.

.................................................................................................................................................................................................

From the System View menu at each DRI node, select

Configuration

→

Cross-Connections

to start the Cross-Connection Wizard.

Result:

The Cross-Connection Wizard screen opens.

.................................................................................................................................................................................................

Select

Create a new cross-connection

, then click

Next

at the bottom of the screen.

.................................................................................................................................................................................................

Select

UPSR Dual Ring Interworking

, then click

Next

at the bottom of the screen.

.................................................................................................................................................................................................

Use the

Select

button to choose the UPSR and then the Add/Drop Tributary.

Click

Next to continue.

Note the direction of cross-connections (East or West) in the Cross-Connection Wizard.

For example, see

Figure 10-10, “Example cross-connections at node 3” (p. 10-59)

and

Figure 10-11, “Example cross-connections at node 2” (p. 10-59)

for the cross-connections at Nodes 2 and 3.

Figure 10-10 Example cross-connections at node 3

m1-1-1 main-1 (West) main-2 (East) m2-1-1

Select

From/To Terminating Node From/To Interconnecting Node a1-1-1

Select

To/From Other Ring

MA-DMX-337-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-59

TDM service provisioning procedures Procedure 10-11: Establish dual ring interworking (DRI) connections

Figure 10-11 Example cross-connections at node 2

m1-1-1 main-1 (West) main-2 (East) m2-1-1

Select

From/To Terminating Node From/To Interconnecting Node

To/From Other Ring a1-1-1

Select

MA-DMX-338-2

8

9

.................................................................................................................................................................................................

Enter a

Circuit Identifier

if required. Verify the cross-connections, then click

Finish

to execute the command.

.................................................................................................................................................................................................

Repeat these steps from

Step 4

to make the cross-connections at each DRI node.

See

Figure 10-12, “Example cross-connections for DRI with UPSR protected OC-n add/drop ports” (p. 10-61)

for an example of the cross-connections that are made at each node to complete the final configuration as shown in

Figure 10-9, “Example of final DRI configuration” (p. 10-58) . The example uses TL1 commands to

illustrate the different cross-connections that are made when using the

Cross-Connection Wizard. The

View

→

Cross-Connections

command at each of the DRI nodes shows the individual cross-connections made from the

Cross-Connection Wizard.

Cross-connections are a combination of 1waypr and 1way. Refer to

Figure 10-13,

“Basic UPSR DRI cross-connections with UPSR protected OC-n add/drop port”

(p. 10-61)

through

Figure 10-17, “Basic UPSR DRI cross-connections with 0X1Sn protected OCn add/drop port” (p. 10-62)

for examples of different add/drop port configurations in the basic UPSR DRI application.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

10-60 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-11: Establish dual ring interworking (DRI) connections

Figure 10-12 Example cross-connections for DRI with UPSR protected OC-n add/drop ports

ent-crs-rr:N ent-crs-rr:N ode3 ode3

:m1-1-1,a1-1-1:ctag::1waypr,m2-1-1;

:m1-1-1,a2-1-1:ctag::1waypr,m2-1-1; ent-crs-rr:N ode3 :m1-1-1,m2-1-1:ctag::1way; ent-crs-rr:Node3:a1-1-1,m1-1-1:ctag::1waypr,a2-1-1;

M1

Node 3

M2 ent-crs-rr:N ode2 :m1-1-1,a1-1-1:ctag::1waypr,m2-1-1; ent-crs-rr:N ode2 :m1-1-1,a2-1-1:ctag::1waypr,m2-1-1; ent-crs-rr:N ode2 :m2-1-1,m1-1-1:ctag::1way; ent-crs-rr:Node2:a1-1-1,m2-1-1:ctag::1waypr,a2-1-1;

Node 2

UPSR Ring 1

M1 M2

Low Speed

Low Speed

Low Speed

Low Speed

UPSR Ring 2

M1 M2 ent-crs-rr:N ode3

Node 4

:m1-1-1,a1-1-1:ctag::1waypr,m2-1-1; ent-crs-rr:N ode3 :m1-1-1,a2-1-1:ctag::1waypr,m2-1-1; ent-crs-rr:N ode3 :m1-1-1,m2-1-1:ctag::1way; ent-crs-rr:Node3:a1-1-1,m1-1-1:ctag::1waypr,a2-1-1;

M1 M2 ent-crs-rr:N ode5

Node 5

:m1-1-1,a1-1-1:ctag::1waypr,m2-1-1; ent-crs-rr:N ode5 :m1-1-1,a2-1-1:ctag::1waypr,m2-1-1; ent-crs-rr:N ode5 :m2-1-1,m1-1-1:ctag::1way; ent-crs-rr:Node5:a1-1-1,m2-1-1:ctag::1waypr,a2-1-1;

MA-DMX-336-2

Figure 10-13 Basic UPSR DRI cross-connections with UPSR protected OC-n add/drop port

Node 3 m1 m2 ent-crs-rr:Node3:a1-1-1,m1-1-1:ctag::1waypr,a2-1-1; ent-crs-rr:N ode3 :m1-1-1,a2-1-1:ctag::1waypr,m2-1-1; ent-crs-rr:N ode3 :m1-1-1,a1-1-1:ctag::1waypr,m2-1-1; ent-crs-rr:N ode3 :m1-1-1,m2-1-1:ctag::1way; a1 a2

UPSR protected

MA-DMX-339-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-61

TDM service provisioning procedures Procedure 10-11: Establish dual ring interworking (DRI) connections

Figure 10-14 Basic UPSR DRI cross-connections with EC-1 add/drop port

Node 3 m1 m2 ent-crs-rr: Node3 :a1-1,m1-1-1:ctag::1way; ent-crs-rr:Node3:m1-1-1,a1-1:ctag::1waypr,m2-1-1; ent-crs-rr: Node3 :m1-1-1,m2-1-1:ctag::1way; a1 a2

1X1 Equipment Protection

MA-DMX-340-2

Figure 10-15 Basic UPSR DRI cross-connections with 1+1 protected OC-n add/drop port

Node 3 m1 m2 ent-crs-rr:Node3:a1-1-1,m1-1-1:ctag::1way; ent-crs-rr:N ode3 :m1-1-1,a1-1-1:ctag::1waypr,m2-1-1; ent-crs-rr:N ode3 :m1-1-1,m2-1-1:ctag::1way; a1 a2

1+1 Protection

MA-DMX-341-2

Figure 10-16 Basic UPSR DRI cross-connections with BLSR protected OC-n add/drop port

Node 3 m1 m2 ent-crs-sts1:Node3:a1-1-1,m1-1-1:ctag::1way:loca=Node 4 ent-crs-sts1:Node3:m1-1-1,a1-1-1:ctag::1waypr,m2-1-1:locz=Node 4 ent-crs-sts1:Node3:m1-1-1,m2-1-1:ctag::1way a1 a2

BLSR Protection

MA-DMX-342-2

.................................................................................................................................................................................................................................

10-62 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-11: Establish dual ring interworking (DRI) connections

Figure 10-17 Basic UPSR DRI cross-connections with 0X1Sn protected OCn add/drop port

Node 3 m1 m2 ent-crs-rr: Node3 :a1-1-1,m1-1-1:ctag::1way; ent-crs-rr:Node3:m1-1-1,a1-1-1:ctag::1waypr,m2-1-1; ent-crs-rr: Node3 :m1-1-1,m2-1-1:ctag::1way; a1 a2

0X1S1

MA-DMX-414-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-63

TDM service provisioning procedures

Procedure 10-12: Provision DS1/DS3 locked cross-connections on a UPSR

.................................................................................................................................................................................................................................

Overview

Use this procedure as an example for provisioning locked VT1.5 or STS-1 cross-connections. Locked cross-connections consist of a cross-connection between a

DSn port and a tributary on one side only of a UPSR ring, for example, a1-1-7-4 to m2-1-11-7-4. Note that the AIDs are that of a ring channel (a1,m2).

This procedure uses examples for DS1 and DS3 type cross-connections to illustrate the steps involved in cross-connections in a single UPSR ring configuration. This procedure uses the CIT Cross-Connection Wizard commands to illustrate the provisioning. The same provisioning may be made using the TL1

ent-crs-( )

command.

Additional considerations when provisioning locked cross-connection:

•

Cross-connections are 2-way using two 1-way cross-connections performed by the

DSn Locked

cross-connection type from the CIT Cross-Connection Wizard.

•

At the local node, cross-connections on the companion timeslot of a locked cross-connection are denied. The same ring timeslot can be reused on non-adjacent spans. In the example, with a locked cross-connection from a1-1-7-4 to m1-1-11-7-4, cross-connections to m2-1-11-7-4 are denied at the local node but are supported at adjacent nodes. However, it would not be possible to carry service using locked cross-connections on m1-1-11-7-4 at adjacent nodes.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Verify that you have the work instructions for this procedure stating the circuit pack and port options to be set, the pass-through and terminating end nodes, and cross-connections being made.

4. Verify the network has been established and that all necessary circuit packs and port options have been provisioned for the service being established.

.................................................................................................................................................................................................................................

10-64 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-12: Provision DS1/DS3 locked cross-connections on a UPSR

Step

1

2

3

4

5

6

Perform the following steps to make the necessary locked cross-connections.

.................................................................................................................................................................................................

Connect the PC and establish a WaveStar

®

CIT session.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Log in to any node in the network and retrieve a map of the network which lists all the systems and how they are connected to each other. From the System View menu select

Administration

→

OSI Routing Map

or

Administration

→

OSI Neighbor Map

.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on the work order or circuit order.

.................................................................................................................................................................................................

From work order or circuit order, determine the terminating (drop) nodes and the pass-through nodes for the service being established.

Important! In ring configurations, you should use the following general rules in establishing cross-connections in each ring.

Cross-Connect Rules

1. All cross-connections to/from the same STS-1 timeslot must be provisioned the same, either all VT1.5 or STS-1.

2. If all 28 VT1.5s (DS1s) in an STS-1 are being passed through at a node in a

VT1.5 path-switched ring, then the cross-connection may be provisioned as either a pass-through STS-1 or VT1.5. However, if you are dropping VT1.5s

from the pass through node in the future, you should provision the pass-throughs as VT1.5 cross-connections.

3. If an STS, or a VT within an STS, on one side of the ring is connected as a locked cross-connection, no cross-connections involving the same STS number on the opposite side are allowed.

.................................................................................................................................................................................................

Log in to each node in the network and verify that each shelf is properly equipped for the service being established. From the System View menu select

View

→

Equipment

.

.................................................................................................................................................................................................

From work order or circuit order, determine the cross-connections to be made at each node associated with the service to be established. See

Figure 10-18, “DS1 locked cross-connections on a UPSR (unprotected)” (p. 10-68) ,

Figure 10-19, “DS3 locked

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-65

TDM service provisioning procedures Procedure 10-12: Provision DS1/DS3 locked cross-connections on a UPSR

7

8

9

cross-connections on a UPSR (unprotected)” (p. 10-68)

and

Figure 10-20, “DS3 locked cross-connections on a UPSR (protected externally)” (p. 10-69)

for DS1/DS3 cross-connection examples.

Important! Cross-connections supporting DS3 services are STS-1 cross-connections. Cross-connections supporting DS1 services may be either STS-1 or VT1.5 cross-connections. Use VT1.5 cross-connections for DS1 services if you expect to cross connect only some of the VT1.5 signals in the STS-1 channel. If

STS-1 cross-connections are made at a shelf, there is a fixed mapping of all 28

VT1.5 cross-connections to a specific shelf group.

.................................................................................................................................................................................................

Starting at one of the terminating nodes for the circuit being established, at each node in the ring use

View

→

Cross-Connections

from the System View menu to verify that the cross-connections specified on the work order or circuit order may be made. If the cross-connections are already assigned to another service or improperly assigned, refer trouble to the organization responsible for facility design. Improperly assigned cross-connections may have to be deleted.

.................................................................................................................................................................................................

At all non-terminating nodes in the network, provision pass-through cross-connections.

From the System View menu select

Configuration

→

Cross-Connections

, then use the Cross-Connection Wizard to make the cross-connections. Select

2-Way

Point-to-Point, Through

for pass through cross-connections.

.................................................................................................................................................................................................

At the terminating (add/drop) nodes of the circuit being established, establish the terminating cross-connections. From the System View menu select

Configuration

→

Cross-Connections

, then use the Cross-Connection Wizard to make the

Locked DSn

cross-connections.

Important! The channel mode provisioning feature provides In-Service, Automatic, or Not Monitored states for VT and STS channels similar to the port modes for

DS1 and DS3 ports. At installation, or when a cross-connection is made to a point of termination, the channel is in the Automatic mode and alarming is suppressed until a valid signal is received. The channel must receive a good signal from the side of the ring being used to cause the channel to transition to in-service.

.................................................................................................................................................................................................................................

10-66 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-12: Provision DS1/DS3 locked cross-connections on a UPSR

10

11

12

13

Locked DSn cross-connections may be made between OLIUs and DS1 or DS3 interfaces, but not TMUX interfaces. Also, remember that the AIDs of the locked cross-connections are that of a ring channel, for example m1-1-4-1-4 or g2-2-1.

.................................................................................................................................................................................................

Verify that the proper connection has been made. From the System View menu select

View

→

Cross-Connections

. If changes are required, return to the Cross-Connection

Wizardd to make them.

.................................................................................................................................................................................................

After all cross-connections have been made, verify that the channels have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Equipment

.

Result:

The View Equipment window opens.

Alarms are not reported until the channel state transitions to in-service (IS) which happens only when a good signal is received. Since there is a connection only to one side of the UPSR ring, no alarms are reported until all upstream connections are correct.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required DS1/DS3 port, then click

Select

at the bottom of the window. Verify the port AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Under

Port Data/Fault

in the parameter display, verify the

Port Monitoring Mode

is

IS (in service). If the

Port Monitoring Mode

is IS, then Stop, you have completed this procedure. Otherwise, perform one of the following:

•

If the Port Monitoring Mode is NMON (Not Monitored),

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, select the required DS1/DS3 port and then click

Select

at the bottom of the window.

2. Under the

Fault Management

section, select AUTO for the

Port Monitoring

Mode

.

3. Click

Apply

at the bottom of the window.

4. Click

Close

to exit the window, then repeat this procedure from

Step 11 .

•

If the

Port Monitoring Mode

is AUTO:

Check the connections at the local cross-connect panel (or equivalent connection point).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-67

TDM service provisioning procedures Procedure 10-12: Provision DS1/DS3 locked cross-connections on a UPSR

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

Figure 10-18 DS1 locked cross-connections on a UPSR (unprotected)

DS1 (VT1.5) Locked DSn cross-connections:

m1-1-4-1-4 to a1-1-1-4

DS1

A

B

Ds3

D

G

Main 1

Node 1

DMXtend

Service #2 (Reuse of VT1.5 #4)

Main 2

Node 4

DMX

DS1 (VT1.5) Locked DSn cross-connections:

a1-1-3-4 to g1-2-4-3-4

DS3

B

C

D

G2 G1

Node 2

DMX

Main 1 Main 2

DS1 (VT1.5) Locked DSn cross-connections:

d1-1-1-4 to m2-1-4-1-4

Service #1

A

Main 1

DMX

tend

= Metropolis DMX

tend

Access Multiplexer

DS1

D

G1 G2

DS1 (VT1.5) Locked DSn cross-connections:

g2-1-4-3-4 to d1-1-3-4

Main 2

Node 3

DMXtend

MA-DMX-392-2

.................................................................................................................................................................................................................................

10-68 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-12: Provision DS1/DS3 locked cross-connections on a UPSR

Figure 10-19 DS3 locked cross-connections on a UPSR (unprotected)

DS3 (STS1) Locked DSn cross-connections:

d1-1 to m2-1-1

B

DS3

D

G

Node 4

DMX

Main 1 Main 2

Node 1

DMXtend

Service #1

DS3 (STS1) Locked DSn cross-connections:

g2-2-1 to b1-1

DS1

A

C

D

G2 G1

Node 4

DMX

Main 1 Main 2

DS3 (STS1) Locked DSn cross-connections:

m1-1-1 to c1-1

Service #2 (Reuse of STS-1 #1)

A

Main 1

DMX

tend

= Metropolis DMX

tend

Access Multiplexer

DS1

D

G1 G2

DS3 (STS1) Locked DSn cross-connections:

b1-1 to g1-1-1

Node 3

DMXtend

Main 2

MA-DMX-393-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-69

TDM service provisioning procedures Procedure 10-12: Provision DS1/DS3 locked cross-connections on a UPSR

Figure 10-20 DS3 locked cross-connections on a UPSR (protected externally)

DS3 (STS1) Locked DSn cross-connections:

d1-2 to m1-1-2

STS-1 #2 d-2

B

External Protection

DS3

D

STS-1 #1 d-1

G

DS3 (STS1) Locked DSn cross-connections:

d1-1 to m2-1-1

Protection for

Service #1

Main 1 Main 2

Node 1

DMXtend

Service #1

STS-1 #2 b-2

External Protection

DS3 (STS1) Locked DSn cross-connections:

g2-2-1 to b1-1 g1-2-2 to b1-2

DS1

A

DS3

B

STS-1 #1 b-1

C D G2 G1

Node 4

DMX

2-Way Point-to-Point, Through cross-connection

m1-1-2 to m2-1-2

Main 1

Node 2

DMX

Main 2

A

Main 1

DMX

tend

= Metropolis DMX

tend

Access Multiplexer

G1 G2

2-Way Point-to-Point, Through cross-connection

g1-1-2 to g2-1-2

Node 3

DMXtend

Main 2

MA-DMX-394-2

.................................................................................................................................................................................................................................

10-70 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures

Procedure 10-13: Provision VT1.5 cross-connections on a

BLSR

.................................................................................................................................................................................................................................

Overview

This procedure provides an example to provision VT1.5 cross-connections on a BLSR ring. This procedure uses the CIT Cross-Connection Wizard commands to illustrate the provisioning. The same provisioning may be made using the TL1

ent-crs-( )

command. Refer to

Figure 10-21, “BLSR VT cross-connection examples” (p. 10-75)

for example cross-connections.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Verify that you have the work instructions for this procedure stating the circuit pack and port options to be set, the pass-through and terminating end nodes, and cross-connections being made.

4. Verify the network has been established and that all necessary circuit packs and port options have been provisioned for the service being established.

5. Review the rules for provisioning in

“VT cross-connections for BLSR” (p. 10-76) .

Step

1

2

Perform the following steps to make the necessary cross-connections.

.................................................................................................................................................................................................

Connect the PC and establish a WaveStar

®

CIT session.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

As an alternative, you can select

View

→

Rings

→

Ring Map

from the System View menu, then select the 2F BLSR port protection group and click

Select

. Select Active

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-71

TDM service provisioning procedures Procedure 10-13: Provision VT1.5 cross-connections on a

BLSR

3

4

(NVM) in the Ring Map Source selection box. You may also Display Ring Map Graph using this command.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map or OSI Routing Map window opens if the

Administration

→

OSI Neighbor Map

or

Administration

→

OSI Routing Map

command was used.

A list of NEs and NE neighbors is displayed if the

View

→

Rings

→

Ring Map

command was used.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on the work order or circuit order.

Verify that the VT cross-connections specified in your work order are supported at the nodes in the path of the cross-connections.

Note the

Ring Node VT Type

for each of the nodes that are participating in the cross-connection. In VT-accessed BLSRs containing VT Type 1 nodes, VT circuits may be provisioned provided they do not pass through a Type 1 node.

Important! Because of the potential for improper squelching, provisioning VT circuits in rings with VT Type 1 nodes is not recommended. Also, VT automatic squelch map generation and VT ring circuit audits are not supported in rings containing VT Type 1 nodes other than Metropolis

®

DMX nodes.

.................................................................................................................................................................................................

From work order or circuit order, determine the terminating (drop) nodes and the pass-through nodes for the service being established.

Important! In ring configurations, you should use the following general rules in establishing cross-connections in each ring.

Cross-Connect Rules

1. All cross-connections to/from the same STS-1 timeslot must be provisioned the same, either all VT1.5 or STS-1.

2. If all 28 VT1.5s (DS1s) in an STS-1 are being passed through at a node in a

VT1.5 ring, then the cross-connection may be provisioned as either a pass-through STS-1 or VT1.5. However, if you are dropping VT1.5s from the pass through node in the future, you should provision the pass-throughs as

VT1.5 cross-connections.

.................................................................................................................................................................................................................................

10-72 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-13: Provision VT1.5 cross-connections on a

BLSR

5

6

7

8

9

10

.................................................................................................................................................................................................

Log in to each node in the network and verify that each shelf is properly equipped for the service being established. From the System View menu select

View

→

Equipment

.

.................................................................................................................................................................................................

From work order or circuit order, determine the cross-connections to be made at each node associated with the service to be established. See

Figure 10-21, “BLSR VT cross-connection examples” (p. 10-75)

for DS1 cross-connection examples.

Important! Cross-connections supporting DS1 services may be either STS-1 or

VT1.5 cross-connections. Use VT1.5 cross-connections for DS1 services if you expect to cross connect only some of the VT1.5 signals in the STS-1 channel. If

STS-1 cross-connections are made at a shelf, there is a fixed mapping of all 28

VT1.5 cross-connections to a specific shelf group.

.................................................................................................................................................................................................

Starting at one of the terminating nodes for the circuit being established, at each node in the ring use

View

→

Cross-Connections

from the System View menu to verify that the cross-connections specified on the work order or circuit order may be made. If the cross-connections are already assigned to another service or improperly assigned, refer trouble to the organization responsible for facility design. Improperly assigned cross-connections may have to be deleted.

.................................................................................................................................................................................................

At all non-terminating nodes in the circuit, provision pass-through cross-connections.

From the System View menu select

Configuration

→

Cross-Connections

, then use the Cross-Connection Wizard to make the cross-connections at all nodes through which the circuit is routed. Select

2-Way Point-to-Point, Through

for pass through cross-connections.

.................................................................................................................................................................................................

At the terminating (add/drop) nodes of the circuit being established, establish the terminating cross-connections. From the System View menu select

Configuration

→

Cross-Connections

, then use the Cross-Connection Wizard to make the

2F BLSR

Add/Drop

cross-connections.

.................................................................................................................................................................................................

Verify that the proper connection has been made. From the System View menu select

View

→

Cross-Connections

. If changes are required, return to the Cross-Connection

Wizard to make them.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-73

TDM service provisioning procedures Procedure 10-13: Provision VT1.5 cross-connections on a

BLSR

11

12

13

.................................................................................................................................................................................................

After all cross-connections have been made, verify that the channels have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Equipment

.

Result:

The View Equipment window opens.

Alarms are not reported until the channel state transitions to in-service (IS) which happens only when a good signal is received. Since there is a connection only to one side of the BLSR ring, no alarms are reported until all upstream connections are correct.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required port, then click

Select

at the bottom of the window. Verify the port AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Under

Port Data/Fault

in the parameter display, verify the

Port Monitoring Mode

is

IS (in service). If the

Port Monitoring Mode

is IS, then Stop, you have completed this procedure. Otherwise, perform one of the following:

•

If the

Port Monitoring Mode

is NMON (Not Monitored),

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, select the required port and then click

Select

at the bottom of the window.

2. Under the

Fault Management

section, select AUTO (Automatic) for the

Port

Monitoring Mode

.

3. Click

Apply

at the bottom of the window.

4. Click

Close

to exit the window, then repeat this procedure from

Step 11 .

•

If the

Port Monitoring Mode

is AUTO:

Check the connections at the local cross-connect panel (or equivalent connection point).

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

10-74 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures Procedure 10-13: Provision VT1.5 cross-connections on a

BLSR

Figure 10-21 BLSR VT cross-connection examples

a1-1-1-1 m2-1-3-1-1 A B C D G

Main 2

Node A

Main 1

m1-1-3-1-1 a1-1-1-1 d1-1-1-1-1 g1-1-2-1-1 m2-1-2-1-1

Node D m2-1-1-1-1

Node B d1-1-1-1-1 g1-1-2-1-1 m1-1-1-1-1 m1-1-2-1-1 m1-1-1-1-1 A B C D G m2-1-1-1-1 m1-1-2

Main 1 Main 2

m2-1-2

Node C

VT Accessed

Node A:

2F BLSR Add/Drop VT1.5 cross-connections: m2-1-3-1-1,a1-1-1-1; Source NE = Node D, VT Source NE = Node D

Node B:

2F BLSR Add/Drop VT1.5 cross-connections: m1-1-1-1-1,d1-1-1-1-1; Source NE = NodeC, VT Source NE = NodeD m1-1-2-1-1,g1-1-2-1-1; Source NE = NodeD, VT Source NE = NodeD

Node C:

2-Way Point-to-Point, Through cross-connections: m1-1-1-1-1,m2-1-1-1-1; Source NE = NodeD, Destination NE = NodeB m1-1-2,m2-1-2; Source NE = NodeD, Destination NE = NodeB, VT Accessed = YES

Node D:

2F BLSR Add/Drop VT1.5 cross-connections: m1-1-3-1-1,a1-1-1-1; Source NE = Node A, VT Source NE = Node A m2-1-1-1-1,d1-1-1-1-1; Source NE = NodeC, VT Source NE = NodeB m2-1-2-1-1,g1-1-2-1-1; Source NE = NodeB, VT Source NE = NodeB

MA-DMX-395-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-75

TDM service provisioning procedures

VT cross-connections for BLSR

.................................................................................................................................................................................................................................

BLSR access

A VT-accessed BLSR must contain VT Type 3 nodes but may also include VT Type 2 and/or VT Type 1 nodes. For BLSRs containing VT Type 1 nodes, VT circuits can be provisioned if they do not pass through a Type 1 node. In rings operating with automatic ring discovery, the

Ring Node VT Type

parameter can be reported using the

View

→

Rings

→

Ring Map

command from the System View menu.

Reference the following for Ring Node VT Type descriptions:

•

Type 1: The node does not support VT BLSR access. All Lucent products which support BLSRs but do not support VT access.

•

Type 2: The node (Release 4.0 and later) supports VT-accessed STS-1 pass-through cross-connections only. VT cross-connection provisioning is not supported. Type 2 nodes are equipped with LNW26B 28, 31, 77, or 121B-159B OC-48 OLIU circuit packs.

•

Type 3: The node (Release 4.0 and later) supports VT cross-connections and

VT-accessed STS-1 pass-through cross-connections. Type 3 nodes are equipped with LNW27, 29, 32, 76, or 221-259 OC-48 OLIU circuit packs or LNW56, 57,

58, 523, 527, 554, or 555 OC-192 OLIU circuit packs.

VT cross-connection parameters

In addition to regular BLSR STS-1 cross-connection parameters, the following parameters are required for provisioning VT1.5 BLSR cross-connections:

•

VT Source NE Name

(

vtloca

): vtloca is the source node TID of a VT1.5 BLSR cross-connection.

•

VT Accessed

(

vtacc

): vtacc is an attribute of a STS-1 BLSR pass-through cross-connection. It specifies whether or not the VTs transported within the STS-1 are cross-connected at the VT1.5 rate at other nodes in the circuit.

Rules for VT Source/Destination NE Name parameters

The following rules apply for specifying parameters when manually provisioning the

VT squelch map entries:

VT Cross-Connection Type

1-way unswitched or 2-way unswitched

VT Source NE Name (vtloca)

Must not be provisioned.

1-way pass-through or 2-way pass-through Must not be provisioned.

2-way add/drop (including inter-ring and switched cross-connections)

Must be provisioned if the source aid is a

VT in a BLSR protection group.

.................................................................................................................................................................................................................................

10-76 365-372-301 R6.0

Issue 15, January 2006

TDM service provisioning procedures VT cross-connections for BLSR

1-way (including inter-ring and switched cross-connections)

Must be provisioned if the source aid is a

VT in a BLSR protection group.

Source/Destination NE Name (loca/locz) parameters

In addition to provisioning

vtloca

parameters when provisioning VT cross-connections, it is also necessary to provision the

Source NE Name

(

loca

) and/or

Destination NE Name

(

locz

) parameters for the STS-1 that is carrying the VT connections. For each direction of transmission, the source/destination node of a

VT-accessed STS-1 is the nearest node in the ring at which VT cross-connections are provisioned to that STS-1. When provisioning multiple VT cross-connections on a single STS-1, the STS-1

loca

/

locz

parameter for all the VT cross-connections must be the same.

If, at a given ring node in a VT circuit, the STS-1 carrying the VT traffic will not be

VT accessed at that node, the user may provision a single STS-1 pass-through cross-connection rather than multiple VT pass-through cross-connections. This single cross-connection will not use VT fabric capacity. For this STS-1 cross-connection it is necessary to provision both the

loca

and

locz

parameters. For each direction of transmission, the source/destination node of this STS-1 is the nearest node in the ring at which VT cross-connections are provisioned to that STS-1.

VT Accessed STS-1 pass-through cross-connections

In addition to provisioning the

loca

and

locz

parameters for VT-accessed STS-1 pass-through cross-connections, it is also necessary to mark these cross-connections as

VT Accessed

(

vtacc

) in order to properly unsquelch these STS-1s at switching nodes if the source or destination node is isolated. Likewise, if an STS-1 pass-through is not supporting VT circuits, it must not be marked as VT Accessed.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

10-77

11

11

provisioning procedures

Overview

.................................................................................................................................................................................................................................

Purpose

This chapter includes procedures necessary to provision Ethernet and Data features in

Metropolis

®

DMX.

Contents

Before you begin

Procedure 11-1: Establishing Ethernet services

Procedure 11-2: Establish point-to-point UPSR protected 1GbE full rate private line service (NOTAG mode)

Procedure 11-3: Establish point-to-point UPSR protected GbE service

(802.1q mode)

Procedure 11-4: Establish point-to-point UPSR protected GbE service

(transparent mode)

Procedure 11-5: Establish Ethernet packet ring on a UPSR

Procedure 11-6: Establish 802.1q mode Ethernet service on established packet ring (UPSR)

Procedure 11-7: Establish transparent mode Ethernet service on established packet ring (UPSR)

Procedure 11-8: Establish Ethernet packet ring on a BLSR without NUT

Procedure 11-9: Establish 802.1q mode Ethernet service on established packet ring (BLSR protected)

Procedure 11-10: Establish transparent mode Ethernet service on established packet ring (BLSR protected)

Procedure 11-11: Provision Ethernet LAN port parameters

Procedure 11-12: Provision Ethernet VCG parameters

11-4

11-5

11-11

11-18

11-28

11-37

11-46

11-51

11-55

11-64

11-68

11-72

11-86

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-1

Ethernet/Data network provisioning procedures Overview

Procedure 11-13: Provision Ethernet circuit pack parameters

Procedure 11-14: Establish point-to-point BLSR protected 1GbE full rate private line service (NOTAG mode)

Procedure 11-15: Establish point-to-point BLSR protected GbE service

(802.1q mode)

Procedure 11-16: Establish point-to-point BLSR protected GbE service

(transparent mode)

Procedure 11-17: Establish Ethernet packet ring on a BLSR with non-preemptible unprotected traffic (NUT)

Procedure 11-18: Add bandwidth to a point-to-point UPSR/BLSR protected GbE service (802.1q mode)

Procedure 11-19: Establish a dedicated multiple point private line UPSR protected GbE service (transparent mode)

Procedure 11-20: Add Fast Ethernet services to Ethernet packet ring –

FE to GbE hairpin

Procedure 11-21: Establish LNW71 10/100-PL Fast Ethernet private line service on UPSR

Procedure 11-22: Establish video broadcast network on UPSR

Procedure 11-23: Establish video broadcast network on BLSR

Procedure 11-24: Make cross-connections for Ethernet service

Cross-Connections for Ethernet

Procedure 11-25: Create preferred spanning tree configuration

Procedure 11-26: Change an existing spanning tree configuration

Procedure 11-27: Create/Delete MAC address on Ethernet port

Procedure 11-28: Provision Q in Q stacked VLAN capability

Procedure 11-29: Perform Ethernet loopback transmission test

Procedure 11-30: Enable/Disable LAN port transmission

Procedure 11-31: Provision Ethernet quality of service (QoS)

Procedure 11-32: Provision Ethernet QoS parameters

Procedure 11-33: Provision LCAS, add/enable/remove tributaries

Procedure 11-34: Establish LNW74 10/100-T/F enhanced Fast Ethernet private line service on UPSR

Procedure 11-35: Establish LNW73/LNW73C FC-DPORT SAN transport service on UPSR

11-96

11-99

11-106

11-115

11-124

11-134

11-140

11-150

11-160

11-168

11-185

11-195

11-207

11-216

11-223

11-228

11-230

11-235

11-237

11-238

11-244

11-249

11-257

11-265

.................................................................................................................................................................................................................................

11-2 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-36: Provision LNW73/LNW73C FC-DPORT circuit pack parameters

Procedure 11-37: Provision FC-DPORT DATA port parameters

Procedure 11-38: Provision FC-DPORT VCG parameters

Procedure 11-39: Make cross-connections for LNW73/LNW73C

FC-DPORT SAN transport service

Procedure 11-40: Establish video multi-channel broadcast network on

UPSR/BLSR (NOTAG mode)

Procedure 11-41: Provision Resilient Packet Ring (RPR)-capable VCG parameters

Procedure 11-42: Provision Resilient Packet Ring (RPR)-specific VCG parameters

Procedure 11-43: Bridge and roll Ethernet cross-connections

Procedure 11-44: Establish Resilient Packet Ring (RPR) on a UPSR

Procedure 11-45: Provision Ethernet quality of service (QoS) - RPR

Overview

11-297

11-301

11-305

11-313

11-323

11-271

11-273

11-277

11-280

11-287

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-3

Ethernet/Data network provisioning procedures

Before you begin

.................................................................................................................................................................................................................................

Before you begin

Prior to performing all procedures in this chapter,

1. If not previously completed, install generic and WaveStar

®

CIT software on the PC.

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

2. Connect PC and establish a WaveStar

®

CIT session.

Refer to

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24) .

Required equipment

All procedures in this chapter require that the following equipment is available:

•

Personal Computer (PC) with WaveStar

®

CIT software installed

•

Wrist strap

Important! If additional equipment is required to perform a specific procedure, that additional equipment is listed in that procedure.

.................................................................................................................................................................................................................................

11-4 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-1: Establishing Ethernet services

.................................................................................................................................................................................................................................

Overview

Use this procedure for examples on provisioning Ethernet services.

This procedure provides references to numerous examples for provisioning Ethernet services. They are intended to be used as reference only to provide you with general

Ethernet related provisioning. The examples given may not match your particular configuration. It is impossible to provide examples for all the configurations you may use.

Important! This procedure assumes that the network system has already been established with all nodes of the network properly equipped and operating for standard SONET transmission.

Establishing/Removing Service

Use the examples provided in these procedures for establishing service. When removing service follow the reverse of the procedures.

Important! Under some circumstances, constant pause frames may be transmitted to the link partner when using the LNW63/74 circuit packs for service. When establishing service, if packets are being transmitted to the port before the circuit has been established with cross-connections and enabled tributaries, stuck pause frames may be sent to the link partner. When disabling service, if enough packets were previously transmitted to the port or continue to be transmitted to the port, stuck pause frames may be sent to the link partner.

•

Enabling service — To prevent pause frames to the link partner, ensure that no traffic is being sent to the port before the full circuit has been established including all cross-connections made and the tributaries enabled. If this is not possible, use the ed-eport TL1 command

admin

parameter or the

Configuration

→

Equipment

command from the System View menu to provision

Port

Administration Control

to DISABLE on the LAN port before establishing the cross-connections and enabling tributaries. After all cross-connections are made and the tributaries enabled, enable Port Administration Control.

•

Disabling service — To prevent pause frames to the link partner, remove all traffic from the port first before disabling tributaries and/or deleting cross-connections. If this is not possible, use the ed-eport TL1 command

admin

parameter or the

Configuration

→

Equipment

command from the System

View menu to provision

Port Administration Control

to DISABLE on the

LAN port before disabling tributaries or removing cross-connections.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-5

Ethernet/Data network provisioning procedures Procedure 11-1: Establishing Ethernet services

Restrictions

A Metropolis

®

DMX Access Multiplexer equipped with LNW26B/28 OC-48 OLIUs

(or functionally equivalent LNW77, LNW121-LNW159, LNW121B-LNW159B OC48

OLIUs) have a capacity limit of 24 STS-1s for Ethernet circuit packs installed in

Function slots A, B, or C. Ethernet service assignments are restricted to VCG v1 and v2 on the LNW67/68 2GbE circuit packs when they are installed in Function slots A,

B, or C. In slot D or Growth slot, VCGs v1, v2, v3, and v4 may be used.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter.

2. Obtain the work instructions for the Ethernet service being established.

3. Be familiar with Ethernet service provisioning or have complete work instructions detailing the particular service being established.

Step

1

2

3

4

Perform the following steps to provision Ethernet services.

.................................................................................................................................................................................................

Click on the

Alarm List

button on the System View window and verify no alarms are present.

.................................................................................................................................................................................................

If any alarms are activated, they must be cleared prior to beginning this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

One at a time, use the WaveStar

®

CIT to log in to each Metropolis

®

DMX terminating end node. From the System View menu at each node, select

View

→

Equipment

.

Result:

The View Equipment window opens.

.................................................................................................................................................................................................

Verify that the Ethernet circuit packs have been installed into the required slot 1 of the

Function Unit group (A-1, B-1, C-1, D-1 or G-1) at each Metropolis

®

DMX NE providing Ethernet service.

.................................................................................................................................................................................................................................

11-6 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-1: Establishing Ethernet services

5

Reference:

•

Procedure 4-12: “Install 10/100 Ethernet circuit packs” (p. 4-50)

•

Procedure 4-13: “Install Gigabit Ethernet circuit packs” (p. 4-54)

.................................................................................................................................................................................................

Note the following general order of provisioning requirements for the type of service being provisioned:

1. Use the

Configuration

→

Equipment

command from the System View menu or the ed-eqpt TL1 command to provision the following for each type of Ethernet circuit pack being provisioned:

•

Set VLAN Tagging Mode (NOTAG, 802.1TAG, TRANS, SWITCHED).

Does not apply to the LNW71, LNW74, or LNW63 circuit packs since they are

NOTAG (Private Line) only.

802.1TAG or TRANS mode applies only to the LNW66/67/68 circuit packs.

SWITCHED mode applies only to the LNW70 and LNW78 circuit packs.

SWITCHED mode allows for provisioning of 802.1TAG or TRANS on a virtual switch basis.

•

Set Ethernet Cross Connect Mode (STS1, STS3c, STS12c).

Ethernet Cross Connect Mode applies only to the LNW70, LNW71 and

LNW78 circuit packs.

STS1 mode: This is the initial value. Only virtual concatenation of STS-1 cross-connections can be used for the LNW71. For the LNW70 and LNW78,

STS-1 and virtual concatenation of STS-1s can be used.

STS3c mode: STS-1 and STS-3c cross connections can be used, but at most one cross connection can be made to each VCG. Applies only to the LNW71 circuit pack.

STS12c mode: only STS-3c and STS-12c cross connections can be used as well as virtual concatenations of STS-3c. Applies only to the LNW70 and LNW78 circuit packs.

•

Select VT Virtual Concatenation mode for the LNW74 circuit pack only.

Specifies the number of STS-1s dedicated to VT virtual concatenation. Value 0 specifies no VT concatenation, value of 12 specifies 12 STS1s are reserved for

VT concatenation.

•

Set Ethernet Port Mode.

Ethernet Port Mode applies only to the LNW70 circuit pack.

GX_FX mode: Sets ports 1-4 to operate with optical GbE PTMs (pluggable transmission modules). Sets ports 5-8 to operate with optical FE PTMs.

GT_FX mode: Sets ports 1-4 to operate with electrical GbE PTMs. Sets ports

5-8 to operate with optical FE PTMs.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-7

Ethernet/Data network provisioning procedures Procedure 11-1: Establishing Ethernet services

6

FT_FX mode: Sets ports 1-4 to operate with electrical FE PTMs. Sets ports 5-8 to operate with optical FE PTMs.

Burst and Credit Interval values may also be specified at this time for the

LNW66/67/68 circuit packs. If required, also assign Alarm Severity Assignment

Profiles.

2. Create Virtual Switches and assign ports (must be done second, if required [does not apply to the NOTAG mode or LNW71, LNW74, or LNW63 circuit packs]).

For the LNW70 and LNW78, if VLAN Tagging Mode is set to SWITCHED, then select the Virtual LAN Tagging Mode (802.1TAG or Transparent) for each virtual switch created.

3. Establish SONET cross-connections.

4. Create Spanning Tree groups and assign ports (does not apply to the NOTAG mode). Does not apply to LNW71, LNW74 or LNW63 circuit packs.

5. Establish VLANs and assign ports (802.1Q Tag Mode ONLY). Does not apply to

LNW71, LNW74 or LNW63 circuit packs.

6. Assign port tags (Transparent Tag mode ONLY). Does not apply to LNW71,

LNW74 or LNW63 circuit packs.

.................................................................................................................................................................................................

Refer to one of the following to use as an example for the service being provided:

•

Procedure 11-2: “Establish point-to-point UPSR protected 1GbE full rate private line service (NOTAG mode)” (p. 11-11)

•

Procedure 11-3: “Establish point-to-point UPSR protected GbE service (802.1q

mode)” (p. 11-18)

•

Procedure 11-4: “Establish point-to-point UPSR protected GbE service (transparent mode)” (p. 11-28)

•

Procedure 11-5: “Establish Ethernet packet ring on a UPSR” (p. 11-37)

•

Procedure 11-6: “Establish 802.1q mode Ethernet service on established packet ring

(UPSR)” (p. 11-46)

•

Procedure 11-7: “Establish transparent mode Ethernet service on established packet ring (UPSR)” (p. 11-51)

•

Procedure 11-8: “Establish Ethernet packet ring on a BLSR without NUT”

(p. 11-55)

•

Procedure 11-9: “Establish 802.1q mode Ethernet service on established packet ring

(BLSR protected)” (p. 11-64)

•

Procedure 11-10: “Establish transparent mode Ethernet service on established packet ring (BLSR protected)” (p. 11-68)

•

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

•

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

•

Procedure 11-13: “Provision Ethernet circuit pack parameters” (p. 11-96)

.................................................................................................................................................................................................................................

11-8 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-1: Establishing Ethernet services

•

Procedure 11-14: “Establish point-to-point BLSR protected 1GbE full rate private line service (NOTAG mode)” (p. 11-99)

•

Procedure 11-15: “Establish point-to-point BLSR protected GbE service (802.1q

mode)” (p. 11-106)

•

Procedure 11-16: “Establish point-to-point BLSR protected GbE service

(transparent mode)” (p. 11-115)

•

Procedure 11-17: “Establish Ethernet packet ring on a BLSR with non-preemptible unprotected traffic (NUT)” (p. 11-124)

•

Procedure 11-18: “Add bandwidth to a point-to-point UPSR/BLSR protected GbE service (802.1q mode)” (p. 11-134)

•

Procedure 11-19: “Establish a dedicated multiple point private line UPSR protected

GbE service (transparent mode)” (p. 11-140)

•

Procedure 11-20: “Add Fast Ethernet services to Ethernet packet ring – FE to GbE hairpin” (p. 11-150)

•

Procedure 11-21: “Establish LNW71 10/100-PL Fast Ethernet private line service on UPSR” (p. 11-160)

•

Procedure 11-22: “Establish video broadcast network on UPSR” (p. 11-168)

•

Procedure 11-23: “Establish video broadcast network on BLSR” (p. 11-185)

•

Procedure 11-24: “Make cross-connections for Ethernet service” (p. 11-195)

•

Procedure 11-25: “Create preferred spanning tree configuration” (p. 11-216)

•

Procedure 11-26: “Change an existing spanning tree configuration” (p. 11-223)

•

Procedure 11-27: “Create/Delete MAC address on Ethernet port” (p. 11-228)

•

Procedure 11-28: “Provision Q in Q stacked VLAN capability” (p. 11-230)

•

Procedure 11-29: “Perform Ethernet loopback transmission test” (p. 11-235)

•

Procedure 11-30: “Enable/Disable LAN port transmission” (p. 11-237)

•

Procedure 11-31: “Provision Ethernet quality of service (QoS)” (p. 11-238)

•

Procedure 11-32: “Provision Ethernet QoS parameters” (p. 11-244)

•

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries” (p. 11-249)

•

Procedure 11-34: “Establish LNW74 10/100-T/F enhanced Fast Ethernet private line service on UPSR” (p. 11-257)

•

Procedure 11-35: “Establish LNW73/LNW73C FC-DPORT SAN transport service on UPSR” (p. 11-265)

•

Procedure 11-36: “Provision LNW73/LNW73C FC-DPORT circuit pack parameters” (p. 11-271)

•

Procedure 11-37: “Provision FC-DPORT DATA port parameters” (p. 11-273)

•

Procedure 11-38: “Provision FC-DPORT VCG parameters” (p. 11-277)

•

Procedure 11-39: “Make cross-connections for LNW73/LNW73C FC-DPORT SAN transport service” (p. 11-280)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-9

Ethernet/Data network provisioning procedures Procedure 11-1: Establishing Ethernet services

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

11-10 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-2: Establish point-to-point UPSR protected 1GbE full rate private line service (NOTAG mode)

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring point-to-point UPSR protected

GbE full rate private line Ethernet service using the NOTAG tagging mode. See

Figure

11-1, “Point-to-Point 1GbE full rate private line example” (p. 11-17)

for an example.

This example indicates a full Gigabit bandwidth of 21 STS1s. For the LNW67/68 circuit packs the VCGs are paired when using path protected cross-connections. For the

LNW70/LNW63 circuit pack, there is no pairing of VCGs and each VCG may have from 1 to 21 STS1s cross-connected to support the bandwidth assignment.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Important! On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a

Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.

Privilege level

You must log in as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter. You must also have complete work instructions that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-11

Ethernet/Data network provisioning procedures Procedure 11-2: Establish point-to-point UPSR protected

1GbE full rate private line service (NOTAG mode)

Step

1

2

3

4

5

Use this procedure as an example for configuring a point-to-point UPSR protected

1GbE full rate private line service (NOTAG mode). See

Figure 11-1, “Point-to-Point

1GbE full rate private line example” (p. 11-17)

for an example.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes, if not already performed.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

and/or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the network (indicating node-to-node connections) and list each node’s TID.

This command may take several minutes to complete depending on the size of the network.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the service to be established.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

If the Ethernet circuit pack is already providing service, changing tagging mode will take down any existing service. The existing tagging mode cannot be changed without removing all existing cross-connections and virtual switch provisioning.

CONFIGURE TAGGING MODE

Determine the existing tagging mode and parameters for the circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the

System View menu, select the CP, then click

Select

. Note the VLAN Tagging Mode, and other parameters.

.................................................................................................................................................................................................................................

11-12 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-2: Establish point-to-point UPSR protected

1GbE full rate private line service (NOTAG mode)

6

.................................................................................................................................................................................................

Select one of the following:

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly to

NOTAG but other parameters are not correct, the tagging mode is NOT set to

NOTAG,

Then...

Proceed to

Step 12 .

Proceed to

Step 9 .

Continue with

Step 7 .

7

8

9

10

11

.................................................................................................................................................................................................

If you are going to change the VLAN Tagging Mode that presently exists AND a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the GbE circuit pack being provisioned, then click

Select

. Note if a virtual switch ID has been assigned.

.................................................................................................................................................................................................

If required, use the TL1

dlt-vrtsw

command or select the

Configuration

→

Data

→

Delete Virtual Switch

command from the System View menu, highlight the circuit pack being provisioned, then click

Select

. Highlight the VRTSW ID being deleted, then click

Apply

.

Read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................

Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu. Select the circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Verify/Select

NOTAG

in the Select VLAN Tagging Mode box.

.................................................................................................................................................................................................

Verify/Enter other parameter values (for example,

Burst Size

,

Credit

Interval

[LNW67/68],

Ethernet Cross Connect Mode

and

Port Configuration

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-13

Ethernet/Data network provisioning procedures Procedure 11-2: Establish point-to-point UPSR protected

1GbE full rate private line service (NOTAG mode)

12

13

14

15

[LNW70]) as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary STS-1 cross-connections to be made at each terminating and non terminating node in the network.

Important! Note that full rate Gigabit service requires 21 STS-1 cross-connections.

.................................................................................................................................................................................................

One at a time at each node in the network, use the TL1

ent-crs-sts1

command to provision the cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard at each of the nodes in the network to provision the cross-connections.

Important! Note that cross-connections at the terminating nodes are add/drop and cross-connections at the non terminating nodes are pass-through.

For the LNW70/LNW63 circuit pack, a VCG may have a bandwidth up to 21

STS1s. Also, there is no pairing of VCGs.

Reference:

(p. 11-195)

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connections have been made.

.................................................................................................................................................................................................

Important! For LNW63/70/74 circuit packs, each tributary cross-connected to a

VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been Enabled in both Input and Ouput Direction.

Use the TL1

ed-vcgtrib

command to enable tributaries, or from the System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit

.................................................................................................................................................................................................................................

11-14 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

16

17

18

19

20

Procedure 11-2: Establish point-to-point UPSR protected

1GbE full rate private line service (NOTAG mode)

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! For LNW63/70/74 circuit packs, at least one tributary at each end of the circuit must be Enabled in order for the VCG to go in service.

If required, after all cross-connections have been made, verify that the WAN (VCG)

Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Click on the

VCG Data

tab. Under the

Fault

section of the parameter display, verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, proceed to

Step 21 .

•

If the VCG Monitoring Mode is

Not Monitored

,

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

VCG Data

tab. Under the

Fault

section, select

Auto

for the

VCG Monitoring Mode

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-15

Ethernet/Data network provisioning procedures Procedure 11-2: Establish point-to-point UPSR protected

1GbE full rate private line service (NOTAG mode)

21

22

23

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 19 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

If proper cross-connections have been made, then indications are that either the far-end or near-end circuit pack at each end of the span has failed or must be reset.

If the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near-end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Apply

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near-end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far-end and near-end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

PROVISION LAN PORTS

Use the TL1

ed-eport

command to provision the LAN port parameters, or select

Configuration

→

Equipment

from the System View menu. Expand the details for the circuit pack, highlight the LAN Port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

Click

Apply

. Read the warning message, then click

Yes

to execute the command.

.................................................................................................................................................................................................

PROVISION VCGS

Use the

ed-vcg

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, if window is not already open from the previous step. Expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

.................................................................................................................................................................................................................................

11-16 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-2: Establish point-to-point UPSR protected

1GbE full rate private line service (NOTAG mode)

24

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

.................................................................................................................................................................................................

Click

Apply

. Read the warning message, then click

Yes

to execute the command.

Click

Close

to exit or repeat from

Step 21

for other port provisioning.

E

N D O F

S

T E P S

Figure 11-1 Point-to-Point 1GbE full rate private line example

Node 1 Node 2

M 1 M 2 M 1

IN

IN

M 2

OUT

D

1

V1

V3

V2

V4

GbE

All Customer Packets allowed on Port 1

D

1

V1

V3

V2

V4

GbE

VLAN Tagging Mode = NOTAG

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=NOTAG

UPSR Ring Add/Drop Cross-connections: m1-1-(25-45),d1-v1-(1-21)

M 2

Node 3

M 1

STS1 2-Way Point-to-Point Through cross-connections m1-1-(25-45),m2-1-(25-45)

NC-DMX-231-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-17

Ethernet/Data network provisioning procedures

Procedure 11-3: Establish point-to-point UPSR protected GbE service (802.1q mode)

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring point-to-point UPSR protected

GbE Ethernet service using the 802.1q tagging mode. See

Figure 11-2, “Point-to-Point

GbE using 802.1q tagging mode” (p. 11-27)

for an example.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Important! On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a

Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.

Privilege level

You must log in as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

•

The tagging mode (802.1q) and virtual switch ID.

Step

1

Use this procedure as an example for configuring point-to-point UPSR protected GbE

Ethernet service using the 802.1q tagging mode. See

Figure 11-2, “Point-to-Point GbE using 802.1q tagging mode” (p. 11-27)

for an example.

.................................................................................................................................................................................................

Use the WaveStar

®

performed.

CIT to log in to one of the terminating nodes, if not already

.................................................................................................................................................................................................................................

11-18 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-3: Establish point-to-point UPSR protected

GbE service (802.1q mode)

2

3

4

5

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the network (indicating node-to-node connections) and list each node’s TID.

This command may take several minutes to complete depending on the size of the network.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the service to be established.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

If the Ethernet circuit pack is already providing service, changing tagging mode will take down any existing service. The existing tagging mode cannot be changed without removing all existing cross-connections and virtual switch provisioning.

CONFIGURE TAGGING MODE

Determine the existing tagging mode and parameters for the circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the

System View menu, select the CP, then click

Select

. Note the VLAN Tagging Mode and other parameter values.

The VLAN Tagging Mode for the LNW67/68 circuit packs must be set to 802.1TAG.

The VLAN Tagging Mode for the LNW70 circuit packs must be set to SWITCHED.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-19

Ethernet/Data network provisioning procedures Procedure 11-3: Establish point-to-point UPSR protected

GbE service (802.1q mode)

6

.................................................................................................................................................................................................

Select one of the following:

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly but other parameters are not correct, the tagging mode is NOT set correctly,

Then...

Proceed to

Step 12 .

Proceed to

Step 9 .

Continue with

Step 7 .

7

8

9

10

11

.................................................................................................................................................................................................

If you are going to change the VLAN Tagging Mode that presently exists AND a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the GbE circuit pack being provisioned, then click

Select

. Note if a virtual switch ID has been assigned.

.................................................................................................................................................................................................

If required, use the TL1

dlt-vrtsw

command or select the

Configuration

→

Data

→

Delete Virtual Switch

command from the System View menu, highlight the circuit pack being provisioned, then click

Select

. Highlight the VRTSW ID being deleted, then click

Apply

.

Read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................

Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu. Select the circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Verify/Select the tagging mode in the Select VLAN Tagging Mode box.

.................................................................................................................................................................................................

Verify/Enter other parameter values (for example,

Burst Size

,

Credit

Interval

[LNW67/68],

Ethernet Cross Connect Mode

and

Port Configuration

.................................................................................................................................................................................................................................

11-20 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-3: Establish point-to-point UPSR protected

GbE service (802.1q mode)

12

[LNW70]), as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service.

If the service you are establishing in this procedure is a second service on an existing

GbE circuit pack with all LAN/WAN ports in the same virtual switch, then the existing virtual switch ID must be retained or the ports not in service must be removed from the existing virtual switch and added to a new virtual switch ID.

Creating virtual switches using the

ent-vrtsw

TL1 command or

Configuration

→

Data

→

Create Virtual Switch

command from the System View menu requires you to select the circuit pack and provision the following parameters :

•

Virtual Switch ID

(

vrtswid

) - Value in the range of 1-4095 for the LNW66/67/68 circuit packs. Value in the range of 1-16 for the LNW70 circuit packs.

•

Virtual LAN Tagging Mode

(

tagmd

) - Value of

802.1TAG

or

Transparent

. Applies to LNW70 only.

•

Ethernet (LAN) Ports

(

eplst

) - List or selection of LAN ports associated with the virtual switch ID.

•

VCG (WAN) Ports

(

vcglst

) - List or selection of VCG ports associated with the virtual switch ID.

CREATE VIRTUAL SWITCH

•

For circuit packs not yet in service with no virtual switch assigned:

– Use the TL1

ent-vrtsw

command to create an assigned virtual switch ID or select

Configuration

→

Data

→

Create Virtual Switch

command from the CIT

System View menu.

For the LNW70 circuit pack, select

802.1TAG

for the

Virtual LAN Tagging

Mode

.

•

For circuit packs not yet in service with a virtual switch assigned:

– If a different virtual switch ID is required, use the TL1

dlt-vrtsw

command to delete an assigned virtual switch ID or select

Configuration

→

Data

→

Delete

Virtual Switch

command from the CIT System View menu.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the selected LAN/WAN ports.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-21

Ethernet/Data network provisioning procedures Procedure 11-3: Establish point-to-point UPSR protected

GbE service (802.1q mode)

13

14

15

16

For the LNW70 circuit pack, select

802.1TAG

for the

Virtual LAN Tagging

Mode

.

•

For circuit packs in service with a virtual switch assigned:

– Use the TL1

ed-vrtsw

command or select

Configuration

→

Data

→

Provision

Virtual Switch

command from the CIT System View menu to remove the required ports from a virtual switch.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the required LAN/WAN ports.

For the LNW70 circuit pack, select

802.1TAG

for the

Virtual LAN Tagging

Mode

.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

In Release 3.0 and earlier, additional STS-1 cross-connection capacity may NOT be

added to an in-service Ethernet circuit pack without service interruption.

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary STS-1 cross-connections to be made at each terminating and non terminating node in the network.

Important! Note that full rate Gigabit service requires 21 STS-1 cross-connections.

.................................................................................................................................................................................................

One at a time at each node in the network, use the TL1

ent-crs-sts1

command to provision the cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard at each of the nodes in the network to provision the cross-connections.

Important! Note that cross-connections at the terminating nodes are add/drop and cross-connections at the non terminating nodes are pass-through.

Reference:

(p. 11-195)

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connections have been made.

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

.................................................................................................................................................................................................................................

11-22 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

17

18

19

20

Procedure 11-3: Establish point-to-point UPSR protected

GbE service (802.1q mode)

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been

Enabled in both Input and Ouput Direction.

If required, use the TL1

ed-vcgtrib

command to enable tributaries, or from the

System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, at least one tributary at each end of the circuit must be Enabled in order for the VCG to go in service.

If required, after all cross-connections have been made, verify that the WAN (VCG)

Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-23

Ethernet/Data network provisioning procedures Procedure 11-3: Establish point-to-point UPSR protected

GbE service (802.1q mode)

21

.................................................................................................................................................................................................

Click on the

VCG Data

tab. Under the

Fault

section of the parameter display, verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, proceed to

Step 22 .

•

If the VCG Monitoring Mode is

Not Monitored

,

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

VCG Data

tab. Under the

Fault

section, select

Auto

for the

VCG Monitoring Mode

.

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 19 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

If proper cross-connections have been made, then indications are that either the far-end or near-end circuit pack at each end of the span has failed or must be reset.

If the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near-end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Apply

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near-end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far-end and near-end circuit packs.

.................................................................................................................................................................................................................................

11-24 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

22

Procedure 11-3: Establish point-to-point UPSR protected

GbE service (802.1q mode)

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

After the VLAN ID for customer untagged frames is assigned and service is established in the 802.1q mode, changing the VLAN ID may affect service. If the VLAN IDs are different, service will be affected.

When the VLAN ID for customer untagged frames is changed at one point in the network, the VLAN ID must be changed at all points.

23

24

25

ASSIGN VLAN IDs

Use the TL1

ent-vlan

command to assign the default VLAN ID for customer untagged frames or the customer VLAN ID for tagged frames to the associated LAN ports and VCG WAN ports. Or select

Configuration

→

Data

→

Create VLAN

command from the CIT System View menu.

Reference:

For example, see

Figure 11-2, “Point-to-Point GbE using 802.1q

tagging mode” (p. 11-27) .

Assume a GbE circuit pack is installed in Function slot d-1 and LAN port 2 at each circuit pack is used for service.

Note that a service has been established between Node 1 and Node 2 for customer untagged frames using a default VLAN ID of 34.

Note that a service has been established between Node 1 and Node 2 for customer tagged frames using a VLAN ID of 55.

.................................................................................................................................................................................................

PROVISION LAN PORTS

Use the TL1

ed-eport

command to provision the LAN port parameters, or select

Configuration

→

Equipment

from the System View menu. Expand the details for the circuit pack, highlight the LAN Port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

Click

Apply

. Read the warning message, then click

Yes

to execute the command.

.................................................................................................................................................................................................

PROVISION VCGS

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-25

Ethernet/Data network provisioning procedures

26

Procedure 11-3: Establish point-to-point UPSR protected

GbE service (802.1q mode)

Use the

ed-vcg

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, if window is not already open from the previous step. Expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

.................................................................................................................................................................................................

Click

Apply

. Read the warning message, then click

Yes

to execute the command.

Click

Close

to exit or repeat from

Step 23

for other port provisioning.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

11-26 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-3: Establish point-to-point UPSR protected

GbE service (802.1q mode)

Figure 11-2 Point-to-Point GbE using 802.1q tagging mode

Node 1 Node 2

M 1 M 2 M 1

IN

M 2

OUT

V3

V1

VLAN IDs 34,55 GbE 2

V4

V2

D

V3

V1

VLAN IDs 34,55 GbE 2

V4

V2

VLAN Tagging Mode=802.1TAG (LNW67/68) or

VLAN Tagging Mode=SWITCHED

Cross Connect Mode=STS1 (LNW70)

Virtual Switch ID = 124 (LNW67/68)

Ethernet (LAN) Ports=d1-2; VCG (WAN) Ports=d1-v3 or

Virtual Switch ID = 124 (LNW70)

Virtual LAN Tagging Mode=802.1TAG

Ethernet (LAN) Ports=d1-2; VCG (WAN) Ports=d1-v3

D

UPSR Ring Add/Drop Cross-connections: m1-1-(22-42),d1-v3-(1-21)

Create VLAN

Ent-vlan:tid:fn-d-1:ctag::34:124:dfeplst=d1-2,vcglst=d1-v3

Ent-vlan:tid:fn-d-1:ctag::55:124:eplst=d1-2,vcglst=d1-v3

M 2

Node 3

M 1

STS1 2-Way Point-to-Point Through cross-connections m1-1-(22-42),m2-1-(22-42)

NC-DMX-229-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-27

Ethernet/Data network provisioning procedures

Procedure 11-4: Establish point-to-point UPSR protected GbE service (transparent mode)

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring point-to-point UPSR protected

GbE Ethernet service using the Transparent tagging mode. See

Figure 11-3,

“Point-to-Point GbE using transparent tagging mode” (p. 11-36)

for an example.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Important! On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a

Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

•

The tagging mode (transparent) and virtual switch ID.

Step

1

Use this procedure as an example for configuring point-to-point UPSR protected GbE

Ethernet service using the Transparent tagging mode.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes, if not already performed.

.................................................................................................................................................................................................................................

11-28 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-4: Establish point-to-point UPSR protected

GbE service (transparent mode)

2

3

4

5

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

This command may take several minutes to complete depending on the size of the network.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the service to be established.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

If the Ethernet circuit pack is already providing service, changing tagging mode will take down any existing service. The existing tagging mode cannot be changed without removing all existing cross-connections and virtual switch provisioning.

CONFIGURE TAGGING MODE

Determine the existing tagging mode and parameters for the circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the

System View menu, select the CP, then click

Select

. Note the VLAN Tagging Mode and other parameter values.

The VLAN Tagging Mode for the LNW67/68 circuit packs must be set to

TRANS

. The

VLAN Tagging Mode for the LNW70 circuit packs must be set to

SWITCHED

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-29

Ethernet/Data network provisioning procedures Procedure 11-4: Establish point-to-point UPSR protected

GbE service (transparent mode)

6

.................................................................................................................................................................................................

Select one of the following:

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly but other parameters are not correct, the tagging mode is NOT set correctly,

Then...

Proceed to

Step 12 .

Proceed to

Step 9 .

Continue with

Step 7 .

7

8

9

10

11

.................................................................................................................................................................................................

If you are going to change the VLAN Tagging Mode that presently exists AND a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the GbE circuit pack being provisioned, then click

Select

. Note if a virtual switch ID has been assigned.

.................................................................................................................................................................................................

If required, use the TL1

dlt-vrtsw

command or select the

Configuration

→

Data

→

Delete Virtual Switch

command from the System View menu, highlight the circuit pack being provisioned, then click

Select

. Highlight the VRTSW ID being deleted, then click

Apply

.

Read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................

Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu. Select the circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Verify/Select the tagging mode in the Select VLAN Tagging Mode box.

.................................................................................................................................................................................................

Verify/Enter other parameter values (for example,

Burst Size

,

Credit

Interval

[LNW67/68],

Ethernet Cross Connect Mode

and

Port Configuration

.................................................................................................................................................................................................................................

11-30 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-4: Establish point-to-point UPSR protected

GbE service (transparent mode)

12

[LNW70]), as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service.

If the service you are establishing in this procedure is a second service on an existing

GbE circuit pack with all LAN/WAN ports in the same virtual switch, then the existing virtual switch ID must be retained or the ports not in service must be removed from the existing virtual switch and added to a new virtual switch ID.

Creating virtual switches using the

ent-vrtsw

TL1 command or

Configuration

→

Data

→

Create Virtual Switch

command from the System View menu requires you to select the circuit pack and provision the following parameters :

•

Virtual Switch ID

(

vrtswid

) - Value in the range of 1-4095 for the LNW66/67/68 circuit packs. Value in the range of 1-16 for the LNW70 circuit packs.

•

Virtual LAN Tagging Mode

(

tagmd

) - Value of

802.1TAG

or

Transparent

. Applies to LNW70 only.

•

Ethernet (LAN) Ports

(

eplst

) - List or selection of LAN ports associated with the virtual switch ID.

•

VCG (WAN) Ports

(

vcglst

) - List or selection of VCG ports associated with the virtual switch ID.

ASSIGN VIRTUAL SWITCH ID

•

For circuit packs not yet in service with no virtual switch assigned:

– Use the TL1

ent-vrtsw

command to create an assigned virtual switch ID or select

Configuration

→

Data

→

Create Virtual Switch

command from the CIT

System View menu.

For the LNW70 circuit pack, select

Transparent

for the

Virtual LAN Tagging

Mode

.

•

For circuit packs not yet in service with a virtual switch assigned:

– Use the TL1

dlt-vrtsw

command to delete an assigned virtual switch ID or select

Configuration

→

Data

→

Delete Virtual Switch

command from the CIT

System View menu, if a different virtual switch ID is required.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the selected LAN/WAN ports.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-31

Ethernet/Data network provisioning procedures Procedure 11-4: Establish point-to-point UPSR protected

GbE service (transparent mode)

13

14

15

16

For the LNW70 circuit pack, select

Transparent

for the

Virtual LAN Tagging

Mode

.

•

For circuit packs in service with a virtual switch assigned:

– Use the TL1

ed-vrtsw

command or select

Configuration

→

Data

→

Provision

Virtual Switch

command from the CIT System View menu to remove the required ports from a virtual switch.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the required LAN/WAN ports.

For the LNW70 circuit pack, select

Transparent

for the

Virtual LAN Tagging

Mode

.

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary STS-1 cross-connections to be made at each terminating and non terminating node in the network.

Important! Note that full rate Gigabit service requires 21 STS-1 cross-connections.

.................................................................................................................................................................................................

One at a time at each node in the network, use the TL1

ent-crs-sts1

command to provision the cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard at each of the nodes in the network to provision the cross-connections.

Important! Note that cross-connections at the terminating nodes are add/drop and cross-connections at the non terminating nodes are pass-through.

Reference:

(p. 11-195)

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connections have been made.

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been

Enabled in both Input and Ouput Direction.

Use the TL1

ed-vcgtrib

command to enable tributaries, or from the System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the

.................................................................................................................................................................................................................................

11-32 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-4: Establish point-to-point UPSR protected

GbE service (transparent mode)

17

18

19

20

21

circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, at least one tributary at each end of the circuit must be Enabled in order for the VCG to go in service.

If required, after all cross-connections have been made, verify that the WAN (VCG)

Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Click on the

VCG Data

tab. Under the

Fault

section of the parameter display, verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, proceed to

Step 22 .

•

If the VCG Monitoring Mode is

Not Monitored

,

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-33

Ethernet/Data network provisioning procedures Procedure 11-4: Establish point-to-point UPSR protected

GbE service (transparent mode)

22

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

VCG Data

tab. Under the

Fault

section, select

Auto

for the

VCG Monitoring Mode

.

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 19 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

If proper cross-connections have been made, then indications are that either the far-end or near-end circuit pack at each end of the span has failed or must be reset.

If the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near-end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Apply

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near-end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far-end and near-end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

CREATE PORT TAGs

Use the TL1

ed-eport

and

ed-vcg

commands to assign port tags to the associated

LAN ports and VCG WAN ports. Or, select

Configuration

→

Data

→

Create Port

Tag

command from the CIT System View menu. Highlight the circuit pack being provisioned, then click

Select

. Provision the parameters as required. Click

Apply

, then click

Yes

to the warning message. Click

Close

to exit.

Important! The Peak Information Rate (PIR) rate limiting feature on the

LNW66/LNW67/LNW68 circuit packs will not be effective in transparent mode if the Ethernet Type (ethertype) parameter for the LAN or WAN VCG ports is provisioned to any value other than FFFF or 8100.

.................................................................................................................................................................................................................................

11-34 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-4: Establish point-to-point UPSR protected

GbE service (transparent mode)

23

24

25

.................................................................................................................................................................................................

PROVISION LAN (Ethernet) PORTS

Use the TL1

ed-eport

command to provision parameters for the LAN port being provisioned. Or, select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the LAN port, then click

Select

.

Provision the parameters as required.

Click

Apply

, then click

Yes

to execute the command. Repeat for all ports being provisioned. Click

Close

to exit or continue with the next step.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

PROVISION WAN (VCG) PORTS

Use the TL1

ed-vcg

command to provision parameters for the VCG ports, as required.

Or, select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Click

Apply

, then click

Yes

to execute the command. Repeat for all ports being provisioned. Click

Close

to exit.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

.................................................................................................................................................................................................

Note that this procedure provided the following example of point-to-point UPSR protected GbE service using Transparent tagging mode.

Reference:

In

Figure 11-3, “Point-to-Point GbE using transparent tagging mode”

(p. 11-36) , assume a GbE circuit pack is installed in Function slot fn-d-1 and LAN

port 2 at each circuit pack is used for service.

Note that a service has been established between Node 1 and Node 2 with a default port tag of 55.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-35

Ethernet/Data network provisioning procedures Procedure 11-4: Establish point-to-point UPSR protected

GbE service (transparent mode)

Figure 11-3 Point-to-Point GbE using transparent tagging mode

Node 1 Node 2

M 1 M 2 M 1 M 2

IN

OUT

GbE

Default Port Tag 55

V3

V1

2

V4

V2

D

GbE

Default Port Tag 55

2

V3

V1

V4

V2

D

VLAN Tagging Mode=TRANS (LNW67/68)

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=Trans or

VLAN Tagging Mode=SWITCHED,Cross Connect Mode=STS1 (LNW70)

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=switched,eccmode=sts1

Virtual Switch ID = 124 (LNW67/68)

Ent-vrtsw:tid:fn-d-1:ctag::124:eplst=d1-2,vcglst=d1-v3 or

Virtual Switch ID = 124, Virtual LAN Tagging Mode=Transparent (LNW70)

Ent-vrtsw:tid:fn-d-1:ctag::124:eplst=d1-2,vcglst=d1-v3,tagmd=Trans

UPSR Ring Add/Drop Cross-connections: m1-1-(22-42),d1-v3-(1-21)

Create Port Tag

Ed-eport-1ge:tid:d1-2:ctag:::dftporttag=55

Ed-vcg:tid:d1-v3:ctag:::addporttag=55

M 2

Node 3

M 1

STS1 2-Way Point-to-Point Through cross-connections m1-1-(22-42),m2-1-(22-42)

NC-DMX-230-2

.................................................................................................................................................................................................................................

11-36 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-5: Establish Ethernet packet ring on a UPSR

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for establishing an Ethernet packet ring on a unidirectional path switched ring (UPSR). A packet ring is a set of Ethernet switches

(Ethernet circuit packs) connected to each other in a ring configuration. When the packet ring is first established, the capacity of the ring is predetermined by the number of STS-1 cross-connections (1-21 [LNW66/67/68], 1-48 [LNW70}) applied to the ring and switches. The tagging mode (

802.1TAG

or Transparent [

Trans

]), virtual switch ID, and spanning tree group is also predetermined. For example, see

Figure 11-4, “Ethernet packet ring on a UPSR” (p. 11-45) .

This procedure assumes that the UPSR ring network configuration has already been established and no alarms are present.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the nodes participating in the packet ring network.

•

The shelf slots, circuit packs, ports, and VCGs involved in the packet ring network.

•

The number and type of cross-connections to be made at each node.

•

The tagging mode (transparent or 802.1q), virtual switch ID, and spanning tree group ID.

Step

1

Use this procedure as an example to establish an Ethernet packet ring on a UPSR ring.

See

Figure 11-4, “Ethernet packet ring on a UPSR” (p. 11-45)

for an example.

.................................................................................................................................................................................................

Use the WaveStar

®

performed.

CIT to log in to one of the terminating nodes, if not already

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-37

Ethernet/Data network provisioning procedures Procedure 11-5: Establish Ethernet packet ring on a

UPSR

2

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

This command may take several minutes to complete depending on the size of the network.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

3

4

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the packet ring being established.

5

.................................................................................................................................................................................................

Verify that the Ethernet circuit packs have been installed into the required slot 1 of the

Function Unit or Growth group (A, B, C, D, or G) at each NE providing Ethernet service.

Reference:

Procedure 4-12: “Install 10/100 Ethernet circuit packs” (p. 4-50)

Procedure 4-13: “Install Gigabit Ethernet circuit packs” (p. 4-54)

.................................................................................................................................................................................................

6

CONFIGURE TAGGING MODE

Determine the existing tagging mode for the circuit pack being provisioned. Use the

TL1

rtrv-eqpt

command or select

View

→

Equipment

from the System View menu, select the CP, then click

Select

. Note the VLAN Tagging Mode and other parameter values.

The VLAN Tagging Mode for the LNW66/67/68 circuit packs must be set to

TRANS

or

802.1TAG

. The VLAN Tagging Mode for the LNW70 circuit packs must be set to

SWITCHED

.

Important! When GbE circuit packs are installed in the shelf, the default

″

NOTAG

″ mode is assigned to the circuit pack. When non private line FE circuit packs are installed in the shelf, the default

″

802.1TAG

″ mode is assigned to the circuit pack.

.................................................................................................................................................................................................................................

11-38 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-5: Establish Ethernet packet ring on a

UPSR

.................................................................................................................................................................................................

7

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly but other parameters are not correct, the tagging mode is NOT set correctly,

Then...

Proceed to

Step 13 .

Proceed to

Step 10

Continue with

.

Step 8 .

8

9

10

11

12

.................................................................................................................................................................................................

If you are going to change the VLAN Tagging Mode that presently exists AND a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the GbE circuit pack being provisioned, then click

Select

. Note if a virtual switch ID has been assigned.

.................................................................................................................................................................................................

If required, use the TL1

dlt-vrtsw

command or select the

Configuration

→

Data

→

Delete Virtual Switch

command from the System View menu, select the circuit pack being provisioned, then click Select. Highlight the VRTSW ID being deleted, then click

Apply

.

Read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................

Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu, select the circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Verify/Select the tagging mode (

802.1TAG

,

TRANS

[LNW66,67,68], or

SWITCHED

[LNW70]) in the VLAN Tagging Mode box.

.................................................................................................................................................................................................

Verify/Enter other parameter values (for example,

Burst Size

,

Credit

Interval

[LNW66/67/68],

Ethernet Cross Connect Mode

and

Port Configuration

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-39

Ethernet/Data network provisioning procedures Procedure 11-5: Establish Ethernet packet ring on a

UPSR

13

[LNW70]), as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service.

If the service you are establishing in this procedure is a second service on an existing circuit pack with all LAN/WAN ports in the same virtual switch, then the existing virtual switch ID must be retained or the ports not in service must be removed from the existing virtual switch and added to a new virtual switch ID.

Creating virtual switches using the

ent-vrtsw

TL1 command or

Configuration

→

Data

→

Create Virtual Switch

command from the System View menu requires you to select the circuit pack and provision the following parameters :

•

Virtual Switch ID

(

vrtswid

) - Value in the range of 1-4095 for the LNW66/67/68 circuit packs. Value in the range of 1-16 for the LNW70 circuit packs.

•

Virtual LAN Tagging Mode

(

tagmd

) - Value of

802.1TAG

or

Transparent

. Applies to LNW70 only.

•

Ethernet (LAN) Ports

(

eplst

) - List or selection of LAN ports associated with the virtual switch ID.

•

VCG (WAN) Ports

(

vcglst

) - List or selection of VCG ports associated with the virtual switch ID.

ASSIGN VIRTUAL SWITCH ID

•

For circuit packs not yet in service with no virtual switch assigned:

– Use the TL1

ent-vrtsw

command to create an assigned virtual switch ID or select

Configuration

→

Data

→

Create Virtual Switch

command from the CIT

System View menu.

For the LNW70 circuit pack, select the required

Virtual LAN Tagging Mode

(

802.1TAG

or

Transparent

).

•

For circuit packs not yet in service with a virtual switch assigned:

– Use the TL1

dlt-vrtsw

command to delete an assigned virtual switch ID or select

Configuration

→

Data

→

Delete Virtual Switch

command from the CIT

System View menu, if a different virtual switch ID is required.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the selected LAN/WAN ports.

.................................................................................................................................................................................................................................

11-40 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-5: Establish Ethernet packet ring on a

UPSR

For the LNW70 circuit pack, select the required

Virtual LAN Tagging Mode

(

802.1TAG

or

Transparent

).

•

For circuit packs in service, on only one set of ports, with a virtual switch assigned:

– Use the TL1

ed-vrtsw

command or select

Configuration

→

Data

→

Provision

Virtual Switch

command from the CIT System View menu to remove the required ports from a virtual switch.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the required LAN/WAN ports.

For the LNW70 circuit pack, select the required

Virtual LAN Tagging Mode

(

802.1TAG

or

Transparent

).

.................................................................................................................................................................................................

CAUTION

14

15

16

Service disruption hazard

In Release 3.0 and earlier, additional STS-1 cross-connection capacity may NOT be

added to an in-service Ethernet circuit pack without service interruption.

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary STS-1 cross-connections to be made at each Ethernet terminating node and any pass-through cross-connections to be made at any non terminating nodes in the network.

.................................................................................................................................................................................................

One at a time at each node in the network, use the TL1

ent-crs-sts1

command to provision the cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard at each non terminating node to provision the

2-Way

Point-to-Point, Through

pass-through cross-connections. Use the Cross-Connection

Wizard at each terminating node to provision the Ethernet

Multipoint

(unswitched) cross-connections. For example, see

Figure 11-4, “Ethernet packet ring on a UPSR”

(p. 11-45) .

Reference:

Refer to

Procedure 11-24: “Make cross-connections for Ethernet service” (p. 11-195)

for cross-connection examples.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

to verify that the proper connections have been made.

.................................................................................................................................................................................................

17

Important! For LNW70 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-41

Ethernet/Data network provisioning procedures

18

19

20

21

Procedure 11-5: Establish Ethernet packet ring on a

UPSR

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been

Enabled in both Input and Ouput Direction.

Use the TL1

ed-vcgtrib

command to enable tributaries, or from the System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, at least one tributary at each end of the circuit must be Enabled in order for the VCG to go in service.

If required, after all cross-connections have been made, verify that the WAN (VCG)

Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................................................

11-42 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-5: Establish Ethernet packet ring on a

UPSR

22

.................................................................................................................................................................................................

Click on the

VCG Data

tab. Under the

Fault

section of the parameter display, verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, proceed to

Step 23 .

•

If the VCG Monitoring Mode is

NMON

(Not Monitored),

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

VCG Data

tab. Under the

Fault

section, select

AUTO

for the

VCG Monitoring Mode

.

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 20 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

If proper cross-connections have been made, then indications are that either the far-end or near-end circuit pack at each end of the span has failed or must be reset.

If the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near-end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Apply

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near-end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far-end and near-end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

23

.................................................................................................................................................................................................

CREATE SPANNING TREE GROUP

If required, determine a preferred spanning tree configuration (span to be blocked under nominal conditions), the preferred root node, and spanning tree root priorities for this service.

Important! Note that it is not necessary to determine a preferred spanning tree configuration. A default spanning tree configuration is configured when you establish the spanning tree group.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-43

Ethernet/Data network provisioning procedures Procedure 11-5: Establish Ethernet packet ring on a

UPSR

24

25

Reference:

(p. 11-216)

Procedure 11-25: “Create preferred spanning tree configuration”

.................................................................................................................................................................................................

Use the TL1 command

ent-stgrp

to assign and provision the parameters for the ports involved in the spanning tree group. Or select

Configuration

→

Data

→

Create

Spanning Tree Group

command from the CIT System View menu. For example, see

Figure 11-4, “Ethernet packet ring on a UPSR” (p. 11-45) .

Important! Networks running 802.1d STP support a maximum of up to nine nodes participating in a spanning tree. Networks with more than nine nodes will not reconfigure properly. Spanning tree default parameters support a network of up to nine nodes.

Networks running 802.1w rapid spanning tree protocol (Release 2 or later) support more than nine nodes participating in a spanning tree. To support more than nine nodes in the spanning tree, the maximum age timer must be increased. Note that spanning tree restoration time increases as the number of nodes increase.

If the network consists of more than nine (9) nodes which are participating in the spanning tree configuration, use the following formula to determine the proper setting for the spanning tree maximum age timer (

stmaxage

): 2 x (N + 1), where N equals the number of nodes.

If the network consists of 20 nodes, then the

stmaxage

timer should be set to 42 seconds: 2 x (20 + 1) = 42.

.................................................................................................................................................................................................

Repeat all the assignments in this procedure at each Ethernet node in the network.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

11-44 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-5: Establish Ethernet packet ring on a

UPSR

Figure 11-4 Ethernet packet ring on a UPSR

M 2

Node A

M 1 M 2

Node B

M 1

IN

OUT

V2

V4

1

V1

V3

D

GbE

VLAN Tagging Mode=Transparent or 802.1q (LNW67/68)

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=TRANS(or 802.1TAG) or

VLAN Tagging Mode=SWITCHED (LNW70)

Cross Connect Mode=STS1 (LNW70)

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=switched,eccmode=sts1

Virtual Switch ID = 123 (LNW67/68)

Ent-vrtsw:tid:fn-d-1:ctag::123:eplst=d1-1,vcglst=d1-v1&d-v2 or

Virtual Switch ID = 123 (LNW70)

Virtual LAN Tagging Mode=Transparent or 802.1TAG (LNW70)

Ent-vrtsw:tid:fn-d-1:ctag::123:eplst=d1-1,vcglst=d1-v1&d1-v2,tagmd=Trans

Cross-Connection Wizard Multipoint Cross-connections:

Source AID: m1-1-(1-21),Destination AID: d1-v1-(1-21)

Source AID: m2-1-(1-21),Destination AID: d1-v2-(1-21)

Spanning Tree Group ID (e.g. 1) ent-stgrp:tid::ctag::1,123:vcglst=d1-v1&d1-v21

Node D

M 1 M 2

V2 V1

3

D

FE

VLAN Tagging Mode = 802.1q or Transparent (LNW66)

Example: ed-eqpt:tid:fn-d-1:ctag:ETHPK:vlantagmd=802.1TAG

Example: ed-eqpt:tid:fn-d-1:ctag:ETHPK:vlantagmd=TRANS

Virtual Switch ID (e.g. 123)

Ent-vrtsw:tid:fn-d-1:ctag::123:eplst=d1-3,vcglst=d1-v1&d1-v2

Cross-Connection Wizard Multipoint Cross-connections:

Source AID: m1-1-(1-21),Destination AID: d1-v1-(1-21)

Source AID: m2-1-(1-21),Destination AID: d1-v2-(1-21)

Spanning Tree Group ID (e.g. 1) ent-stgrp:tid::ctag::1,123:vcglst=d1-v1&d1v2

M 1

Node C

M 2

V1 V2

D

STS1 2-Way Point-to-Point Through cross-connections m1-1-(1-21),m2-1-(1-21)

10

FE

VLAN Tagging Mode = 802.1q or Transparent (LNW66)

Example: ed-eqpt:tid:fn-d-1:ctag:ETHPK:vlantagmd=802.1TAG

Example: ed-eqpt:tid:fn-d-1:ctag:ETHPK:vlantagmd=TRANS

Packet Ring on UPSR using multipoint (unswitched) cross-connections

Virtual Switch ID (e.g. 123) fn-

Cross-Connection Wizard Multipoint Cross-connections:

Source AID: m1-1-(1-21),Destination AID: d1-v1-(1-21)

Source AID: m2-1-(1-21),Destination AID: d1-v2-(1-21)

Spanning Tree Group ID (e.g. 1) ent-stgrp:tid::ctag::1,123:vcglst=d1-v1&d1-v2

NC-DMX-232-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-45

Ethernet/Data network provisioning procedures

Procedure 11-6: Establish 802.1q mode Ethernet service on established packet ring (UPSR)

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring Ethernet service using the 802.1q

tagging mode on an established packet ring. See

Figure 11-5, “Example 1 service on

UPSR using 802.1q tagging mode” (p. 11-49)

and

Figure 11-6, “Example 2 service on

UPSR using 802.1q tagging mode” (p. 11-49)

for examples.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Important! The packet ring must already be established on the UPSR before continuing. This procedure assumes the packet ring is established with the necessary tagging modes, virtual switch IDs, cross-connections, and spanning tree groups established. See

Procedure 11-5: “Establish Ethernet packet ring on a

UPSR” (p. 11-37) .

On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

•

The tagging mode (802.1q) and virtual switch ID.

•

The VLAN IDs being assigned.

.................................................................................................................................................................................................................................

11-46 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-6: Establish 802.1q mode Ethernet service on established packet ring (UPSR)

Step

1

2

3

4

5

Use this procedure as an example for configuring Ethernet service on a UPSR protected packet ring using the 802.1q tagging mode. See

Figure 11-5, “Example 1 service on UPSR using 802.1q tagging mode” (p. 11-49)

and

Figure 11-6, “Example 2 service on UPSR using 802.1q tagging mode” (p. 11-49)

for examples.

.................................................................................................................................................................................................

Use the WaveStar

®

performed.

CIT to log in to one of the terminating nodes, if not already

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the terminating nodes, circuit packs, LAN ports, virtual switch ID, and VLAN IDs associated with the service being established.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

After the VLAN ID for customer untagged frames is assigned and service is established in the 802.1q mode, changing the VLAN ID may affect service. If the VLAN IDs are different, service will be affected.

When the VLAN ID for customer untagged frames is changed at one point in the network, the VLAN ID must be changed at all points.

ASSIGN VLAN IDs TO ESTABLISH SERVICE

Use the TL1

ent-vlan

command to assign the default VLAN ID for customer untagged frames or the customer VLAN ID for tagged frames to the associated LAN ports and VCG WAN ports. Or, select

Configuration

→

Data

→

Create VLAN

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-47

Ethernet/Data network provisioning procedures Procedure 11-6: Establish 802.1q mode Ethernet service on established packet ring (UPSR)

6

7

command from the CIT System View menu. For example, see

Figure 11-5, “Example 1 service on UPSR using 802.1q tagging mode” (p. 11-49) .

Important! When configuring a multipoint service in 802.1q mode, if spanning tree

BPDUs from a customer are to be transported across the network, then the same default VLAN must be assigned to all ports associated with the multipoint service.

Reference:

In

Figure 11-5, “Example 1 service on UPSR using 802.1q tagging mode” (p. 11-49) , assume a GbE circuit pack is installed in Function slot d-1 at

Node A using LAN port 1. Assume FE circuit packs are installed in Function slot d-1 at Node B (using LAN port 3) and at Node C (using LAN port 10). Assume the packet ring has already been established.

Note that a service has been established between Node C, Node B, and Node A for customer tagged frames using a VLAN ID of 55.

.................................................................................................................................................................................................

PROVISION LAN PORTS

Use the TL1

ed-eport

command to provision the LAN port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the LAN port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

PROVISION VCGS

Use the

ed-vcg

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

11-48 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-6: Establish 802.1q mode Ethernet service on established packet ring (UPSR)

Figure 11-5 Example 1 service on UPSR using 802.1q tagging mode

Node A Node B

M 2 M 1

M 2 M 1

V2

V4

1

V1

V3

D

GbE

VLAN ID=55

Default VLAN ID=34

V2 V1

D

3

FE

VLAN ID=55

Ent-vlan:NodeB:fn-d-1:ctag::34:123:vcglst=d1-v1&d1-v2

Ent-vlan:NodeB:fn-d-1:ctag::55:123:eplst=d1-3,vcglst=d1-v1&d1-v2

Ent-vlan:NodeA:fn-d-1:ctag::34:123:dfeplst=d1-1,vcglst=d1-v1&d1-v2

Ent-vlan:NodeA:fn-d-1:ctag::55:123:eplst=d1-1,vcglst=d1-v1&d1-v2

M 2

Node E

Service on

UPSR

using multipoint (unswitched) cross-connections

Node D Node C

M 1 M 2 M 1 M 2

OUT

M 1

IN

V1 V2

V4 V3

1

D

GbE

Default VLAN ID=34

V1 V2

D

STS1 2-Way Point-to-Point Through cross-connections m1-1-(1-21),m2-1-(1-21)

10

FE

VLAN ID=55

Ent-vlan:NodeC:fn-d-10:ctag::34:123:vcglst=d1-v1&d1-v2

Ent-vlan:NodeC:fn-d-10:ctag::55:123:eplst=d1-10,vcglst=d1-v1&d1-v2

Ent-vlan:NodeE:fn-d-1:ctag::55:123:vcglst=d1-v1&d1-v2

Ent-vlan:NodeE:fn-d-1:ctag::34:123:dfeplst=d1-1,vcglst=d1-v1&d1-v2

NC-DMX-228-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-49

Ethernet/Data network provisioning procedures Procedure 11-6: Establish 802.1q mode Ethernet service on established packet ring (UPSR)

Figure 11-6 Example 2 service on UPSR using 802.1q tagging mode

Node A Node B

M 2 M 1 M 2 M 1

V2

V4

1

V1

V3

D

GbE

VLAN ID=55

V2 V1

D

3 FE

VLAN ID=55

Ent-vlan:NodeB:fn-d-1:ctag::55:123:eplst=d1-3,vcglst=d1-v1&d1-v2

Ent-vlan:NodeA:fn-d-1:ctag::55:123:eplst=d1-1,vcglst=d1-v1&d1-v2

M 1

Adding Service on Established UPSR Packet Ring (802.1q Mode)

Node D

M 2

IN

M 1

Node C

M 2

OUT

STS1 2-Way Point-to-Point Through cross-connections m1-1-(1-21),m2-1-(1-21)

V1 V2

D

10

FE

VLAN ID=55

Ent-vlan:NodeC:fn-d-1:ctag::55:123:eplst=d1-10,vcglst=d1-v1&d1-v2

NC-DMX-227-2

.................................................................................................................................................................................................................................

11-50 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-7: Establish transparent mode Ethernet service on established packet ring (UPSR)

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring Ethernet service using the

Transparent tagging mode on an established packet ring. See

Figure 11-7, “Example service on UPSR using transparent tagging mode” (p. 11-54)

for an example.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Important! The packet ring must already be established on the UPSR before continuing. This procedure assumes the packet ring is established with the necessary tagging modes, virtual switch IDs, cross-connections, and spanning tree groups established. See

Procedure 11-5: “Establish Ethernet packet ring on a

UPSR” (p. 11-37) .

On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment. See

″

Auto-negotiation disable

″

(5-3) in Chapter 5,

″

Ethernet

″ for more information.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

•

The tagging mode (Transparent) and virtual switch ID.

•

The Port Tags being assigned.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-51

Ethernet/Data network provisioning procedures Procedure 11-7: Establish transparent mode Ethernet service on established packet ring (UPSR)

Step

1

2

3

4

5

6

Use this procedure as an example for configuring Ethernet service on a UPSR protected packet ring using the Transparent tagging mode. See

Figure 11-7, “Example service on UPSR using transparent tagging mode” (p. 11-54)

for an example.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes, if not already performed.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the terminating nodes, circuit packs, LAN ports, virtual switch ID, and VLAN IDs associated with the service being established.

.................................................................................................................................................................................................

CREATE PORT TAGs

Use the TL1

ed-eport

and

ed-vcg

commands to assign port tags to the associated

LAN ports and VCG WAN ports. Or, select

Configuration

→

Data

→

Create Port

Tag

command from the CIT System View menu. Highlight the circuit pack being provisioned, then click

Select

. Provision the parameters as required. Click

Apply

, then click

Yes

to the warning message. Click

Close

to exit.

Important! The Peak Information Rate (PIR) rate limiting feature on the

LNW66/LNW67/LNW68 circuit packs will not be effective in transparent mode if the Ethernet Type (ethertype) parameter for the LAN or WAN VCG ports is provisioned to any value other than FFFF or 8100.

.................................................................................................................................................................................................

PROVISION LAN (Ethernet) PORTS

.................................................................................................................................................................................................................................

11-52 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

7

Procedure 11-7: Establish transparent mode Ethernet service on established packet ring (UPSR)

Use the TL1

ed-eport

command to provision parameters for the LAN port being provisioned. Or, select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the LAN port, then click

Select

.

Provision the parameters as required.

Click

Apply

, then click

Yes

to execute the command. Repeat for all ports being provisioned. Click

Close

to exit or continue with the next step.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

PROVISION WAN (VCG) PORTS

Use the TL1

ed-vcg

command to provision parameters for the VCG ports, as required.

Or, select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Click

Apply

, then click

Yes

to execute the command. Repeat for all ports being provisioned. Click

Close

to exit.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-53

Ethernet/Data network provisioning procedures Procedure 11-7: Establish transparent mode Ethernet service on established packet ring (UPSR)

Figure 11-7 Example service on UPSR using transparent tagging mode

Node A Node B

M 2 M 1 M 2 M 1

V2

V4

1

V1

V3

D

GbE

Default Port Tag=55 ed-eport-1ge:NodeA:d1-1:ctag:::dftporttag=55 ed-vcg:NodeA:d1-v1:ctag:::addporttag=55 ed-vcg:NodeA:d1-v2:ctag:::addporttag=55

V2 V1

D

3

FE

Default Port Tag=55 ed-eport-1ge:NodeB:d1-3:ctag:::dftporttag=55 ed-vcg:NodeB:d1-v1:ctag:::addporttag=55 ed-vcg:NodeB:d1-v2:ctag:::addporttag=55

Adding Service on Established UPSR Packet Ring (Transparent Mode)

M 1

Node D

M 2

IN

M 1

Node C

M 2

STS1 2-Way Point-to-Point Through cross-connections m1-1-(1-21),m2-1-(1-21)

OUT

V1 V2

D

10

FE

Default Port Tag=55 ed-eport-1ge:NodeC:d1-10:ctag:::dftporttag=55 ed-vcg:NodeC:d1-v1:ctag:::addporttag=55 ed-vcg:NodeC:d1-v2:ctag:::addporttag=55

NC-DMX-226-2

.................................................................................................................................................................................................................................

11-54 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-8: Establish Ethernet packet ring on a BLSR without NUT

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for establishing an Ethernet packet ring on a bidirectional line switched ring (BLSR) without using Nonpreemptible Unprotected

Traffic (NUT) access (Release 3 and later). A packet ring is a set of Ethernet switches

(Ethernet circuit packs) connected to each other in a ring configuration. When the packet ring is first established, the capacity of the ring is predetermined by the number of STS-1 cross-connections (1-21 [LNW67/68], 1-48 [LNW70]) applied to the ring and switches. The tagging mode, virtual switch ID, and spanning tree group is also predetermined. For example, see

Figure 11-8, “SONET layer BLSR protected Ethernet packet ring on a BLSR without NUT” (p. 11-63) .

This procedure assumes that the BLSR ring network configuration has already been established and no alarms are present.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters.

Important! This configuration is only possible using the LNW67/68/70 GbE circuit packs. The LNW70 circuit pack allows cross-connections to any of the 32 VCGs in

SWITCHED mode. On the LNW67/68 circuit packs, cross-connections must be made to both VCG 1 and VCG 3, therefore requiring all 4 VCGs. The LNW66 FE circuit pack only has 2 VCGs. No multipoint cross-connections are allowed in this configuration.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the nodes participating in the packet ring network.

•

The shelf slots, circuit packs, ports, VCGs involved in the packet ring network.

•

The number and type of cross-connections to be made at each node.

For circuit packs not supporting LCAS, once the capacity of the packet ring is established, additional capacity (cross-connections) may not be added in service without service interruption.

•

The tagging mode (transparent or 802.1q), virtual switch ID, and spanning tree group ID.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-55

Ethernet/Data network provisioning procedures Procedure 11-8: Establish Ethernet packet ring on a

BLSR without NUT

Step

1

2

3

4

5

Use this procedure as an example to establish an Ethernet packet ring on a BLSR ring.

See

Figure 11-8, “SONET layer BLSR protected Ethernet packet ring on a BLSR without NUT” (p. 11-63)

for an example.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes, if not already performed.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

to retrieve a node-to-node listing of every node in the network.

As an alternative, you can select

View

→

Rings

→

Ring Map

from the System View menu, then select the 2F BLSR port protection group and click

Select

. Select

NVMRING in the Ring Map Source selection box. You may also Display Ring Map

Graph using this command.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map window opens if the

Administration

→

OSI

Routing Map

command was used.

A list of NEs and NE neighbors is displayed if the

View

→

Rings

→

Ring Map

command was used.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the packet ring being established.

.................................................................................................................................................................................................

Verify that the Ethernet circuit packs have been installed into the required slot 1 of the

Function Unit or Growth group (A, B, C, D, or G) at each NE providing Ethernet service.

Reference:

Procedure 4-13: “Install Gigabit Ethernet circuit packs” (p. 4-54)

.................................................................................................................................................................................................

6

Important! If the Ethernet circuit pack is already in service, the existing tagging mode cannot be changed without removing all existing service.

.................................................................................................................................................................................................................................

11-56 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-8: Establish Ethernet packet ring on a

BLSR without NUT

7

CONFIGURE TAGGING MODE

Determine the existing tagging mode for the circuit pack being provisioned. Use the

TL1

rtrv-eqpt

command or select

View

→

Equipment

from the System View menu, select the CP, then click

Select

. Note the VLAN Tagging Mode and other parameter values.

The VLAN Tagging Mode for the LNW67/68 circuit packs must be set to

TRANS

or

802.1TAG

. The VLAN Tagging Mode for the LNW70 circuit packs must be set to

SWITCHED

.

Important! When GbE circuit packs are installed in the shelf, the default

″

NOTAG

″ mode is assigned to the circuit pack.

.................................................................................................................................................................................................

Select one of the following:

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly but other parameters are not correct, the tagging mode is NOT set correctly,

Then...

Proceed to

Step 12 .

Proceed to

Step 10 .

Continue with

Step 8 .

8

9

.................................................................................................................................................................................................

If you are going to change the VLAN Tagging Mode that presently exists AND a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the GbE circuit pack being provisioned, then click

Select

. Note if a virtual switch ID has been assigned.

.................................................................................................................................................................................................

If required, use the TL1

dlt-vrtsw

command or select the

Configuration

→

Data

→

Delete Virtual Switch

command from the System View menu, select the circuit pack being provisioned, then click Select. Highlight the VRTSW ID being deleted, then click

Apply

.

Read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-57

Ethernet/Data network provisioning procedures Procedure 11-8: Establish Ethernet packet ring on a

BLSR without NUT

10

11

12

13

.................................................................................................................................................................................................

Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu, select the circuit pack being provisioned, then click

Select

.

Verify/Select the tagging mode (

802.1TAG

,

TRANS

[LNW66,67,68], or

SWITCHED

[LNW70]) in the VLAN Tagging Mode box.

.................................................................................................................................................................................................

Verify/Enter other parameter values (for example,

Burst Size

,

Credit

Interval

[LNW67/68],

Ethernet Cross Connect Mode

and

Port Configuration

[LNW70]), as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service.

ASSIGN VIRTUAL SWITCH ID

•

For circuit packs not yet in service with no virtual switch assigned:

– Use the TL1

ent-vrtsw

command to create an assigned virtual switch ID or select

Configuration

→

Data

→

Create Virtual Switch

command from the CIT

System View menu.

For the LNW70 circuit pack, select the required

Virtual LAN Tagging Mode

(

802.1TAG

or

Transparent

).

•

For circuit packs not yet in service with a virtual switch assigned:

– Use the TL1

dlt-vrtsw

command to delete an assigned virtual switch ID or select

Configuration

→

Data

→

Delete Virtual Switch

command from the CIT

System View menu, if a different virtual switch ID is required.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the selected LAN/WAN ports.

For the LNW70 circuit pack, select the required

Virtual LAN Tagging Mode

(

802.1TAG

or

Transparent

).

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

.................................................................................................................................................................................................................................

11-58 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-8: Establish Ethernet packet ring on a

BLSR without NUT

14

15

16

Determine the necessary STS-1 cross-connections to be made at each terminating node and any pass-through cross-connections to made at any non terminating nodes in the network.

.................................................................................................................................................................................................

One at a time at each node in the network, use the TL1

ent-crs-sts1

command to provision the cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard to provision the

2F BLSR Add/Drop

Ethernet and

2-Way

Point-to-Point, Through

pass-through cross-connections. For example, see

Figure

11-8, “SONET layer BLSR protected Ethernet packet ring on a BLSR without NUT”

(p. 11-63) .

Important! Cross-connections at the terminating nodes must be made to both VCG

1 and VCG 3.

Reference:

Refer to

Procedure 11-24: “Make cross-connections for Ethernet service” (p. 11-195)

for cross-connection examples.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

to verify that the proper connections have been made.

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been

Enabled in both Input and Ouput Direction.

If required, use the TL1

ed-vcgtrib

command to enable tributaries, or from the

System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-59

Ethernet/Data network provisioning procedures

17

18

19

20

21

Procedure 11-8: Establish Ethernet packet ring on a

BLSR without NUT

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, at least one tributary at each end of the circuit must be Enabled in order for the VCG to go in service.

If required, after all cross-connections have been made, verify that the WAN (VCG)

Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Click on the

VCG Data

tab. Under the

Fault

section of the parameter display, verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, proceed to

Step 22 .

•

If the VCG Monitoring Mode is

NMON

(Not monitored),

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

VCG Data

tab. Under the

Fault

section, select

AUTO

for the

VCG Monitoring Mode

.

.................................................................................................................................................................................................................................

11-60 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-8: Establish Ethernet packet ring on a

BLSR without NUT

22

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 19 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

If proper cross-connections have been made, then indications are that either the far-end or near-end circuit pack at each end of the span has failed or must be reset.

If the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near-end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Apply

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near-end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far-end and near-end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

CREATE SPANNING TREE GROUP

If required, determine a preferred spanning tree configuration (span to be blocked under nominal conditions), the preferred root node, and spanning tree root priorities for this service.

Important! It is not necessary to determine a preferred spanning tree configuration.

A default spanning tree configuration is configured when you establish the spanning tree group.

Reference:

(p. 11-216)

Procedure 11-25: “Create preferred spanning tree configuration”

23

.................................................................................................................................................................................................

Use the TL1

ent-stgrp

command to assign and provision the parameters for the ports involved in the spanning tree group. Or select

Configuration

→

Data

→

Create

Spanning Tree Group

command from the CIT System View menu. For example, see

Figure 11-8, “SONET layer BLSR protected Ethernet packet ring on a BLSR without

NUT” (p. 11-63) .

Important! Both VCGs at each terminating node must be part of the same spanning tree group.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-61

Ethernet/Data network provisioning procedures Procedure 11-8: Establish Ethernet packet ring on a

BLSR without NUT

24

Spanning tree default parameters support a network of up to nine nodes.

Networks running 802.1w rapid spanning tree protocol (Release 2 or later) support more than nine nodes participating in a spanning tree. To support more than nine nodes in the spanning tree, the maximum age timer must be increased. Note that spanning tree restoration time increases as the number of nodes increase.

If the network consists of more than nine (9) nodes which are participating in the spanning tree configuration, use the following formula to determine the proper setting for the spanning tree maximum age timer (

stmaxage

): 2 x (N + 1), where N equals the number of nodes.

If the network consists of 16 nodes, then the

stmaxage

timer should be set to 34 seconds: 2 x (16 + 1) = 34.

.................................................................................................................................................................................................

Repeat all the assignments in this procedure at each Ethernet node in the network.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

11-62 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-8: Establish Ethernet packet ring on a

BLSR without NUT

Figure 11-8 SONET layer BLSR protected Ethernet packet ring on a BLSR without NUT

Node A Node B

M 2 M 1 M 2 M 1

IN

V3

1

V1

2 GbE

Node A 2F BLSR Add/Drop Cross-connections: d1-v1-(1-21),m1-1-(1-21) Source NE=Node B m2-1-(1-21),d1-v3-(1-21) Source NE=Node D

OUT

V3

1

V1

2 GbE

Node B 2F BLSR Add/Drop Cross-connections: m2-1-(1-21),d1-v3-(1-21) Source NE=Node A d1-v1-(1-21),m1-1-(1-21) Source NE=Node C

Packet Ring (GbE Only) on BLSR without NUT

M 1

Node D

M 2 M 1

Node X

M 2 M 1

Node C

M 2

V1

V1

V3 V3

1 2

GbE

2-Way Point-to-Point, Through Cross-connections m1-1-(1-21),m2-1-(1-21)

Node D 2F BLSR Add/Drop Cross-connections: m2-1-(1-21),d1-v3-(1-21) Source NE=Node C d1-v1-(1-21),m1-1-(1-21) Source NE=Node A

Source NE=Node D

Destination NE=Node C

1 2 GbE

Node C 2F BLSR Add/Drop Cross-connections: m2-1-(1-21),d1-v3-(1-21) Source NE=Node B d1-v1-(1-21),m1-1-(1-21) Source NE=Node D

Basic provisioning at all nodes (LNW70):

VLAN Tagging Mode=SWITCHED (LNW70)

Cross Connect Mode=STS1 (LNW70)

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=switched,eccmode=sts1

Virtual Switch ID = 123

Virtual LAN Tagging Mode=Transparent or 802.1TAG

Ethernet (LAN) Ports: d1-1, d1-2

VCG (WAN) Ports: d1-v1, d1-v3

Cross-connections: See examples in figure above

Spanning Tree Group ID (for example, 1)

VCG (WAN) Ports: d1-v1, d1-v3

Basic provisioning at all nodes (LNW67/68):

VLAN Tagging Mode = 802.1TAG or Transparent

Virtual Switch ID (for example, 123)

Ethernet (LAN) Ports: d1-1, d1-2

VCG (WAN) Ports: d1-v1, d1-v3

Cross-connections: See examples in figure above

Spanning Tree Group ID (for example, 1)

VCG (WAN) Ports: d1-v1, d1-v3

NC-DMX-233-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-63

Ethernet/Data network provisioning procedures

Procedure 11-9: Establish 802.1q mode Ethernet service on established packet ring (BLSR protected)

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring Ethernet service using the 802.1q

tagging mode on an established packet ring on a BLSR. See

Figure 11-9, “Example service on BLSR using 802.1q tagging mode” (p. 11-67)

for an example.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Important! The packet ring must already be established on the BLSR before continuing. This procedure assumes the packet ring is established with the necessary tagging modes, virtual switch IDs, cross-connections, and spanning tree groups established. See

Procedure 11-8: “Establish Ethernet packet ring on a BLSR without NUT” (p. 11-55) .

On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

•

The tagging mode (802.1q) and virtual switch ID.

•

The VLAN IDs being assigned.

.................................................................................................................................................................................................................................

11-64 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-9: Establish 802.1q mode Ethernet service on established packet ring (BLSR protected)

Step

1

2

Use this procedure as an example for configuring 802.1q tagging mode Ethernet service on an established packet ring in a BLSR ring.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes, if not already performed.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

to retrieve a node-to-node listing of every node in the network.

As an alternative, you can select

View

→

Rings

→

Ring Map

from the System View menu, then select the 2F BLSR port protection group and click

Select

. Select

NVMRING in the Ring Map Source selection box. You may also Display Ring Map

Graph using this command.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map window opens if the

Administration

→

OSI

Routing Map

command was used.

A list of NEs and NE neighbors is displayed if the

View

→

Rings

→

Ring Map

command was used.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

3

4

.................................................................................................................................................................................................

From your work instructions, determine the terminating nodes, circuit packs, LAN ports, virtual switch ID, WAN (VCG) ports, and VLAN IDs associated with the service being established.

.................................................................................................................................................................................................

CAUTION

5

Service disruption hazard

After the VLAN ID for customer untagged frames is assigned and service is established in the 802.1q mode, changing the VLAN ID may affect service. If the VLAN IDs are different, service will be affected.

When the VLAN ID for customer untagged frames is changed at one point in the network, the VLAN ID must be changed at all points.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-65

Ethernet/Data network provisioning procedures Procedure 11-9: Establish 802.1q mode Ethernet service on established packet ring (BLSR protected)

6

7

ASSIGN VLAN IDs TO ESTABLISH SERVICE

Use the TL1

ent-vlan

command to assign the default VLAN ID for customer untagged frames and/or the customer VLAN ID for tagged frames to the associated

LAN ports and VCG WAN ports. Or, select

Configuration

→

Data

→

Create VLAN

command from the CIT System View menu. For example, see

Figure 11-9, “Example service on BLSR using 802.1q tagging mode” (p. 11-67) .

Important! When configuring a multiple point service in 802.1q mode, if spanning tree BPDUs from a customer are to be transported across the network, then the same default VLAN must be assigned to all ports associated with the service.

Reference:

In

Figure 11-9, “Example service on BLSR using 802.1q tagging mode” (p. 11-67) , assume a GbE circuit pack is installed in Function slot d-1, LAN

port 1 at each circuit pack is used for service, and the packet ring has already been established.

Note that a service has been established between Node D and Node A for customer untagged frames using a default VLAN ID of 34.

Note that a service has been established among Node C, Node B, and Node A for customer tagged frames using a VLAN ID of 55.

.................................................................................................................................................................................................

PROVISION LAN PORTS

Use the TL1

ed-eport

command to provision the LAN port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the LAN port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

PROVISION VCGS

Use the

ed-vcg

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

11-66 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-9: Establish 802.1q mode Ethernet service on established packet ring (BLSR protected)

Figure 11-9 Example service on BLSR using 802.1q tagging mode

Node A Node B

M 2 M 1 M 2 M 1

V3

1

V1

2

GbE

VLAN ID=55

Default VLAN ID=34 ent-vlan:NodeA:fn-d-1:ctag::34:123:dfeplst=d1-1,vcglst= ent-vlan:NodeA: :fnd-1:ctag::55:123:eplst=d1-1,vcglst= d1d1v1& v1& d1d1v3 v3

V3

1

V1

2

GbE

VLAN ID=55 ent-vlan:NodeB: :fn-

:fnd-1:ctag::55:123:eplst=d1-1,vcglst= d1d1d1ent-vlan:NodeB: d-1:ctag::34:123:vcglst= v1& v3 v1& d1v3

M 1

Adding Service on Established

BLSR

Packet Ring (802.1q Mode)

Node D Node C

M 2 M 1

IN

M 2

OUT

V1

1

V3

2 GbE

Default VLAN ID=34 ent-vlan:NodeD: ent-vlan:NodeD:

:fn-

:fnd-1:ctag::34:123:dfeplst=d1-1,vcglst= d-1:ctag::55:123:vcglst= d1v1& d1v3 d1v1& d1v3

V1

1

V3

2 GbE

VLAN ID=55 ent-vlan:NodeC: :fn-

:fnd-1:ctag::55:123:eplst=d1-1,vcglst= d1d1d1ent-vlan:NodeC: d-1:ctag::34:123:vcglst= v1& v3 v1& d1v3

NC-DMX-238-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-67

Ethernet/Data network provisioning procedures

Procedure 11-10: Establish transparent mode Ethernet service on established packet ring (BLSR protected)

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring Ethernet service using the

Transparent tagging mode on an established packet ring on a BLSR. See

Figure 11-10,

“Example service on BLSR using transparent tagging mode” (p. 11-71)

for an example.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Important! The packet ring must already be established on the BLSR before continuing. This procedure assumes the packet ring is established with the necessary tagging modes, virtual switch IDs, cross-connections, and spanning tree groups established. See

Procedure 11-8: “Establish Ethernet packet ring on a BLSR without NUT” (p. 11-55) .

On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

•

The tagging mode (Transparent) and virtual switch ID.

•

The Port Tags being assigned.

.................................................................................................................................................................................................................................

11-68 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Step

Procedure 11-10: Establish transparent mode Ethernet service on established packet ring (BLSR protected)

1

2

3

4

5

Use this procedure as an example for configuring Transparent tagging mode Ethernet service on a BLSR.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes, if not already performed.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

to retrieve a node-to-node listing of every node in the network.

As an alternative, you can select

View

→

Rings

→

Ring Map

from the System View menu, then select the 2F BLSR port protection group and click

Select

. Select

NVMRING in the Ring Map Source selection box. You may also Display Ring Map

Graph using this command.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map window opens if the

Administration

→

OSI

Routing Map

command was used.

A list of NEs and NE neighbors is displayed if the

View

→

Rings

→

Ring Map

command was used.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the terminating nodes, circuit packs, LAN ports, virtual switch ID, WAN (VCG) ports, and VLAN IDs associated with the service being established.

.................................................................................................................................................................................................

CREATE PORT TAGs

Use the TL1

ed-eport

and

ed-vcg

commands to assign port tags to the associated

LAN ports and VCG WAN ports. Or, select

Configuration

→

Data

→

Create Port

Tag

command from the CIT System View menu. Highlight the circuit pack being provisioned, then click

Select

. Provision the parameters as required. Click

Apply

, then click

Yes

to the warning message. Click

Close

to exit.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-69

Ethernet/Data network provisioning procedures Procedure 11-10: Establish transparent mode Ethernet service on established packet ring (BLSR protected)

6

7

Important! The Peak Information Rate (PIR) rate limiting feature on the

LNW66/LNW67/LNW68 circuit packs will not be effective in transparent mode if the Ethernet Type (ethertype) parameter for the LAN or WAN VCG ports is provisioned to any value other than FFFF or 8100.

.................................................................................................................................................................................................

PROVISION LAN (Ethernet) PORTS

Use the TL1

ed-eport

command to provision parameters for the LAN port being provisioned. Or, select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the LAN port, then click

Select

.

Provision the parameters as required.

Click

Apply

, then click

Yes

to execute the command. Repeat for all ports being provisioned. Click

Close

to exit or continue with the next step.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

PROVISION WAN (VCG) PORTS

Use the TL1

ed-vcg

command to provision parameters for the VCG ports, as required.

Or, select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Click

Apply

, then click

Yes

to execute the command. Repeat for all ports being provisioned. Click

Close

to exit.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

11-70 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-10: Establish transparent mode Ethernet service on established packet ring (BLSR protected)

Figure 11-10 Example service on BLSR using transparent tagging mode

Node A Node B

M 2 M 1 M 2 M 1

V3

1

V1

2 GbE

Default Port Tag=55 Default Port Tag=34 ed-eport-1ge:NodeA:d1-1:ctag:::dftporttag=55 ed-eport-1ge:NodeA:d1-2:ctag:::dftporttag=34 ed-vcg:NodeA:d1-v1:ctag:::addporttag=55&34 ed-vcg:NodeA:d1-v3:ctag:::addporttag=55&34

V3

1

V1

2

GbE

Default Port Tag=34 ed-eport-1ge:NodeB:d1-2:ctag:::dftporttag=34 ed-vcg:NodeB:d1-v1:ctag:::addporttag=55&34 ed-vcg:NodeB:d1-v3:ctag:::addporttag=55&34

M 1

Adding Service on Established

BLSR

Packet Ring (Transparent Mode)

Node D Node C

M 2 M 1

IN

M 2

V1

1

V3

2 GbE

Default Port Tag=55 ed-eport-1ge:NodeD:d1-1:ctag:::dftporttag=55 ed-vcg:NodeD:d1-v1:ctag:::addporttag=55&34 ed-vcg:NodeD:d1-v3:ctag:::addporttag=55&34

OUT

V1

1

V3

2 GbE

Default Port Tag=55 ed-eport-1ge:NodeC:d1-1:ctag:::dftporttag=55 ed-vcg:NodeC:d1-v1:ctag:::addporttag=55&34 ed-vcg:NodeC:d1-v3:ctag:::addporttag=55&34

NC-DMX-237-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-71

Ethernet/Data network provisioning procedures

Procedure 11-11: Provision Ethernet LAN port parameters

.................................................................................................................................................................................................................................

Overview

This procedure provides a list of provisionable parameters for Ethernet LAN ports.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The values to be set for each parameter.

Step

1

2

Use this procedure as a reference for provisionable LAN eport parameters.

.................................................................................................................................................................................................

Use the

ed-eport

TL1 command or select

Configuration

→

Equipment

from the

System View menu for the majority of parameters. Expand the details for the circuit pack, select (highlight) the LAN Port, then click

Select

.

Result:

Exceptions to provisioning parameters from the

Configuration

→

Equipment

command will be noted in this procedure.

Reference:

Appendix A, “Provisionable parameters”

.................................................................................................................................................................................................

Use

Table 11-1, “ED-EPORT command provisionable parameters” (p. 11-73)

as reference to provision the necessary LAN port parameters from your work instructions.

Important! Some of the parameters may have already been provisioned from earlier procedures for establishing service or packet rings.

E

N D O F

S

T E P S

ED-EPORT command parameters

Table 11-1, “ED-EPORT command provisionable parameters” (p. 11-73)

lists the provisionable parameters for the

ed-eport

command:

.................................................................................................................................................................................................................................

11-72 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-11: Provision Ethernet LAN port parameters

Parameter

dplxmd epmode eppm tcamd

Table 11-1 ED-EPORT command provisionable parameters

Description

Provisioned Duplex Mode

may have one of the following values:

•

Half

•

Full

•

Auto (initial value)

Duplex Mode applies only to LNW66 10/100T Fast Ethernet ports.

Ethernet

Port Monitoring Mode

may have one of the following values:

•

Auto (initial value) - The port automatically transitions to the in-service state upon detection on the port of a valid input.

•

NMON (not monitored)

Data Port PM Enable

. Use the

Performance

→

Prov PM Settings

command from the System View menu to set this performance monitoring parameter to one of the following values:

•

Enable (initial value)

•

Disable

This parameter controls whether Ethernet performance monitoring is enabled or disabled for the specified Ethernet port.

TCA Monitoring Mode

. This parameter specifies whether performance monitoring Threshold Crossing Alert reporting is enabled or disabled for the port. Use the

Performance

→

Prov PM Settings

command from the

System View menu to set this performance monitoring parameter to one of the following values:

•

Enable

•

Disable (initial value)

TCA reporting will not begin until tcamd is enabled and port monitoring mode is enabled (eppm = Enabled), and the port is in service (epmode =

IS).

tcamd

does not apply to LNW78.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-73

Ethernet/Data network provisioning procedures Procedure 11-11: Provision Ethernet LAN port parameters

Parameter

fcmd autoneg lnrate

Table 11-1 ED-EPORT command provisionable parameters (continued)

Description

Flow Control Mode

may have one of the following values:

•

Enable (Enable Transmit & Receive)

•

Disable (Disable Transmit & Receive)

•

AUTO - autonegotiate (initial value)

•

Drop - Disable end-to-end flow-control Transmit & Receive

ENABLE and DISABLE only control Network-element controlled (local) flow-control. Both ENABLE and DISABLE still allow Customer

Equipment controlled end-to-end flow-control. Initial value is ENABLE.

DROP applies only to the LNW63, LNW70, and LNW74. DROP both disables Network-element controlled flow-control and drops end-to-end flow-control messages.

AUTO does not apply to optical FE ports (ports 17-24) on the LNW74, to optical ports on LNW70, or to FE electrical PTM ports. Initial value is

ENABLE.

fcmd

does not apply to LNW78.

Auto-Negotiation

may have one of the following values:

•

ENABLE - Enables autonegotiation (initial value)

•

DISABLE - Disables autonegotiation

When autonegotiation is Disabled, if any of fcmd, lnrate, mdix or dplxmd parameters are set to AUTO, the NE maintains previously resolved operational states. If a state is unresolved, the following settings take effect:

•

fcmd = ENABLE

•

lnrate = 100M

•

dplxmd = FULL

•

mdix = MDI

This parameter does not apply to optical Fast Ethernet (FE) ports; ports

5-8 on the LNW70 circuit pack or ports 17-24 on the LNW74 circuit pack. This parameter does not apply to Electrical PTM GbE/FE ports.

This parameter does not apply to LNW78.

Port

Provisioned Line Rate

for 10/100T Fast Ethernet (FE) and 10/100-PL

Private Line Ports, may be assigned one of the following values:

•

10M (sets the port as a 10 Mbs port)

•

100M (sets the port as a 100 Mbs port)

•

AUTO (initial value [auto negotiates the port rate])

Parameter ONLY applies to FE ports on LNW66, LNW71, and LNW74

(electrical only) circuit packs.

.................................................................................................................................................................................................................................

11-74 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-11: Provision Ethernet LAN port parameters

Parameter

dftporttag dftpri

Table 11-1 ED-EPORT command provisionable parameters (continued)

Description

Default Port Tag

Create Port Tag

(Default Vlan ID) from the

Configuration

→

Data

→ command is an integer in the range

″

1-4093

″

, or

″

0

″

. A

″

0

″ means that the user does not want a default value to be set.

This parameter is valid only in TRANSPARENT mode and after the port is already assigned as a member of a Virtual Switch (VRTSW).

The dftporttag value cannot be on or be provisioned in the active composite list of Port Tag identifiers added by the addporttag.

This parameter does not apply to the LNW71 10/100-PL Private Line ports, the LNW74 10/100 T/F Fast Ethernet ports, or the LNW63 GBE PL

Gigabit Ethernet Private Line ports.

For LNW70 and LNW78 packs only

dftporttag

values can be provisioned in another virtual switch.

Port Default Priority

Legal values for LNW66, LNW67, and LNW68 ports are

•

High

•

Low

•

Not Applicable (initial value)

A high priority gives a port a higher priority for service than another port.

On the LNW70, this parameter is used to provision the default CoS. This parameter is only valid if the selected port is part of a virtual switch and the vlantagmd of the circuit pack is SWITCHED and the porttype is

BOUNDARY. The allowed values for dftpri are integers in the range 0 to

3 and NA. Value 3 is the highest priority and 0 (initial value) the lowest.

This parameter is not valid if trafmgmtmd is set to TAGPORT or

COSTAGPORT. This parameter is also ignored if trafmgmtmd is set to

PORT and hlayercos is set to DSCP.

On the LNW78, this parameter is the provisioned default CoS having effect only if trafmgmtmd is PORT or COSPORT. The allowed values for dftpri are integers in the range 1 (Class C - lowest priority) to 3 (Class A

- highest value). 1 is the initial value. Changing dftpri is only possible when all QoS services created on this port are deleted. In this scenario, traffic is not interrupted but is metered until the new QoS services are created for the new dftpri.

This parameter does not apply to the LNW63, LNW71, or LNW74 ports.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-75

Ethernet/Data network provisioning procedures Procedure 11-11: Provision Ethernet LAN port parameters

Parameter

tagfilter bcratelimit stpp stpcost sthellotm

Table 11-1 ED-EPORT command provisionable parameters (continued)

Description

Tag Filter

. This parameter is used to enable/disable VLAN/Port Tag filtering and may be one of the following:

•

ENABLE (valid for the LNW70 and LNW78)

•

DISABLE: allows all VLANs/port tags on a port (only valid for the

LNW70).

This parameter does not apply to the LNW63, LNW71, or LNW74

Ethernet ports.

Broadcast and Multicast rate limit. This is the data rate limit, in Mbps, for incoming packets whose destination address is the broadcast address

(FF-FF-FF-FF-FF-FF). It also includes all multicast addresses

(XO-XX-XX-XX-XX-XX where “O” is an odd hexadecimal digit) including Bridge Filtered MAC group addresses used by PAUSE frames,

BPDUs, Link Aggregation, etc. It also limits incoming packets whose destination address has not been learned (and therefore are broadcasted).

This limit applies to the aggregate of all traffic at a port. While broadcast rate limiting is always enabled at a port, setting the limit greater than or equal to the port speed has the effect of no rate limiting.

Valid value is an integer between 0 and 1000000, representing Kbps. A value of 0 (initial value) disables broadcast rate limiting.

Parameter valid for LNW70 and LNW78 circuit packs, if the selected port is part of a virtual switch and the VLAN Tagging Mode of its Ethernet circuit pack is Switched.

Spanning Tree Port Priority (0-255)

. Values range from 0 to 255. The initial value is 128.

This parameter not valid in NOTAG mode.

This parameter applies only to the LNW70.

Spanning Tree Path Cost (0-65535)

. Value is an integer in the range from

1 to 65535. The initial value is 65535.

This parameter not valid in NOTAG mode.

This parameter applies only to the LNW70.

Spanning Tree Hello Timer (1-10 secs.)

. Value is an integer in the range from 1 to 10 seconds. The initial value is 2 seconds.

This parameter not valid in NOTAG mode.

This parameter applies only to the LNW70.

.................................................................................................................................................................................................................................

11-76 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-11: Provision Ethernet LAN port parameters

Parameter

epss stvid ethfcs admin addporttag

Table 11-1 ED-EPORT command provisionable parameters (continued)

Description

Port Spanning Tree Status

. Values:

•

ENABLE (Initial value) - Enables Ethernet port for spanning tree.

•

DISABLE - Disables Ethernet port for spanning tree.

When enabling the Ethernet port for spanning tree, the retrieved spanning tree status could be BLOCKED, DISCARDING or some other status value, depending on the state of the spanning tree; ENABLE is not a retrieved value.

This parameter not valid in NOTAG mode.

This parameter applies only to the LNW70.

Spanning Tree VLAN ID (0 - 4095)

. Values:

•

An integer in the range 0 to 4095. The value 0 means no VLAN tag.

Initial value is 0.

This parameter not valid in NOTAG mode.

This parameter applies only to the LNW70.

Ethernet Frame Check Sequence

(FCS). Controls whether to drop errored frames due to FCS or let them pass. Regardless of this setting, errored frames are always counted in the EFCRC counter. Values:

•

ENABLE (Initial value) - Drop errored frames.

•

DISABLE - Pass errored frames.

This parameter applies only to the LNW63.

Port Administration Control

. This parameter is used to enable/disable a port. It will enable/disable all frames to and from a port. Values:

•

ENABLE - Enables frames to/from port.

•

DISABLE - Disables frames to/from port.

Port Tag

identifiers, from the

Configuration

→

Data

→

Create Port Tag

command, to be added. Values: An integer in the range 1 to 4,093.

The addporttag value cannot be the same as a value provisioned for the

dftporttag parameter.

Except for the LNW70 and LNW78 circuit packs, this parameter is valid only in TRANSPARENT mode and may not be a value in another Virtual

Switch.

For the LNW70 and LNW78 circuit packs, this parameter is valid when vlantagmd is set to SWITCHED and the port belongs to a virtual switch with tagmd set to Transparent. Values can also be provisioned in another virtual switch.

This parameter does not apply to the LNW63, LNW71, or LNW74,

Ethernet ports.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-77

Ethernet/Data network provisioning procedures Procedure 11-11: Provision Ethernet LAN port parameters

Parameter

delporttag rcf rcf-linkdown

Table 11-1 ED-EPORT command provisionable parameters (continued)

Description

List of

Port Tag

identifiers to be deleted. Values: An integer in the range

1 to 4,093. The initial status of this list is empty.

The addporttag or delporttag parameter can be provisioned by this command but not both. They must be provisioned by separate command instances.

This parameter is valid when vlantagmd is set to TRANS or when

vlantagmd is set to SWITCHED.

and the port belongs to a virtual switch with tagmd set to TRANS.

This parameter does not apply to the LNW63, LNW71, or LNW74.

Remote Client Fail

. This parameter enables/disables Remote Client Fail message detection and generation.

Values:

•

ENABLE - Enables Remote Client Fail message

•

DISABLE - Disables Remote Client Fail message (Initial value)

This parameter applies only to the LNW63 and the LNW70 and LNW74 circuit packs when VLAN Tagging Mode (vlantagmd) is set to NOTAG.

This parameter must be enabled at both ends of the circuit in order to function.

Remote Client Fail Link Shutdown

. When rcf is enabled, this parameter controls link shutdown by Remote Client Fail message reception.

Values:

•

ENABLE - Enables link shutdown (Initial Value)

•

DISABLE - Disables link shutdown.

This parameter applies only to the LNW63, LNW70, and LNW74 circuit packs when VLAN Tagging Mode (vlantagmd) is set to NOTAG.

Link Loss Return (LLR) is a feature on some external equipment.

External equipment with LLR enabled will stop sending link pulses back to the LNW63/70/74 if the LNW63/70/74 has stopped transmitting link pulses to the external equipment due to a link shutdown performed by the

Remote Client Fail Link Shutdown feature. Therefore, when the

LNW63/70/74 is connected to equipment that has the Link Loss Return feature enabled, the Remote Client Fail Link Shutdown (rcf-linkdown) option should be disabled to avoid a link shutdown locking problem.

Customers planning to use the CSF feature with RCF-Linkdown enabled should disable LLR on the external equipment.

.................................................................................................................................................................................................................................

11-78 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-11: Provision Ethernet LAN port parameters

Parameter

jumbo mtu_size

Table 11-1 ED-EPORT command provisionable parameters (continued)

Description

JUMBO Frame Support

. This parameter specifies whether JUMBO frames of up to 10240 bytes are supported on the port, addressed by the aid.

Disabling JUMBO support improves latency for sub-rate services and drops JUMBO size frames.

Values:

•

ENABLE (Initial Value)

•

DISABLE

This parameter applies only to the LNW71 circuit pack.

Note:

The LNW66, LNW67 and LNW68 do not have a setting for maximum frame size. For these packs, the maximum size of the frame is the same as for the LNW71 when jumbo is DISABLE (1536 bytes maximum including MAC DA through MAC FCS inclusive).

Note:

Other circuit packs do not use the jumbo parameter (see mtu_size).

The MTU size parameter specifies the Maximum Transmission Unit

(MTU) size (in bytes) supported on the port. The MTU size is the size of the payload in the Ethernet frame, excluding Source and Destination

Address, Type and CRC field, but including all VLAN tags. Any VLAN on the frames or added to the frame by the system will effectively reduce the maximum MTU size. This parameter applies only to the LNW63,

LNW70, LNW74, and LNW78 circuit packs.

•

For LNW63/70/78 ports, the valid value is an integer in the range 46 to 10222 (default is 1508).

•

For LNW74 ports, the valid value is an integer in the range 1500 to

9614 (default is 1508).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-79

Ethernet/Data network provisioning procedures Procedure 11-11: Provision Ethernet LAN port parameters

Parameter

mdix ethertype porttype

Table 11-1 ED-EPORT command provisionable parameters (continued)

Description

Crossover Mode

. This parameter sets the crossover mode for the port.

Values:

•

Auto (Initial default):

The system determines if crossover is needed, then automatically sets the port to AUTOMDIX or AUTOMDI mode.

•

MDIX:

RJ-45 TXP/TXN pins are transmit

RJ-45 RXP/RXN pins are receive

•

MDI:

RJ-45 TXP/TXN pins are receive

RJ-45 RXP/RXN pins are transmit

This parameter does not apply to the LNW66/67/68 circuit packs or to optical ports.

For the LNW74 circuit pack, when autoneg is set to DISABLE, mdix is automatically set to MDIX.

The mdix parameter applies to electrical SPF (GbE/FE) ports.

Ethernet Type

field (TPID). Used to interwork with other vendors’ equipment using stacked VLAN.

This parameter is only valid when the VLAN Tagging Mode of the circuit pack is Transparent.

For the LNW70/LNW78 circuit packs, this parameter is only valid if the selected port on the pack is part of a virtual switch (the VLAN Tagging

Mode of the virtual switch must be Transparent) and the VLAN Tagging

Mode of the circuit pack is Switched. Values:

•

A string in the range

″

0601

″ to

″

FFFF

″

.

•

The default value is

″

FFFF

″

(hexadecimal).

Port Type

. Specifies whether the port is at the boundary of the DiffServ domain or is a port interior to the DiffServ domain. Used in provisioning

QoS services.

Valid values are

•

Boundary (Initial value)

•

Interior

This parameter applies only to the LNW70 and LNW78 circuit ports, when the port is part of a virtual switch, and vlantagmd is SWITCHED.

For LNW78 the only allowed value is Boundary.

.................................................................................................................................................................................................................................

11-80 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-11: Provision Ethernet LAN port parameters

Parameter

trafmgmtmd

Table 11-1 ED-EPORT command provisionable parameters (continued)

Description

Traffic Management Mode

. Specifies how the packets will be divided into traffic flows and the services that can be provided at the port.

Values are:

•

NOTC: This mode is valid for ports with porttype BOUNDARY only in TRANS and 802.1Q tagmd. It is also valid for Private Line ports.

There is no traffic conditioning of packets that are received at the port. This mode allows interworking with LNW66/67/68.

•

PORT (Initial value): This mode is valid for ports with porttype

BOUNDARY only in TRANS and 802.1Q tagmd (see ENT-VRTSW).

It is also valid for Private Line ports. All traffic received at the port is processed by a single traffic conditioner. The user_priority bits are remarked with the dftpri and the drop precedence determined from the traffic conditioner according to the provisioned mapping (see

ED-ERATE).

When the hlayercos parameter is set to DSCP, All traffic received at the port with the same Differentiated Services Code Point (DSCP) is processed by a single traffic conditioner for the CoS that is provisioned for that DSCP (see dscp2cos). There can be one service for each provisioned CoS (up to 4) at the port. The user_priority (L2) bits are remarked with the CoS and the drop precedence, which was determined from the traffic conditioner, according to the provisioned dscp2cos mapping.

When hlayercos is set to NONE, all traffic received at the port is processed by a single traffic conditioner. The user priority bits are remarked with the dftpri and the drop precedence determined from the traffic conditioner according to the provisioned mapping.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-81

Ethernet/Data network provisioning procedures Procedure 11-11: Provision Ethernet LAN port parameters

Parameter

qwt_ntwkAF

Table 11-1 ED-EPORT command provisionable parameters (continued)

Description

•

COSPORT: This mode is valid for ports with porttype BOUNDARY only in 802.1Q tagmd. All traffic received at the port that is tagged with the same 802.1p user priority is processed by a single traffic conditioner for the CoS that is provisioned for that user priority (see userpri2cos in ED-ERATE). There can be one service for each provisioned CoS (up to 4) at the port. The user priority bits are remarked with the CoS and the drop precedence, which was determined from the traffic conditioner, according to the provisioned user priority mapping (see ED-ERATE).

•

TAGPORT: This mode is valid for ports with porttype BOUNDARY only in 802.1Q tagmd. All traffic received at the port that is tagged with the same VLANid is processed by a single traffic conditioner.

The user priority bits are remarked with the dftpri2cos (see

ED-ERATE) and the drop precedence determined from the traffic conditioner according to the provisioned mapping (see ED-ERATE).

•

COSTAGPORT: This mode is valid for ports with porttype

BOUNDARY only in 802.1Q tagmd. All traffic received at the port that is tagged with the same VLANid and the same CoS is processed by a single traffic conditioner for the VLANid and that CoS. There can be one service for each provisioned CoS (up to 4) on each provisioned VLANid at the port. The user priority bits are remarked with the CoS and the drop precedence, which was determined from the traffic conditioner, according to the provisioned user priority mapping (see ED-ERATE).

Setting trafmgmtmd to TAGPORT or COSTAGPORT is not allowed when tagfilter is DISABLE. For the same reason, it is not allowed to set tagfilter to DISABLE when trafmgmtmd is TAGPORT or COSTAGPORT.

This parameter applies to the LNW70 and LNW78 circuit pack but for the

LNW78 the only values are PORT and COSPORT.

Network Port AF Queue Weighting Factor (WF)

. Specifies the weighting factor used by the queue service algorithm for the AF queue for packets coming from network ports. (A network port is a port without a default

VLAN/Port Tag.) Valid value is an integer between 1 and 100 (highest weight). Default is 64.

This parameter applies only if the port is part of a virtual switch when the circuit pack VLAN Tagging Mode (vlantagmd) is set to SWITCHED.

Parameter only applies to the LNW70.

.................................................................................................................................................................................................................................

11-82 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-11: Provision Ethernet LAN port parameters

Parameter

qwt_custAF

Table 11-1 ED-EPORT command provisionable parameters (continued)

Description

Customer Port AF Queue Weighting Factor (WF)

. Specifies the weighting factor used by the queue service algorithm for the AF queue for packets coming from customer ports. A customer port is a port with a default

VLAN/Port Tag, or an Ethernet (LAN) port. Valid value is an integer between 1 and 100 (highest weight). Default is 36.

This parameter applies only if the port is part of a virtual switch when the circuit pack VLAN Tagging Mode (vlantagmd) is set to SWITCHED.

Parameter only applies to the LNW70.

qsz

Total Queue Size

. Specifies the total queue size for the port, including the

EF and AF queues as well as the management queues. Valid value is an integer between 0 and 256 Kbytes (default is 256 Kbytes). The value cannot be greater than the maximum supported frame size (Refer to the

MTU Size parameter.

This parameter applies only if the port is part of a virtual switch when the circuit pack VLAN Tagging Mode (vlantagmd) is set to SWITCHED.

qsz

for LNW78 specifies the size of the individual queues for the port

(the same size for each).

Parameter only applies to the LNW70 and the LNW78.

qminthldy qmaxthldy

Yellow Packet Minimum (Min) Drop Threshold

. Specifies the minimum dropping threshold for yellow packets used by the drop algorithm.

Expressed as a percentage of the total queue size (qsz). Valid value is an integer between 0 and 100% (default is 33%). Value must be less than or equal to Yellow Max Drop Threshold.

This parameter applies only if the port is part of a virtual switch when the circuit pack VLAN Tagging Mode (vlantagmd) is set to SWITCHED.

Parameter only applies to the LNW70 and the LNW78.

Yellow Maximum (Max) Drop Threshold

. Specifies the maximum dropping threshold for yellow packets used by the drop algorithm. Expressed as a percentage of the total queue size (qsz). Valid value is an integer between

0 and 100% (default is 50%). Value must be greater than or equal to qminthldy and less than or equal to qminthldg.

This parameter applies only if the port is part of a virtual switch when the circuit pack VLAN Tagging Mode (vlantagmd) is set to SWITCHED.

Parameter only applies to the LNW70 and the LNW78.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-83

Ethernet/Data network provisioning procedures Procedure 11-11: Provision Ethernet LAN port parameters

Parameter

qminthldg qdropwt0 qdropwt1 qdropwt2 qdropwt3

Table 11-1 ED-EPORT command provisionable parameters (continued)

Description

Green Minimum (Min) Drop Threshold

. Specifies the minimum dropping threshold for yellow packets used by the drop algorithm. Expressed as a percentage of the total queue size (qsz). Valid value is an integer between

1 and 100% (default is 90%). Value must be greater than or equal to qmaxthldy.

This parameter applies only if the port is part of a virtual switch when the circuit pack VLAN Tagging Mode (vlantagmd) is set to SWITCHED.

Parameter only applies to the LNW70 and the LNW78.

CoS 0 Packets Drop Probability Mark

. Specifies the maximum drop probability mark for CoS 0 packets used by the drop algorithm. Valid value is an integer between 0 and 100% (default value is 100%).

qdropwt0 must be

≥ qdropwt1

≥ qdropwt2

≥ qdropwt3.

This parameter applies only if the port is part of a virtual switch when the circuit pack VLAN Tagging Mode (vlantagmd) is set to SWITCHED.

Parameter only applies to the LNW70.

CoS 1 Packets Drop Probability Mark

. Specifies the maximum drop probability mark for CoS 1 packets used by the drop algorithm. Valid value is an integer between 0 and 100% (default value is 100%).

qdropwt0 must be

≥ qdropwt1

≥ qdropwt2

≥ qdropwt3.

This parameter applies only if the port is part of a virtual switch when the circuit pack VLAN Tagging Mode (vlantagmd) is set to SWITCHED.

Parameter only applies to the LNW70 and the LNW78.

CoS 2 Packets Drop Probability Mark

. Specifies the maximum drop probability mark for CoS 2 packets used by the drop algorithm. Valid value is an integer between 0 and 100% (default value is 100%).

qdropwt0 must be

≥ qdropwt1

≥ qdropwt2

≥ qdropwt3.

This parameter applies only if the port is part of a virtual switch when the circuit pack VLAN Tagging Mode (vlantagmd) is set to SWITCHED.

Parameter only applies to the LNW70 and the LNW78.

CoS 3 Packets Drop Probability Mark

. Specifies the maximum drop probability mark for CoS 3 packets used by the drop algorithm. Valid value is an integer value between 0 and 100% (default value is 50%).

qdropwt0 must be

≥ qdropwt1

≥ qdropwt2

≥ qdropwt3.

This parameter applies only if the port is part of a virtual switch when the circuit pack VLAN Tagging Mode (vlantagmd) is set to SWITCHED.

Parameter only applies to the LNW70 and the LNW78.

.................................................................................................................................................................................................................................

11-84 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-11: Provision Ethernet LAN port parameters

Parameter

hlayercos

Table 11-1 ED-EPORT command provisionable parameters (continued)

Description

Higher Layer Class of Service (CoS)

.

This parameter determines whether the packets are classified by a higher level protocol, such as Diffserv Code Point (DSCP) in the IP header.

Values are:

•

NONE: Higher layer is not used for classification (default).

•

DSCP: Higher layer DSCP bits in the IP header are used for classification.

Notes: Higher layer classification is supported only when

trafmgmtmd

is set to

PORT

.

hlayercos

is ignored in other

trafmgmtmd

modes.

hlayercos

parameter applies only to the LNW70.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-85

Ethernet/Data network provisioning procedures

Procedure 11-12: Provision Ethernet VCG parameters

.................................................................................................................................................................................................................................

Overview

This procedure provides a list of provisionable parameters for virtual concatenation groups (VCGs).

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The values to be set for each parameter.

Step

1

2

Use this procedure as a reference for provisioning VCG parameters.

.................................................................................................................................................................................................

Use the

ed-vcg

TL1 command or select

Configuration

→

Equipment

from the

System View menu for the majority of parameters. Expand the details for the circuit pack, select (highlight) the VCG port, then click

Select

.

Result:

Exceptions to provisioning parameters from the

Configuration

→

Equipment

command will be noted in this procedure.

Reference:

Appendix A, “Provisionable parameters”

.................................................................................................................................................................................................

Use

Table 11-2, “ED-VCG command provisionable parameters” (p. 11-87) as reference

to provision the necessary parameters from your work instructions.

Important! Some of the parameters may have already been provisioned from earlier procedures for establishing service or packet rings.

E

N D O F

S

T E P S

ED-VCG command parameters

Table 11-2, “ED-VCG command provisionable parameters” (p. 11-87)

lists the provisionable parameters for the ed-vcg command:

.................................................................................................................................................................................................................................

11-86 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-12: Provision Ethernet VCG parameters

Parameter

stpp stpcost sthellotm stvid vmode vss

Table 11-2 ED-VCG command provisionable parameters

Description

Spanning Tree Port Priority (0-255)

. Values range from 0 to 255. The initial value is 128.

This parameter not valid in NOTAG mode.

This parameter does not apply to the LNW63, LNW71, LNW74, or

LNW78 ports.

Spanning Tree Path Cost (0-65535)

. Value is an integer in the range from

1 to 65535. The initial value is 10.

This parameter not valid in NOTAG mode.

This parameter does not apply to the LNW63, LNW71, LNW74, or

LNW78 ports.

Spanning Tree Hello Timer (1-10 secs.)

. Value is an integer in the range from 1 to 10 seconds. The initial value is 2 seconds.

This parameter not valid in NOTAG mode.

This parameter does not apply to the LNW63, LNW71, LNW74, or

LNW78 ports.

Spanning Tree VLAN ID (0 - 4095)

. Values:

•

An integer in the range 0 to 4095. The value 0 means no VLAN tag.

Initial value is 4095

This parameter not valid in NOTAG mode.

This parameter applies only to the LNW70.

VCG Monitoring Mode

may have one of the following values:

•

AUTO - port automatically goes in-service (IS) when a valid input is received.

•

NMON (not monitored)

VCG Spanning Tree Status

. Values are as follows:

•

Enable (initial value): Enables VCG port for spanning tree

•

Disable: Disables VCG port for spanning tree

When enabling the VCG port for Spanning Tree, the retrieved spanning tree status could be

″ blocked

″

,

″ discarded

″

, or some other status value depending on the state of the spanning tree.

This parameter is not valid in NOTAG mode.

This parameter does not apply to the LNW63, LNW71, LNW74, or

LNW78 ports.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-87

Ethernet/Data network provisioning procedures Procedure 11-12: Provision Ethernet VCG parameters

Parameter

dftpri addporttag delporttag

Table 11-2 ED-VCG command provisionable parameters (continued)

Description

Port Default Priority

A high priority gives a port a higher priority for service than another port.

On the LNW70, this parameter is used to provision the default CoS. It only pertains to ports with porttype BOUNDARY. The allowed values for dftpri are integers in the range 0 to 3 and NA. Value 3 is the highest priority and 0 (initial value) the lowest. This parameter is not valid if trafmgmtmd is set to TAGPORT or COSTAGPORT.

This parameter applies only to the LNW70 ports.

Port Tag

identifiers, from the

Configuration

→

Data

→

Create Port Tag

command, to be added.

Composite list of port tag identifiers to be added. Values are an ampersand (&) (TL1 command) or comma (,) (WaveStar

®

CIT) separated list of port tag identifiers. Port tag identifiers are integers in the range from 1 to 4093.

The addporttag value cannot be the same as a value provisioned for the dftporttag parameter.

Except for the LNW70 circuit pack, this parameter is valid only in

TRANS (transparent) mode and may not be a value in another Virtual

Switch.

For the LNW70 circuit pack, this parameter is valid when the LNW70

VLAN Tagging Mode (vlantagmd) is set to SWITCHED and the port belongs to a virtual switch with tagmd set to TRANS.

This parameter does not apply to the LNW63, LNW71, LNW74 or

LNW78 ports.

List of

Port Tag

identifiers to be deleted. Values: An integer in the range

1 to 4,093. The initial status of this list is empty.

The addporttag or delporttag parameters can be provisioned by this command but not both. They must be provisioned by separate command instances.

This parameter is valid when vlantagmdis set to TRANS or when

vlantagmdis set to SWITCHED and the port belongs to a virtual switch with tagmdset to TRANS.

This parameter does not apply to the LNW63, LNW71, LNW74 or

LNW78 ports.

.................................................................................................................................................................................................................................

11-88 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-12: Provision Ethernet VCG parameters

Parameter

dftporttag tagfilter vpm psctl

Table 11-2 ED-VCG command provisionable parameters (continued)

Description

Default Port Tag

Create Port Tag

(Default Vlan ID) from the

Configuration

→

Data

→ command is an integer in the range

″

1-4093

″

, or

″

0

″

. A

″

0

″ means that the user does not want a default value to be set.

Except for the LNW70 circuit pack, this parameter is valid only in

TRANS (transparent) mode and may not be a value in another Virtual

Switch.

For the LNW70 circuit pack, this parameter is valid when the LNW70

VLAN Tagging Mode (vlantagmd) is set to SWITCHED and the port belongs to a virtual switch with tagmd set to TRANS.

The dftporttag value cannot be on or be provisioned in the active composite list of Port Tag identifiers added by the addporttag.

This parameter does not apply to the LNW63, LNW71 or LNW74 ports.

Tag Filter

. This parameter is used to enable/disable VLAN/Port Tag filtering and may be one of the following:

•

ENABLE (initial value) - filters tags allowed on the port.

•

DISABLE - enables all VLANs/Port Tags on the port

This parameter does not apply to the LNW63, LNW71, LNW74 or

LNW78 ports.

VCG PM Enable

. This parameter controls when performance monitoring is enabled for the specified VCG. Use the

Performance

→

Prov PM

Settings

command from the System View menu to set this performance monitoring parameter to one of the following values:

•

Enable (initial value)

•

Disable

Pause Control

. Pause Control may have one of the following values:

•

TRANSPARENT (full rate end-to-end flow control)

Enable Pause control pass-through

Disable Pause control generation

•

LOCAL (initial value) (sub-rate local flow control)

Disable Pause control pass-through

Enable Pause control generation

•

NONE

Disable Pause control pass-through

Disable Pause control generation

This parameter does not apply to the LNW63, LNW70, LNW71, or

LNW74 Ethernet ports.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-89

Ethernet/Data network provisioning procedures Procedure 11-12: Provision Ethernet VCG parameters

Parameter

ethertype tcamd mtu_size

Table 11-2 ED-VCG command provisionable parameters (continued)

Description

Ethernet Type (in Hex.)

field (TPID). Used to interwork with other vendors’ equipment using stacked VLAN.

Values:

•

A string in the range

″

0601

″ to

″

FFFF

″

.

•

The default value is

″

FFFF

″

(hexadecimal).

Except for the LNW70, this parameter is valid only when vlantagmd is set to TRANS (transparent) mode.

For the LNW70 circuit pack, this parameter is valid when the LNW70

VLAN Tagging Mode (vlantagmd) is set to SWITCHED and the port belongs to a virtual switch with tagmd set to TRANS.

When the Ethertype parameter is provisioned to any value other than

FFFF or 8100, the PIR rate limiting feature on the

LNW66/LNW67/LNW68 is not effective in transparent mode.

TCA Mode Enable

. This parameter specifies whether performance monitoring Threshold Crossing Alert reporting is enabled or disabled for the port, addressed by the aid.

•

Enabled

•

Disabled (initial value)

TCA reporting will not begin until tcamd is enabled and port monitoring mode is enabled (vpm = ENABLE), and the port is in service (vmode =

IS).

This parameter does not apply to the LNW78 ports.

The MTU size parameter specifies the Maximum Transmission Unit

(MTU) size (in bytes) supported on the port. The MTU size is the size of the payload in the Ethernet frame, excluding Source and Destination

Address, Type and CRC field, but including all VLAN tags. Any VLAN on the frames or added to the frame by the system will effectively reduce the maximum MTU size. This parameter applies only to the

LNW70 and LNW78 circuit packs.

•

The valid value is an integer in the range 46 to 10222 (default is

1508).

.................................................................................................................................................................................................................................

11-90 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-12: Provision Ethernet VCG parameters

Parameter

gfp_fcs bcratelimit lcasmd

Table 11-2 ED-VCG command provisionable parameters (continued)

Description

GFP Frame Check Sequence

. This parameter controls the handling of the

GFP FCS field for the specified VCG. The valid values are

•

ENABLE

•

DISABLE

Parameter ONLY valid for LNW63, LNW70 and LNW74 circuit packs.

When interworking with equipment that does NOT support GFP FCS, the parameter should be set to DISABLE.

On the LNW63 and LNW74 circuit packs, this parameter only controls the transmit of the GFP FCS. The GFP FCS on receipt will be handled depending on the presence or not of the GFP FCS field as indicated by the received PFI bit. If GFP FCS is present it will always be checked.

On the LNW70 circuit packs this parameter controls both the transmit and receive of the GFP FCS. On receipt, the GFP FCS field will be checked for (and should be present) when gfp_fcs is ENABLED, and the

GFP FCS will NOT be checked for (and should NOT be present) when gfp_fcs is DISABLED.

Broadcast and Multicast rate limit. This is the data rate limit, in Mbps, for incoming packets whose destination address is the broadcast address

(FF-FF-FF-FF-FF-FF). It also includes all multicast addresses

(XO-XX-XX-XX-XX-XX where “O” is an odd hexadecimal digit) including Bridge Filtered MAC group addresses used by PAUSE frames,

BPDUs, Link Aggregation, etc. It also limits incoming packets whose destination address has not been learned (and therefore are broadcasted).

This limit applies to the aggregate of all traffic at a port. While broadcast rate limiting is always enabled at a port, setting the limit greater than or equal to the port speed has the effect of no rate limiting.

Valid value is an integer value between 0 and 1000000 representing

Kbps. A value of 0 (initial value) disables broadcast rate limiting.

Parameter ONLY valid for LNW70 circuit packs. This parameter is valid if the selected port is part of a virtual switch and the VLAN Tagging

Mode of its Ethernet circuit pack is Switched.

LCAS Mode

. This parameter controls whether LCAS (Link Capacity

Adjustment Scheme) is enabled for the specified VCG. When enabled, the LCAS protocol allows for hitless changes to the provisioned size of the VCG.

Values for LCAS Mode:

•

ENABLE (initial value)

•

DISABLE

The lcasmd parameter applies only to the LNW63, LNW70 and LNW74 circuit packs

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-91

Ethernet/Data network provisioning procedures Procedure 11-12: Provision Ethernet VCG parameters

Parameter

htmr wtr vcat

Table 11-2 ED-VCG command provisionable parameters (continued)

Description

Hold-Off Timer (in milliseconds)

. This parameter specifies the delay between when a tributary is detected faulty and when it is automatically removed from the VCG. It allows underlying protection, if any, to react first for removal of failed links. It applies to all tributaries in the specified VCG

Values:

•

0 to 10,000 ms (10 sec), in 100 millisecond steps. Initial value is

200ms.

•

99,999 ms (represents infinity).

If the vlantagmd is changed to SWITCHED on the LNW70, htmr values for all VCGs will be set to the initial value of 99,999.

This parameter applies only to the LNW63, LNW70 and LNW74

Ethernet ports and is in effect only if LCAS Mode (lcasmd) is set to

ENABLE.

Wait-to-Restore (in seconds)

. This parameter specifies the delay between when a tributary, previously removed from the VCG because of fault, is detected to be normal and when it is automatically returned to the VCG.

It applies to all tributaries in the specified VCG.

Values are from 0 to 3600 seconds in 1 second steps (initial value = 5).

This parameter applies only to the LNW63, LNW70 and LNW74

Ethernet ports and is in effect only if LCAS Mode (lcasmd) is set to

ENABLE.

Virtual Concatenation Mode

. Specifies whether H4 is inserted/monitored for the specified VCG. It has effect only when a single trib, not VT, is cross-connected to the VCG, to allow interworking with non-VCAT equipment.

Valid values are

•

ENABLE (default)

•

DISABLE

The vcat parameter applies only to the LNW63, LNW70 and LNW74 circuit packs.

.................................................................................................................................................................................................................................

11-92 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-12: Provision Ethernet VCG parameters

Parameter

porttype trafmgmtmd qwt_ntwkAF qwt_custAF

Table 11-2 ED-VCG command provisionable parameters (continued)

Description

Port Type

. Specifies whether the port is at the boundary of the DiffServ domain or is a port interior to the DiffServ domain. Used in provisioning

QoS services.

Values are:

•

BOUNDARY

•

INTERIOR (initial value)

This parameter applies only to the LNW70 circuit port, when the port is part of a virtual switch, and vlantagmd is SWITCHED.

Traffic Management Mode

. Specifies how the packets will be divided into traffic flows and the services that can be provided at the port.

Values are:

•

NOTC: Layer 2 bridging will occur but there will be no QoS services at the port.

•

PORT: one QoS service per port

•

COSPORT: one QoS service per Class of Service (COS) value per port

•

TAGPORT: one QoS service per Tag ID value per port

•

COSTAGPORT: QoS service per Class of Service (COS) value per

Tag ID value per port

Network Port AF Queue Weighting Factor (WF)

. Specifies the weighting factor used by the queue service algorithm for the AF queue for packets coming from network ports. (A network port is a port without a default

VLAN/Port Tag.) Valid value is an integer between 1 and 100 (highest weight). Default is 64.

This parameter applies only to an LNW70 circuit pack port that is part of a virtual switch when the circuit pack VLAN Tagging Mode

(vlantagmd) is set to SWITCHED.

Customer Port AF Queue Weighting Factor (WF)

. Specifies the weighting factor used by the queue service algorithm for the AF queue for packets coming from customer ports. A customer port is a port with a default

VLAN/Port Tag, or an Ethernet (LAN) port. Valid value is an integer between 1 and 100 (highest weight). Default is 36.

This parameter applies only to an LNW70 circuit pack port that is part of a virtual switch when the circuit pack VLAN Tagging Mode

(vlantagmd) is set to SWITCHED.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-93

Ethernet/Data network provisioning procedures Procedure 11-12: Provision Ethernet VCG parameters

Parameter

qsz qminthldy qmaxthldy qminthldg qdropwt0

Table 11-2 ED-VCG command provisionable parameters (continued)

Description

Total Queue Size

. Specifies the total queue size for the port, including the EF and AF queues as well as the management queues. Valid value is an integer between 0 and 256 Kbytes (default is 256 Kbytes). The value cannot be greater than the maximum supported frame size (Refer to the

MTU Size parameter.

This parameter applies only to an LNW70 circuit pack port that is part of a virtual switch when the circuit pack VLAN Tagging Mode

(vlantagmd) is set to SWITCHED.

Yellow Packet Minimum (Min) Drop Threshold

. Specifies the minimum dropping threshold for yellow packets used by the drop algorithm.

Expressed as a percentage of the total queue size (qsz). Valid value is an integer between 0 and 100% (default is 33%). Value must be less than or equal to Yellow Max Drop Threshold.

This parameter applies only to an LNW70 circuit pack port that is part of a virtual switch when the circuit pack VLAN Tagging Mode

(vlantagmd) is set to SWITCHED.

Yellow Maximum (Max) Drop Threshold

. Specifies the maximum dropping threshold for yellow packets used by the drop algorithm. Expressed as a percentage of the total queue size (qsz). Valid value is an integer between 0 and 100% (default is 50%). Value must be greater than or equal to qminthldy and less than or equal to qminthldg.

This parameter applies only to an LNW70 circuit pack port that is part of a virtual switch when the circuit pack VLAN Tagging Mode

(vlantagmd) is set to SWITCHED.

Green Minimum (Min) Drop Threshold

. Specifies the minimum dropping threshold for yellow packets used by the drop algorithm. Expressed as a percentage of the total queue size (qsz). Valid value is an integer between 1 and 100% (default is 90%). Value must be greater than or equal to qmaxthldy.

This parameter applies only to an LNW70 circuit pack port that is part of a virtual switch when the circuit pack VLAN Tagging Mode

(vlantagmd) is set to SWITCHED.

CoS 0 Packets Drop Probability Mark

. Specifies the maximum drop probability mark for CoS 0 packets used by the drop algorithm. Valid value is an integer between 0 and 100% (default value is 100%).

qdropwt0 must be

≥ qdropwt1

≥ qdropwt2

≥ qdropwt3.

This parameter applies only to an LNW70 circuit pack port that is part of a virtual switch when the circuit pack VLAN Tagging Mode

(vlantagmd) is set to SWITCHED.

.................................................................................................................................................................................................................................

11-94 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-12: Provision Ethernet VCG parameters

Parameter

qdropwt1 qdropwt2 qdropwt3 ethfcs

Table 11-2 ED-VCG command provisionable parameters (continued)

Description

CoS 1 Packets Drop Probability Mark

. Specifies the maximum drop probability mark for CoS 1 packets used by the drop algorithm. Valid value is an integer between 0 and 100% (default value is 100%).

qdropwt0 must be

≥ qdropwt1

≥ qdropwt2

≥ qdropwt3.

This parameter applies only to an LNW70 circuit pack port that is part of a virtual switch when the circuit pack VLAN Tagging Mode

(vlantagmd) is set to SWITCHED.

CoS 2 Packets Drop Probability Mark

. Specifies the maximum drop probability mark for CoS 2 packets used by the drop algorithm. Valid value is an integer between 0 and 100% (default value is 100%).

qdropwt0 must be

≥ qdropwt1

≥ qdropwt2

≥ qdropwt3.

This parameter applies only to an LNW70 circuit pack port that is part of a virtual switch when the circuit pack VLAN Tagging Mode

(vlantagmd) is set to SWITCHED.

CoS 3 Packets Drop Probability Mark

. Specifies the maximum drop probability mark for CoS 3 packets used by the drop algorithm. Valid value is an integer value between 0 and 100% (default value is 50%).

qdropwt0 must be

≥ qdropwt1

≥ qdropwt2

≥ qdropwt3.

This parameter applies only to an LNW70 circuit pack port that is part of a virtual switch when the circuit pack VLAN Tagging Mode

(vlantagmd) is set to SWITCHED.

Ethernet Frame Check Sequence

(FCS). Controls whether to drop errored frames due to FCS or let them pass. Regardless of this setting, errored frames are always counted in the EFCRC counter. Values:

•

ENABLE (Initial value) - Drop errored frames.

•

DISABLE - Pass errored frames.

This parameter applies only to the LNW63.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-95

Ethernet/Data network provisioning procedures

Procedure 11-13: Provision Ethernet circuit pack parameters

.................................................................................................................................................................................................................................

Overview

This procedure provides a list of provisionable parameters for Ethernet circuit packs.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The values to be set for each parameter.

Step

1

2

Use this procedure as a reference for provisioning Ethernet circuit pack parameters.

.................................................................................................................................................................................................

Use the

ed-eqpt

TL1 command or select

Configuration

→

Equipment

from the

System View menu. Select the Ethernet circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Use

Table 11-3, “ED-EQPT command provisionable parameters” (p. 11-97)

as reference to provision the necessary parameters from your work instructions.

E

N D O F

S

T E P S

ED-EQPT command parameters

Table 11-3, “ED-EQPT command provisionable parameters” (p. 11-97)

lists the provisionable parameters for the Ethernet circuit packs:

.................................................................................................................................................................................................................................

11-96 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-13: Provision Ethernet circuit pack parameters

Parameter

vlantagmd eccmode vt_vcat

Table 11-3 ED-EQPT command provisionable parameters

Description

Vlan Tagging Mode

.

•

802.1TAG

- IEEE 802.1Q mode. Default value for FE circuit packs. Allows VLAN ID assignments to LAN and VCG ports for customer identification. Does not apply to the LNW70,

LNW71, or the LNW74 circuit packs.

•

TRANS

- Transparent mode. Allows Port Tag provisioning independent of customer VLANs. Does not apply to the

LNW70, LNW71, or the LNW74 circuit packs.

•

NOTAG

- No VLAN or port tag assignments. Accepts all customer packets. Default value for Gigabit Ethernet circuit packs. Only mode of operation for the LNW71 and LNW74 circuit packs.

•

SWITCHED

- In this mode, switched Ethernet ports are allowed on the Ethernet circuit pack. The vlantagmd (TRANS or

802.1TAG) is selectable per virtual switch (ent-vrtsw), not on the circuit pack. Applies only to the LNW70 circuit pack. This mode is also the only mode that applies to the LNW78 circuit pack.

Ethernet Cross Connect Mode

•

STS1

- STS-1 Cross-Connect mode supports only STS-1 cross-connections. For the LNW71, STS1 mode supports one or two STS-1 cross-connections to each of 24 VCGs (1-24). For the LNW70 and LNW78, STS1 mode supports up to 48 STS-1 cross-connections to each VCG.

•

STS3c

- STS-3c Cross-Connect mode supports at most one

STS-3c or one STS-1 cross-connection to each of the first 16

VCGs (1-16), (VCGs 17-24 are not used). Applies only to the

LNW71 circuit pack.

•

STS12c

- STS-12c Cross-Connect mode supports STS-3c,

STS12c,or virtual concatenated STS3c cross-connections to each

VCG. Applies to the LNW70 and LNW78 circuit packs.

This parameter does not apply to the LNW74 circuit pack.

VT Virtual Concatenation

: Determines the number of STS-1s dedicated to VT virtual concatenation.

A value of

0

indicates that VT virtual concatenation is disabled. A value of

12

indicates that 12 STS-1s (336 VT1.5s) are reserved for

VT virtual concatenation. Up to 63 VT1.5s may be assigned to any

VCG.

Only applies to the LNW74 circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-97

Ethernet/Data network provisioning procedures Procedure 11-13: Provision Ethernet circuit pack parameters

Parameter

brst cint enetmd

Table 11-3 ED-EQPT command provisionable parameters (continued)

Description

Burst Size

(1-255): Burst size determines the length or size of the burst that will be allowed by the peak information rate (PIR) policer. The valid range is 1 to 255. The default is 5.

A larger value of burst size means that larger bursts will be allowed; a smaller value of burst size means that the PIR is more strictly enforced and less

″ burstability

″ is allowed. This parameter affects policing for all VLANs (in 802.1Q mode) or all port tags (in transparent mode).

This parameter does not apply to the LNW63, LNW70, LNW71,

LNW74, or LNW78 Ethernet circuit packs.

Credit Interval

(1-4095): Credit interval for adding tokens to the token buckets used by the peak information rate (PIR) policer. The valid range is 1 to 4095. The default is 125, which corresponds to an interval of approximately 65.5 ms.

The minimum value of 1 corresponds to an interval of 524.288 us.

The maximum value of 4095 corresponds to 2.15 sec. This parameter affects policing for all VLANs (in 802.1Q mode) or all port tags (in transparent mode).

This parameter does not apply to the LNW63, LNW70, LNW71,

LNW74, or LNW78 Ethernet circuit packs.

Ethernet

Port Configuration

. This parameter allows the Ethernet ports to operate with different PTMs. This parameter is valid when

type = ETHPK

. Values are:

•

GX_FX

(initial value).

For the LNW70, sets ports 1-4 to operate with optical GbE

PTMs. Sets ports 5-8 to operate with optical FE PTMs.

For the LNW78, sets ports 1-2 to operate with optical GbE

PTMs. Sets ports 5-8 to operate with optical FE PTMs.

•

GT_FX

For the LNW70, sets ports 1-4 to operate with electrical GbE

PTMs. Sets ports 5-8 to operate with optical FE PTMs.

•

FT_FX

For the LNW70, sets ports 1-4 to operate with electrical FE

PTMs. Sets ports 5-8 to operate with optical FE PTMs.

•

GX

(initial value)

For the LNW63 sets ports 1-4 to operate with optical GbE

PTMs.

.................................................................................................................................................................................................................................

11-98 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-14: Establish point-to-point BLSR protected

1GbE full rate private line service (NOTAG mode)

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring point-to-point BLSR protected full rate GbE private line Ethernet service using the NOTAG tagging mode. See

Figure

11-11, “Point-to-Point 1GbE full rate private line example” (p. 11-105)

for an example.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Important! On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a

Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

Step

1

Use this procedure as an example for configuring a point-to-point BLSR protected

1GbE full rate private line service (NOTAG mode). See

Figure 11-11, “Point-to-Point

1GbE full rate private line example” (p. 11-105)

for an example.

.................................................................................................................................................................................................

Use the WaveStar

®

performed.

CIT to log in to one of the terminating nodes, if not already

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-99

Ethernet/Data network provisioning procedures Procedure 11-14: Establish point-to-point BLSR protected

1GbE full rate private line service (NOTAG mode)

2

3

4

5

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Neighbor Map

command and note the NEs connected to Main 1 and Main 2.

Access each of the NEs identified and select the

Administration

→

OSI Neighbor

Map

command and note the NEs connected to Main 1 and Main 2.

Repeat the above until the backbone ring can be sketched.

As an alternative, you can select

View

→

Rings

→

Ring Map

from the System View menu, then select the 2F BLSR port protection group and click

Select

. Select

NVMRING in the Ring Map Source selection box. You may also Display Ring Map

Graph using this command.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map window opens if the

Administration

→

OSI

Neighbor Map

command was used.

A list of NEs and NE neighbors is displayed if the

View

→

Rings

→

Ring Map

command was used.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the service to be established.

.................................................................................................................................................................................................

Important! If the Ethernet circuit pack is already in service, the existing tagging mode cannot be changed without removing all existing cross-connections and virtual switch provisioning.

CONFIGURE TAGGING MODE

Determine the existing tagging mode and parameters for the circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the

System View menu, select the CP, then click

Select

. Note the VLAN Tagging Mode, and other parameters.

.................................................................................................................................................................................................................................

11-100 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-14: Establish point-to-point BLSR protected

1GbE full rate private line service (NOTAG mode)

6

.................................................................................................................................................................................................

Select one of the following:

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly to

NOTAG but other parameters are not correct, the tagging mode is NOT set to

NOTAG,

Then...

Proceed to

Step 12 .

Proceed to

Step 9 .

Continue with

Step 7 .

7

8

9

10

11

.................................................................................................................................................................................................

If you are going to change the VLAN Tagging Mode that presently exists AND a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the GbE circuit pack being provisioned, then click

Select

. Note if a virtual switch ID has been assigned.

.................................................................................................................................................................................................

If required, use the TL1

dlt-vrtsw

command or select the

Configuration

→

Data

→

Delete Virtual Switch

command from the System View menu, highlight the circuit pack being provisioned, then click

Select

. Highlight the VRTSW ID being deleted, then click

Apply

.

Read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................

Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu. Select the circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Verify/Select

NOTAG

in the Select VLAN Tagging Mode box.

.................................................................................................................................................................................................

Verify/Enter other parameter values (for example,

Burst Size

,

Credit

Interval

[LNW67/68],

Ethernet Cross Connect Mode

and

Port Configuration

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-101

Ethernet/Data network provisioning procedures Procedure 11-14: Establish point-to-point BLSR protected

1GbE full rate private line service (NOTAG mode)

12

13

14

15

[LNW70]) as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary STS-1 cross-connections to be made at each non terminating node in the network and the

2F BLSR Add/Drop

cross-connections to be made at the terminating nodes.

Important! Note that full rate Gigabit service requires 21 STS-1 cross-connections.

.................................................................................................................................................................................................

One at a time at each node in the network, use the TL1

ent-crs-sts1

command to provision the cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard at each of the nodes in the network to provision the

2-Way

Point-to-Point, Through

and

2F BLSR Add/Drop

cross-connections.

Important! Note that cross-connections at the terminating nodes are add/drop and cross-connections at the non terminating nodes are pass-through.

Reference:

(p. 11-195)

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connections have been made.

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been

Enabled in both Input and Ouput Direction.

If required, use the TL1

ed-vcgtrib

command to enable tributaries, or from the

System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

.................................................................................................................................................................................................................................

11-102 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

16

17

18

19

20

Procedure 11-14: Establish point-to-point BLSR protected

1GbE full rate private line service (NOTAG mode)

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, at least one tributary at each end of the circuit must be Enabled in order for the VCG to go in service.

If required, after all cross-connections have been made, verify that the WAN (VCG)

Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Click on the

VCG Data

tab. Under the

Fault

section of the parameter display, verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, proceed to

Step 21 .

•

If the VCG Monitoring Mode is

NMON

(Not Monitored),

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

VCG Data

tab. Under the

Fault

section, select

AUTO

for the

VCG Monitoring Mode

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-103

Ethernet/Data network provisioning procedures Procedure 11-14: Establish point-to-point BLSR protected

1GbE full rate private line service (NOTAG mode)

21

22

23

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 18 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

If proper cross-connections have been made, then indications are that either the far-end or near-end circuit pack at each end of the span has failed or must be reset.

If the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near-end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Apply

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near-end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far-end and near-end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

PROVISION LAN PORTS

Use the TL1

ed-eport

command to provision the LAN port parameters, or select

Configuration

→

Equipment

from the System View menu. Expand the details for the circuit pack, highlight the LAN Port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

Click

Apply

. Read the warning message, then click

Yes

to execute the command.

Repeat from

Step 21

for each LAN port being provisioned.

.................................................................................................................................................................................................

PROVISION VCGS

Use the

ed-vcg

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, if window is not already open from the previous step. Expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

.................................................................................................................................................................................................................................

11-104 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-14: Establish point-to-point BLSR protected

1GbE full rate private line service (NOTAG mode)

24

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

.................................................................................................................................................................................................

Click

Apply

. Read the warning message, then click

Yes

to execute the command.

Repeat from

Step 23

for all WAN (VCG) port you want to provision. Click

Close

to exit.

E

N D O F

S

T E P S

Figure 11-11 Point-to-Point 1GbE full rate private line example

Node 4

Node 3

M 2 M 1

IN

OUT

M 2 M 1

OUT

IN

All Customer Packets allowed on Port 1

V1

1

V2

D

V3 V4

GbE

VLAN Tagging Mode = NOTAG

Ed-eqpt:Node3:fn-d-1:ctag::ETHPK:vlantagmd=NOTAG

Node 3 2F BLSR Add/Drop Cross-connections: m1-1-(1-21),d1-v1-(1-21) Source NE=Node 1

M 1

Node 1

M 2

Normal Traffic

M 1

Node 2

M 2

V1

1

V2

D

V3 V4

GbE

VLAN Tagging Mode = NOTAG

Ed-eqpt:Node1:fn-d-1:ctag::ETHPK:vlantagmd=NOTAG

Node 1 2F BLSR Add/Drop Cross-connections: m2-1-(1-21),d1-v1-(1-21) Source NE=Node 3

2-Way Point-to-Point, Through Cross-connections m1-1-(1-21),m2-1-(1-21)

Source NE=Node 1

Destination NE=Node 3

NC-DMX-280-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-105

Ethernet/Data network provisioning procedures

Procedure 11-15: Establish point-to-point BLSR protected GbE service (802.1q mode)

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring point-to-point BLSR protected

GbE Ethernet service using the 802.1q tagging mode. See

Figure 11-12, “Point-to-Point

GbE using 802.1q tagging mode” (p. 11-114)

for an example.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Important! On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a

Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

•

The tagging mode (802.1q) and virtual switch ID.

Step

1

Use this procedure as an example for configuring point-to-point BLSR protected GbE

Ethernet service using the 802.1q tagging mode. See

Figure 11-12, “Point-to-Point GbE using 802.1q tagging mode” (p. 11-114)

for an example.

.................................................................................................................................................................................................

Use the WaveStar

®

performed.

CIT to log in to one of the terminating nodes, if not already

.................................................................................................................................................................................................................................

11-106 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-15: Establish point-to-point BLSR protected

GbE service (802.1q mode)

2

3

4

5

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Neighbor Map

command and note the NEs connected to Main 1 and Main 2.

Access each of the NEs identified and select the

Administration

→

OSI Neighbor

Map

command and note the NEs connected to Main 1 and Main 2.

Repeat the above until the backbone ring can be sketched.

As an alternative, you can select

View

→

Rings

→

Ring Map

from the System View menu, then select the 2F BLSR port protection group and click

Select

. Select

NVMRING in the Ring Map Source selection box. You may also Display Ring Map

Graph using this command.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map window opens if the

Administration

→

OSI

Neighbor Map

command was used.

A list of NEs and NE neighbors is displayed if the

View

→

Rings

→

Ring Map

command was used.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the service to be established.

.................................................................................................................................................................................................

Important! If the Ethernet circuit pack is already in service, the existing tagging mode cannot be changed without removing all existing cross-connections and virtual switch provisioning.

CONFIGURE TAGGING MODE

Determine the existing tagging mode and parameters for the circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the

System View menu, select the CP, then click

Select

. Note the VLAN Tagging Mode and other parameter values.

The VLAN Tagging Mode for the LNW67/68 circuit packs must be set to

802.1TAG

.

The VLAN Tagging Mode for the LNW70 circuit packs must be set to

SWITCHED

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-107

Ethernet/Data network provisioning procedures Procedure 11-15: Establish point-to-point BLSR protected

GbE service (802.1q mode)

6

.................................................................................................................................................................................................

Select one of the following:

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly but other parameters are not correct, the tagging mode is NOT set correctly,

Then...

Proceed to

Step 12 .

Proceed to

Step 9 .

Continue with

Step 7 .

7

8

9

.................................................................................................................................................................................................

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the GbE circuit pack being provisioned, then click

Select

. Note if a virtual switch ID has been assigned.

If a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

.................................................................................................................................................................................................

If a virtual switch has been provisioned, delete it by using the TL1

dlt-vrtsw

command or select the

Configuration

→

Data

→

Delete Virtual Switch

command from the System View menu, highlight the circuit pack being provisioned, then click

Select

. Highlight the VRTSW ID being deleted, then click

Apply

.

Read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................

Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu. Select the circuit pack being provisioned, then click

Select

.

10

.................................................................................................................................................................................................

Verify/Select the tagging mode in the Select VLAN Tagging Mode box.

.................................................................................................................................................................................................

11

Verify/Enter other parameter values (for example,

Burst Size

,

Credit

Interval

[LNW67/68],

Ethernet Cross Connect Mode

[LNW70]), as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

.................................................................................................................................................................................................................................

11-108 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-15: Establish point-to-point BLSR protected

GbE service (802.1q mode)

12

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service.

If the service you are establishing in this procedure is a second service on an existing

GbE circuit pack with all LAN/WAN ports in the same virtual switch, then the existing virtual switch ID must be retained or the ports not in service must be removed from the existing virtual switch and added to a new virtual switch ID.

ASSIGN VIRTUAL SWITCH ID

•

For circuit packs not yet in service with no virtual switch assigned:

– Use the TL1

ent-vrtsw

command to create an assigned virtual switch ID or select

Configuration

→

Data

→

Create Virtual Switch

command from the CIT

System View menu.

For the LNW70 circuit pack, select

802.1TAG

for the

Virtual LAN Tagging

Mode

.

•

For circuit packs not yet in service with a virtual switch assigned:

– Use the TL1

dlt-vrtsw

command to delete an assigned virtual switch ID or select

Configuration

→

Data

→

Delete Virtual Switch

command from the CIT

System View menu, if a different virtual switch ID is required.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the selected LAN/WAN ports.

For the LNW70 circuit pack, select

802.1TAG

for the

Virtual LAN Tagging

Mode

.

•

For circuit packs in service with a virtual switch assigned:

– Use the TL1

ed-vrtsw

command or select

Configuration

→

Data

→

Provision

Virtual Switch

command from the CIT System View menu to remove the required ports from a virtual switch.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the required LAN/WAN ports.

For the LNW70 circuit pack, select

802.1TAG

for the

Virtual LAN Tagging

Mode

.

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

13

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-109

Ethernet/Data network provisioning procedures

14

15

16

Procedure 11-15: Establish point-to-point BLSR protected

GbE service (802.1q mode)

Determine the necessary

2F BLSR Add/Drop

and

2-Way Point-to-Point, Through

STS-1 cross-connections to be made at each terminating and non terminating node in the network.

Important! Note that full rate Gigabit service requires 21 STS-1 cross-connections.

.................................................................................................................................................................................................

One at a time at each node in the network, use the TL1

ent-crs-sts1

command to provision the cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard at each of the non terminating nodes in the network to provision the

2-Way Point-to-Point, Through

cross-connections, and at the terminating Ethernet nodes to provision the

2F BLSR Add/Drop

cross-connections.

Important! Note that cross-connections at the terminating nodes are add/drop and cross-connections at the non terminating nodes are pass-through.

Reference:

(p. 11-195)

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connections have been made.

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been

Enabled in both Input and Ouput Direction.

If required, use the TL1

ed-vcgtrib

command to enable tributaries, or from the

System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

.................................................................................................................................................................................................................................

11-110 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

17

18

19

20

21

Procedure 11-15: Establish point-to-point BLSR protected

GbE service (802.1q mode)

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, at least one tributary at each end of the circuit must be Enabled in order for the VCG to go in service.

If required, after all cross-connections have been made, verify that the WAN (VCG)

Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Click on the

VCG Data

tab. Under the

Fault

section of the parameter display, verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, proceed to

Step 22 .

•

If the VCG Monitoring Mode is

NMON

(Not Monitored),

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

VCG Data

tab. Under the

Fault

section, select

AUTO

for the

VCG Monitoring Mode

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-111

Ethernet/Data network provisioning procedures Procedure 11-15: Establish point-to-point BLSR protected

GbE service (802.1q mode)

22

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 19 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

If proper cross-connections have been made, then indications are that either the far-end or near-end circuit pack at each end of the span has failed or must be reset.

If the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near-end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Apply

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near-end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far-end and near-end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

After the VLAN ID for customer untagged frames is assigned and service is established in the 802.1q mode, changing the VLAN ID may affect service. If the VLAN IDs are different, service will be affected.

When the VLAN ID for customer untagged frames is changed at one point in the network, the VLAN ID must be changed at all points.

ASSIGN VLAN IDs

Use the TL1

ent-vlan

command to assign the default VLAN ID for customer untagged frames or the customer VLAN ID for tagged frames to the associated LAN ports and VCG WAN ports. Or select

Configuration

→

Data

→

Create VLAN

command from the CIT System View menu. For example, see

Figure 11-12,

“Point-to-Point GbE using 802.1q tagging mode” (p. 11-114) .

.................................................................................................................................................................................................................................

11-112 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-15: Establish point-to-point BLSR protected

GbE service (802.1q mode)

23

24

25

26

Reference:

In

Figure 11-12, “Point-to-Point GbE using 802.1q tagging mode”

(p. 11-114) , assume a GbE circuit pack is installed in Function slot d-1 and LAN

port 2 at each circuit pack is used for service.

Note that a service has been established between Node 1 and Node 3 for customer untagged frames using a default VLAN ID of 34.

Note that a service has been established between Node 1 and Node 3 for customer tagged frames using a VLAN ID of 55.

.................................................................................................................................................................................................

PROVISION LAN PORTS

Use the TL1

ed-eport

command to provision the LAN port parameters, or select

Configuration

→

Equipment

from the System View menu. Expand the details for the circuit pack, highlight the LAN Port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

Click

Apply

. Read the warning message, then click

Yes

to execute the command.

.................................................................................................................................................................................................

PROVISION VCGS

Use the

ed-vcg

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, if window is not already open from the previous step. Expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

.................................................................................................................................................................................................

Click

Apply

. Read the warning message, then click

Yes

to execute the command.

Click

Close

to exit or repeat from

Step 23

for other port provisioning.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-113

Ethernet/Data network provisioning procedures Procedure 11-15: Establish point-to-point BLSR protected

GbE service (802.1q mode)

Figure 11-12 Point-to-Point GbE using 802.1q tagging mode

Node 4

Node 3

M 2 M 1

IN

OUT

M 2 M 1

OUT

IN

M 1

D

LNW67/68

VLAN Tagging Mode=802.1TAG

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=802.1TAG

V1

2

Virtual Switch ID = 124 (LNW67/68)

Ethernet (LAN) Ports=d1-2; VCG (WAN) Ports=d1-v3

V2

Node 3 2F BLSR Add/Drop Cross-connections: m1-1-(1-21),d1-v3-(1-21) Source NE=Node 1

Create VLAN

Ent-vlan:tid:fn-d-1:ctag::34:124:dfeplst=d1-2,vcglst=d1-v3

Ent-vlan:tid:fn-d-1:ctag::55:124:eplst=d1-2,vcglst=d1-v3

Node 1

Node 2

M 2

M 1

V3 V4

GbE

VLAN IDs 34,55

M 2

Normal Traffic

D

V1 V2

VLAN IDs 34,55

2

V3 V4

GbE

2-Way Point-to-Point, Through Cross-connections m2-1-(1-21),m1-1-(1-21)

Source NE=Node 3

Destination NE=Node 1

LNW70

VLAN Tagging Mode=SWITCHED (LNW70)

Cross Connect Mode=STS1 (LNW70)

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=switched,eccmode=sts1

Virtual Switch ID = 124 (LNW70)

Virtual LAN Tagging Mode= 802.1TAG (LNW70)

Ent-vrtsw:tid:fn-d-1:ctag::124:eplst=d1-2,vcglst=d1-v3,tagmd=802.1TAG

Node 1 2F BLSR Add/Drop Cross-connections: m2-1-(1-21),d1-v3-(1-21) Source NE=Node 3

Create VLAN

Ent-vlan:tid:fn-d-1:ctag::34:124:dfeplst=d1-2,vcglst=d1-v3

Ent-vlan:tid:fn-d-1:ctag::55:124:eplst=d1-2,vcglst=d1-v3

NC-DMX-281-2

.................................................................................................................................................................................................................................

11-114 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-16: Establish point-to-point BLSR protected GbE service (transparent mode)

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring initial point-to-point BLSR protected GbE Ethernet service using the transparent tagging mode. See

Figure 11-13,

“Point-to-Point GbE using transparent tagging mode” (p. 11-123)

for an example.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Important! On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a

Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

•

The tagging mode (Transparent) and virtual switch ID.

Step

1

Use this procedure as an example for configuring point-to-point BLSR protected GbE

Ethernet service using the transparent tagging mode. See

Figure 11-13, “Point-to-Point

GbE using transparent tagging mode” (p. 11-123)

for an example.

.................................................................................................................................................................................................

Use the WaveStar

®

performed.

CIT to log in to one of the terminating nodes, if not already

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-115

Ethernet/Data network provisioning procedures Procedure 11-16: Establish point-to-point BLSR protected

GbE service (transparent mode)

2

3

4

5

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Neighbor Map

command and note the NEs connected to Main 1 and Main 2.

Access each of the NEs identified and select the

Administration

→

OSI Neighbor

Map

command and note the NEs connected to Main 1 and Main 2.

Repeat the above until the backbone ring can be sketched.

As an alternative, you can select

View

→

Rings

→

Ring Map

from the System View menu, then select the 2F BLSR port protection group and click

Select

. Select

NVMRING in the Ring Map Source selection box. You may also Display Ring Map

Graph using this command.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map window opens if the

Administration

→

OSI

Neighbor Map

command was used.

A list of NEs and NE neighbors is displayed if the

View

→

Rings

→

Ring Map

command was used.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the service to be established.

.................................................................................................................................................................................................

Important! If the Ethernet circuit pack is already in service, the existing tagging mode cannot be changed without removing all existing cross-connections and virtual switch provisioning.

CONFIGURE TAGGING MODE

Determine the existing tagging mode and parameters for the circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the

System View menu, select the CP, then click

Select

. Note the VLAN Tagging Mode and other parameter values.

The VLAN Tagging Mode for the LNW67/68 circuit packs must be set to

TRANS

. The

VLAN Tagging Mode for the LNW70 circuit packs must be set to

SWITCHED

.

.................................................................................................................................................................................................................................

11-116 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-16: Establish point-to-point BLSR protected

GbE service (transparent mode)

6

.................................................................................................................................................................................................

Select one of the following:

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly but other parameters are not correct, the tagging mode is NOT set correctly,

Then...

Proceed to

Step 12 .

Proceed to

Step 9 .

Continue with

Step 7 .

7

8

9

.................................................................................................................................................................................................

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the GbE circuit pack being provisioned, then click

Select

. Note if a virtual switch ID has been assigned.

If a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

.................................................................................................................................................................................................

If a virtual switch has been provisioned, delete it by using the TL1

dlt-vrtsw

command or select the

Configuration

→

Data

→

Delete Virtual Switch

command from the System View menu, highlight the circuit pack being provisioned, then click

Select

. Highlight the VRTSW ID being deleted, then click

Apply

.

Read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................

Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu. Select the circuit pack being provisioned, then click

Select

.

10

.................................................................................................................................................................................................

Verify/Select the tagging mode in the Select VLAN Tagging Mode box.

.................................................................................................................................................................................................

11

Verify/Enter other parameter values (for example,

Burst Size

,

Credit

Interval

[LNW67/68],

Ethernet Cross Connect Mode

[LNW70]), as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-117

Ethernet/Data network provisioning procedures Procedure 11-16: Establish point-to-point BLSR protected

GbE service (transparent mode)

12

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service.

If the service you are establishing in this procedure is a second service on an existing

GbE circuit pack with all LAN/WAN ports in the same virtual switch, then the existing virtual switch ID must be retained or the ports not in service must be removed from the existing virtual switch and a new virtual switch created.

ASSIGN VIRTUAL SWITCH ID

•

For circuit packs not yet in service with no virtual switch assigned:

– Use the TL1

ent-vrtsw

command to create an assigned virtual switch ID or select

Configuration

→

Data

→

Create Virtual Switch

command from the CIT

System View menu.

For the LNW70 circuit pack, select

Transparent

for the

Virtual LAN Tagging

Mode

.

•

For circuit packs not yet in service with a virtual switch assigned:

– Use the TL1

dlt-vrtsw

command to delete an assigned virtual switch ID or select

Configuration

→

Data

→

Delete Virtual Switch

command from the CIT

System View menu, if a different virtual switch ID is required.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the selected LAN/WAN ports.

For the LNW70 circuit pack, select

Transparent

for the

Virtual LAN Tagging

Mode

.

•

For circuit packs in service with a virtual switch assigned:

– Use the TL1

ed-vrtsw

command to change an assigned virtual switch ID or select

Configuration

→

Data

→

Provision Virtual Switch

command from the

CIT System View menu to add/remove ports from a virtual switch.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the selected LAN/WAN ports.

For the LNW70 circuit pack, select

Transparent

for the

Virtual LAN Tagging

Mode

.

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

13

.................................................................................................................................................................................................................................

11-118 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

14

15

16

Procedure 11-16: Establish point-to-point BLSR protected

GbE service (transparent mode)

Determine the necessary

2F BLSR Add/Drop

and

2-Way Point-to-Point, Through

STS-1 cross-connections to be made at each terminating and non terminating node in the network.

Important! Note that full rate Gigabit service requires 21 STS-1 cross-connections.

.................................................................................................................................................................................................

One at a time at each node in the network, use the TL1

ent-crs-sts1

command to provision the cross-connections. Or, select

Configuration

→

Cross-Connections \

from the System View menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard at each of the non terminating nodes in the network to provision the

2-Way Point-to-Point, Through

cross-connections, and at the terminating

Ethernet nodes to provision the

2F BLSR Add/Drop

cross-connections.

Important! Note that cross-connections at the terminating nodes are add/drop and cross-connections at the non terminating nodes are pass-through.

Reference:

(p. 11-195)

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connections have been made.

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been

Enabled in both Input and Ouput Direction.

If required, use the TL1

ed-vcgtrib

command to enable tributaries, or from the

System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-119

Ethernet/Data network provisioning procedures

17

18

19

20

21

Procedure 11-16: Establish point-to-point BLSR protected

GbE service (transparent mode)

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, at least one tributary at each end of the circuit must be Enabled in order for the VCG to go in service.

If required, after all cross-connections have been made, verify that the WAN (VCG)

Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Click on the

VCG Data

tab. Under the

Fault

section of the parameter display, verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, proceed to

Step 22 .

•

If the VCG Monitoring Mode is

NMON

(Not Monitored),

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

VCG Data

tab. Under the

Fault

section, select

AUTO

for the

VCG Monitoring Mode

.

.................................................................................................................................................................................................................................

11-120 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-16: Establish point-to-point BLSR protected

GbE service (transparent mode)

22

23

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 19 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

If proper cross-connections have been made, then indications are that either the far-end or near-end circuit pack at each end of the span has failed or must be reset.

If the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near-end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Apply

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near-end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far-end and near-end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

CREATE PORT TAGs

Use the TL1

ed-eport

and

ed-vcg

commands to assign port tags to the associated

LAN ports and VCG WAN ports. Or, select

Configuration

→

Data

→

Create Port

Tag

command from the CIT System View menu. Highlight the circuit pack being provisioned, then click

Select

. Provision the parameters as required. Click

Apply

, then click

Yes

to the warning message. Click

Close

to exit.

Important! The Peak Information Rate (PIR) rate limiting feature on the

LNW66/LNW67/LNW68 circuit packs will not be effective in transparent mode if the Ethernet Type (ethertype) parameter for the LAN or WAN VCG ports is provisioned to any value other than FFFF or 8100.

.................................................................................................................................................................................................

PROVISION LAN (Ethernet) PORTS

Use the TL1

ed-eport

command to provision parameters for the LAN port being provisioned. Or, select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the LAN port, then click

Select

.

Provision the parameters as required.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-121

Ethernet/Data network provisioning procedures Procedure 11-16: Establish point-to-point BLSR protected

GbE service (transparent mode)

24

Click

Apply

, then click

Yes

to execute the command. Repeat for all ports being provisioned. Click

Close

to exit or continue with the next step.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

PROVISION WAN (VCG) PORTS

Use the TL1

ed-vcg

command to provision parameters for the VCG ports, as required.

Or, select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Click

Apply

, then click

Yes

to execute the command. Repeat for all ports being provisioned. Click

Close

to exit.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

11-122 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-16: Establish point-to-point BLSR protected

GbE service (transparent mode)

Figure 11-13 Point-to-Point GbE using transparent tagging mode

Node 4

Node 3

M 2 M 1

IN

OUT

M 2 M 1

OUT

IN

M 1

LNW67/68

All Customer Packets allowed on Port 2

VLAN Tagging Mode=Trans

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=Trans

Node 1

Create Port Tag

Ed-eport-1ge:tid:d1-2:ctag:::dftporttag=55

Ed-vcg:tid:d1-v3:ctag:::addporttag=55

D

V1

Virtual Switch ID = 124 (LNW67/68)

Ethernet (LAN) Ports=d1-2; VCG (WAN) Ports=d1-v3

Node 3 2F BLSR Add/Drop Cross-connections: m1-1-(1-21),d1-v3-(1-21) Source NE=Node 1

2

V2 V4

GbE

Default Port Tag 55

Node 2

V3

M 2

M 1 M 2

Normal Traffic

D

V1 V2

V3 V4

GbE

2-Way Point-to-Point, Through Cross-connections

2

Default Port Tag 55

LNW70

All Customer Packets allowed on Port 2

VLAN Tagging Mode=SWITCHED (LNW70)

Cross Connect Mode=STS1 (LNW70)

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=switched,eccmode=sts1

Virtual Switch ID = 124 (LNW70)

Virtual LAN Tagging Mode= 802.1TAG (LNW70)

Ent-vrtsw:tid:fn-d-1:ctag::124:eplst=d1-2,vcglst=d1-v3,tagmd=TRANS m1-1-(1-21),m2-1-(1-21)

Source NE=Node 1

Destination NE=Node 3

Node 1 2F BLSR Add/Drop Cross-connections: m2-1-(1-21),d1-v3-(1-21) Source NE=Node 3

Create Port Tag

Ed-eport-1ge:tid:d1-2:ctag:::dftporttag=55

Ed-vcg:tid:d1-v3:ctag:::addporttag=55

MA-DMX-282-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-123

Ethernet/Data network provisioning procedures

Procedure 11-17: Establish Ethernet packet ring on a BLSR with non-preemptible unprotected traffic (NUT)

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for establishing an Ethernet packet ring on a bidirectional line switched ring (BLSR) with Nonpreemptible Unprotected Traffic

(NUT) access (Release 3 or later).

A packet ring is a set of Ethernet switches (Ethernet circuit packs) connected to each other in a ring configuration. When the packet ring is first established, the capacity of the ring is predetermined by the number of STS-1 cross-connections (1-21

[LNW66/67/68], 1-48 [LNW70]) applied to the ring and switches. The tagging mode, virtual switch ID, and spanning tree group is also predetermined. For example, see

Figure 11-14, “Ethernet packet ring on a BLSR with NUT” (p. 11-133) .

This procedure assumes that the BLSR ring network configuration has already been established and no alarms are present.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the nodes participating in the packet ring network.

•

The shelf slots, circuit packs, ports, VCGs involved in the packet ring network.

•

The number and type of cross-connections to be made at each node.

For circuit packs not supporting LCAS, once the capacity of the packet ring is established, additional capacity (cross-connections) may not be added in service without service interruption.

•

The tagging mode (transparent or 802.1q), virtual switch ID, and spanning tree group ID.

.................................................................................................................................................................................................................................

11-124 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-17: Establish Ethernet packet ring on a

BLSR with non-preemptible unprotected traffic (NUT)

Step

1

2

3

4

5

Use this procedure as an example to establish an Ethernet packet ring on a BLSR ring using NUT. See

Figure 11-14, “Ethernet packet ring on a BLSR with NUT”

(p. 11-133)

for an example.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes, if not already performed.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Neighbor Map

command and note the NEs connected to Main 1 and Main 2.

Access each of the NEs identified and select the

Administration

→

OSI Neighbor

Map

command and note the NEs connected to Main 1 and Main 2.

Repeat the above until the backbone ring can be sketched.

As an alternative, you can select

View

→

Rings

→

Ring Map

from the System View menu, then select the 2F BLSR port protection group and click

Select

. Select

NVMRING in the Ring Map Source selection box. You may also Display Ring Map

Graph using this command.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map window opens if the

Administration

→

OSI

Neighbor Map

command was used.

A list of NEs and NE neighbors is displayed if the

View

→

Rings

→

Ring Map

command was used.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the packet ring being established.

.................................................................................................................................................................................................

Verify that the Ethernet circuit packs have been installed into the required slot 1 of the

Function Unit or Growth group (A, B, C, D, or G) at each NE providing Ethernet service.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-125

Ethernet/Data network provisioning procedures Procedure 11-17: Establish Ethernet packet ring on a

BLSR with non-preemptible unprotected traffic (NUT)

6

Reference:

Procedure 4-13: “Install Gigabit Ethernet circuit packs” (p. 4-54)

.................................................................................................................................................................................................

Important! If the Ethernet circuit pack is already in service, the existing tagging mode cannot be changed without removing all existing cross-connections and virtual switch provisioning.

CONFIGURE TAGGING MODE

Determine the existing tagging mode for the circuit pack being provisioned. Use the

TL1

rtrv-eqpt

command or select

View

→

Equipment

from the System View menu, select the CP, then click

Select

. Note the VLAN Tagging Mode and other parameter values.

The VLAN Tagging Mode for the LNW66/67/68 circuit packs must be set to

TRANS

or

802.1TAG

. The VLAN Tagging Mode for the LNW70 circuit packs must be set to

SWITCHED

.

Important! When GbE circuit packs are installed in the shelf, the default

″

NOTAG

″ mode is assigned to the circuit pack. When FE circuit packs are installed in the shelf, the default

″

802.1TAG

″ mode is assigned to the circuit pack.

.................................................................................................................................................................................................

7

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly but other parameters are not correct, the tagging mode is NOT set correctly,

Then...

Proceed to

Step 13 .

Proceed to

Step 10 .

Continue with

Step 8 .

8

.................................................................................................................................................................................................

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the GbE circuit pack being provisioned, then click

Select

. Note if a virtual switch ID has been assigned.

If a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

.................................................................................................................................................................................................................................

11-126 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-17: Establish Ethernet packet ring on a

BLSR with non-preemptible unprotected traffic (NUT)

9

10

11

12

13

.................................................................................................................................................................................................

If a virtual switch has been provisioned, delete it by using the TL1

dlt-vrtsw

command or select the

Configuration

→

Data

→

Delete Virtual Switch

command from the System View menu, select the circuit pack being provisioned, then click

Select. Highlight the VRTSW ID being deleted, then click

Apply

.

Read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................

Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu, select the circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Verify/Select the tagging mode (

802.1TAG

,

TRANS

[LNW66/67/68], or

SWITCHED

[LNW70]) in the VLAN Tagging Mode box.

.................................................................................................................................................................................................

Verify/Enter other parameter values (for example,

Burst Size

,

Credit

Interval

[LNW66/67/68],

Ethernet Cross Connect Mode

and

Port Configuration

[LNW70]), as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service.

If the service you are establishing in this procedure is a second service on an existing

GbE circuit pack with all LAN/WAN ports in the same virtual switch, then the existing virtual switch ID must be retained or the ports not in service must be removed from the existing virtual switch and added to a new virtual switch ID.

ASSIGN VIRTUAL SWITCH ID

•

For circuit packs not yet in service with no virtual switch assigned:

– Use the TL1

ent-vrtsw

command to create an assigned virtual switch ID or select

Configuration

→

Data

→

Create Virtual Switch

command from the CIT

System View menu.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-127

Ethernet/Data network provisioning procedures Procedure 11-17: Establish Ethernet packet ring on a

BLSR with non-preemptible unprotected traffic (NUT)

14

15

For the LNW70 circuit pack, select the required

Virtual LAN Tagging Mode

(

802.1TAG

or

Transparent

).

•

For circuit packs not yet in service with a virtual switch assigned:

– Use the TL1

dlt-vrtsw

command to delete an assigned virtual switch ID or select

Configuration

→

Data

→

Delete Virtual Switch

command from the CIT

System View menu, if a different virtual switch ID is required.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the selected LAN/WAN ports.

For the LNW70 circuit pack, select the required

Virtual LAN Tagging Mode

(

802.1TAG

or

Transparent

).

•

For circuit packs in service with a virtual switch assigned:

– Use the TL1

ed-vrtsw

command or select

Configuration

→

Data

→

Provision

Virtual Switch

command from the CIT System View menu to remove the required ports from a virtual switch.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the required LAN/WAN ports.

For the LNW70 circuit pack, select the required

Virtual LAN Tagging Mode

(

802.1TAG

or

Transparent

).

.................................................................................................................................................................................................

PROVISION NUT VALUES

Select

Configuration

→

Equipment

from the System View menu. Or use the TL1

ed-protn-acc

command to provision the NUT values.

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Select

Ptn Grp

tab from the bottom of the window, then select the required 2F BLSR group and click

Select

.

Result:

Parameters display for the selected protection group

16

.................................................................................................................................................................................................

Under Local NUT,

•

Select the

NUT Rate

as

STS1

•

Select the

Time Slot Number(s)

(

1-24

for OC-48 or

1-96

for OC-192) you are provisioning.

•

Select the

NUT Protection Attribute

as

Not Protected

.

Important! Note that each timeslot used for the multipoint cross-connections for the packet ring must be provisioned at each node (including intermediate pass-through nodes) with the NUT attribute of

Not Protected

.

.................................................................................................................................................................................................................................

11-128 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-17: Establish Ethernet packet ring on a

BLSR with non-preemptible unprotected traffic (NUT)

17

18

19

20

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary

Multipoint

STS-1 cross-connections to be made to each

VCG at each terminating node. Determine any

2-Way Point-to-Point, Through

pass through cross-connections to be made at any non terminating nodes in the network.

Important! Note that, for full rate Gigabit packet rings on an OC-48 BLSR, cross-connections for the first packet ring using VCG 1(2) should use cross-connection time slots 1-21.

.................................................................................................................................................................................................

One at a time at each node in the network, use the TL1

ent-crs-sts1

command to provision the cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard to provision the

Multipoint

Ethernet and the

2-Way

Point-to-Point, Through

pass-through cross-connections. For example, see

Figure

11-14, “Ethernet packet ring on a BLSR with NUT” (p. 11-133) .

Reference:

Refer to

Procedure 11-24: “Make cross-connections for Ethernet service” (p. 11-195)

for cross-connection examples.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

to verify that the proper connections have been made.

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been

Enabled in both Input and Ouput Direction.

If required, use the TL1

ed-vcgtrib

command to enable tributaries, or from the

System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-129

Ethernet/Data network provisioning procedures

21

22

23

24

25

Procedure 11-17: Establish Ethernet packet ring on a

BLSR with non-preemptible unprotected traffic (NUT)

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, at least one tributary at each end of the circuit must be Enabled in order for the VCG to go in service.

If required, after all cross-connections have been made, verify that the WAN (VCG)

Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Click on the

VCG Data

tab. Under the

Fault

section of the parameter display, verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, proceed to

Step 26 .

•

If the VCG Monitoring Mode is

NMON

, (Not Monitored),

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

VCG Data

tab. Under the

Fault

section, select

AUTO

for the

VCG Monitoring Mode

.

.................................................................................................................................................................................................................................

11-130 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-17: Establish Ethernet packet ring on a

BLSR with non-preemptible unprotected traffic (NUT)

26

27

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 23 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

If proper cross-connections have been made, then indications are that either the far-end or near-end circuit pack at each end of the span has failed or must be reset.

If the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near-end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Apply

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near-end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far-end and near-end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

CREATE SPANNING TREE GROUP

If required, determine a preferred spanning tree configuration (span to be blocked under nominal conditions), the preferred root node, and spanning tree root priorities for this service.

Important! It is not necessary to determine a preferred spanning tree configuration.

A default spanning tree configuration is configured when you establish the spanning tree group.

Reference:

(p. 11-216)

Procedure 11-25: “Create preferred spanning tree configuration”

.................................................................................................................................................................................................

Use the TL1

ent-stgrp

command to assign and provision the parameters for the ports involved in the spanning tree group. Or select

Configuration

→

Data

→

Create

Spanning Tree Group

command from the CIT System View menu. For example, see

Figure 11-14, “Ethernet packet ring on a BLSR with NUT” (p. 11-133) .

Important! Spanning tree default parameters support a network of up to nine nodes.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-131

Ethernet/Data network provisioning procedures Procedure 11-17: Establish Ethernet packet ring on a

BLSR with non-preemptible unprotected traffic (NUT)

28

Networks running 802.1w rapid spanning tree protocol (Release 2 or later) support more than nine nodes participating in a spanning tree. To support more than nine nodes in the spanning tree, the maximum age timer must be increased. Note that spanning tree restoration time increases as the number of nodes increase.

If the network consists of more than nine (9) nodes which are participating in the spanning tree configuration, use the following formula to determine the proper setting for the spanning tree maximum age timer (

stmaxage

): 2 x (N + 1), where N equals the number of nodes.

If the network consists of 16 nodes, then the

stmaxage

timer should be set to 34 seconds: 2 x (16 + 1) = 34.

.................................................................................................................................................................................................

Repeat all the assignments in this procedure at each Ethernet node in the network.

Important! All Ethernet nodes in the network must be in the same spanning tree group (that is, all VCGs, at each node, participating in the same spanning tree group must be assigned to the same spanning tree group ID).

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

11-132 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-17: Establish Ethernet packet ring on a

BLSR with non-preemptible unprotected traffic (NUT)

Figure 11-14 Ethernet packet ring on a BLSR with NUT

Node A Node B

M 2 M 1 M 2

OUT IN

M 1

IN

OUT

V2 V1 V2 V1

1 2 GbE

Multipoint (unswitched) cross-connections: m1-1-(1-21) to d1-v1-(1-21) m2-1-(1-21) to d1-v2-(1-21)

1 2 GbE

Multipoint (unswitched) cross-connections: m1-1-(1-21) to d1-v1-(1-21) m2-1-(1-21) to d1-v2-(1-21)

Packet Ring on

BLSR

using Multipoint (unswitched) Cross-Connections

M 1

Node D

M 2

M 1

Node X

M 2 M 1

Node C

M 2

V1 V2 V1 V2

1 2 GbE

2-Way Point-to-Point, Through Cross-connections m1-1-(1-21),m2-1-(1-21)

Source NE=Node D

Destination NE=Node C

Multipoint (unswitched) cross-connections: m1-1-(1-21) to d1-v1-(1-21) m2-1-(1-21) to d1-v2-(1-21)

1 2 GbE

Multipoint (unswitched) cross-connections: m1-1-(1-21) to d1-v1-(1-21) m2-1-(1-21) to d1-v2-(1-21)

Basic Provisioning at all nodes with ethernet:

LNW66/67/68

VLAN Tagging Mode = 802.1TAG or TRANS ed-eqpt:tid:fn-d-1:ctag:ETHPK:vlantagmd=802.1q (Trans)

LNW70

VLAN Tagging Mode=SWITCHED (LNW70)

Cross Connect Mode=STS1 (LNW70)

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=switched,eccmode=sts1

Virtual Switch ID (for example, 123)

Ethernet (LAN) Ports = d1-1

VCG (WAN) Ports = d1-v1, d1-v2

Virtual Switch ID (for example, 123)

Virtual LAN Tagging Mode=Transparent or 802.1TAG

Ethernet (LAN) Ports = d1-1

VCG (WAN) Ports = d1-v1, d1-v2

NUT Value for cross-connections:

Configuration > Provision, select Ptn Grp, select BLSR protection group, click Provision. Provision NUT Value to “Not Protected” for all timeslots being used.

Cross-connections: See examples in figure above.

Spanning Tree Group ID (for example, 1) ent-stgrp:tid::ctag::1,123:vcglst=d1-v1&d1-v2

Configuration > Data > Create A Spanning Tree, select ethernet circuit pack, click Select, enter parameters.

NC-DMX-277-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-133

Ethernet/Data network provisioning procedures

Procedure 11-18: Add bandwidth to a point-to-point

UPSR/BLSR protected GbE service (802.1q mode)

.................................................................................................................................................................................................................................

Overview

Use this procedure as an example for adding bandwidth to an in service point-to-point

UPSR/BLSR protected GbE Ethernet service using circuit packs not supporting LCAS.

For circuit packs supporting LCAS, see

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries” (p. 11-249) .

This procedure provides an example for adding bandwidth to an in service point-to-point UPSR/BLSR protected GbE Ethernet service with minimal service interruption. This example uses the 802.1q tagging mode.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the

Cross-Connection Wizard to perform the cross-connection provisioning in this procedure and the

Configuration

→

Data

→

Create VLAN

to provision new VLANs.

From the System View menu, select

Configuration

→

Cross-Connections

to invoke the wizard.

See

Figure 11-15, “Example of adding bandwidth on UPSR” (p. 11-138)

and

Figure

11-16, “Example of adding bandwidth on BLSR” (p. 11-138)

for examples.

Important! To minimize service interruption, plan the addition of cross-connections. For example, do any new pass-through cross-connections first.

Then at the appropriate time, coordinate and make the add/drop cross-connections at the terminating nodes at the same time, as close as possible.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of additional cross-connections to be made at each node.

•

The tagging mode (802.1q) and virtual switch ID.

•

Notify the customers on the existing service of the impending service interruption and coordinate your activities accordingly.

•

Plan the activity of adding cross-connections to minimize service interruption.

.................................................................................................................................................................................................................................

11-134 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-18: Add bandwidth to a point-to-point

UPSR/BLSR protected GbE service (802.1q mode)

Step

1

2

Use this procedure as an example for adding bandwidth (cross-connections) to a point-to-point UPSR/BLSR protected GbE Ethernet service using the 802.1q tagging mode.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes, if not already performed.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Neighbor Map

command and note the NEs connected to Main 1 and Main 2.

Access each of the NEs identified and select the

Administration

→

OSI Neighbor

Map

command and note the NEs connected to Main 1 and Main 2.

Repeat the above until the backbone ring can be sketched.

As an alternative for BLSR rings, you can select

View

→

Rings

→

Ring Map

from the

System View menu, then select the 2F BLSR port protection group and click

Select

.

Select NVMRING in the Ring Map Source selection box. You may also Display Ring

Map Graph using this command.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map window opens if the

Administration

→

OSI

Neighbor Map

command was used.

A list of NEs and NE neighbors is displayed if the

View

→

Rings

→

Ring Map

command was used.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

3

4

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, ports, and cross-connections to be made at each node associated with the service being added.

5

.................................................................................................................................................................................................

At each node in the network, use the

View

→

Cross-Connections

command from the

System View menu at each node to verify that the new cross-connections are available for assignment at each NE. If any of the new cross-connections are already assigned, you must resolve the problem before continuing with this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-135

Ethernet/Data network provisioning procedures Procedure 11-18: Add bandwidth to a point-to-point

UPSR/BLSR protected GbE service (802.1q mode)

6

7

8

9

10

11

.................................................................................................................................................................................................

ESTABLISH SONET PASS THROUGH CROSS-CONNECTIONS

Determine the necessary

2-Way Point-to-Point, Through

STS-1 cross-connections to be made at each non terminating node in the network.

.................................................................................................................................................................................................

One at a time at each non terminating node in the network, use the TL1

ent-crs-sts1

command to provision the pass-through cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection

Wizard. Use the Cross-Connection Wizard at each of the non terminating nodes in the network to provision the

2-Way Point-to-Point, Through

cross-connections.

Important! Note that cross-connections at the terminating nodes are add/drop and cross-connections at the non terminating nodes are pass-through.

Reference:

(p. 11-195)

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each non terminating node to verify that the proper connections have been made.

.................................................................................................................................................................................................

ESTABLISH SONET ADD/DROP CROSS-CONNECTIONS

At each terminating node in the network, coordinate your activities to activate the necessary cross-connections at the same time. Note that there will be some service interruption.

Use The TL1

ent-crs-sts1

command to provision the add/drop cross-connections. Or, select

Configuration

→

Cross-Connections

from the system view menu to start the

Cross-Connection Wizard. Use the Cross-Connection Wizard at each of the terminating nodes in the network to provision the

UPSR Ring Add/Drop

or

2F BLSR Add/Drop

cross-connections.

Important! Enter all your parameters for the cross-connections and coordinate with the other end as to when you enter/apply the command.

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

.................................................................................................................................................................................................................................

11-136 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

12

Procedure 11-18: Add bandwidth to a point-to-point

UPSR/BLSR protected GbE service (802.1q mode)

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

ASSIGN VLAN IDs

If adding new customers, use the TL1

ent-vlan

command to assign the new customer

VLAN ID to the associated LAN ports and VCG WAN ports. Or select

Configuration

→

Data

→

Create VLAN

command from the CIT System View menu to open the

Create New VLAN provisioning window.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-137

Ethernet/Data network provisioning procedures Procedure 11-18: Add bandwidth to a point-to-point

UPSR/BLSR protected GbE service (802.1q mode)

Figure 11-15 Example of adding bandwidth on UPSR

Node 1 Node 2

M 1 M 2 M 1

OUT

IN

M 2

IN

V3

V1

V4

V2

VLAN IDs 34,55

GbE 2

New VLAN ID 60

D

OUT

V3

V1

V4

V2

VLAN IDs 34,55

GbE 2

New VLAN ID 60

D

Step 2: Do UPSR Ring Add/Drop Cross-connections at the same time at Nodes 1 and 2: m1-1-(5-6),d1-v3-(5-6)

Step 3: Add new VLAN 60 to LAN/WAN ports at Nodes 1 and 2.

Ent-vlan:tid:fn-d-1:ctag::60:124:eplst=d1-2,vcglst=d1-v3

M 2

Node 3

M 1

Step 1: Do STS1 2-Way Point-to-Point, Through Cross-connections at all non terminating nodes: m1-1-(5-6),m2-1-(5-6) .

Original configuration:

Customer VLANs 34 and 55 share 4 STS1s in a point-to-point configuration.

Customers share 4 STS1s in Main, m1-1-(1-4), connected to VCG timeslots 1-4.

Virtual Switch ID=124

New configuration:

Add 2 more cross-connections, m1-1-5 and m1-1-6, for additional bandwidth.

Add new VLAN, 60, at each of the terminating nodes, Node 1 and Node 2.

Virtual Switch ID=124

Steps:

1. Add 2-Way Point-to-Point, Through cross-connection at Node 3.

2. At the same time, add the UPSR Ring Add/Drop cross-connections at Nodes 1 and 2.

3. Add VLAN ID 60 at Nodes 1 and 2.

NC-DMX-278-2

.................................................................................................................................................................................................................................

11-138 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-18: Add bandwidth to a point-to-point

UPSR/BLSR protected GbE service (802.1q mode)

Figure 11-16 Example of adding bandwidth on BLSR

Node 4

Node 3

M 2 M 1

IN

OUT

M 2 M 1

OUT

IN

VLAN IDs 34,55

New VLAN ID 60

Step 2: Do 2F BLSR Add/Drop cross-connections at the same time at Nodes 1 and 3

Node1:m2-1-(5-6),d1-v3-(5-6) Source NE = Node 3

Node3:m1-1-(5-6),d1-v3-(5-6) Source NE = Node 1

Step 3: Add new VLAN 60 to LAN/WAN ports at Nodes 1 and 3.

Ent-vlan:tid:fn-d-1:ctag::60:124:eplst=d1-2,vcglst=d1-v3

D

V1 V2

2

V3 V4

GbE

M 1

Node 1

M 2

Normal Traffic

M 1

Node 2

M 2

D

V1 V2

2

VLAN IDs 34,55

New VLAN ID 60

V3 V4

GbE

Step 1: Do STS1 2-Way Point-to-Point, Through Cross-connections at all non terminating nodes: m1-1-(5-6),m2-1-(5-6)

Source NE = Node 1, Destination NE = Node 3

Original configuration:

Customer VLANs 34 and 55 share 4 STS1s in a point-to-point configuration.

Customers share 4 STS1s (1-4) in Main, connected to VCG timeslots 1-4.

Virtual Switch ID=124

New configuration:

Add 2 more cross-connections, timeslots 5-6, for additional bandwidth.

Add new VLAN, 60, at each of the terminating nodes, Node 1 and Node 3.

Virtual Switch ID=124

Steps:

1. Add

2-Way Point-to-Point, Through

2. At the same time, add cross-connections at Nodes 1 and 3.

cross-connection at Node 2.

2F BLSR Add/Drop

3. Add VLAN ID 60 at Nodes 1 and 3.

NC-DMX-279-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-139

Ethernet/Data network provisioning procedures

Procedure 11-19: Establish a dedicated multiple point private line UPSR protected GbE service (transparent mode)

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring a dedicated multiple point private line UPSR protected GbE Ethernet service using the Transparent tagging mode.

This procedure illustrates a dedicated bandwidth, private line service with per link bandwidth granularity with multiple connections. Although this procedure uses the transparent mode, this configuration could use the 802.1q tagging mode with VLAN assignments. Cross-connections and VCG assignments are the major considerations in this type of configuration. See

Figure 11-17, “Dedicated multiple point GbE using transparent tagging mode” (p. 11-148)

and

Figure 11-18, “Dedicated multiple point

GbE private line cross-connections” (p. 11-148) .

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Important! On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a

Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

•

The tagging mode (transparent) and virtual switch ID.

.................................................................................................................................................................................................................................

11-140 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Step

Procedure 11-19: Establish a dedicated multiple point private line UPSR protected GbE service (transparent mode)

1

2

3

4

5

Use this procedure as an example for configuring a dedicated multiple point private line UPSR protected GbE Ethernet service using the Transparent tagging mode.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to each of the terminating nodes, if not already performed.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Neighbor Map

command and note the NEs connected to Main 1 and Main 2.

Access each of the NEs identified and select the

Administration

→

OSI Neighbor

Map

command and note the NEs connected to Main 1 and Main 2.

Repeat the above until the backbone ring can be sketched.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the service to be established. Refer to

Figure

11-17, “Dedicated multiple point GbE using transparent tagging mode” (p. 11-148)

and

Figure 11-18, “Dedicated multiple point GbE private line cross-connections”

(p. 11-148)

for provisioning at each node.

.................................................................................................................................................................................................

At each node in the network, use the

View

→

Cross-Connections

command from the

System View menu at each node to verify that the new cross-connections are available for assignment at each NE. If any of the new cross-connections are already assigned, you must resolve the problem before continuing with this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-141

Ethernet/Data network provisioning procedures

6

Procedure 11-19: Establish a dedicated multiple point private line UPSR protected GbE service (transparent mode)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

If the Ethernet circuit pack is already providing service, changing tagging mode will take down any existing service. The existing tagging mode cannot be changed without removing all existing cross-connections and virtual switch provisioning.

CONFIGURE TAGGING MODE

Determine the existing tagging mode and parameters for the circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the

System View menu, select the CP, then click

Select

. Note the VLAN Tagging Mode and other parameter values.

The VLAN Tagging Mode for the LNW67/68 circuit packs must be set to

TRANS

. The

VLAN Tagging Mode for the LNW70 circuit packs must be set to

SWITCHED

.

7

.................................................................................................................................................................................................

Select one of the following:

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly but other parameters are not correct, the tagging mode is NOT set correctly,

Then...

Proceed to

Step 13 .

Proceed to

Step 10 .

Continue with

Step 8 .

8

.................................................................................................................................................................................................

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the GbE circuit pack being provisioned, then click

Select

. Note if a virtual switch ID has been assigned.

If a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

.................................................................................................................................................................................................

9

If a virtual switch already exists, use the TL1

dlt-vrtsw

command or select the

Configuration

→

Data

→

Delete Virtual Switch

command from the System View menu, highlight the circuit pack being provisioned, then click

Select

. Highlight the

VRTSW ID being deleted, then click

Apply

.

.................................................................................................................................................................................................................................

11-142 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-19: Establish a dedicated multiple point private line UPSR protected GbE service (transparent mode)

Read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

10

.................................................................................................................................................................................................

Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu. Select the circuit pack being provisioned, then click

Select

.

11

12

.................................................................................................................................................................................................

Verify/Select the tagging mode in the Select VLAN Tagging Mode box.

.................................................................................................................................................................................................

Verify/Enter other parameter values (for example,

Burst Size

,

Credit

Interval

[LNW67/68],

Ethernet Cross Connect Mode

and

Port Configuration

[LNW70]), as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

13

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service.

If the service you are establishing in this procedure is a second service on an existing

GbE circuit pack with all LAN/WAN ports in the same virtual switch, then the existing virtual switch ID must be retained or the ports not in service must be removed from the existing virtual switch and added to a new virtual switch ID.

ASSIGN VIRTUAL SWITCH ID

•

For circuit packs not yet in service with no virtual switch assigned:

– Use the TL1

ent-vrtsw

command to create an assigned virtual switch ID or select

Configuration

→

Data

→

Create Virtual Switch

command from the CIT

System View menu.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-143

Ethernet/Data network provisioning procedures Procedure 11-19: Establish a dedicated multiple point private line UPSR protected GbE service (transparent mode)

For the LNW70 circuit pack, select

Transparent

for the

Virtual LAN Tagging

Mode

.

•

For circuit packs not yet in service with a virtual switch assigned:

– Use the TL1

dlt-vrtsw

command to delete an assigned virtual switch ID or select

Configuration

→

Data

→

Delete Virtual Switch

command from the CIT

System View menu, if a different virtual switch ID is required.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the selected LAN/WAN ports.

For the LNW70 circuit pack, select

Transparent

for the

Virtual LAN Tagging

Mode

.

•

For circuit packs in service with a virtual switch assigned:

– Use the TL1

ed-vrtsw

command or select

Configuration

→

Data

→

Provision

Virtual Switch

command from the CIT System View menu to remove the required ports from a virtual switch.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the required LAN/WAN ports.

For the LNW70 circuit pack, select

Transparent

for the

Virtual LAN Tagging

Mode

.

.................................................................................................................................................................................................

14

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary STS-1 cross-connections to be made at each terminating and non terminating node in the network.

Important! Note that cross-connections at the terminating nodes are add/drop and cross-connections at the non terminating nodes are pass-through.

15

.................................................................................................................................................................................................

One at a time at each node in the network, use the TL1

ent-crs-sts1

command to provision the pass-through and add/drop cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection

Wizard. Use the Cross-Connection Wizard at each of the nodes in the network to provision the cross-connections.

Important! Note that the sum of the three individual STS-1 links in an OC-48 ring configuration cannot exceed a total of 48 STS-1s. In an OC-192 ring configuration, the total of the three links cannot exceed 63 STS-1s. An individual link cannot exceed the maximum of 21 STS-1s.

.................................................................................................................................................................................................................................

11-144 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-19: Establish a dedicated multiple point private line UPSR protected GbE service (transparent mode)

Reference:

(p. 11-195)

Procedure 11-24: “Make cross-connections for Ethernet service”

16

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connections have been made.

.................................................................................................................................................................................................

17

18

Important! For LNW70 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been

Enabled in both Input and Ouput Direction.

If required, use the TL1

ed-vcgtrib

command to enable tributaries, or from the

System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

19

20

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, at least one tributary at each end of the circuit must be Enabled in order for the VCG to go in service.

If required, after all cross-connections have been made, verify that the WAN (VCG)

Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-145

Ethernet/Data network provisioning procedures Procedure 11-19: Establish a dedicated multiple point private line UPSR protected GbE service (transparent mode)

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

21

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

22

.................................................................................................................................................................................................

Click on the

VCG Data

tab. Under the

Fault

section of the parameter display, verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, proceed to

Step 23 .

•

If the VCG Monitoring Mode is

NMON

(Not Monitored),

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

VCG Data

tab. Under the

Fault

section, select

AUTO

for the

VCG Monitoring Mode

.

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 20 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

If proper cross-connections have been made, then indications are that either the far-end or near-end circuit pack at each end of the span has failed or must be reset.

If the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near-end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Apply

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near-end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far-end and near-end circuit packs.

.................................................................................................................................................................................................................................

11-146 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-19: Establish a dedicated multiple point private line UPSR protected GbE service (transparent mode)

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

23

24

25

.................................................................................................................................................................................................

CREATE PORT TAGs

Use the TL1

ed-eport

and

ed-vcg

commands to assign port tags to the associated

LAN ports and VCG WAN ports. Or, select

Configuration

→

Data

→

Create Port

Tag

command from the CIT System View menu. Highlight the circuit pack being provisioned, then click

Select

. Provision the parameters as required. Click

Apply

, then click

Yes

to the warning message. Click

Close

to exit.

Important! The Peak Information Rate (PIR) rate limiting feature on the

LNW66/LNW67/LNW68 circuit packs will not be effective in transparent mode if the Ethernet Type (ethertype) parameter for the LAN or WAN VCG ports is provisioned to any value other than FFFF or 8100.

.................................................................................................................................................................................................

PROVISION LAN (Ethernet) PORTS

Use the TL1

ed-eport

command to provision parameters for the LAN port being provisioned. Or, select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the LAN port, then click

Select

.

Provision the parameters as required.

Click

Apply

, then click

Yes

to execute the command. Repeat for all ports being provisioned. Click

Close

to exit or continue with the next step.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

PROVISION WAN (VCG) PORTS

Use the TL1

ed-vcg

command to provision parameters for the VCG ports, as required.

Or, select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Click

Apply

, then click

Yes

to execute the command. Repeat for all ports being provisioned. Click

Close

to exit.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-147

Ethernet/Data network provisioning procedures Procedure 11-19: Establish a dedicated multiple point private line UPSR protected GbE service (transparent mode)

Figure 11-17 Dedicated multiple point GbE using transparent tagging mode

Node A

Node B

M 1 M 2

M 1 M 2

D

GbE

V1

1

V2 V3 V4

VLAN Tagging Mode=Transparent (LNW67/68)

Ed-eqpt:NodeA:fn-d-1:ctag::ETHPK:vlantagmd=Trans or

VLAN Tagging Mode=SWITCHED,Cross Connect Mode=STS1 (LNW70)

Ed-eqpt:NodeA:fn-d-1:ctag::ETHPK:vlantagmd=switched,eccmode=sts1

Virtual Switch ID = 124 (LNW67/68)

Ent-vrtsw:NodeA:fn-d-1:ctag::124:eplst=d1-1,vcglst=d1-v1&d1-v3 or

Virtual Switch ID = 124, Virtual LAN Tagging Mode=Transparent (LNW70)

Ent-vrtsw:NodeA:fn-d-1:ctag::124:eplst=d1-1,vcglst=d1-v1&d1-v3,tagmd=Trans

Ent-crs-sts1: See Figure on next page for

Cross-connections

Ed-eport-1ge:NodeA:d1-1:ctag:::dftporttag=55

Ed-vcg:NodeA:d1-v1:ctag:::addporttag=55

Ed-vcg:NodeA:d1-v3:ctag:::addporttag=55

D

GbE

V1

1

V2

V3 V4

Tagging Mode=Transparent (LNW67/68)

Ed-eqpt:NodeB:fn-d-1:ctag::ETHPK:vlantagmd=Trans

Virtual Switch ID = 124

Ent-vrtsw:NodeB:fn-d-1:ctag::124:eplst=d1-1,vcglst=d1-v1&d1-v3

Ent-crs-sts1: See Figure on next page for

Cross-connections

Ed-eport-1ge:NodeB:d1-1:ctag:::dftporttag=55

Ed-vcg:NodeB:d1-v1:ctag:::addporttag=55

Ed-vcg:NodeB:d1-v3:ctag:::addporttag=55

M 2

Node D

M 1

M 2

Node X

M 1

M 2

Node C

M 1

D

V1 V2

GbE

1

Tagging Mode=Transparent (LNW67/68)

Ed-eqpt:NodeD:fn-d-1:ctag::ETHPK:vlantagmd=Trans

Virtual Switch ID = 124

Ent-vrtsw:NodeD:fn-d-1:ctag::124:eplst=d1-1,vcglst=d1-v1

Ent-crs-sts1: See Figure 2 for Cross-connections

Ed-eport-1ge:NodeD:d1-1:ctag:::dftporttag=55

Ed-vcg:NodeD:d1-v1:ctag:::addporttag=55

D

GbE

1

V1 V2

Tagging Mode=Transparent (LNW67/68)

Ed-eqpt:NodeC:fn-d-1:ctag::ETHPK:vlantagmd=Trans

Virtual Switch ID = 124

Ent-vrtsw:NodeC:fn-d-1:ctag::124:eplst=d1-1,vcglst=d1-v1

Ent-crs-sts1: See Figure 2 for Cross-connections

Ed-eport-1ge:NodeC:d1-1:ctag:::dftporttag=55

Ed-vcg:NodeC:d1-v1:ctag:::addporttag=55

NC-DMX-284-2

.................................................................................................................................................................................................................................

11-148 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-19: Establish a dedicated multiple point private line UPSR protected GbE service (transparent mode)

Figure 11-18 Dedicated multiple point GbE private line cross-connections

Node A

Node B

M 1 M 2

Link B (Node A to Node B)

STS-1 Timeslots 9-29

21 STS-1s total

M 1 M 2

D

V1 V2 V3 V4

GbE 1

UPSR Ring Add/Drop cross-connections

NodeA:m1-1-(1-8),d1-v1-(1-8)

NodeA:m1-1-(9-29),d1-v3-(1-21)

2-Way Point-to-Point, Through cross-connections

NodeA:m1-1-(30-37),m2-1-(30-37)

Link A (Node D to Node A)

STS-1 Timeslots 1-8

Node D

M 2 M 1

D

M 2

Node X

M 1

V1 V2

V3 V4

GbE

1

UPSR Ring Add/Drop cross-connections

NodeB:m1-1-(30-37),d1-v1-(1-8)

NodeB:m1-1-(9-29),d1-v3-(1-21)

2-Way Point-to-Point, Through cross-connections

NodeB:m1-1-(1-8),m2-1-(1-8)

Link C (Node B to Node C)

STS-1 Timeslots 30-37

Node C

M 2 M 1

D

V1 V2

STS1 2-Way Point-to-Point Through cross-connections

GbE 1

UPSR Ring Add/Drop cross-connections

NodeD:m1-1-(1-8),d1-v1-(1-8)

2-Way Point-to-Point, Through cross-connections

NodeD:m1-1-(9-37),m2-1-(9-37) m1-1-(1-37),m2-1-(1-37)

D

V1 V2

GbE 1

UPSR Ring Add/Drop cross-connections

NodeC:m1-1-(30-37),d1-v1-(1-8)

2-Way Point-to-Point, Through cross-connections

NodeC:m1-1-(1-29),m2-1-(1-29)

NC-DMX-285-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-149

Ethernet/Data network provisioning procedures

Procedure 11-20: Add Fast Ethernet services to Ethernet packet ring – FE to GbE hairpin

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for adding 10/100T Fast Ethernet (FE) circuit pack services to a GbE packet ring. This procedure uses hairpin cross-connections and parameter settings to bind the FE services into an existing packet ring. See

Figure

11-19, “Ethernet packet ring on a UPSR” (p. 11-158)

and

Figure 11-20, “FE to GbE

Ethernet hairpin cross-connections and provisioning on packet ring” (p. 11-158)

for an example.

When the packet ring is first established, the capacity of the ring is predetermined by the number of STS-1 cross-connections applied to the ring and switches. The tagging mode (

802.1TAG

or Transparent [

Trans

]), virtual switch ID, and spanning tree group assigned to the GbE circuit pack is also predetermined. This procedure uses the 802.1q

tagging mode for an example.

This procedure assumes that a UPSR ring network configuration has already been established and no alarms are present. It also assumes that service has already been established from Node A, LAN port d1-1, WAN (VCG) d1-v1 and d1-v2 to Node C

LAN port d1-10, WAN (VCG) d1-v1 and d1-v2, using VLAN ID 103.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the nodes participating in the packet ring network.

•

The shelf slots, circuit packs, ports, VCGs involved in the packet ring network.

•

The number and type of cross-connections to be made at each node.

Note, that once the capacity of the packet ring is established, additional capacity

(cross-connections) may not be added in service without service interruption.

•

The tagging mode (transparent or 802.1q), virtual switch ID, and spanning tree group ID.

.................................................................................................................................................................................................................................

11-150 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Step

Procedure 11-20: Add Fast Ethernet services to Ethernet packet ring – FE to GbE hairpin

1

2

3

4

5

Use this procedure as an example to add FE services to an Ethernet packet ring on a

UPSR ring.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to each of the terminating nodes, if not already performed.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Neighbor Map

command and note the NEs connected to Main 1 and Main 2.

Access each of the NEs identified and select the

Administration

→

OSI Neighbor

Map

command and note the NEs connected to Main 1 and Main 2.

Repeat the above until the backbone ring can be sketched.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with this service.

.................................................................................................................................................................................................

Has the packet ring already been established? See

Figure 11-19, “Ethernet packet ring on a UPSR” (p. 11-158)

for an example.

If...

No,

Yes,

Then...

Establish the packet ring first, then continue with the next step.

Procedure 11-5: “Establish Ethernet packet ring on a UPSR” (p. 11-37)

Continue with the next step.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-151

Ethernet/Data network provisioning procedures Procedure 11-20: Add Fast Ethernet services to Ethernet packet ring – FE to GbE hairpin

6

7

.................................................................................................................................................................................................

Verify/Install the Fast Ethernet circuit pack into the required slot 1 of the Function

Unit group (A, B, C, or D) at the NE with the GbE circuit pack being used for the hairpin connections (Node A in this example).

Reference:

Procedure 4-12: “Install 10/100 Ethernet circuit packs” (p. 4-50)

.................................................................................................................................................................................................

CONFIGURE FE TAGGING MODE

Determine the existing tagging mode for the FE circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the System View menu, select the FE CP, then click

Select

. Note the VLAN Tagging Mode, Burst Size, and Credit Interval parameters.

Important! The tagging mode must be the same on both circuit packs being connected.

When FE circuit packs are installed in the shelf, the default

802TAG

mode is assigned to the circuit pack.

.................................................................................................................................................................................................

8

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly but other parameters are not correct, the tagging mode is NOT set correctly,

Then...

Proceed to

Step 14 .

Proceed to

Step 11 .

Continue with

Step 9 .

9

10

.................................................................................................................................................................................................

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the FE circuit pack being provisioned, then click

Select

. Note if a virtual switch ID has been assigned.

If a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

.................................................................................................................................................................................................

If a virtual switch has been provisioned, delete it by using the TL1

dlt-vrtsw

command or select the

Configuration

→

Data

→

Delete Virtual Switch

command

.................................................................................................................................................................................................................................

11-152 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-20: Add Fast Ethernet services to Ethernet packet ring – FE to GbE hairpin

11

12

13

14

from the System View menu, select the circuit pack being provisioned, then click

Select. Highlight the VRTSW ID being deleted, then click

Apply

.

Read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................

Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu, select the circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Verify/Select the tagging mode (

802.1TAG

) in the Select VLAN Tagging Mode box.

.................................................................................................................................................................................................

Verify/Enter the

Burst Size

and

Credit Interval

parameter values as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service.

ASSIGN VIRTUAL SWITCH ID TO FE PORTS

•

For circuit packs not yet in service with no virtual switch assigned:

– Use the TL1

ent-vrtsw

command to create an assigned virtual switch ID or select

Configuration

→

Data

→

Create Virtual Switch

command from the CIT

System View menu.

Note that the Virtual Switch ID for this example should be set to 123, the same

ID as in the GbE circuit pack on the packet ring. Also note that LAN ports c1-2 and c1-3, and VCG c1-v1 are assigned to the virtual switch.

•

For circuit packs not yet in service with a virtual switch assigned:

– Use the TL1

dlt-vrtsw

command to delete an assigned virtual switch ID or select

Configuration

→

Data

→

Delete Virtual Switch

command from the CIT

System View menu, if a different virtual switch ID is required.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the selected LAN/WAN ports.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-153

Ethernet/Data network provisioning procedures Procedure 11-20: Add Fast Ethernet services to Ethernet packet ring – FE to GbE hairpin

15

16

17

18

Note that the Virtual Switch ID for this example should be set to 123, the same

ID as in the GbE circuit pack on the packet ring. Also note that LAN ports c-2 and c-3, and VCG c-v1 are assigned to the virtual switch.

.................................................................................................................................................................................................

Add VCG port to Virtual Switch ID on GbE, if required.

Note that in this example,

Figure 11-19, “Ethernet packet ring on a UPSR” (p. 11-158) ,

we only assigned VCGs d1-v1 and d1-v2 to virtual switch ID 123 when we created the packet ring. We now need to add VCG d1-v3 to the same virtual switch ID. Note that we should have added d1-v3 to the virtual switch when we established the packet ring.

Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the GbE circuit pack being provisioned, then click

Select

. Determine if VCG d1-v3 is already assigned to virtual switch ID

123.

If VCG d1-v3 is not assigned to virtual switch ID 123, use the TL1

ed-vrtsw

command or select the

Configuration

→

Data

→

Provision Virtual Switch

command from the System View menu, select the circuit pack being provisioned, then click

Select

. Highlight and Select the Available AID d1-v3 to move the

VCG (WAN) Port

d1-v3 to the Selected AID column. Click

Apply

, then click

Close

to exit.

.................................................................................................................................................................................................

ESTABLISH HAIRPIN CROSS-CONNECTIONS

Determine the necessary

2-Way Hairpin

STS-1 cross-connections to be made between the FE circuit pack and the GbE circuit pack.

Note that the

2-Way Hairpin

cross-connections between the FE and GbE in this example must be made between the FE and GbE v3(v4) since the GbE VCG group v1 and v2 are part of the multipoint packet ring cross-connection.

.................................................................................................................................................................................................

Use the TL1

ent-crs-sts1

command to provision the cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the

Cross-Connection Wizard. Use the Cross-Connection Wizard to provision the

2-Way

Hairpin

cross-connections. For example, see

Figure 11-20, “FE to GbE Ethernet hairpin cross-connections and provisioning on packet ring” (p. 11-158) .

Reference:

Refer to

Procedure 11-24: “Make cross-connections for Ethernet service” (p. 11-195)

for cross-connection examples.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

to verify that the proper connections have been made.

.................................................................................................................................................................................................................................

11-154 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-20: Add Fast Ethernet services to Ethernet packet ring – FE to GbE hairpin

19

20

21

22

23

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

If required, after all cross-connections have been made, verify that the WAN (VCG)

Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Click on the

VCG Data

tab. Under the

Fault

section of the parameter display, verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, proceed to

Step 24 .

•

If the VCG Monitoring Mode is

Not Monitored

,

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

VCG Data

tab. Under the

Fault

section, select

Auto

for the

VCG Monitoring Mode

.

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 21 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-155

Ethernet/Data network provisioning procedures Procedure 11-20: Add Fast Ethernet services to Ethernet packet ring – FE to GbE hairpin

24

25

26

If proper cross-connections have been made, then indications are that either the far-end or near-end circuit pack at each end of the span has failed or must be reset.

If the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near-end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Apply

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near-end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far-end and near-end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

ASSIGN VLAN IDs TO ESTABLISH SERVICE

Use the TL1

ent-vlan

command to assign the default VLAN ID for customer untagged frames or the customer VLAN ID for tagged frames to the associated LAN ports and VCG WAN ports on the FE and GbE circuit packs. Or, select

Configuration

→

Data

→

Create VLAN

command from the CIT System View menu. For example, see

Figure 11-20, “FE to GbE Ethernet hairpin cross-connections and provisioning on packet ring” (p. 11-158) .

.................................................................................................................................................................................................

PROVISION LAN PORTS

Use the TL1

ed-eport

command to provision the LAN port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the

Ethernet circuit pack, highlight the LAN port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

PROVISION VCGS

Use the

ed-vcg

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the

Ethernet circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Important! Enable full rate end-to-end flow control for the VCGs involved in the hairpin cross-connection by setting

Pause Control (psctl)

to

TRANSPARENT

for the

.................................................................................................................................................................................................................................

11-156 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-20: Add Fast Ethernet services to Ethernet packet ring – FE to GbE hairpin

VCGs involved in the hairpin cross-connection. In this example you would set

Pause Control to

TRANSPARENT

for VCG c1-v1 on the FE circuit pack, and for

VCG d1-v3 on the GbE circuit pack.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-157

Ethernet/Data network provisioning procedures Procedure 11-20: Add Fast Ethernet services to Ethernet packet ring – FE to GbE hairpin

Figure 11-19 Ethernet packet ring on a UPSR

M 2

Node A

M 1 M 2

Node B

M 1

IN

OUT

V2

V4

1

V1

V3

D

GbE

VLAN Tagging Mode=Transparent or 802.1q (LNW67/68)

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=TRANS(or 802.1TAG) or

VLAN Tagging Mode=SWITCHED (LNW70)

Cross Connect Mode=STS1 (LNW70)

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=switched,eccmode=sts1

Virtual Switch ID = 123 (LNW67/68)

Ent-vrtsw:tid:fn-d-1:ctag::123:eplst=d1-1,vcglst=d1-v1&d-v2 or

Virtual Switch ID = 123 (LNW70)

Virtual LAN Tagging Mode=Transparent or 802.1TAG (LNW70)

Ent-vrtsw:tid:fn-d-1:ctag::123:eplst=d1-1,vcglst=d1-v1&d1-v2,tagmd=Trans

Cross-Connection Wizard Multipoint Cross-connections:

Source AID: m1-1-(1-21),Destination AID: d1-v1-(1-21)

Source AID: m2-1-(1-21),Destination AID: d1-v2-(1-21)

Spanning Tree Group ID (e.g. 1) ent-stgrp:tid::ctag::1,123:vcglst=d1-v1&d1-v21

Node D

M 1 M 2

V2 V1

3

D

FE

VLAN Tagging Mode = 802.1q or Transparent (LNW66)

Example: ed-eqpt:tid:fn-d-1:ctag:ETHPK:vlantagmd=802.1TAG

Example: ed-eqpt:tid:fn-d-1:ctag:ETHPK:vlantagmd=TRANS

Virtual Switch ID (e.g. 123)

Ent-vrtsw:tid:fn-d-1:ctag::123:eplst=d1-3,vcglst=d1-v1&d1-v2

Cross-Connection Wizard Multipoint Cross-connections:

Source AID: m1-1-(1-21),Destination AID: d1-v1-(1-21)

Source AID: m2-1-(1-21),Destination AID: d1-v2-(1-21)

Spanning Tree Group ID (e.g. 1) ent-stgrp:tid::ctag::1,123:vcglst=d1-v1&d1v2

M 1

Node C

M 2

V1 V2

D

STS1 2-Way Point-to-Point Through cross-connections m1-1-(1-21),m2-1-(1-21)

10

FE

VLAN Tagging Mode = 802.1q or Transparent (LNW66)

Example: ed-eqpt:tid:fn-d-1:ctag:ETHPK:vlantagmd=802.1TAG

Example: ed-eqpt:tid:fn-d-1:ctag:ETHPK:vlantagmd=TRANS

Packet Ring on UPSR using multipoint (unswitched) cross-connections

Virtual Switch ID (e.g. 123) fn-

Cross-Connection Wizard Multipoint Cross-connections:

Source AID: m1-1-(1-21),Destination AID: d1-v1-(1-21)

Source AID: m2-1-(1-21),Destination AID: d1-v2-(1-21)

Spanning Tree Group ID (e.g. 1) ent-stgrp:tid::ctag::1,123:vcglst=d1-v1&d1-v2

NC-DMX-232-2

.................................................................................................................................................................................................................................

11-158 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-20: Add Fast Ethernet services to Ethernet packet ring – FE to GbE hairpin

Figure 11-20 FE to GbE Ethernet hairpin cross-connections and provisioning on packet ring

Node A Node B

M 2 M 1 M 2 M 1

OUT IN

IN

OUT

C

V2 V1

V2

V3

FE 2 3

VLAN 101VLAN 102

V1

V4

1

D

V2 V1

D

GbE VLANs 103, 101, 102

VLAN 102 3 FE

Ent-vlan:NodeB:fn-d-1:ctag::102:123:eplst=d1-3,vcglst=d1-v1&d1-v2

Ed-vrtsw:NodeA:fn-d-1:ctag::123:addvcg=d1-v3

FE Tagging Mode = 802.1q

Example: ed-eqpt:NodeA:fn-c-1:ctag:ETHPK:vlantagmd=802.1q

Virtual Switch ID (e.g. 123)

Example: ent-vrtsw:NodeA:fn-c-1:ctag::123:eplst=c1-2&c1-3,vcglst=c1-v1

NodeA 2-Way Hairpin cross-connections:c1-v1-(1-21),d1-v3-(1-21)

Ent-vlan:NodeA:fn-d-1:ctag::101:123:eplst=d1-1,vcglst=d1-v3

Ent-vlan:NodeA:fn-c-1:ctag::101:123:eplst=c1-2,vcglst=d1-v1

Ent-vlan:NodeA:fn-c-1:ctag::102:123:eplst=c1-3,vcglst=d1-v1

Ent-vlan:NodeA:fn-d-1:ctag::102:123:eplst=d1-1,vcglst=d1-v3,d1-v2,d1-v1

Node D Node C

M 1 M 2 M 1 M 2

OUT IN

IN

OUT

VLAN 103

V1 V2

D

10

FE

NC-DMX-286-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-159

Ethernet/Data network provisioning procedures

Procedure 11-21: Establish LNW71 10/100-PL Fast Ethernet private line service on UPSR

.................................................................................................................................................................................................................................

Overview

This procedure provides examples for:

•

Configuring point-to-point UPSR protected fast Ethernet private line service using the LNW71 10/100-PL Private Line Ethernet circuit pack. See

Figure 11-21,

“Point-to-Point 10/100-PL private line service, STS1 cross-connect mode, one

STS1” (p. 11-164) ,

Figure 11-22, “Point-to-Point 10/100-PL private line service,

STS1 cross-connect mode, two STS1s” (p. 11-164) , and

Figure 11-23, “Two point-to-point 10/100-PL private line services, STS3c cross-connect mode, one

STS1 service and one STS3c service” (p. 11-165)

for examples.

–

Figure 11-21, “Point-to-Point 10/100-PL private line service, STS1 cross-connect mode, one STS1” (p. 11-164)

illustrates a UPSR protected point-to-point private line service using STS1 cross-connect mode and one

STS1 cross-connection.

–

Figure 11-22, “Point-to-Point 10/100-PL private line service, STS1 cross-connect mode, two STS1s” (p. 11-164)

illustrates a UPSR protected point-to-point private line service using STS1 cross-connect mode and two

STS1 cross-connection.

–

Figure 11-23, “Two point-to-point 10/100-PL private line services, STS3c cross-connect mode, one STS1 service and one STS3c service” (p. 11-165)

illustrates two UPSR protected point-to-point private line services from one node to two other nodes using STS3c cross-connect mode and one STS1 cross-connection for one service and an STS-3c cross-connection for the other service.

•

Configuring unprotected (no SONET protection) private line services with multipoint cross-connections, external customer equipment protection. See

Figure

11-24, “Unprotected 10/100-PL private line services using multipoint cross-connections, STS1 cross-connect mode, external customer protected”

(p. 11-166)

for an example.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Important! If the LNW71 10/100-PL circuit pack is being used in Function groups

A, B, or C and the Main slots are equipped with LNW26B OC-48 OLIUs or functionally equivalent OLIUs with PWDM compatible optics, then cross-connections may only be made to the first 12 VCGs in STS-1 mode or the first 8 VCGs in STS-3c mode.

.................................................................................................................................................................................................................................

11-160 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-21: Establish LNW71 10/100-PL Fast

Ethernet private line service on UPSR

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

Step

1

2

3

4

Use this procedure as an example for configuring fast Ethernet private line service. See

Figures for examples.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes, if not already performed.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

and/or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

This command may take several minutes to complete depending on the size of the network.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the service to be established.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-161

Ethernet/Data network provisioning procedures Procedure 11-21: Establish LNW71 10/100-PL Fast

Ethernet private line service on UPSR

5

6

7

8

9

10

.................................................................................................................................................................................................

Verify that the Ethernet circuit packs have been installed into the required slot 1 of the

Function Unit group (A, B, C, or D) at each NE providing Ethernet service.

Reference:

Procedure 4-12: “Install 10/100 Ethernet circuit packs” (p. 4-50)

.................................................................................................................................................................................................

Important! If the Ethernet circuit pack is already in service, the existing cross-connect mode cannot be changed without removing all existing VCG cross-connections.

CONFIGURE CROSS-CONNECT MODE

Determine the existing Cross-Connect mode for the circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the System View menu, select the CP, then click

Select

. Note the Cross-Connect mode.

.................................................................................................................................................................................................

If required, use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu, select the circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Verify/Select the Cross-Connect mode (STS1 or STS3c) in the

Cross-Connect Mode

box. Click

Apply

, then click

Close

to exit.

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary cross-connections to be made at each terminating and non terminating node in the network.

Important! STS-1 Cross-Connect mode supports one or two STS-1 cross-connections to each of 24 VCGs (1-24). STS-3c Cross-Connect mode supports at most one STS-3c or one STS-1 cross-connection to each of the first 16

VCGs (1-16), (VCGs 17-24 are not used).

In STS3c mode, if an STS1 cross-connection is made to a VCG, it must be made to the first (1) STS1 tributary of the VCG. In STS1 mode, the first STS1 cross-connection made to a VCG should be made to the first (1) STS1 tributary of the VCG (for example, d-v13-1).

.................................................................................................................................................................................................

One at a time at each non terminating node in the network, use the TL1

ent-crs-sts1

or

ent-crs-sts3c

command to provision the pass-through cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the

.................................................................................................................................................................................................................................

11-162 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-21: Establish LNW71 10/100-PL Fast

Ethernet private line service on UPSR

11

12

13

14

15

Cross-Connection Wizard. Use the Cross-Connection Wizard at each of the nodes in the network to provision the cross-connections.

Important! Note that cross-connections at the terminating nodes are add/drop and cross-connections at the non terminating nodes are pass-through.

Reference:

(p. 11-195)

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

One at a time at each terminating node in the network, use the TL1

ent-crs-sts1

or

ent-crs-sts3c

command to provision the add/drop cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the

Cross-Connection Wizard. Use the Cross-Connection Wizard at each of the nodes in the network to provision the cross-connections.

Reference:

(p. 11-195)

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connections have been made.

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

PROVISION LAN PORTS

Use the TL1

ed-eport

command to provision the LAN port parameters, or select

Configuration

→

Equipment

from the System View menu. Expand the details for the circuit pack, highlight the LAN Port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

16

.................................................................................................................................................................................................

Click

Apply

. Read the warning message, then click

Yes

to execute the command.

.................................................................................................................................................................................................

17

PROVISION VCGS

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-163

Ethernet/Data network provisioning procedures

18

Procedure 11-21: Establish LNW71 10/100-PL Fast

Ethernet private line service on UPSR

Use the

ed-vcg

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, if window is not already open from the prevision step. Expand the details for the circuit pack, highlight the

VCG port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

.................................................................................................................................................................................................

Click

Apply

. Read the warning message, then click

Yes

to execute the command.

Click

Close

to exit or repeat from

Step 16

for other port provisioning.

E

N D O F

S

T E P S

Figure 11-21 Point-to-Point 10/100-PL private line service, STS1 cross-connect mode, one STS1

Node A Node B

M 1 M 2 M 1 M 2

OUT

IN

IN

OUT

V1 V13

D

V24

1 13

Cross-Connect Mode = STS1

UPSR Ring Add/Drop cross-connections

Range: m1-1-(1-48),d1-v13-(1-2)

Example: m1-1-1,d1-v13-1

2-Way Point-to-Point, Through Cross-connections

Range:m1-1-(1-48),m2-1-(1-48)

Example:m1-1-1,m2-1-1

Example of 10/100-PL 2-Way UPSR Ring Add/Drop cross-connections using one STS1 for point-to-point private line service

M 2

Node D

M 1

OUT

IN

V24

...

V13 V1

D

13 1

Cross-Connect Mode = STS1

UPSR Ring Add/Drop cross-connections

Range: m1-1-(1-48),d1-v13-(1-2)

Example: m1-1-1,d1-v13-1

IN

OUT

M 2

Node C

M 1

2-Way Point-to-Point, Through Cross-connections

Range:m1-1-(1-48),m2-1-(1-48)

Example:m1-1-1,m2-1-1

MA-DMX-325-2

.................................................................................................................................................................................................................................

11-164 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-21: Establish LNW71 10/100-PL Fast

Ethernet private line service on UPSR

Figure 11-22 Point-to-Point 10/100-PL private line service, STS1 cross-connect mode, two STS1s

Node A Node B

M 1 M 2

OUT IN

M 1 M 2

IN

OUT

V1 V13

D

V24

13

Cross-Connect Mode = STS1

UPSR Ring Add/Drop cross-connections

Node A:m1-1-1,d1-v13-1

Node A:m1-1-2,d1-v13-2

2-Way Point-to-Point, Through Cross-connections

Node B:m1-1-1,m2-1-1

Node B:m1-1-2,m2-1-2

Example of 10/100-PL 2-Way UPSR Ring Add/Drop cross-connections using two STS1s for point-to-point private line service

M 2

Node D

M 1

V24

...

V13 V1

D

13

Cross-Connect Mode = STS1

UPSR Ring Add/Drop cross-connections

Node D:m1-1-1,d1-v13-1

Node D:m1-1-2,d1-v13-2

OUT

IN

IN

OUT

M 2

Node C

M 1

2-Way Point-to-Point, Through Cross-connections

Node C:m1-1-1,m2-1-1

Node C:m1-1-2,m2-1-2

MA-DMX-324-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-165

Ethernet/Data network provisioning procedures Procedure 11-21: Establish LNW71 10/100-PL Fast

Ethernet private line service on UPSR

Figure 11-23 Two point-to-point 10/100-PL private line services, STS3c cross-connect mode, one STS1 service and one STS3c service

Node A

M 1 M 2 Node B

OUT

IN

M 1 M 2

V1 V13

1 13

Cross-Connect Mode = STS3c

D

V16

UPSR Ring Add/Drop STS3C

Node A:m1-1-4,d1-v13-1 cross-connections

UPSR Ring Add/Drop STS1 cross-connections

Node A:m1-1-1,d1-v1-1

IN

OUT

2-Way Point-to-Point, Through

Node B:m1-1-1,m2-1-1

STS1 Cross-connections

2-Way Point-to-Point, Through STS3 Cross-connections

Node B:m1-1-4,m2-1-4

Example: 10/100-PL 2-Way UPSR Ring Add/Drop cross-connections, two point-to-point private line services, STS3c and STS1 mode

M 2

Node D

M 1

OUT

IN

V16 ...

V13 V1

D

13

Cross-Connect Mode = STS3

UPSR Ring Add/Drop STS3C

Node D:m1-1-4,d1-v13-1 cross-connections

2-Way Point-to-Point, Through

Node D:m1-1-1,m2-1-1

STS1 Cross-connections

IN

M 2

Node C

M 1

OUT

V24...

V13

V1

D

1

Cross-Connect Mode = STS1

UPSR Ring Add/Drop STS1

Node C:m1-1-1,d1-v1-1 cross-connections

2-Way Point-to-Point, Through

Node C:m1-1-4,m2-1-4

STS3C Cross-connections

MA-DMX-326-2

.................................................................................................................................................................................................................................

11-166 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-21: Establish LNW71 10/100-PL Fast

Ethernet private line service on UPSR

Figure 11-24 Unprotected 10/100-PL private line services using multipoint cross-connections, STS1 cross-connect mode, external customer protected

Node A Node B

M 1 M 2 M 1 M 2

OUT

IN

IN

OUT

V1

V2

V13

1 13

Customer Equipment

D

V24

Cross-Connect Mode = STS1

Multipoint (unswitched) cross-connections

Range: m1-1-(1-48),d1-v1-(1-2)

Example: m1-1-(1-2),d1-v1-(1-2)

2-Way Point-to-Point, Through Cross-connections

Range: m1-1-(1-48),m2-1-(1-48)

Example: m1-1-(1-2),m2-1-(1-2)

Example of 10/100-PL Multipoint (unswitched) cross-connections to an OC-48 UPSR

M 2

Node D

M 1 M 2

Node C

M 1

OUT

IN

IN

OUT

V24 V13 V1

Cross-Connect Mode = STS1

13 1

Customer Equipment

Multipoint (unswitched) cross-connections

Range: m1-1-(1-48),d1-v1-(1-2)

Example: m1-1-(1-2),d1-v1-(1-2)

V24 V13 V1

13 1

Customer Equipment

Multipoint (unswitched) cross-connections

Range: m1-1-(1-48),d1-v1-(1-2)

Example: m1-1-(1-2),d1-v1-(1-2)

MA-DMX-328-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-167

Ethernet/Data network provisioning procedures

Procedure 11-22: Establish video broadcast network on UPSR

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring a video broadcast network with a bidirectional control channel on a UPSR ring using Gigabit Ethernet circuit packs and

802.1q tagging mode.

The control ring is optional and only needed if control data needs to be sent to/from the remote sites.

Frames sent from the head end source node must be Multicast frames.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters.

This procedure consists of essentially three parts:

•

The first part verifies the network and sets the tagging mode and other parameters for the Ethernet packs being used.

•

The second part establishes the downstream video broadcast ring.

•

The third part establishes a multipoint packet ring for upstream control functions.

Refer to

Figure 11-25, “Provisioning Ethernet nodes for video broadcast ring”

(p. 11-181)

and

Figure 11-26, “Provisioning cross-connections for video broadcast ring” (p. 11-181)

for provisioning the video broadcast ring. Refer to

Figure 11-27,

“Provisioning Ethernet nodes for control packet ring” (p. 11-182)

and

Figure 11-28,

“Provisioning cross-connections for control packet ring” (p. 11-183)

for provisioning the control packet ring.

This procedure assumes that the UPSR SONET ring network configuration has already been established and no alarms are present.

Important! On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a

Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

.................................................................................................................................................................................................................................

11-168 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-22: Establish video broadcast network on

UPSR

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

•

The tagging mode (this procedure uses 802.1q), virtual switch IDs, and spanning tree groups to be created at each node.

•

The VLAN IDs being assigned to the video broadcast traffic and to the control traffic.

Important! This procedure is typically performed at full rate Gigabit service; full rate Gigabit service requires 21 STS-1 cross-connections. Ensure that you have a sufficient number of STS-1s available.

Step

1

2

3

Use this procedure as an example for configuring a video broadcast network with upstream control functions.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes, if not already performed.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

and/or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

This command may take several minutes to complete depending on the size of the network.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-169

Ethernet/Data network provisioning procedures Procedure 11-22: Establish video broadcast network on

UPSR

4

5

6

.................................................................................................................................................................................................

From your work instructions, determine the terminating nodes, circuit packs, LAN ports, WAN (VCG) ports, virtual switch ID, cross-connections, spanning tree group ID, and VLAN IDs associated with the service being established.

.................................................................................................................................................................................................

Verify that the Ethernet circuit packs have been installed into the required slot 1 of the

Function Unit or Growth group (A, B, C, D, or G) at each NE providing Ethernet service.

Reference:

Procedure 4-13: “Install Gigabit Ethernet circuit packs” (p. 4-54)

.................................................................................................................................................................................................

CONFIGURE TAGGING MODE

At each NE providing this Ethernet service, determine the existing tagging mode for the Ethernet circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the System View menu, select the CP, then click

Select

. Note the VLAN Tagging Mode and other parameter values.

The VLAN Tagging Mode for the LNW66/67/68 circuit packs must be set to

TRANS

or

802.1TAG

. The VLAN Tagging Mode for the LNW70 circuit packs must be set to

SWITCHED

.

Important! When GbE circuit packs are installed in the shelf, the default

″

NOTAG

″ mode is assigned to the circuit pack.

.................................................................................................................................................................................................

7

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly but other parameters are not correct, the tagging mode is NOT set correctly,

Then...

Proceed to

Step 13 .

Proceed to

Step 10 .

Continue with

Step 8 .

8

.................................................................................................................................................................................................

If you are going to change the VLAN Tagging Mode that presently exists AND a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

.................................................................................................................................................................................................................................

11-170 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-22: Establish video broadcast network on

UPSR

9

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the GbE circuit pack being provisioned, then click

Select

. Note if a virtual switch ID has been assigned.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service.

If the service you are establishing in this procedure is a second service on an existing

GbE circuit pack with all LAN/WAN ports in the same virtual switch, then the existing virtual switch ID must be retained or the ports not in service must be removed from the existing virtual switch and added to a new virtual switch ID.

10

11

12

If a virtual switch is assigned, use the TL1

dlt-vrtsw

command or select the

Configuration

→

Data

→

Delete Virtual Switch

command from the System View menu, select the circuit pack being provisioned, then click Select. Highlight the

VRTSW ID being deleted, then click

Apply

.

Read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................

Provision circuit pack parameters. Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu, select the circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Verify/Select the tagging mode (

802.1TAG

,

TRANS

, or

SWITCHED

) in the VLAN Tagging

Mode box.

Important! This procedure uses 802.1TAG mode to illustrate the provisioning.

.................................................................................................................................................................................................

Verify/Enter other parameter values (for example,

Burst Size

,

Credit Interval

[LNW66/67/68],

Ethernet Cross Connect Mode

and

Port Configuration

[LNW70]), as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-171

Ethernet/Data network provisioning procedures Procedure 11-22: Establish video broadcast network on

UPSR

13

14

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

END OF STEPS TO PROVISION CIRCUIT PACKS

.................................................................................................................................................................................................

BEGIN VIDEO BROADCAST RING PROVISIONING

See

Figure 11-25, “Provisioning Ethernet nodes for video broadcast ring” (p. 11-181) .

Assign Virtual Switch ID:

•

For circuit packs not yet in service with no virtual switch assigned:

– Use the TL1

ent-vrtsw

command to create an assigned virtual switch ID or select

Configuration

→

Data

→

Create Virtual Switch

command from the CIT

System View menu.

•

For circuit packs not yet in service with a virtual switch assigned:

– Use the TL1

dlt-vrtsw

command to delete an assigned virtual switch ID or select

Configuration

→

Data

→

Delete Virtual Switch

command from the CIT

System View menu, if a different virtual switch ID is required.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the selected LAN/WAN ports.

For the LNW70 circuit pack, select the required

Virtual LAN Tagging Mode

(

802.1TAG

or

Transparent

). This procedure uses 802.1TAG mode to illustrate the provisioning.

•

For circuit packs in service, on only one set of ports, with a virtual switch assigned:

– Use the TL1

ed-vrtsw

command or select

Configuration

→

Data

→

Provision

Virtual Switch

command from the CIT System View menu to remove the required ports from a virtual switch.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the required LAN/WAN ports.

For the LNW70 circuit pack, select the required

Virtual LAN Tagging Mode

(

802.1TAG

or

Transparent

).

For the video broadcast ring in this example, note that we assigned a virtual switch ID of 4095 to LAN port d1-1 and VCG port d1-v1 at each participating node. See

Figure

11-25, “Provisioning Ethernet nodes for video broadcast ring” (p. 11-181) .

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary STS-1 cross-connections to be made at the head end node, each Ethernet terminating node, and any pass through cross-connections to be made at

.................................................................................................................................................................................................................................

11-172 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-22: Establish video broadcast network on

UPSR

15

16

17

18

19

20

any non terminating nodes in the network. See

Figure 11-26, “Provisioning cross-connections for video broadcast ring” (p. 11-181)

for an example.

.................................................................................................................................................................................................

One at a time at each node in the network, select

Configuration

→

Cross-

Connections

from the System View menu to start the Cross-Connection Wizard.

Select

Create a new Cross-Connections

, then click

Next

at the bottom of the screen.

Reference:

(p. 11-195) .

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

Use the Cross-Connection Wizard at each non terminating node to provision the two-way pass-through (

2-Way Point-to-Point, Through

) cross-connections.

.................................................................................................................................................................................................

Use the Cross-Connection Wizard at the head end source node to provision the

Ethernet one-way add (

1-Way Point-to-Point

) cross-connections.

.................................................................................................................................................................................................

Use the Cross-Connection Wizard at the remote terminating nodes to provision the one-way path protected drop (

1-Way Path Protected Drop from a UPSR Ring

) and two-way pass-through (

2-Way Point-to-Point, Through

) cross-connections.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

to verify that the proper cross-connections have been made.

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been

Enabled in the Input or Ouput Direction, as required.

If not already performed when cross-connections were made, use the TL1

ed-vcgtrib

command to enable tributaries, or from the System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-173

Ethernet/Data network provisioning procedures

21

22

23

24

25

Procedure 11-22: Establish video broadcast network on

UPSR

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made at each node in the ring, click on the

Alarm List

button on the System View window and verify no new alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

VERIFY PORT MONITORING MODE

After all cross-connections have been made at each node in the ring, verify that the

WAN (VCG) Ports being used have gone in service (IS) at each terminating node.

From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Important! Note that the VCG port at the head end source node will not show in-service since it is not provisioned to receive packets.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Click on the

Fault/Alarms

tab. Verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, click

Close

to exit then proceed to

Step 26 .

•

If the VCG Monitoring Mode is

NMON

(Not Monitored),

.................................................................................................................................................................................................................................

11-174 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-22: Establish video broadcast network on

UPSR

26

27

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

Fault/Alarms

tab, select

AUTO

for the

VCG Monitoring Mode

.

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 23 .

•

If the VCG Monitoring Mode is

AUTO

:

Verify that the VCG Trib Membership provisioning is correct. Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

If proper cross-connections have been made, then indications are that either the far end or near end circuit pack at each end of the span has failed or must be reset. If

the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Select

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far end and near end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

ASSIGN VLAN IDs TO VIDEO BROADCAST RING NETWORK

Use the TL1

ent-vlan

command to assign the VLAN ID for the associated LAN ports and VCG WAN ports. Or, select

Configuration

→

Data

→

Create VLAN

command from the CIT System View menu. For example, see

Figure 11-25, “Provisioning

Ethernet nodes for video broadcast ring” (p. 11-181) .

In this example, we assign VLAN 2567 to the associated LAN (d1-1) and VCG

(d1-v1) ports at the head end and terminating nodes.

.................................................................................................................................................................................................

PROVISION LAN PORTS

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-175

Ethernet/Data network provisioning procedures

28

29

Procedure 11-22: Establish video broadcast network on

UPSR

Use the TL1

ed-eport

command to provision the LAN port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the LAN Port (for example, Port 1), then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

PROVISION VCGS

Use the

ed-vcg

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

END OF STEPS TO PROVISION VIDEO BROADCAST RING

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service.

If the service you are establishing in this procedure is a second service on an existing

GbE circuit pack with all LAN/WAN ports in the same virtual switch, then the existing virtual switch ID must be retained or the ports not in service must be removed from the existing virtual switch and added to a new virtual switch ID.

BEGIN CONTROL PACKET RING PROVISIONING

See

Figure 11-27, “Provisioning Ethernet nodes for control packet ring” (p. 11-182) .

Assign Virtual Switch ID:

•

For circuit packs not yet in service with no virtual switch assigned:

– Use the TL1

ent-vrtsw

command to create an assigned virtual switch ID or select

Configuration

→

Data

→

Create Virtual Switch

command from the CIT

System View menu.

•

For circuit packs not yet in service with a virtual switch assigned:

– Use the TL1

dlt-vrtsw

command to delete an assigned virtual switch ID or select

Configuration

→

Data

→

Delete Virtual Switch

command from the CIT

System View menu, if a different virtual switch ID is required.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the selected LAN/WAN ports.

.................................................................................................................................................................................................................................

11-176 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

30

31

32

33

34

35

Procedure 11-22: Establish video broadcast network on

UPSR

•

For circuit packs in service, on only one set of ports, with a virtual switch assigned:

– Use the TL1

ed-vrtsw

command or select

Configuration

→

Data

→

Provision

Virtual Switch

command from the CIT System View menu to remove the required ports from a virtual switch.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the required LAN/WAN ports.

For the control packet ring in this example, note that we assigned a virtual switch

ID of 250 to LAN port d1-2 and VCG ports d1-v3 and d1-v4 at each participating node. See

Figure 11-27, “Provisioning Ethernet nodes for control packet ring”

(p. 11-182) .

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary Multipoint (unswitched) STS-1 cross-connections to be made at each Ethernet terminating node and any two-way pass-through cross-connections to be made at any non terminating nodes in the network. See

Figure 11-28, “Provisioning cross-connections for control packet ring” (p. 11-183)

for an example.

.................................................................................................................................................................................................

One at a time at each node in the network, select

Configuration

→

Cross-

Connections

from the System View menu to start the Cross-Connection Wizard.

Select

Create a new cross-connection

, then click

Next

at the bottom of the screen.

Reference:

Refer to

Procedure 11-24: “Make cross-connections for Ethernet service” (p. 11-195)

for cross-connection examples.

.................................................................................................................................................................................................

Use the Cross-Connection Wizard at each non terminating node to provision the two-way pass-through (

2-Way Point-to-Point, Through

) cross-connections.

.................................................................................................................................................................................................

Use the Cross-Connection Wizard at each terminating node to provision the Ethernet

Multipoint

(unswitched) cross-connections.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

to verify that the proper cross-connections have been made.

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no new alarms are present.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-177

Ethernet/Data network provisioning procedures Procedure 11-22: Establish video broadcast network on

UPSR

36

37

38

39

.................................................................................................................................................................................................

If new alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

If required, after all cross-connections have been made, verify that the WAN (VCG)

Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Click on the

Fault/Alarms

tab. Verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, click

Close

to exit then proceed to

Step 40 .

•

If the VCG Monitoring Mode is

NMON

(Not Monitored),

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

Fault/Alarms

tab, select

AUTO

for the

VCG Monitoring Mode

.

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 37 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

.................................................................................................................................................................................................................................

11-178 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-22: Establish video broadcast network on

UPSR

40

If proper cross-connections have been made, then indications are that either the far end or near end circuit pack at each end of the span has failed or must be reset. If

the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Select

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far end and near end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

CREATE SPANNING TREE GROUP

If required, determine a preferred spanning tree configuration (span to be blocked under nominal conditions), the preferred root node, and spanning tree root priorities for this service.

Important! Note that it is not necessary to determine a preferred spanning tree configuration. A default spanning tree configuration is configured when you establish the spanning tree group.

Reference:

(p. 11-216)

Procedure 11-25: “Create preferred spanning tree configuration”

41

.................................................................................................................................................................................................

At each Ethernet node, use the TL1 command

ent-stgrp

to assign and provision the parameters for the ports (d1-v3 and d1-v4 in this example) involved in the spanning tree group. Or, select

Configuration

→

Data

→

Create Spanning Tree Group

command from the CIT System View menu. For example, see

Figure 11-27,

“Provisioning Ethernet nodes for control packet ring” (p. 11-182) .

Important! Networks running 802.1d STP (Release 1.1) support a maximum of up to nine nodes participating in a spanning tree. Networks with more than nine nodes will not reconfigure properly. Spanning tree default parameters support a network of up to nine nodes.

Networks running 802.1w rapid spanning tree protocol (Release 2 or later) support more than nine nodes participating in a spanning tree. To support more than nine nodes in the spanning tree, the maximum age timer must be increased. Note that spanning tree restoration time increases as the number of nodes increase.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-179

Ethernet/Data network provisioning procedures Procedure 11-22: Establish video broadcast network on

UPSR

42

43

44

If the network consists of more than nine (9) nodes which are participating in the spanning tree configuration, use the following formula to determine the proper setting for the spanning tree maximum age timer (

stmaxage

): 2 x (N + 1), where N equals the number of nodes.

If the network consists of 20 nodes, then the

stmaxage

timer should be set to 42 seconds: 2 x (20 + 1) = 42.

.................................................................................................................................................................................................

ASSIGN VLAN IDs TO CONTROL RING NETWORK

Use the TL1

ent-vlan

command to assign the VLAN ID for the associated LAN ports and VCG WAN ports. Or, select

Configuration

→

Data

→

Create VLAN

command from the CIT System View menu. For example, see

Figure 11-27, “Provisioning

Ethernet nodes for control packet ring” (p. 11-182) .

In this example, we assign VLAN 4093 to the associated LAN (d1-2) and VCGs

(d1-v3 and d1-v4) ports at each node.

.................................................................................................................................................................................................

PROVISION LAN PORTS

Use the TL1

ed-eport

command to provision the LAN port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the LAN port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

PROVISION VCGS

Use the

ed-vcg

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

11-180 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-22: Establish video broadcast network on

UPSR

Figure 11-25 Provisioning Ethernet nodes for video broadcast ring

Head End Source

Node A

M 2 M 1

M 1

Node B

M 2

GbE

1

V1 V2

V3 V4

D

2

Example:

Tagging Mode = 802.1q

ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=802.1TAG;

Virtual Switch ID (e.g. 4095) ent-vrtsw:tid:fn-d-1:ctag::4095:eplst=d1-1,vcglst=d1-v1;

Cross-Connections: See related figure

VLAN ID (e.g. 2567) ent-vlan:tid:fn-d-1:ctag::2567,4095:eplst=d1-1,vcglst=d1-v1;

Node X

M 1 M 2

M 1

Node C

M 2

D

V1 V2 V3 V4

GbE

1 2

D

V1 V2 V3 V4

GbE

1 2

MA-DMX-382-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-181

Ethernet/Data network provisioning procedures Procedure 11-22: Establish video broadcast network on

UPSR

Figure 11-26 Provisioning cross-connections for video broadcast ring

Head End Source

Node A

M 2 M 1

GbE

1

V1 V2

V3 V4

D

2

Cross-Connection Wizard commands

Type of Connections: 1-Way Point-to-Point

Source AID: d1-v1-1+, Destination AID: m1-1-1+

Source AID: d1-v1-1+, Destination AID: m2-1-1+

Rate: STS1

Range: 21 (STS1s)

M 1

Node B

M 2

M 1

Node X

M 2

M 1

Node C

M 2

D

V1 V2 V3 V4

GbE

1

STS1 2-Way Point-to-Point, Through m1-1-(1-21),m2-1-(1-21)

Cross-connections at Nodes B and C

Cross-Connection Wizard commands

Type of Cross-connection: 1-Way Path Protected Drop from a UPSR Ring

Source AID: m1-1-1+, Destination AID: d1-v1-1+

Rate: STS1

Range: 21 (STS1s)

Type of Cross-connection: 2-Way Point-to-Point, Through

Source AID: m1-1-1+, Destination AID: m2-1-1+

Rate: STS1

Range: 21 (STS1s)

D

V1 V2 V3 V4

GbE

1

MA-DMX-383-2

.................................................................................................................................................................................................................................

11-182 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-22: Establish video broadcast network on

UPSR

Figure 11-27 Provisioning Ethernet nodes for control packet ring

Head End Source

Node A

M 2 M 1

V1

V4

V2

V3

GbE

1 2

D

M 1

Node B

M 2

Example:

Tagging Mode = 802.1q

Virtual Switch ID (e.g. 250) ent-vrtsw:tid:fn-d-1:ctag::250:eplst=d1-2,vcglst=d1-v3&d1-v4;

Spanning Tree Group ID (e.g. 1) ent-stgrp:tid::ctag::1,250:vcglst=d1-v3&d1v4

Cross-Connections: See related figure

VLAN ID (e.g. 4093)

Ent-vlan:tid:fn-d-1:ctag::4093,250:eplst=d1-2,vcglst=d1-v3&d1-v4;

Node X Node C

M 1 M 2

M 1 M 2

V1

V3

V2

V4

GbE 1 2

D

V1

V3

V2

V4

GbE 1 2

D

MA-DMX-384-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-183

Ethernet/Data network provisioning procedures Procedure 11-22: Establish video broadcast network on

UPSR

Figure 11-28 Provisioning cross-connections for control packet ring

Head End Source

Node A

M 2 M 1

M 1

Node B

M 2

V1

V4

V2

V3

GbE

1 2

D

Cross-Connection Wizard commands

Type of Cross-connection: Multipoint

Source AID: m1-1-22, Destination AID: d1-v3-1

Source AID: m2-1-22, Destination AID: d1-v4-1

Rate: STS1

Circuit ID: If required

Range: 3 (STS1s)

M 1

Node X

M 2

M 1

Node C

M 2

V1

V3

V2

V4

GbE

1

2

D

STS1 2-Way Point-to-Point, Through m1-1-(22-24),m2-1-(22-24)

Cross-Connection Wizard commands

Type of Cross-connection: Multipoint

Rate: STS1

Source AID: m1-1-22, Destination AID: d1-v3-1

Source AID: m2-1-22, Destination AID: d1-v4-1

Circuit ID: If required

Range: 3 (STS1s)

V1

V3

V2

V4

GbE 1 2

D

Cross-Connection Wizard commands

Type of Cross-connection: Multipoint

Rate: STS1

Source AID: m1-1-22, Destination AID: d1-v3-1

Source AID: m2-1-22, Destination AID: d1-v4-1

Circuit ID: If required

Range: 3 (STS1s)

MA-DMX-385-2

.................................................................................................................................................................................................................................

11-184 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-23: Establish video broadcast network on BLSR

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring a video broadcast network BLSR ring using Gigabit Ethernet circuit packs and 802.1q tagging mode.

Frames sent from the head end source node must be Multicast frames.

This procedure uses TL1 commands and specific WaveStar

®

illustrate the detailed provisioning parameters.

CIT menu selections to

This procedure consists of essentially two parts:

•

The first part verifies the network and sets the tagging mode and other parameters for the Ethernet packs being used.

•

The second part establishes the downstream video broadcast ring.

Refer to

Figure 11-29, “Provisioning Ethernet nodes for video broadcast ring”

(p. 11-193)

and

Figure 11-30, “Provisioning cross-connections for video broadcast ring” (p. 11-193)

for provisioning the video broadcast ring.

This procedure assumes that the BLSR SONET ring network configuration has already been established and no alarms are present.

Important! On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a

Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

•

The tagging mode (this procedure uses 802.1q), virtual switch IDs, and spanning tree groups to be created at each node.

•

The VLAN IDs being assigned to the video broadcast traffic.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-185

Ethernet/Data network provisioning procedures Procedure 11-23: Establish video broadcast network on

BLSR

Step

1

2

3

4

5

6

Use this procedure as an example for configuring a video broadcast network on a

BLSR ring.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes, if not already performed.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

View

→

Rings

→

Ring Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

This command may take several minutes to complete depending on the size of the network.

Result:

The View Ring Map window opens.

.................................................................................................................................................................................................

Expand ring details,

Select

the

2F BLSR

ring, then verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the terminating nodes, circuit packs, LAN ports, WAN (VCG) ports, virtual switch ID, cross-connections, spanning tree group ID, and VLAN IDs associated with the service being established.

.................................................................................................................................................................................................

Verify that the Ethernet circuit packs have been installed into the required slot 1 of the

Function Unit or Growth group (A, B, C, D, or G) at each NE providing Ethernet service.

Reference:

Procedure 4-13: “Install Gigabit Ethernet circuit packs” (p. 4-54)

.................................................................................................................................................................................................

CONFIGURE TAGGING MODE

At each NE providing this Ethernet service, determine the existing tagging mode for the Ethernet circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the System View menu, select the CP, then click

Select

. Note the VLAN Tagging Mode and other parameter values.

.................................................................................................................................................................................................................................

11-186 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-23: Establish video broadcast network on

BLSR

The VLAN Tagging Mode for the LNW66/67/68 circuit packs must be set to

TRANS

or

802.1TAG

. The VLAN Tagging Mode for the LNW70 circuit packs must be set to

SWITCHED

.

Important! When GbE circuit packs are installed in the shelf, the default

″

NOTAG

″ mode is assigned to the circuit pack.

.................................................................................................................................................................................................

7

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly but other parameters are not correct, the tagging mode is NOT set correctly,

Then...

Proceed to

Step 13 .

Proceed to

Step 10 .

Continue with

Step 8 .

8

9

.................................................................................................................................................................................................

If you are going to change the VLAN Tagging Mode that presently exists AND a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1

rtrv-vrtsw

command or select the

View

→

Data

→

Virtual Switch

command from the System View menu, select the GbE circuit pack being provisioned, then click

Select

. Note if a virtual switch ID has been assigned.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service.

If the service you are establishing in this procedure is a second service on an existing

GbE circuit pack with all LAN/WAN ports in the same virtual switch, then the existing virtual switch ID must be retained or the ports not in service must be removed from the existing virtual switch and added to a new virtual switch ID.

If a virtual switch is assigned, use the TL1

dlt-vrtsw

command or select the

Configuration

→

Data

→

Delete Virtual Switch

command from the System View

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-187

Ethernet/Data network provisioning procedures Procedure 11-23: Establish video broadcast network on

BLSR

10

menu, select the circuit pack being provisioned, then click Select. Highlight the

VRTSW ID being deleted, then click

Apply

.

Read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................

Provision circuit pack parameters. Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu, select the circuit pack being provisioned, then click

Select

.

11

12

.................................................................................................................................................................................................

Verify/Select the tagging mode (

802.1TAG

,

TRANS

[LNW66,67,68], or

SWITCHED

[LNW70]) in the VLAN Tagging Mode box.

Important! This procedure uses 802.1TAG mode to illustrate the provisioning.

.................................................................................................................................................................................................

Verify/Enter other parameter values (for example,

Burst Size

,

Credit Interval

[LNW66/67/68],

Ethernet Cross Connect Mode

and

Port Configuration

[LNW70]), as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

END OF STEPS TO PROVISION CIRCUIT PACKS

13

.................................................................................................................................................................................................

BEGIN VIDEO BROADCAST RING PROVISIONING

See

Figure 11-29, “Provisioning Ethernet nodes for video broadcast ring” (p. 11-193) .

Assign Virtual Switch ID:

•

For circuit packs not yet in service with no virtual switch assigned:

– Use the TL1

ent-vrtsw

command to create an assigned virtual switch ID or select

Configuration

→

Data

→

Create Virtual Switch

command from the CIT

System View menu.

For the LNW70 circuit pack, select the required

Virtual LAN Tagging Mode

(

802.1TAG

or

Transparent

).

•

For circuit packs not yet in service with a virtual switch assigned:

– Use the TL1

dlt-vrtsw

command to delete an assigned virtual switch ID or select

Configuration

→

Data

→

Delete Virtual Switch

command from the CIT

System View menu, if a different virtual switch ID is required.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the selected LAN/WAN ports.

.................................................................................................................................................................................................................................

11-188 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-23: Establish video broadcast network on

BLSR

14

15

16

17

For the LNW70 circuit pack, select the required

Virtual LAN Tagging Mode

(

802.1TAG

or

Transparent

).

•

For circuit packs in service, on only one set of ports, with a virtual switch assigned:

– Use the TL1

ed-vrtsw

command or select

Configuration

→

Data

→

Provision

Virtual Switch

command from the CIT System View menu to remove the required ports from a virtual switch.

– Use the TL1 command

ent-vrtsw

command or select

Configuration

→

Data

→

Create Virtual Switch

to create a new virtual switch ID containing the required LAN/WAN ports.

For the LNW70 circuit pack, select the required

Virtual LAN Tagging Mode

(

802.1TAG

or

Transparent

).

For the video broadcast ring in this example, note that we assigned a virtual switch ID of 4095 to LAN port d1-1 and VCG port d1-v1 at each participating node. See

Figure

11-29, “Provisioning Ethernet nodes for video broadcast ring” (p. 11-193) .

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary one-way (

1-Way Point-to-Point

) STS-1 cross-connections to be made at the head end node, each Ethernet terminating node, and any one-way pass through (

1-Way Point-to-Point, Through

) cross-connections to be made at any non terminating nodes in the network. See

Figure 11-30, “Provisioning cross-connections for video broadcast ring” (p. 11-193)

for an example.

.................................................................................................................................................................................................

One at a time at each node in the network, select

Configuration

→

Cross-

Connections

from the System View menu to start the Cross-Connection Wizard.

Select

Create a new cross-connection

, then click

Next

at the bottom of the screen.

Reference:

(p. 11-195) .

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

Use the Cross-Connection Wizard at each non terminating node to provision the one-way pass-through (

1-Way Point-to-Point, Through

) cross-connections.

.................................................................................................................................................................................................

Use the Cross-Connection Wizard at the head end source node to provision the

Ethernet one-way add (

1-Way Point-to-Point

) cross-connections.

.................................................................................................................................................................................................

18

Use the Cross-Connection Wizard at the remote terminating nodes to provision the one-way drop (

1-Way Point-to-Point

) and one-way pass-through (

1-Way

Point-to-Point, Through

) cross-connections.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-189

Ethernet/Data network provisioning procedures Procedure 11-23: Establish video broadcast network on

BLSR

19

20

21

22

23

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

to verify that the proper cross-connections have been made.

.................................................................................................................................................................................................

Important! For LNW70 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been

Enabled in the Input or Ouput Direction, as required.

If not already performed when cross-connections were made, use the TL1

ed-vcgtrib

command to enable tributaries, or from the System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made at each node in the ring, click on the

Alarm List

button on the System View window and verify no new alarms are present.

.................................................................................................................................................................................................

If new alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

VERIFY PORT MONITORING MODE

After all cross-connections have been made at each node in the ring, verify that the

WAN (VCG) Ports being used have gone in service (IS) at each terminating node.

From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Important! Note that the VCG port at the head end source node will not show in-service since it is not provisioned to receive packets.

.................................................................................................................................................................................................................................

11-190 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-23: Establish video broadcast network on

BLSR

24

25

26

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Click on the

Fault/Alarms

tab. Verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, click

Close

to exit then proceed to

Step 26 .

•

If the VCG Monitoring Mode is

NMON

(Not Monitored),

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

Fault/Alarms

tab, select

AUTO

for the

VCG Monitoring Mode

.

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 23 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

If proper cross-connections have been made, then indications are that either the far end or near end circuit pack at each end of the span has failed or must be reset. If

the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Select

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far end and near end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

ASSIGN VLAN IDs TO BROADCAST RING NETWORK

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-191

Ethernet/Data network provisioning procedures

27

28

Procedure 11-23: Establish video broadcast network on

BLSR

Use the TL1

ent-vlan

command to assign the VLAN ID for the associated LAN ports and VCG WAN ports. Or, select

Configuration

→

Data

→

Create VLAN

command from the CIT System View menu.

Reference:

For example, see

Figure 11-29, “Provisioning Ethernet nodes for video broadcast ring” (p. 11-193) .

In this example, we assign VLAN 2567 to the associated LAN (d1-1) and VCG

(d1-v1) ports at the head end and terminating nodes.

.................................................................................................................................................................................................

PROVISION LAN PORTS

Use the TL1

ed-eport

command to provision the LAN port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the LAN Port (for example, Port 1), then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

PROVISION VCGS

Use the

ed-vcg

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

11-192 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-23: Establish video broadcast network on

BLSR

Figure 11-29 Provisioning Ethernet nodes for video broadcast ring

Head End Source

Node A

M 2 M 1

GbE

V1 V2 V3 V4

D

1 2

M 1

Node B

M 2 M 1

Node X

M 2 M 1

Node C

M 2

D

V1 V2

GbE 1

V3 V4

2

D

V1 V2

GbE 1

V3 V4

2

Example provisioning Nodes A, B, and C:

Tagging Mode = 802.1q

ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=802.1TAG;

Configuration > Equipment

Virtual Switch ID (e.g. 4095) ent-vrtsw:tid:fn-d-1:ctag::4095:eplst=d1-1,vcglst=d1-v1;

Configuration > Data > Create Virtual Switch

Cross-Connections: See related figure

VLAN ID (e.g. 2567) ent-vlan:tid:fn-d-1:ctag::2567,4095:eplst=d1-1,vcglst=d1-v1;

Configuration > Data > Create VLAN

MA-DMX-397-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-193

Ethernet/Data network provisioning procedures Procedure 11-23: Establish video broadcast network on

BLSR

Figure 11-30 Provisioning cross-connections for video broadcast ring

Head End Source

Node A

M 2 M 1

M 1

Node B

M 2

V1 V2 V3 V4

D

GbE 1 2

Cross-Connection Wizard commands

Type of Cross-connection: 1-Way

Point-to-Point

Source AID: d1-v1-1+

Destination AID: m2-1-1+

Rate: STS1

Range: 21 (STS1s)

Circuit Identifier: If required

Destination NE Name: NodeC

Video Broadcast Ring

M 1

Node X

M 2 M 1

Node C

M 2

D

GbE

V1

1

V2 V3

2

V4

Cross-Connection Wizard commands

Type of Cross-connection: 1-Way

Point-to-Point

Source AID: m1-1-1+, Destination AID: d1-v1-1+

STS1 1-Way Point-to-Point, Through m1-1-(1-21),m2-1-(1-21)

Source NE Name: NodeA

Destination NE Name: NodeC

Rate: STS1

Range: 21 (STS1s)

VT Accessed: NO

Rate: STS1

Range: 21 (STS1s)

Circuit Identifier: If required

Source NE Name: NodeA

D

V1 V2

GbE 1

V3 V4

2

Cross-Connection Wizard commands

Type of Cross-connection: 1-Way

Point-to-Point

Source AID: m1-1-1+, Destination AID: d1-v1-1+

Rate: STS1

Range: 21 (STS1s)

Circuit Identifier: If required

Source NE Name: NodeA

Type of Cross-connection: 1-Way Point-to-Point, Through

Source AID: m1-1-1+, Destination AID: m2-1-1+

Rate: STS1

Range: 21 (STS1s)

Circuit Identifier: If required

Source NE Name: NodeA

Destination NE Name: NodeC

VT Accessed: NO

MA-DMX-398-2

.................................................................................................................................................................................................................................

11-194 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-24: Make cross-connections for Ethernet service

.................................................................................................................................................................................................................................

Overview

This procedure provides examples for making cross-connections for Ethernet service.

The examples use the WaveStar

®

CIT Cross-Connection Wizard commands in most examples to illustrate the provisioning. Cross-connection provisioning using TL1 commands requires the use of multiple 1way, 1 waypr, and 1way unswitched cross-connections to make the appropriate cross-connections. Refer to the Metropolis

®

DMX Access Multiplexer TL1 Message Details, 365-372-306, regarding cross-connections using the

ent-crs-rr

command.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Step

1

Use this procedure as an example for making cross-connections for Ethernet service.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

2

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Neighbor Map

command and note the NEs connected to Main 1 and Main 2.

Access each of the NEs identified and select the

Administration

→

OSI Neighbor

Map

command and note the NEs connected to Main 1 and Main 2.

Repeat the above until the backbone ring can be sketched.

For BLSR rings, you can select

View

→

Rings

→

Ring Map

from the System View menu, then select the 2F BLSR port protection group and click

Select

. Select

NVMRING in the Ring Map Source selection box. You may also Display Ring Map

Graph using this command.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map window opens if the

Administration

→

OSI

Neighbor Map

command was used.

A list of NEs and NE neighbors is displayed if the

View

→

Rings

→

Ring Map

command was used.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-195

Ethernet/Data network provisioning procedures Procedure 11-24: Make cross-connections for Ethernet service

3

4

5

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the cross-connections to be made at each node associated with the service to be established.

The following figures illustrate the cross-connection rate, type, and STSn AID addresses when using the WaveStar

®

CIT Cross-Connection Wizard in the following steps.

•

Figure 11-31, “UPSR Ring Add/Drop cross-connections” (p. 11-199)

illustrates a path protected OC-48 ring network with UPSR Ring Add/Drop STS1 cross-connections for Ethernet service.

•

Figure 11-32, “Multipoint mixed GbE and FE cross-connections on a UPSR”

(p. 11-199)

and

Figure 11-33, “Multipoint GbE cross-connections on a UPSR”

(p. 11-200)

illustrate OC-48 ring networks with Multipoint (1way unswitched)

STS1 cross-connections for Ethernet service.

•

Figure 11-34, “SONET protected 2F BLSR Add/Drop cross-connections on a BLSR without NUT” (p. 11-201)

illustrates a BLSR protected OC-48 ring network with

2F BLSR Add/Drop (1way) STS1 cross-connections for Ethernet service.

•

Figure 11-35, “Multipoint (1way unswitched) cross-connections on a BLSR with

NUT” (p. 11-202)

illustrates a BLSR protected OC-48 ring network with

Multipoint (1way unswitched) STS1 cross-connections using NUT for Ethernet service.

•

Figure 11-36, “Point-to-Point 10/100-PL private line service, STS1 cross-connect mode, One STS1” (p. 11-203)

illustrates a Point-to-Point 10/100-PL Private Line

Service, using STS1 Cross-Connect Mode with one STS1.

•

Figure 11-37, “Multipoint 10/100-PL private line service, STS1 cross-connect mode, External Customer Protected” (p. 11-204)

illustrates a 10/100-PL Private

Line Service, using STS1 Cross-Connect Mode, Multipoint (1way unswitched)

STS1 cross-connections, and protected by external customer equipment.

•

Figure 11-38, “Two point-to-point 10/100-T/F private line services, STS3c and

VT1.5” (p. 11-205)

illustrates two Point-to-Point 10/100-T/F Private Line Services using STS3c and VT1.5 cross-connections.

.................................................................................................................................................................................................

Starting at one of the nodes in the ring for the circuit being established, select

View

→

Cross-Connections

at each node in the ring to verify that the cross-connections specified on the work instructions may be made.

If cross-connections are already assigned or improperly assigned, refer trouble to the provisioning organization. Improperly assigned cross-connections may have to be deleted, or a different timeslot must be selected for the service being selected.

.................................................................................................................................................................................................................................

11-196 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-24: Make cross-connections for Ethernet service

6

7

8

9

.................................................................................................................................................................................................

One at a time, at each non terminating node, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection

Wizard. Use the Cross-Connection Wizard at all non terminating nodes in the network to provision the 2-Way Point-to-Point, Through STSn pass-through cross-connections for the Ethernet service being provided.

Reference:

“Cross-Connections for Ethernet ” (p. 11-207)

.................................................................................................................................................................................................

One at a time, at each terminating node, select

Configuration

→

Cross-Connections

from the

System View

menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard at all terminating nodes in the network to provision the STSn add/drop cross-connections.

Important! When multiple VCG tributaries are used to provide an Ethernet service, the VCG tributaries must be connected in the same order at both ends. See

Reference.

Reference:

“Cross-Connections for Ethernet ” (p. 11-207)

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connections have been made.

.................................................................................................................................................................................................

Important! For LNW63/70/74/78 circuit packs, each tributary cross-connected to a

VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been Enabled in the Input or Ouput Direction, as required.

Use the TL1

ed-vcgtrib

command to enable tributaries, or from the System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-197

Ethernet/Data network provisioning procedures

10

11

Procedure 11-24: Make cross-connections for Ethernet service

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

11-198 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-24: Make cross-connections for Ethernet service

Figure 11-31 UPSR Ring Add/Drop cross-connections

Node 1

DMX OC-48

Node 2

DMX OC-48

M 1 M 2 M 1 M 2

Ring 1 IN

OUT

IN

Ring 2

OUT

IN OUT

A

V2

1 2

V1

GbE

B C D G

A B

C

D

G

2-Way Point-to-Point, Through cross-connections

UPSR Ring Add/Drop cross-connections: m1-1-(1-21) to a1-v1-(1-21)

OUT

IN

IN

OUT

M 2

Node 5

DMX OC-48

M 1

OUT

IN

IN

OUT

M 2

Node 4

DMX OC-48

M 1

OUT

IN

A B C D G

2-Way Point-to-Point, Through cross-connections

A

V2 V1

GbE

1 2

B C D G

UPSR Ring Add/Drop cross-connections: m1-1-(1-21) to a1-v1-(1-21)

Example: Pass through cross-connections at Nodes 2,3,5, and 6: m1-1-(1-21),m2-1-(1-21)

NC-DMX-086-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-199

Ethernet/Data network provisioning procedures Procedure 11-24: Make cross-connections for Ethernet service

Figure 11-32 Multipoint mixed GbE and FE cross-connections on a UPSR

Node 1

DMX OC-48

Node 2

DMX OC-48

M 1 M 2 M 1 M 2

Ring 1 IN

OUT

IN OUT

Ring 2

OUT

IN OUT IN

A

V1 V2

GbE

1 2

B C D G

A

V1

1

V2

FE

24

B C D G

Multipoint (unswitched) cross-connections: m1-1-(1-21) to a1-v1-(1-21) m2-1-(1-21) to a1-v2-(1-21)

Multipoint (unswitched) cross-connections: m1-1-(1-21) to a1-v1-(1-21) m2-1-(1-21) to a1-v2-(1-21)

IN

OUT

Node 4

DMX OC-48

M 2 M 1

OUT

IN

IN

OUT

Node 3

DMX OC-48

M 2 M 1

OUT

IN

1

A

V2

FE

V1

24

B C D G

1

A

V2

FE

V1

24

B C D G

Multipoint (unswitched) cross-connections: m1-1-(1-21) to a1-v1-(1-21) m2-1-(1-21) to a1-v2-(1-21)

NC-DMX-083-2

.................................................................................................................................................................................................................................

11-200 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-24: Make cross-connections for Ethernet service

Figure 11-33 Multipoint GbE cross-connections on a UPSR

Node 1

DMX OC-48

Node 2

DMX OC-48

M 1 M 2 M 1 M 2

Ring 1 IN OUT IN

Ring 2

OUT

IN OUT

OUT

IN

A

V1 V2

GbE

1 2

B C D G

A B C D G

2-Way Point-to-Point, Through cross-connections m1-1-(1-21),m2-1-(1-21)

Multipoint (unswitched) cross-connections: m1-1-(1-21) to a1-v1-(1-21) m2-1-(1-21) to a1-v2-(1-21)

IN

OUT

M 2

Node 5

DMX OC-48

M 1

OUT

IN

IN

OUT

M 2

Node 4

DMX OC-48

M 1

OUT

IN

A

V2 V1

GbE

1 2

B C D G

A

V2 V1

GbE

1 2

B C D G

Multipoint (unswitched) cross-connections: m1-1-(1-21) to a1-v1-(1-21) m2-1-(1-21) to a1-v2-(1-21)

NC-DMX-084-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-201

Ethernet/Data network provisioning procedures Procedure 11-24: Make cross-connections for Ethernet service

Figure 11-34 SONET protected 2F BLSR Add/Drop cross-connections on a BLSR without NUT

Node A Node B

M 2 M 1 M 2 M 1

IN

V1

V3

1 2 GbE

Node A 2F BLSR Add/Drop Cross-connections: m1-1-(1-21), 1-v1-(1-21) Source NE=Node B m2-1-(1-21),d1-v3-(1-21) Source NE=Node D

OUT

V1

V3

1 2 GbE

Node B 2F BLSR Add/Drop Cross-connections: m1-1-(1-21), 1-v1-(1-21) Source NE=Node C m2-1-(1-21),d1-v3-(1-21) Source NE=Node A

M 1

Node D

M 2 M 1

Node X

M 2 M 1

Node C

M 2

V1 V1

V3 V3

1 2 GbE

2-Way Point-to-Point, Through Cross-connections m1-1-(1-21),m2-1-(1-21)

Source NE=Node D

Destination NE=Node C

Node D 2F BLSR Add/Drop Cross-connections: m1-1-(1-21), 1-v1-(1-21) Source NE=Node A m2-1-(1-21),d1-v3-(1-21) Source NE=Node C

1 2

GbE

Node C 2F BLSR Add/Drop Cross-connections: m1-1-(1-21), 1-v1-(1-21) Source NE=Node D m2-1-(1-21),d1-v3-(1-21) Source NE=Node B

NC-DMX-236-2

.................................................................................................................................................................................................................................

11-202 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-24: Make cross-connections for Ethernet service

Figure 11-35 Multipoint (1way unswitched) cross-connections on a BLSR with

NUT

Node A Node B

M 2 M 1 M 2 M 1

OUT IN

IN

V2 V1

1 2 GbE

Multipoint (unswitched) cross-connections: m1-1-(1-21) to d1-v1-(1-21) m2-1-(1-21) to d1-v2-(1-21)

OUT

V2 V1

1 2 GbE

Multipoint (unswitched) cross-connections: m1-1-(1-21) to d1-v1-(1-21) m2-1-(1-21) to d1-v2-(1-21)

Packet Ring on

BLSR

using Multipoint (unswitched) cross-connections

M 1

Node D

M

2 M 1

Node X

M 2

M 1

Node C

M 2

V2 V1 V2 V1

1 2 GbE

2-Way Point-to-Point, Through Cross-connections m1-1-(1-21),m2-1-(1-21)

Source NE=Node D

Destination NE=Node C

Multipoint (unswitched) cross-connections: m1-1-(1-21) to d1-v1-(1-21) m2-1-(1-21) to d1-v2-(1-21)

1 2 GbE

Multipoint (unswitched) cross-connections: m1-1-(1-21) to d1-v1-(1-21) m2-1-(1-21) to d1-v2-(1-21)

NC-DMX-283-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-203

Ethernet/Data network provisioning procedures Procedure 11-24: Make cross-connections for Ethernet service

Figure 11-36 Point-to-Point 10/100-PL private line service, STS1 cross-connect mode, One STS1

Node A Node B

M 1 M 2 M 1 M 2

OUT

IN

IN

OUT

V1

V13

D

V24

1 13

Cross-Connect Mode = STS1

UPSR Ring Add/Drop cross-connections

Range: m1-1-(1-48),d1-v13-(1-2)

Example: m1-1-1,d1-v13-1

2-Way Point-to-Point, Through Cross-connections

Range:m1-1-(1-48),m2-1-(1-48)

Example:m1-1-1,m2-1-1

Example of 10/100-PL 2-Way UPSR Ring Add/Drop cross-connections using one STS1 for point-to-point private line service

M 2

Node D

M 1

OUT

IN

V24

...

V13 V1

D

13 1

Cross-Connect Mode = STS1

UPSR Ring Add/Drop cross-connections

Range: m1-1-(1-48),d1-v13-(1-2)

Example: m1-1-1,d1-v13-1

IN

OUT

M 2

Node C

M 1

2-Way Point-to-Point, Through Cross-connections

Range:m1-1-(1-48),m2-1-(1-48)

Example:m1-1-1,m2-1-1

MA-DMX-325-2

.................................................................................................................................................................................................................................

11-204 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-24: Make cross-connections for Ethernet service

Figure 11-37 Multipoint 10/100-PL private line service, STS1 cross-connect mode, External Customer Protected

Node A Node B

M 1 M 2 M 1 M 2

OUT IN

IN

OUT

V1 V2 V13

1 13

Customer Equipment

D

V24

Cross-Connect Mode = STS1

Multipoint (unswitched) cross-connections

Range: m1-1-(1-48),d1-v1-(1-2)

Example: m1-1-(1-2),d1-v1-(1-2)

2-Way Point-to-Point, Through Cross-connections

Range: m1-1-(1-48),m2-1-(1-48)

Example: m1-1-(1-2),m2-1-(1-2)

Example of 10/100-PL Multipoint (unswitched) cross-connections to an OC-48 UPSR

M 2

Node D

M 1 M 2

Node C

M 1

OUT

IN

IN

OUT

V24 V13 V1

13 1

Customer Equipment

Cross-Connect Mode = STS1

Multipoint (unswitched) cross-connections

Range: m1-1-(1-48),d1-v1-(1-2)

Example: m1-1-(1-2),d1-v1-(1-2)

V24 V13 V1

13 1

Customer Equipment

Multipoint (unswitched) cross-connections

Range: m1-1-(1-48),d1-v1-(1-2)

Example: m1-1-(1-2),d1-v1-(1-2)

MA-DMX-328-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-205

Ethernet/Data network provisioning procedures Procedure 11-24: Make cross-connections for Ethernet service

Figure 11-38 Two point-to-point 10/100-T/F private line services, STS3c and

VT1.5

Node A

M 1 M 2 Node B

OUT

IN

M 1 M 2

IN

V1

V13

1 13

VT Virtual Concatenation = 12

D

V24

UPSR Ring Add/Drop cross-connections

STS3c : m1-1-13,d1-v13-1

VT1.5: m1-1-{1-n}-{1-7}-{1-4},d1-v1-vt{1-63}

OUT

2-Way Point-to-Point, Through cross-connections

STS3c: m1-1-13,m2-1-13

VT1.5: m1-1-{1-n}-{1-7}-{1-4},m2-1-{1-n}-{1-7}-{1-4}

Example: 10/100-T/F UPSR Ring Add/Drop cross-connections, two point-to-point private line services, STS3c and VT1.5

M 2

Node D

M 1

OUT

IN

V24 ...

V13 V1

D

13

UPSR Ring Add/Drop cross-connections

STS3c: m1-1-13,d1-v13-1

2-Way Point-to-Point, Through cross-connections

VT1.5: m1-1-{1-n}-{1-7}-{1-4},m2-1-{1-n}-{1-7}-{1-4}

M 2

Node C

M 1

IN

OUT

V24...

V13

V1

D

1

VT Virtual Concatenation = 12

UPSR Ring Add/Drop cross-connections

VT1.5: m1-1-{1-n}-{1-7}-{1-4},d1-v1-vt{1-63}

2-Way Point-to-Point, Through cross-connections

STS3c: m1-1-13,m2-1-13

MA-DMX-412-2

.................................................................................................................................................................................................................................

11-206 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Cross-Connections for Ethernet

.................................................................................................................................................................................................................................

Cross-Connections for Ethernet

Cross-connections supporting Ethernet services vary according to the type of circuit pack being used:

•

LNW63 GBE-PL Ethernet circuit packs support STS1, STS3c, or STS12c cross-connections.

•

LNW66/67/68 Ethernet circuit packs support STS1 cross-connections.

•

LNW70 100/1G-FXS Ethernet circuit packs support STS1, STS3c, or STS12c cross-connections.

•

LNW71 10/100-PL Ethernet circuit packs support STS1 and STS3c cross-connections.

•

LNW74 10/100-T/F Ethernet circuit packs support STS1, STS3c, and VT1.5

cross-connections.

•

LNW78 100/1G-FSR Ethernet circuit packs support STS1, STS3c, or STS12c cross-connections.

LNW63 Ethernet circuit packs:

For the LNW63 Ethernet circuit packs, each Ethernet virtual concatenation group

(VCG) may have from 1 to 21 STS1s cross-connected to support the bandwidth assignment up to a maximum of 48 STS1s for the circuit pack. The maximum capacity may be divided among the 4 VCGs.

Cross-connect rates:

•

STS1 or STS1 VCAT. Maximum of 21 STS-1s for each VCG.

•

STS3c or STS3c VCAT. Maximum of 7 STS3c with 19 (1,4,7,10...) as the largest number STS1.

•

STS12c. Supports 1 STS-12c.

LNW66/67/68 Ethernet circuit packs:

For the LNW66/67/68 Ethernet circuit packs, each Ethernet virtual concatenation group

(VCG) may have from 1 to 21 STS1s cross-connected to support the bandwidth assignment.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-207

Ethernet/Data network provisioning procedures Cross-Connections for Ethernet

LNW70 Ethernet circuit packs:

•

STS1 Ethernet Cross Connect Mode – LNW70 Ethernet circuit packs in STS1 cross connect mode support up to 48 STS1s to individual VCGs with the following restrictions:

– VCG 1-2 — Supports up to 48 STS-1s.

– VCG 3-28 — Supports up to 32 STS-1s.

– VCG 29-32— Supports up to 10 STS-1s.

•

STS12c Ethernet Cross Connect Mode – LNW70 Ethernet circuit packs in STS12c cross connect mode support one STS12c or virtual concatenation (VCAT) of up to

16 STS3c cross-connections with restrictions. The STS1 numbers used for STS3c cross-connects may be 1, 4, 7, 10, 13, 16, 19, 22, 25, 28, 31, 34, 37, 40, 43, 46.

Individual VCGs have the following restrictions:

– VCG 1-2 — Supports VCAT of up to 16 STS-3Cs or one STS-12c. The highest number of STS-3C that can be used in the order of 1, 4, 7, ... is 46.

– VCG 3-28 — Supports VCAT of up to 10 STS-3Cs or one STS-12c. The highest number of STS-3C that can be used in the order of 1, 4, 7, ... is 28.

– VCG 29-32 — Supports VCAT of up to 3 STS-3Cs. The highest number of

STS-3C that can be used in the order of 1, 4, 7, ... is 7.

VCG Usage:

•

NOTAG VLAN Tagging Mode – When the LNW70 is used in Private Line

(NOTAG) mode, there are 8 VCG’s and there is a fixed mapping between 8

Ethernet ports and VCG ports: LAN-1 maps to VCG-1, etc.

•

SWITCHED VLAN Tagging Mode – When the LNW70 is used in SWITCHED mode, there are 32 VCG’s. Cross-connections are established in the same way as in the NOTAG mode but there is no fixed mapping between LAN ports and VCGs.

LNW71 10/100-PL Ethernet circuit packs:

•

STS1 Ethernet Cross Connect Mode – For the LNW71 10/100-PL circuit pack, one

or two STS1 cross-connections may be made to each of the 24 VCGs in STS1 mode. In STS1 mode, the first STS1 cross-connection made to a VCG should be made to the first (1) STS1 tributary of the VCG.

•

STS3c Ethernet Cross Connect Mode – In STS3c mode, at most one STS-3c or one

STS-1 cross-connection may be made to each of the first 16 VCGs (1-16), (VCGs

17-24 are not used). In STS3c mode, if an STS1 cross-connection is made to a

VCG, it must be made to the first (1) STS1 tributary of the VCG.

.................................................................................................................................................................................................................................

11-208 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Cross-Connections for Ethernet

LNW74 10/100-T/F Ethernet circuit packs:

•

VT Virtual Concatenation = 0 – LNW74 10/100-T/F Ethernet circuit packs with VT

Virtual Concatenation set to 0 does not allow VT mapping and all 48 STS-1s are available for STS-1 VCAT and STS-3c. One to three STS-1s or one STS-3c may be assigned to each of the 24 VCGs up to the total capacity of 48 STS1s for the circuit pack.

•

VT Virtual Concatenation = 12 – LNW74 10/100-T/F Ethernet circuit packs with

VT Virtual Concatenation set to 12 allows VT mapping with 12 STS-1s reserved for VT mapping. The remaining 36 STS-1s are then available for STS-1 VCAT or

STS-3c. Up to 336 VT1.5s may be used with up to 63 assigned to any VCG.

Ports may be provisioned until all the available 48 STS-1 equivalent bandwidth

(including VT1.5s) is used.

LNW78 100/1G-FSR Ethernet circuit packs:

•

STS1 Ethernet Cross Connect Mode – Supports virtual concatenation of STS1s up to a maximum of 24 STS1s cross-connected to each VCG. Three or more STS1s must be cross-connected.

•

STS12c Ethernet Cross Connect Mode – Supports virtual concatenation of up to 8

STS3c or one STS12c to each VCG.

Important rules for cross-connections

Ethernet cross-connections tie together VCG tributaries in two or more Ethernet circuit packs through SONET STS-1 tributaries. For example, a cross-connection of m1-1-1 to d1-v1-1 at Node A, and a cross-connection of m1-1-1 to g1-v1-5 at Node B ties d1-v1-1 (VCG1, tributary 1) at Node A to g1-v1-5 (VCG1, tributary 5) at Node B.

When more than one VCG STS1 tributary is being cross-connected to provide an

Ethernet service, the order in which the VCG tributaries are connected must be the same at both ends of a span. If the order is not correct, transmission will not be established. See examples below.

For multiple VCG STS1 tributary cross-connections, it is strongly suggested that VCG tributary cross-connections begin at VCG STS1 tributary #1, then VCG tributary #2, and so forth to the last cross-connection. It is also suggested that the VCG tributary cross-connections be made in an increasing (ascending) order at each end of the span as shown in the example that works.

This example works:

NODE A d1-v1-5 <-> m1-1-1 d1-v1-6 <-> m1-1-2

NODE B m1-1-1 <-> g1-v1-1 m1-1-2 <-> g1-v1-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-209

Ethernet/Data network provisioning procedures Cross-Connections for Ethernet d1-v1-7 <-> m1-1-3

This example does not work:

NODE A d1-v1-5 <-> m1-1-1 d1-v1-6 <-> m1-1-2 d1-v1-7 <-> m1-1-3 m1-1-3 <-> g1-v1-3

NODE B m1-1-1 <-> g1-v1-3 m1-1-2 <-> g1-v1-2 m1-1-3 <-> g1-v1-1

For the LNW66/67/68 Ethernet circuit packs, a VCG alarm (indicating a tributary mismatch) would be raised in the case of the above example that does not work and transmission would not be established.

For the LNW71 10/100-PL circuit pack, transmission would not be established, but no alarm is raised to indicate a tributary mismatch.

Cross connect types

This section uses WaveStar

®

CIT Cross-Connection Wizard commands to describe some considerations when using path protected and unswitched cross-connections. Path protected cross-connections in this section include

UPSR Ring Add/Drop

,

2F BLSR

Add/Drop

, and

2-Way Point-to-Point, Through

. Unswitched cross-connections are

Multipoint

.

Cross-connection provisioning using TL1 commands requires the use of multiple 1way,

1 waypr, and 1way unswitched cross-connections to make the appropriate cross-connections.

Multipoint

equivalent TL1 cross-connections are provisioned using four 1way unswitched cross-connections.

UPSR Ring Add/Drop

equivalent TL1 cross-connections are provisioned using two 1way and one 1waypr cross-connections.

2F BLSR Add/Drop

and

2-Way Point-to-Point, Through

equivalent TL1 cross-connections are provisioned using two 1way cross-connections.

Multipoint (unswitched) Cross-connections for LNW63/70 circuit packs

For the LNW63 and LNW70 in NOTAG mode there is a fixed mapping between the

Ethernet ports and VCG ports. Any VCG can be connected to either main slot. For the

LNW63/70, there is no pairing of the VCGs when using multipoint cross-connections.

For the LNW70 in Switched mode, there is no fixed mapping between VCGs and LAN ports.

Multipoint (unswitched) Cross-connections for LNW66/67/68 circuit packs

Multipoint cross-connections are made by specifying an odd VCG number. The paired

(next higher number) VCG is then automatically cross-connected. For example, when a

.................................................................................................................................................................................................................................

11-210 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Cross-Connections for Ethernet

Multipoint connection is made to an STS trib in VCG1 (e.g. a1-v1-1), a connection is automatically made internally to the corresponding STS trib in VCG2 (e.g. a1-v2-1).

VCG v2 and associated trib then become unavailable for other connections. For the

LNW67/68 circuit packs, when a connection is made to an STS trib in VCG3, a connection is automatically made internally to the corresponding STS trib in VCG4.

VCG v4 and associated trib then become unavailable for other connections.

The timeslot on the odd VCG is connected to Main-1 (West in case of a ring) and the same timeslot on the next higher (even) VCG is connected to Main-2 (East in case of a ring).

Multipoint (unswitched) Cross-connections for LNW71 circuit packs

In STS1 cross-connect mode, multipoint cross-connections may be made to all 24

VCGs. When a multipoint cross-connection is made to an STS trib in VCG

″ n

″

, where n=1-12, (for example, v3), a connection is automatically made internally to the corresponding STS trib in VCG

″ n+12

″

(for example, v15).

In STS3c cross-connect mode, multipoint cross-connections may be made to the first

16 VCGs (1-16). When a multipoint cross-connection is made to an STS trib in VCG

″ n

″

, where n=1-8, (for example, v2), a connection is automatically made internally to the corresponding STS trib in VCG

″ n+8

″

(for example, v10).

Multipoint (unswitched) Cross-connections for LNW74 circuit packs

The LNW74 circuit pack does not support multipoint cross-connections.

Multipoint (unswitched) Cross-connections for LNW78 circuit packs

Any VCG can be connected to either main slot. There is a fixed mapping between the

RPR IF and the VCG pairs. The RPR IF is addressed using the odd-numbered VCG of the pair. In this release, there is only one RPR IF, VCG v1.

Path protected (add/drop) cross-connections for LNW66/67/68 circuit packs

When a path protected connection is made to an STS trib in VCG1, then VCG2 is unused and unavailable for any connection. For LNW67/68 circuit packs, when a path protected connection is made to an STS trib in VCG3, then VCG4 is unused and unavailable for any connection.

Path protected (add/drop) Cross-connections for LNW63/70 circuit packs

There is no pairing of SONET-protected cross-connections, any available VCG can be used.

Path protected (add/drop) Cross-connections for LNW71 circuit packs

Path protected cross-connections may be made to all 24 VCGs in STS1 mode. In

STS3c mode, cross-connections may be made to all of the first 16 (1-16) VCGs.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-211

Ethernet/Data network provisioning procedures Cross-Connections for Ethernet

Path protected (add/drop) cross-connections for LNW74 circuit packs

Cross-connections may be made to all 24 VCGs. One to three STS-1s or one STS-3c may be assigned to each of the 24 VCGs up to the total capacity of 48 STS1s for the circuit pack. When VT Virtual Concatenation is set to 12, up to 336 VT1.5s may be used with up to 63 assigned to any VCG.

Path protected (add/drop) Cross-connections for LNW78 circuit packs

The LNW78 circuit pack does not support path protected cross-connections.

Path protected (add/drop, pass-through) cross-connections

Path protected cross-connections using the WaveStar

®

CIT Cross-Connection Wizard request a two-way add/drop or pass-through cross-connection be established between the source and destination in a ring.

Figure 11-39, “2-Way Point-to-Point, Through cross-connection” (p. 11-212)

illustrates a pass-through cross-connection from one side of the ring to the other.

Figure 11-39 2-Way Point-to-Point, Through cross-connection

2-Way Point-to-Point, Through

Main 1 (m1) Main 2 (m2)

NC-DMX-085-2

Figure 11-40, “UPSR Ring Add/Drop cross-connection” (p. 11-212)

illustrates an

Ethernet 2waypr add/drop cross-connection on a UPSR ring.

Figure 11-40 UPSR Ring Add/Drop cross-connection

UPSR Ring Add/Drop

Main 1 (m1) Main 2 (m2)

VCG-n

A, B, C, D, G -1

A, B, C, D, G -2

EMPTY

NC-DMX-077-2

.................................................................................................................................................................................................................................

11-212 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Cross-Connections for Ethernet

Figure 11-41, “FE to GbE 2-Way Hairpin cross-connection” (p. 11-213)

illustrates a

2waypr hairpin cross-connection between a Fast Ethernet circuit pack and a Gigabit

Ethernet circuit pack.

Figure 11-41 FE to GbE 2-Way Hairpin cross-connection

2-Way Hairpin

Main 1 (m1)

Main 2 (m2)

VCG-n

FE (v1)

GbE (v1,v3)

VCG-n

FE (v1)

GbE (v1,v3)

NC-DMX-287-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-213

Ethernet/Data network provisioning procedures Cross-Connections for Ethernet

Figure 11-42, “2F BLSR Add/Drop cross-connection” (p. 11-214)

illustrates an

Ethernet 2-way add/drop cross-connection on a BLSR ring.

Figure 11-42 2F BLSR Add/Drop cross-connection

M 1(2)

M 2(1)

A, B, C, D, G-1

VCGn

Solid lines depict normal working tributaries

Dashed lines depict protection tributaries when BLSR protection is active nc-dmx-235

Multipoint (unswitched)

A multipoint (unswitched) cross-connection is established between the source and destination in a non-path switched ring configuration. The

Multipoint

cross-connect type can only be selected if an Ethernet interface is being addressed. When an Ethernet interface is multipoint cross-connected, the signal locking mechanism is provided.

.................................................................................................................................................................................................................................

11-214 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Cross-Connections for Ethernet

Figure 11-43, “Multipoint (unswitched) cross-connection” (p. 11-215)

illustrates a multipoint cross-connection.

Figure 11-43 Multipoint (unswitched) cross-connection

Main 1 (m1)

Multipoint

Main 2 (m2)

LNW66/67/68

LNW71(STS1)

LNW71(STS3c)

Examples:

VCGn

VCGn

VCGn

GbE

FE

V1(V3)

V1

PL (STS1) V1

PL (STS3c) V1

A, B, C, D, G -1

VCGn+1

VCGn+12

VCGn+8

V2(V4)

V2

V13

V9

A, B, C, D, G -2

EMPTY

MA-DMX-327-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-215

Ethernet/Data network provisioning procedures

Procedure 11-25: Create preferred spanning tree configuration

.................................................................................................................................................................................................................................

Overview

This procedure provides an example to determine (and create) your preferred spanning tree configuration.

Important! Networks running 802.1d STP (Release 1.1) support a maximum of up to nine nodes participating in a spanning tree. Networks with more than nine nodes will not reconfigure properly. Spanning tree default parameters support a network of up to nine nodes.

Networks running 802.1w rapid spanning tree protocol (Release 2 or later) support more than nine nodes participating in a spanning tree. To support more than nine nodes in the spanning tree, the maximum age timer must be increased. Note that spanning tree restoration time increases as the number of nodes increase.

If the network consists of more than nine (9) nodes which are participating in the spanning tree configuration, use the following formula to determine the proper setting for the spanning tree maximum age timer (

stmaxage

): 2 x (N + 1), where N equals the number of nodes.

For example, if the network consists of 16 nodes, then the

stmaxage

timer should be set to 34 seconds: 2 x (16 + 1) = 34.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Before you begin this procedure, you should:

•

Refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter.

•

Know your network configuration

•

Know which nodes in the network are participating in the spanning tree configuration for the service being configured

•

Have a knowledge of Ethernet services and spanning tree configurations

Step

1

Use the following procedure as an example for determining the preferred spanning tree configuration.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to a terminating Metropolis

®

DMX shelf.

.................................................................................................................................................................................................................................

11-216 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-25: Create preferred spanning tree configuration

2

3

4

5

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu at each node, select

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions and the network map, determine the nodes in the ring at which Ethernet services are provided and are part of the same spanning tree group.

Important! When determining if the ring consists of an odd or even number of nodes, count only the nodes at which Ethernet service is being provided in the same spanning tree configuration. If a node in the ring has only SONET pass through cross-connections for Ethernet services, that node is not counted in determining an odd or even configuration. The figures in this procedure assume all nodes are providing Ethernet service.

.................................................................................................................................................................................................

Determine if the ring consists of an odd or even number of nodes.

If...

there are an ODD number of nodes in the ring, there are an EVEN number of nodes in the ring,

Then...

Continue with

Step 6 .

Proceed to

Step 12 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-217

Ethernet/Data network provisioning procedures Procedure 11-25: Create preferred spanning tree configuration

6

.................................................................................................................................................................................................

Refer to

Figure 11-44, “Spanning tree odd node example” (p. 11-218)

for rings with an odd number of nodes.

Figure 11-44 Spanning tree odd node example

Node 1 Node 2

M 1 M 2

M 1

Ring 1

Ring 2

M 2

In this example, Node 5 is selected as the preferred root node because it is opposite the normally blocked span. We set the spanning tree root priority to zero (0) at Node 5.

M 2

Node 4

M 1 M 2

Node 3

M 1

Example: Span chosen to be normally blocked nc-dmx-101

7

8

.................................................................................................................................................................................................

Select the span that should be blocked under nominal conditions. The span should be selected based on traffic patterns to get the most efficient use of capacity on both sides of the ring during nominal conditions.

The span between Nodes 2 and 3 was selected in this example.

.................................................................................................................................................................................................

Determine the preferred root node. The preferred root node in an odd-number node ring is the node on the ring opposite the span which should be normally blocked.

In the odd node configuration figure above, Node 5 is the preferred root node.

.................................................................................................................................................................................................................................

11-218 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-25: Create preferred spanning tree configuration

9

10

11

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to the preferred root node.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Data

→

Create Spanning Tree

Group

or use the

ent-stgrp

TL1 command.

Result:

The Create Spanning Tree Group window opens displaying the parameters for the spanning tree group.

.................................................................................................................................................................................................

Set the spanning tree Root Priority parameter (strp) to zero (0) at the preferred root node (Node 5 in this example).

At ALL other Ethernet nodes in the ring, set the spanning tree root priority to the default value of 32768.

END OF STEPS FOR ODD NODE EXAMPLE

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-219

Ethernet/Data network provisioning procedures Procedure 11-25: Create preferred spanning tree configuration

12

.................................................................................................................................................................................................

Refer to

Figure 11-45, “Spanning tree even node example” (p. 11-220)

for rings with an EVEN number of nodes:

Figure 11-45 Spanning tree even node example

Node 1 Node 2

M 1 M 2

M 1 M 2

Ring 1

Ring 2

(2) In this example, either Node 1 or

Node 6 may be selected as the preferred root node. We choose Node 1, and set the spanning tree root priority to zero (0).

(3) Because we chose Node 1 as the preferred root node, the spanning tree root priority at Node 5 is set to 10 in this example.

M 2

Node 5

M 1 M 2

Node 4

M 1

(1) Span chosen to be normally blocked nc-dmx-100

13

.................................................................................................................................................................................................

Select the span that should be blocked under nominal conditions. The span should be selected based on traffic patterns to get the most efficient use of capacity on both sides of the ring during nominal conditions.

The span between Nodes 3 and 4 was selected in this example.

.................................................................................................................................................................................................

14

Determine the preferred root node. The preferred root node in an even-number node ring may be either of the two nodes at the opposite ends of the span that is opposite to the span which is normally blocked.

In the even node configuration figure above, either Node 1 or Node 6 may be selected as the preferred root node. Note that there are 2 spans between Node 3 and Node 1,

.................................................................................................................................................................................................................................

11-220 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-25: Create preferred spanning tree configuration

15

16

and two spans between Node 4 and Node 6. In this example, we choose Node 1 to be the preferred root node.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to the preferred root node.

.................................................................................................................................................................................................

From the

System View

menu, select

Configuration

→

Data

→

Create Spanning Tree

Group

or use the

ent-stgrp

TL1 command.

Result:

The Create Spanning Tree Group window opens displaying the parameters for the spanning tree group.

17

18

19

20

.................................................................................................................................................................................................

Set the spanning tree Root Priority parameter (strp) to zero (0) at the preferred root node (Node 1 in this example).

.................................................................................................................................................................................................

Determine the node opposite the selected preferred root node.

In this example, Node 4 is the node opposite Node 1, the preferred root node. Note that there are two nodes on either side of the ring between Node 1 and Node 4.

.................................................................................................................................................................................................

At the node (in this example, Node 4) opposite the selected preferred root node, follow the span that is NOT normally blocked to the next node in that direction around the ring.

In this example, the span to the right of Node 4 is normally blocked; therefore, you would follow the span to the left of Node 4 to Node 5.

.................................................................................................................................................................................................

At the node determined in the previous step (in this example, Node 5), use the

WaveStar

®

CIT to log in to the node.

21

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Data

→

Create Spanning Tree

Group

or use the

ent-stgrp

TL1 command.

Result:

The Create Spanning Tree Group window opens displaying the parameters for the spanning tree group.

.................................................................................................................................................................................................

22

Set the spanning tree Root Priority parameter (strp) to 10 (or any value from 1 to

32767).

Important! The spanning tree root priority for ALL other Ethernet nodes in the ring should be set to the default value of 32768.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-221

Ethernet/Data network provisioning procedures Procedure 11-25: Create preferred spanning tree configuration

.......................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

11-222 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-26: Change an existing spanning tree configuration

.................................................................................................................................................................................................................................

Overview

This procedure provides an example of how to change an existing spanning tree configuration by changing the spanning tree path cost at one of the nodes.

This procedure might be used if traffic patterns change and dictate that a reconfiguration would provide more efficient service.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Safety precautions

To assure both personal safety and the proper functioning of the Metropolis

®

DMX

Access Multiplexer, it is imperative to review and understand these warnings and precautions prior to performing this procedure.

CAUTION

Service disruption hazard

A minimal amount of service interruption may be encountered when performing this procedure.

Be sure to follow your work instructions in performing this procedure.

Before you begin

Before you begin this procedure, you should:

•

Refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter.

•

Know your network configuration.

•

Know which nodes in the network are participating in the spanning tree configuration for the service being configured.

•

Have a knowledge of Ethernet services and spanning tree configurations.

•

Have detailed work instructions for performing this procedure.

•

Know which span in the spanning tree configuration is normally blocked and which span you are going to reconfigure as blocked.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-223

Ethernet/Data network provisioning procedures Procedure 11-26: Change an existing spanning tree configuration

•

Know which node is the root node (root bridge) in the configuration.

•

Know the spanning tree group ID (stgrpid) of the spanning tree group being reconfigured.

Step

1

2

3

4

5

Use this procedure as an example to reconfigure an existing spanning tree configuration.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to a terminating Metropolis

®

DMX shelf.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions and the network map, determine the nodes in the ring at which Ethernet services are provided and are part of the same spanning tree group.

Figure 11-46, “Existing spanning tree configuration” (p. 11-226)

for an example.

.................................................................................................................................................................................................

Use the

rtrv-stgrp

command or the

View

→

Data

→

Spanning Tree Group

command from the System View menu at each node to determine which node is the root node (root bridge), the spanning tree root path cost (

strtpcost

), the VCG spanning tree port role (

stprole

), and the VCG spanning tree path cost (

stpcost

) for each VCG AID in the spanning tree group. Make a note of these parameter values at each node.

.................................................................................................................................................................................................................................

11-224 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-26: Change an existing spanning tree configuration

6

7

8

Reference:

See

Figure 11-46, “Existing spanning tree configuration” (p. 11-226) .

Assuming VCGs v1 and v2 are used at each node, if you logged into Node 5, the root bridge, you should see a root path cost of zero (0), and each VCG port would have a port role of Designated.

At Nodes 1 and 2, you should see Port Roles for VCG v1 at both nodes as being

root port, indicating traffic toward the root bridge. At Nodes 3 and 4, you should see Port Roles for VCG v2 at both nodes as being root port, indicating traffic toward the root bridge.

.................................................................................................................................................................................................

PRINCIPLES OF SPANNING TREE AND PORT COST

Refer to

Figure 11-46, “Existing spanning tree configuration” (p. 11-226)

and read the following to understand how spanning tree blocks a span:

To have spanning tree block a span, the spanning tree root path cost is set equally at the two bridges (nodes) at each end of the blocked span. The spanning tree root path cost (

strtpcost

) at a node (bridge) is the sum of the path costs of the root port VCGs that connect the node to the root node.

Assume that in the original configuration the spanning tree path cost (

stpcost

) for each VCG is set to the default of 10 at each node. Node 2 is connected to root

Node 5 through VCG v1 at Node 2 and VCG v1 at Node 1. Therefore, the root path cost of Node 2 is 20, which is the sum of the path costs of Node 2 VCG v1 and Node 1 VCG v1 (10 + 10 = 20).

Node 3 is connected to root Node 5 through VCG v2 at Node 3 and VCG v2 at

Node 4. Therefore, the root path cost of Node 3 is also 20, which is the sum of the path costs of Node 3 VCG v2 and Node 4 VCG v2 (10 + 10 = 20).

.................................................................................................................................................................................................

Assume that your traffic studies indicate a more efficient service would be obtained by blocking the span between Node 3 and Node 4 instead of the presently blocked span between Node 2 and Node 3.

.................................................................................................................................................................................................

HOW TO CHANGE PATH COST TO RECONFIGURE SPANNING TREE

To change the spanning tree configuration to block the span between Nodes 3 and 4, we need to have the root path cost of Node 3 and Node 4 set equally.

We can increase the spanning tree path cost (

stpcost

) at the root port (VCG v2) on

Node 4. To change the path cost, use either the

ed-vcg

command or select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, select the VCG, then click on the Spanning Tree tab. Change the value in the

Spanning Tree Path Cost

box, then click

Apply

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-225

Ethernet/Data network provisioning procedures Procedure 11-26: Change an existing spanning tree configuration

Reference:

Refer to

Figure 11-47, “New spanning tree configuration” (p. 11-226) .

If the span between Nodes 3 and 4 is going to be blocked, then Node 3 will be connected to root Node 5 through Node 3 VCG v1, Node 2 VCG v1, and Node 1

VCG v1. The root path cost at Node 3 will then be 30, the sum of the path costs of root port VCG v1 at Nodes 3, 2, and 1 (10 + 10 +10 = 30).

We need to ensure the root path cost at Node 4 is also 30. Note that Node 4 is connected to root Node 5 only through Node 4’s VCG v2. If we increase the path cost at Node 4 VCG v2 to 30, then the root path cost at Node 4 will also be 30.

Since the root path cost at Node 4 is now equal to the root path cost at Node 3, the span between Nodes 3 and 4 will be blocked.

E

N D O F

S

T E P S

Figure 11-46 Existing spanning tree configuration

Node 1 Node 2

V1 is RP

STPCOST = 10

M 1 M 2

OC-48

M 1 M 2

Ring 1

Ring 2

STPCOST = 10

V1 V2

V2 is DP

STPCOST = 10

V2 Is DP

V1 V2

V1 is RP

STPCOST = 10

Normal traffic flow with spanning tree

In this example, Node 5 is the preferred root node (root bridge)

V1 is DP

STPCOST = 10

M 2

Node 4

M 1

OC-48

Normal traffic flow with spanning tree

M 2

Node 3

M 1

V2 V1

V2 is RP

STPCOST = 10

DP - Designated Port

RP - Root Port

STPCOST - Spanning Tree Path Cost

V1 Is DP

V2 V1

V2 is RP

STPCOST = 10 STPCOST = 10

Example: Original span chosen to be normally blocked

nc-dmx-209

.................................................................................................................................................................................................................................

11-226 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Figure 11-47 New spanning tree configuration

Node 1 Node 2

V1 is RP

STPCOST = 10

M 1 M 2

M 1

Ring 1

M 2

Ring 2

V1 V2

Procedure 11-26: Change an existing spanning tree configuration

V2 Is DP

V1 V2

V1 is RP

STPCOST = 10 V2 is DP

V2 is DP

STPCOST = 10

In this example, Node 5 is the preferred root node (root bridge)

V1 is DP

STPCOST = 10

Node 4

M 2 M 1

Normal traffic flow with spanning tree

V2 V1

V2 is RP

Change STPCOST = 30

DP - Designated Port

RP - Root Port

STPCOST - Spanning Tree Path Cost

M 2

Node 3

M 1

V1 is RP

STPCOST = 10

V2 V1

Example: New span chosen to be normally blocked

nc-dmx-210

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-227

Ethernet/Data network provisioning procedures

Procedure 11-27: Create/Delete MAC address on Ethernet port

.................................................................................................................................................................................................................................

Overview

Use this procedure to provision MAC address on an Ethernet port provisioned for

802.1Q or TRANS (transparent) mode. Does not apply to circuit packs provisioned for

NOTAG mode.

The

Configuration

→

Data

→

Create (or Delete) MAC Address

command (

ent-mac/dlt-mac

TL1 command) from the System View menu allows you to add/delete or modify a MAC address on a port.

Use this command to provision persistent and filtered MAC Tag addresses. A persistent

MAC will bypass the normal aging process. Filtering on a MAC address allows an operator to drop frames from a disruptive user based on the MAC+VLAN/tag address.

Packets received by any port in that VLAN/Port Tag on the pack with the MAC as filtered will be dropped.

When provisioning a MAC address, the MAC address must be valid, a VLAN/Port Tag must be specified, and the type must be specified. The VLAN or Port Tag must already exist in the circuit pack and be assigned to the selected LAN/WAN port. Unicast only

MAC addresses are supported.

Sample TL1 command:

ent-mac:TID123:growth-1:123456::00443454A300,53,filtered:portaid=g-1;

Privilege level

You must login at least as a General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The shelf slots, circuit packs, ports, MAC addresses, VLAN/Port Tag being provisioned.

•

The MAC Address type (Persistent or Filtered) being assigned.

Step

1

Use the following procedure to provision MAC Addresses:

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to the Metropolis

®

DMX shelf.

.................................................................................................................................................................................................................................

11-228 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-27: Create/Delete MAC address on

Ethernet port

2

3

4

5

6

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Select

Configuration

→

Data

→

Create (or Delete) MAC Address

from the System

View menu.

Result:

The Create MAC Address or Delete MAC Address window opens.

.................................................................................................................................................................................................

Select the circuit pack being provisioned, then click

Select

.

Result:

The Create MAC Address or Delete MAC Address window opens.

.................................................................................................................................................................................................

Click on an entry in the table presented to Add/Modify an entry (if Create was chosen), or to Delete an entry (if Delete was chosen).

Result:

A window opens displaying the parameters you have chosen and the options you may perform.

.................................................................................................................................................................................................

Select the required options (parameters) in the display window to add/modify/delete the necessary parameters.

.................................................................................................................................................................................................

Click on one of the buttons at the bottom of the window to

Add

/

Modify

or

Delete

the selections, as required.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-229

Ethernet/Data network provisioning procedures

Procedure 11-28: Provision Q in Q stacked VLAN capability

.................................................................................................................................................................................................................................

Overview

Use this procedure as a reference to provision the LAN/WAN Ethertype parameters

(Tag Protocol Identifier [TPID] ) and port tags for stacked VLANs.

The examples in this procedure use a 3-node UPSR ring to illustrate the provisioning.

It is assumed that the ring is properly provisioned for a multipoint (unswitched)

Ethernet service using transparent (TRANS) mode at each of the Ethernet circuit packs.

Prior provisioning includes provisioning the necessary multipoint (unswitched) cross-connections and setting up a virtual switch containing the LAN ports and VCG

(WAN) ports being used.

In these examples, Node 1 is considered to be the customer interface node (ingress) and Node 3 is considered to be the network interface node that connects to a QinQ switch/router. Node 2 is configured to be a packet layer pass-through where the pass-through is performed by the switch, not at the SONET layer, in anticipation of service being added.

Privilege level

You must login at least as a General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The shelf slots, circuit packs, ports, being provisioned.

•

The Ethernet Type values (TPID), port tag VLANs being assigned.

Step

1

2

Use the following examples for provisioning Ethertype and port tag parameters:

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to the Metropolis

®

DMX shelf.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Use the

Configuration

→

Data

→

Create Port Tag

from the System View menu to provision the port tags, if not already performed. Use the

Configuration

→

Equipment

command, select the port, to provision the port parameters, including the

.................................................................................................................................................................................................................................

11-230 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-28: Provision Q in Q stacked VLAN capability

Ethernet Type (TPID)

value located under the

Traffic Provisioning

tab of the port parameters. Or, use the

ed-eport/ed-vcg

TL1 commands to provision the parameters in these examples.

Important! The Peak Information Rate (PIR) rate limiting feature on the

LNW66/LNW67/LNW68 circuit packs will not be effective in transparent mode if the Ethernet Type (ethertype) parameter for the LAN or WAN VCG ports is provisioned to any value other than FFFF or 8100.

E

N D O F

S

T E P S

Node

Example 1: Standard untagged frame

See

Figure 11-48, “Example 1 configuration” (p. 11-231)

for this example.

Figure 11-48 Example 1 configuration

Node 2

Node 1

B

8100, 1024

8100, 1024

8100, 1024

8100, 1024

Untagged

Untagged

A

Node 1

8100, 1024

Customer

Interface

Node

Network

Interface

Node

Node 3

8100, 1024

TPID = 8100

PortTag VLAN = 1024

C

QinQ Switch

8100, 1024

8100, 1024

MA-DMX-379

This example assumes that:

•

The incoming traffic at Node 1 consists of

″ standard untagged frames

″

(no TPID value or TPID value other than FFFF or 8100).

•

Provisioning is performed as illustrated in the following table

Table 11-4 Provisioning for example 1

LAN (eport)

TPID dftporttag addporttag

WAN (vcg)

TPID dftporttag addporttag

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-231

Ethernet/Data network provisioning procedures

Node 1

Node 2

Node 3

Procedure 11-28: Provision Q in Q stacked VLAN capability

Table 11-4 Provisioning for example 1 (continued)

FFFF

(8100 for

LNW70)

1024 8100

8100 1024

8100

8100

1024

1024

1024

As a result of the provisioning illustrated in

Figure 11-48, “Example 1 configuration”

(p. 11-231) , and the prior assumptions, the following results are obtained:

•

A data stream of

″ standard tagged frames

″ with a TPID value of 8100, port tag

VLAN value of 1024, and default priority value is assigned at Node 1 and transmitted out the LAN (eport) at Node 3.

•

The frame headers at the points labeled A, B, and C contain the following data:

A

B

Table 11-5 Expected results for frame headers in example 1

Points Destination Address Source Address VLAN TPID & Tag

(Outer)

VLAN TPID &

Tag (Inner)

C

C

C

C

A

A

A

NA (not applicable)

81 00 04 00

81 00 04 00

NA

NA

NA

...

.................................................................................................................................................................................................................................

11-232 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-28: Provision Q in Q stacked VLAN capability

Example 2: Standard VLAN tagged frames

See

Figure 11-49, “ Example 2 configuration” (p. 11-233)

for this example.

Node

Node 1

Node 2

Node 3

Figure 11-49 Example 2 configuration

VLAN Tagged

8100, 500, P

8100, 500, P

A

Node 1

Node 1

B

8100, 1024, Q

8100, 500, P

8100, 1024, Q

8100, 500, P

Customer

Interface

Node

Node 2

8100, 1024, Q

8100, 500, P

8100, 1024, Q

8100, 500, P

Network

Interface

Node

8100, 500, P 8100, 1024, Q

8100, 500, P

Node 3

QinQ Switch

8100, 1024, Q

8100, 500, P

8100, 1024, Q

8100, 500, P

C

TPID = 8100

Default PortTag VLAN = 1024

Customer VLAN Tag = 500

P = Customer Priority Value

Q = Default Priority Value on LAN Port

MA-DMX-381

This example assumes that:

•

The incoming traffic at Node 1 consists of

″ standard VLAN tagged frames

″

(TPID value 8100), VLAN port tag set to 500, and the priority set to a non-default value

(P).

•

Provisioning is performed as illustrated in the following table.

Table 11-6 Provisioning for example 2

LAN (eport)

TPID

FFFF

(8100 for

LNW70) dftporttag

1024 addporttag

WAN (vcg)

TPID

8100 dftporttag

8100 1024

8100

8100 addporttag

1024

1024

1024

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-233

Ethernet/Data network provisioning procedures Procedure 11-28: Provision Q in Q stacked VLAN capability

As a result of the provisioning illustrated in

Figure 11-49, “ Example 2 configuration”

(p. 11-233) , and the prior assumptions, the following results are obtained:

•

A data stream of

″ double tagged frames

″ is transmitted out the eport on Node 3.

The inner tag (8100, 500, and priority value [P]) are the ones provided by the end customer at Node 1. The outer tag (8100, 1024, and default priority value [Q] for

LAN port) are assigned by Node 1.

•

The frame headers at the points labeled A, B, and C contain the following data:

Points Destination Address Source Address

A

B

C

C

C

C

Table 11-7 Expected results for frame headers in example 2

A

A

A

VLAN TPID & Tag

(Outer)

NA

81 00 04 00

81 00 04 00

VLAN TPID &

Tag (Inner)

81 00 01 F4

81 00 01 F4

81 00 01 F4

...

.................................................................................................................................................................................................................................

11-234 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-29: Perform Ethernet loopback transmission test

.................................................................................................................................................................................................................................

Overview

Use this procedure to perform an Ethernet loopback transmission test. It is assumed that the Ethernet packet ring or point-to-point service has been configured using the procedures in this chapter.

Privilege level

You must login as a General or Privileged user to complete this procedure.

Important! The following rules apply for this test:

•

Only out-of-service testing may be performed.

•

Only one loopback is allowed on a circuit pack.

•

Only one loopback is allowed on any one port in a multipoint packet ring, even if they are on different nodes

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The shelf slots, circuit packs, ports that are being tested.

You must have an Ethernet test set capable of applying the external test signal required for this procedure.

Step

1

2

Use the following procedure to perform the loopback test:

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to the near end Metropolis

®

DMX shelf.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Review the following test set considerations:

•

Set the Destination Address to

″

Broadcast

″

(all Fs [FFFFFFFF}).

•

Provision the test set data frames for the type of provisioned service being tested.

•

Set the frame size to 1024 bytes.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-235

Ethernet/Data network provisioning procedures

3

4

5

6

7

Procedure 11-29: Perform Ethernet loopback transmission test

•

Set the transmission mode to send a single packet or to send a continuous stream at a rate much less than the interface and VCG rates.

•

Make sure the VLAN tag is appropriate for the source and loopback ports.

.................................................................................................................................................................................................

For the circuit being tested, perform a terminal loopback at the far-end node port.

Select

Fault

→

Analysis

→

Loopback

from the System View menu at the far-end node. Expand the circuit pack details, select the port, then click

Select

at the bottom of the screen.

.................................................................................................................................................................................................

Verify the port AID, then select

Operate

. Click on

Apply

at the bottom of the window.

Read the warning message, then click

Yes

to operate the command.

.................................................................................................................................................................................................

Connect the near end port to the Ethernet test set and start sending traffic.

.................................................................................................................................................................................................

Verify traffic is being received at the source node Ethernet test set.

.................................................................................................................................................................................................

Use the

Fault

→

Analysis

→

Loopback

command to release the loopback. Repeat this procedure for all circuits being tested.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

11-236 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-30: Enable/Disable LAN port transmission

.................................................................................................................................................................................................................................

Overview

Use this procedure to enable/disable LAN port transmission.

Privilege level

You must login at least as a General or Privileged user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail the shelf slots, circuit packs, ports that are being enabled/disabled.

Step

1

2

3

Use the following procedure to enable/disable LAN port transmission.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to the Metropolis

®

DMX shelf.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Select the

Configuration

→

Equipment

from the System View menu. Select and expand the details for the circuit pack containing the LAN port. Highlight the LAN

Port, then click

Select

.

.................................................................................................................................................................................................

Important! Disabling a LAN port will disable all frames to and from the port.

Click on the

″

Port Data

″ tab. For

Port Administration Control

, select

ENABLE

to enable the LAN port. Select

DISABLE

to disable the LAN port. Click

Apply

, read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-237

Ethernet/Data network provisioning procedures

Procedure 11-31: Provision Ethernet quality of service (QoS)

.................................................................................................................................................................................................................................

Overview

Use this procedure as a reference to provision Ethernet Quality of Service (QoS). Refer to the section at the end of these steps for a detailed overview.

Important! This procedure applies only to LNW70 circuit packs.

Privilege level

You must login at least as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The shelf slots, circuit packs, ports, being provisioned.

•

The type of QoS service being provisioned and all the related parameter values.

All the required regular Ethernet service parameters must have already been provisioned using the procedures in this chapter. This includes any packet rings, vlan tagging modes, customer vlan/port tags, virtual switches, and related LAN and VCG port parameters.

Step

1

2

Use the following to provision a QoS service.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to the Metropolis

®

DMX shelf.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Use the

Configuration

→

Equipment

command from the System View menu, select the circuit pack, then select the port being provisioned. Click on the

Queue

Management

tab. Provision the queue management parameters, as required. Or, use the

ed-eport/ed-vcg

TL1 commands to provision the queue parameters.

Repeat this step for each port in the network service.

.................................................................................................................................................................................................................................

11-238 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-31: Provision Ethernet quality of service

(QoS)

3

4

5

6

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

or

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

.................................................................................................................................................................................................

Use the

Configuration

→

Data

→

Provision QoS Service

command from the System

View menu, select the circuit pack, then select the port being provisioned. Or, use the

ed-erate

TL1 command to provision the parameters for the QoS service.

Reference:

Procedure 11-32: “Provision Ethernet QoS parameters” (p. 11-244)

.................................................................................................................................................................................................

Select the

Port Type

as

Boundary

(Interior ports are not provisionable in this release.)

Select the

Traffic Management Mode

.

.................................................................................................................................................................................................

Provision the parameters as required from your work order for the traffic management mode selected.

.................................................................................................................................................................................................

Verify your settings, then click

Apply

. Read the warning message, then click

Yes

to execute the command. Click Close to exit.

E

N D O F

S

T E P S

Ethernet QoS

Use as a reference to provision Ethernet Quality of Service (QoS).

The Metropolis

®

DMX uses the differentiated services (DiffServ) model for the QoS feature. Traffic flow to the network is regulated only at the ingress ports.

The DiffServ model has two types of ports:

•

Boundary port - port at the edge of the DiffServ domain.

•

Interior port - port internal to the DiffServ domain.

A LAN/VCG port may be a boundary or interior port. When a VCG is provisioned as a boundary port, only NOTC traffic management mode is supported.

Selection of these port parameters may be done using the

ed-eport

and

ed-vcg

TL1 commands, or

Configuration

→

Data

→

Provision QoS Service

from the WaveStar

®

CIT system menu, selecting the port, then select

Port Type

.

QoS Services/Traffic Management Modes

A basic QoS service is defined as a particular traffic flow that uses a single traffic conditioner. A number of services can be provisioned at a Boundary port. Interior ports do not have traffic conditioners. The configuration of these services is defined as one

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-239

Ethernet/Data network provisioning procedures Procedure 11-31: Provision Ethernet quality of service

(QoS) of five traffic management modes (

trafmgmtmd

) . The mode specifies how the packets will be divided into traffic flows and the services that can be provided at the port. All services at one port must be in the same traffic management mode. The total number of QoS services on the LNW70 circuit pack is 400.

The traffic management modes are defined as follows:

•

PORT mode - Allowed in all VLAN tagging modes and in Private Line mode. One

QoS service per port, when higher layer protocol classification is not used

(ED-EPORT parameter hlayercos is NONE). One QoS service per cos value per port when hlayercos is set DSCP (not available in Private Line mode).

•

COSPORT mode - Allowed only in 802.1TAG mode. One QoS service and one TC for each Class of Service (CoS) at the port.

•

TAGPORT mode - Allowed only in 802.1TAG mode. One QoS service and one TC for each packet tag (802.1q or CID) at the port. All traffic received at the port that is tagged with the same VLAN ID is processed by a single traffic conditioner.

•

COSTAGPORT mode - Allowed only in 802.1TAG mode. One QoS service and one TC for each CoS for each packet tag at the port

•

NOTC mode - Allowed in all VLAN tagging modes and in Private Line mode. In this mode all traffic is bridged through the switch as usual but there is no traffic conditioning performed on the traffic. NOTC mode emulates the (limited) QoS behavior on the older circuit packs (user_priority values 0 ,1, 2 and 3 are mapped to CoS 0 and user_priority values 4, 5, 6 and 7 are mapped to CoS 3; no modification of user_priority bits in user packets).

Selection of these port parameters may be done using the

ed-eport

and

ed-vcg

TL1 commands, or

Configuration

→

Data

→

Provision QoS Service

from the WaveStar

®

CIT system menu, selecting the port, then select

Traffic Management Mode

.

Classes of Service

Data packets classified at the ingress port result in unique traffic flows. Multiple flows can be mapped into a single Class of Service (COS). There may be up to four classes of service (CoS level 0, 1, 2, 3) supporting expedited forwarding (EF) and assured forwarding (AF) service. Class 3 supports expedited forwarding, low latency. Classes

0, 1, 2 support various degrees of assured, guaranteed, forwarding including best effort.

Selection of these parameters may be done using the

ent/ed-erate

TL1 commands, or

Configuration

→

Data

→

Provision QoS Service

from the WaveStar

®

CIT system menu, selecting the port, then selecting

Traffic Management Mode

.

Traffic Conditioning

Traffic conditioning is performed on the ingress packets at Boundary Ports by metering the packets and either marking or policing as appropriate. This is used to enforce the guarantees and limitations specified in a Service Level Agreement (SLA). Within the network, queueing and scheduling functions provide a network that is engineered to

.................................................................................................................................................................................................................................

11-240 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-31: Provision Ethernet quality of service

(QoS) satisfy all of the attached customers’ SLA requirements. There is no traffic conditioning on Interior ports.

Traffic Conditioner Parameters

Traffic Conditioner (TC) parameters include PIR, CIR, PBS, and CBS.

•

PIR - Peak Information Rate. This is the peak information rate of the traffic conditioner function in Mbps. This is the PIR for the service addressed by the trafmgmtmd, port aid, tagid and cos. Value is from 0 to 1000. A value of 0 means that the PIR function is bypassed and there is no policing of the traffic. The value of PIR must be greater than or equal to CIR.

•

CIR - Committed Information Rate. This is the committed information rate of the traffic conditioner function in Mbps for the service addressed by the trafmgmtmd, port aid, tagid, and cos. Value is from 0 to 1000. The value of cir must be less than or equal to pir. A value of 0 means that there is no network commitment on incoming traffic. All traffic will be considered excess traffic

•

PBS - Peak Burst Size. This is the peak burst size in kilobytes for the service addressed by the trafmgmtmd, port aid, tagid, and cos. Value is from 0 to 1024.

•

CBS - Committed Burst Size. This is the committed burst size in kilobytes for the service addressed by the trafmgmtmd, port aid, tagid, and cos. Value is from 1 to

1024. The value of CBS must be less than or equal to PBS. In case of Private Line

(vlantagmd set to NOTAG), the CBS value cannot be set (it inherits the PBS value).

Selection of these parameters may be done using the

ent/ed-erate

TL1 commands, or

Configuration

→

Data

→

Provision QoS Service

from the WaveStar

®

CIT system menu, then selecting the port.

Metering, Policing, and Color Marking

Metering measures the data rate with conformance levels determined by three color markers:

•

Red - data rates greater than the PIR or PBS.

•

Yellow - data rates less than or equal to PIR or PBS, but greater than CIR or CBS.

•

Green - data rates less than or equal to CIR or CBS.

Policing discards red packets at the boundary ports. The remaining yellow and green packets determine drop precedence (DP).

Packets ingressing at boundary ports are remarked. Packets user priority is altered to reflect COS and DP. The COS is encoded in the 2 most significant bits in the user_priority field of the VLAN tag. The DP is encoded in the least significant bit in the user_priority field of the VLAN tag. In COSPORT or COSTAGPORT mode, user priority bit values map to the specified COS value. It is a map consisting of 8 elements left-to-right in increasing order of user priority.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-241

Ethernet/Data network provisioning procedures Procedure 11-31: Provision Ethernet quality of service

(QoS)

The bitmap shows which of the 8 user priority values map to the current COS:

•

COS 0 - 01100000

•

COS 1 - 10010000

•

COS 2 - 00001100

•

COS 3 - 00000011

In TAGPORT mode, the traffic class is set for all packets that ingress the port with a tagid and sets the COS value that will be inserted into the packet prior to egressing the

NE. The COS value is inserted into the user_priority bits.

In PORT mode, the traffic class is set for all packets that ingress the port and the COS value is set based on the default priority of the port. The COS value is inserted into the packet prior to egressing the NE.

Selection of these parameters may be done using the

ent/ed-erate

TL1 commands, or

Configuration

→

Data

→

Provision QoS Service

from the WaveStar

®

CIT system menu, then selecting the port.

Queue Management

Each port supports configurable thresholds expressed as a percentage of the total queue allocation. Each queue is controlled by setting the size of the queues, the queue weights and the drop thresholds for yellow and green packets. The performance of each CoS level is controlled by setting the dropping probabilities for each CoS level.

Traffic that was admitted into the network within the terms of a Service Level

Agreement (SLA) can be differentiated and given preferential treatment at the queue in order to satisfy the SLA service guarantees.

Provisioning of these port parameters may be done using the

ed-eport

and

ed-vcg

TL1 commands, or Configuration

→

Equipment from the WaveStar

®

CIT system menu, selecting the port, then selecting

Queue Management

.

The following TL1 command (WaveStar

®

CIT) parameters determine the maximum queue size and the minimum and maximum dropping thresholds for yellow and green packets:

• qsz - Maximum queue size.

Total Queue Size (in Kbytes)

• qminthldg - Minimum dropping threshold for green packets.

Green Packet Min

Drop Threshold (in %)

• qmaxthldy - Maximum dropping threshold for yellow packets.

Yellow Packet Max

Drop Threshold (in %)

• qminthldy - Minimum dropping threshold for yellow packets.

Yellow Packet Min

Drop Threshold (in %)

.................................................................................................................................................................................................................................

11-242 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-31: Provision Ethernet quality of service

(QoS)

The following TL1 command (WaveStar

®

CIT) parameters specify the weighting factor used by the queue service algorithm for the AF queue for packets coming from network or customer ports. EF packets are given strict priority over AF packets.

• qwt_ntwkAF - Weighting factor for the queue that serves AF packets from network ports.

Network Port AF Queue Weighting Factor

• qwt_custAF - Weighting factor for the queue that serves AF packets from customer ports.

Customer Port AF Queue Weighting Factor

The following TL1 command (WaveStar

®

CIT) parameters determine the maximum drop probability for COS 0, 1, 2, 3 packets:

• qdropwt0 - Specifies maximum drop probability for COS 0 packets.

CoS 0

Packets Drop Probability Mark (in %)

• qdropwt1 - Specifies maximum drop probability for COS 1 packets.

CoS 1

Packets Drop Probability Mark (in %)

• qdropwt2 - Specifies maximum drop probability for COS 2 packets.

CoS 2

Packets Drop Probability Mark (in %)

• qdropwt3 - Specifies maximum drop probability for COS 3 packets.

CoS 3

Packets Drop Probability Mark (in %)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-243

Ethernet/Data network provisioning procedures

Procedure 11-32: Provision Ethernet QoS parameters

.................................................................................................................................................................................................................................

Overview

This procedure provides a list of provisionable parameters for quality of service parameters set using the

ent/ed-erate

command, or selecting

Configuration

→

Data

→

Provision QoS Service

from the WaveStar

®

CIT System menu.

Also see

Procedure 11-31: “Provision Ethernet quality of service (QoS)” (p. 11-238) .

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The values to be set for each parameter.

Step

1

2

Use this procedure as a reference for creating an Ethernet QoS service on circuit packs that support QoS services parameters.

.................................................................................................................................................................................................

Use the

ent-erate

TL1 command or select

Configuration

→

Data

→

Provision QoS

Service

from the System View menu. Select the Ethernet circuit pack being provisioned, then click

Select

.

Reference:

(p. 11-238)

Procedure 11-31: “Provision Ethernet quality of service (QoS)”

.................................................................................................................................................................................................

Use

Table 11-8, “ENT-ERATE command provisionable parameters” (p. 11-245)

as reference to provision the necessary parameters from your work instructions.

E

N D O F

S

T E P S

ENT-ERATE command parameters

Table 11-8, “ENT-ERATE command provisionable parameters” (p. 11-245)

lists the provisionable parameters for the Quality of Service (QoS):

.................................................................................................................................................................................................................................

11-244 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-32: Provision Ethernet QoS parameters

Parameter

tagid cos

Table 11-8 ENT-ERATE command provisionable parameters

Description

Tag ID

. Represents the VLAN ID in the 802.1TAG mode, or the

Port Tag ID in the TRANS mode.

Value: An integer in the range of 1 to 4093.

If trafmgmtmd is set to PORT or COSPORT then tagid must be blank.

If trafmgmtmd is set to TAGPORT or COSTAGPORT, then a valid numerical value for tagid must be entered and it must be a value that has been previously provisioned at the port.

tagid

must be blank on a LNW78 pack.

The

CoS

parameter applies to the LNW70 and the LNW78 circuit packs only. It specifies the class of service that the parameters in this command apply to.

For the LNW70, the allowed value is an integer between 0 and 3.

•

The value of 0 specifies CoS level 0.

•

The value of 1 specifies CoS level 1.

•

The value of 2 specifies CoS level 2.

•

The value of 3 specifies CoS level 3.

For the LNW70:

•

If

trafmgmtmd

is set to PORT and the ED-EPORT

hlayercos

is set to DSCP, then a valid

cos

must be entered.

•

If

trafmgmtmd

is set to PORT and the ED-EPORT

hlayercos

is set to NONE, then

cos

must be blank.

•

If

trafmgmtmd

is set to COSPORT or COSTAGPORT, then a valid numerical value for

cos

must be entered.

For the LNW78, the allowed value is an integer between 1 and 3.

•

The value of 1 specifies CoS level 1 (Class C)

•

The value of 2 specifies CoS level 2 (Class B)

•

The value of 3 specifies CoS level 2 (Class A)

For the LNW78:

•

If

trafmgmtmd

is set to PORT, then

cos

must be blank.

•

If

trafmgmtmd

is set to COSPORT, then a valid numerical value for

cos

must be entered.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-245

Ethernet/Data network provisioning procedures Procedure 11-32: Provision Ethernet QoS parameters

Parameter

cbs cir pbs

Table 11-8 ENT-ERATE command provisionable parameters (continued)

Description

CBS

. Committed Burst Size. This is the committed burst size in kilobytes (1024 bytes) for the service addressed by the trafmgmtmd, port aid, tagid, and cos.

Value: An integer in the range of 1 to 1024. For the LNW78 the range is 1 to 256. Default is 10.

Default value is chosen because it guarantees that the burst size is at least the max frame size possible (when jumbo frames up to 10K are used).

In case of Private Line (vlantagmd set to NOTAG), the cbs value cannot be set (it takes on the pbs value).

On an LNW78,

cbs

cannot be set for CoS level 1.

CIR

. Committed Information Rate. This is the committed information rate of the traffic conditioner function in Mbps for the service addressed by the trafmgmtmd, port aid, tagid, and cos.

Value: An integer in the range of 0 to 1000. Default value is 0.

The value of cir must be less than or equal to pir.

A value of 0 means that there is no network commitment on incoming traffic. All traffic will be considered excess traffic.

A value of 1000 means that there is no policing of the traffic, traffic will flow unconditioned.

In case of Private Line (vlantagmd set to NOTAG), the cir value cannot be set (it takes on the pir value)

On an LNW78,

cir

cannot be set for CoS level 1.

PBS

. Peak Burst Size. This is the peak burst size in kilobytes (1024 bytes) for the service addressed by the trafmgmtmd, port aid, tagid, and cos.

Value is an integer in the range of 1 to 1024. For the LNW78 pack the range is 1 to 256. Default value is 20.

The value of pbs must be greater than or equal to cbs.

The default value of 20 is chosen because it guarantees that the burst size is at least the max frame size possible (when jumbo frames up to 10K are used).

On an LNW78,

pbs

cannot be set for CoS level 3.

.................................................................................................................................................................................................................................

11-246 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-32: Provision Ethernet QoS parameters

Parameter

pir qospm dftpri2cos

Table 11-8 ENT-ERATE command provisionable parameters (continued)

Description

PIR

. Peak Information Rate. This is the peak information rate of the traffic conditioner function in Mbps. This is the pir for the service addressed by the trafmgmtmd, port aid, tagid, and cos.

Value is an integer in the range of 0 to 1000. Default value is 1000.

The value of pir must be greater than or equal to cir

A value of 1000 means that there is no policing of the traffic, traffic will flow unconditioned. A value of 0 means that the traffic is halted, 0 Mbps.

On an LNW78,

pir

cannot be set for CoS level 3.

QoS PM

. Enables/Disables Performance Monitoring data collection for the service addressed by the trafmgmtmd, port aid, tagid, and cos. Counters for the service will be re-initialized to 0 when qospm is toggled from DISABLE to ENABLE.

Values:

•

ENABLE - QoS performance monitoring is enabled (initial value)

•

DISABLE - QoS performance monitoring disabled

Default CoS

. This parameter sets the traffic class of all packets that ingress the port with tagid and sets the cos value that will be inserted into the packet prior to egressing the NE. The cos value will be inserted into the user_priority bits. This parameter is only applicable if the port pointed to by aid has trafmgmtmd set to

TAGPORT.

Values: Integers 0, 1, 2, 3. Default is 0.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-247

Ethernet/Data network provisioning procedures Procedure 11-32: Provision Ethernet QoS parameters

Parameter

userpri2cos dscp2cos

Table 11-8 ENT-ERATE command provisionable parameters (continued)

Description

User PB

. This parameter shows the user priority bit values that map to the specified cos value. It is a map consisting of 8 elements left-to-right in increasing order of user priority, where each element specifies whether the user priority value maps to the CoS (“1”) or not (“0”).

Parameter is only valid is If Traffic Management Mode set to

COSPORT or COSTAGPORT.

Values allowed: A string of 8 characters from the set (“0”,”1”).

Default value:

• cos 0 : 01100000

• cos 1 : 10010000

• cos 2 : 00001100

• cos 3 : 00000011

This parameter does not apply to the LNW78 pack. The mapping is specified by IEEE 802.17a-2004.

Differentiated Services Code Point (DSCP) to associated CoS Level

(cos) map

. This parameter lists the DSCP integer (six bits of the

DS field) values that map to the specified cos value. This parameter is only applicable if the port pointed to by aid has trafmgmtmd set to PORT and hlayercos set to DSCP.

Values: A list of integers between 0 and 64. The value 64 is used to classify non DSCP traffic to a cos. Any number can only be mapped to one service.

Any DSCP value that is not mapped to a cos will default to CoS 0, even if cos 0 was not created using (ENT-ERATE). If value 64 (for non IP frames) is not assigned to a cos, it will be assigned by default to CoS 0.

Default value:

• cos 0 :

0-9&11&13&15&26&28&30&34&36&38&44&50&52&54&

58&60&62

• cos 1 : 16-25&27&29&31

• cos 2 : 10&12&14&32&33&35&37&39&40&43&45&47&64

• cos 3 : 46&48&49&51&53&55-57&59&61&63

This parameter is only applicable to the LNW70 pack.

.................................................................................................................................................................................................................................

11-248 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-33: Provision LCAS, add/enable/remove tributaries

.................................................................................................................................................................................................................................

Overview

Use this procedure to enable/disable LCAS or add/enable/remove tributaries to

LCAS-enabled VCGs.

LCAS allows for in-service hitless addition or removal of tributary members of a

Virtual Concatenation Group (VCG) to vary its bandwidth. It also allows for automatic removal and restoration of failed members.

Tributary members may be any supported SONET tributary rate (e.g. STS-1, STS-Nc,

VT1.5 tributaries) but never a mix of rates. When a trib is added which is tardier than current members, the entire VCG is retarded to allow it to join. This is accomplished by a temporary decrease in the output payload rate, while the current members are buffered for time-alignment.

The LCAS protocol is unidirectional in that the source side controls the hitless operations. The sink side only assists by indicating whether it is ready and acknowledging completion. This means that LCAS requires a return path for signaling from the sink back to the source. Single one-way cross-connections will not provide a return path. Therefore, for each span, two-way cross-connections must be made. Then, in order to be hitless, removal operations must be sequenced between the two ends, always starting at the source side of each unidirectional link.

Important! LCAS and this procedure apply only to LNW70 and LNW74 Ethernet circuit packs. If only one end has LCAS enabled or the far end does not support

LCAS, transmission operates normally in the non-LCAS mode. The standing condition NOTLCAS is generated when LCAS is enabled but the far end is detected as not supporting LCAS. It is cleared either when LCAS is disabled locally or the far end is detected to support LCAS.

Privilege level

You must login at least as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The shelf slots, circuit packs, ports, being provisioned.

•

The network configuration and termination points.

•

The number of tributaries being added or removed and related aids.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-249

Ethernet/Data network provisioning procedures

Step

Procedure 11-33: Provision LCAS, add/enable/remove tributaries

1

.................................................................................................................................................................................................

Determine the VCGs at each terminating end (source and sink) of the circuit being provisioned.

For example:

•

Figure 11-50, “2-way cross-connections on a UPSR” (p. 11-255)

illustrates a path protected OC-48 ring network with STS1 cross-connections for Ethernet service. In this example, VCG v1 at Node 1 and VCG v1 at Node 4 serve as the source/sink and sink/source for LCAS provisioning.

Enabling LCAS requires that LCAS be Enabled for v1 at each terminating node.

Adding tributaries requires that LCAS be Enabled, cross-connections made, and

VCG membership enabled for each of the tributaries at the source and sink.

Removing tributaries requires a distinct order of removal: Disable local source tributary, disable remote source and sink tributaries, disable local sink tributary. In this example, you would Disable the source (Input Membership) at VCG v1 at

Node 1; Disable the source (Input Membership) and sink (Output Membership) at

VCG v1 at Node 4; then Disable the sink (Output Membership) at VCG v1 at

Node 1. Cross-connections for the disabled tributaries may then be removed as required.

•

Figure 11-51, “Multipoint GbE cross-connections on a UPSR” (p. 11-255)

illustrates an OC-48 ring network with multipoint STS1 cross-connections for

Ethernet service. In this example, there are three separate links relating to LCAS provisioning. Note that at each add/drop node (Node 1, Node 5, and Node 4), two separate VCGs (v1 and v2) serve as both source and sink for LCAS provisioning.

Enabling LCAS requires that LCAS be Enabled for both v1 and v2 at each terminating node.

Adding tributaries requires that LCAS be Enabled, cross-connections made, and

VCG membership enabled for each of the tributaries at all sources and sinks.

Removing tributaries requires a distinct order of removal: Disabling local source tributary, disabling remote source and sink tributaries, disabling local sink tributary.

In this example, each individual link is treated separately. For example, in the link from Main 1 at Node 1 to Main 2 at Node 5, you would Disable the source (Input

Membership) at VCG v1 at Node 1; Disable the source (Input Membership) and sink (Output Membership) at VCG v2 at Node 5; then Disable the sink (Output

Membership) at VCG v1 at Node 1. Then, repeat the sequence for the link from

Node 5 v1 to Node 4 v2, then from Node 4 v1 to Node 1 v2.

2

.................................................................................................................................................................................................

If ...

you are disabling LCAS, or enabling

LCAS for the first time,

Then ...

continue with

Step 3 .

.................................................................................................................................................................................................................................

11-250 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

If ...

you are adding tributaries to an LCAS

Enabled VCG, you are enabling tributaries previously added to an LCAS Enabled VCG, you are removing tributaries from an

LCAS Enabled VCG,

Procedure 11-33: Provision LCAS, add/enable/remove tributaries

Then ...

proceed to

Step 8 .

proceed to

Step 10 .

proceed to

Step 14 .

3

4

5

.................................................................................................................................................................................................

ENABLE/DISABLE LCAS FOR SELECTED VCGs

Determine the VCGs at each end (source and sink) of the circuit being provisioned.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to the Metropolis

®

DMX shelves.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Use the

Configuration

→

Equipment

command from the System View menu, select the circuit pack, then select the VCG port being provisioned. Click

Select

.

Important! Changing between LCAS-Enabled to LCAS-Disabled on an in-service

VCG may not be hitless.

6

.................................................................................................................................................................................................

Click on the

LCAS

tab. Provision the LCAS parameters, as required. Or, use the

ed-vcg

TL1 command to provision the LCAS parameters.

LCAS parameters:

•

LCAS Mode

:

ENABLE

(default) or

DISABLE

LCAS on the specified VCG.

•

Hold-Off Timer (in milliseconds)

: Specifies the delay time between when a tributary is detected faulty and when it is automatically removed from the VCG.

•

Wait-To-Restore (in seconds)

: Specifies the delay time between when a previously removed tributary is detected to be normal and when it is automatically returned to the VCG.

LCAS and non-LCAS interworking is supported but the change between LCAS enabled/disabled and LCAS disabled/enabled may not be hitless.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

.................................................................................................................................................................................................

7

Repeat from

Step 4

for each VCG port being provisioned.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-251

Ethernet/Data network provisioning procedures Procedure 11-33: Provision LCAS, add/enable/remove tributaries

8

9

10

11

12

13

END OF STEPS TO ENABLE OR DISABLE LCAS.

.................................................................................................................................................................................................

ADDING TRIBUTARIES

Use the WaveStar

®

CIT to log in to the Metropolis

®

DMX shelf, as required.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Make all required pass-through and add/drop cross-connections, if not already performed.

The cross-connections providing transmission between the Source and Sink VCG’s can occur at any time. Similarly the Source and Sink can be activated in any order. Only when all components are in place and enabled does the tributary member get added.

Tributaries may be enabled (default) when the cross-connections are made or disabled and then enabled at a later time.

Procedure 11-24: “Make cross-connections for Ethernet service” (p. 11-195)

END OF STEPS FOR ADDING TRIBUTARIES.

.................................................................................................................................................................................................

ENABLING TRIBUTARIES

Use the WaveStar

®

CIT to log in to the Metropolis

®

DMX shelf, as required.

.................................................................................................................................................................................................

Use the

Configuration

→

Equipment

command from the System View menu, select the Ethernet circuit pack, select the VCG port, then select the tributary (Trib) being provisioned. Click

Select

.

Or, use the

ed-vcgtrib

TL1 command to provision parameters.

.................................................................................................................................................................................................

In the Tributary provisioning screen, select

Enabled

for the

VCG Membership

for both the

Input

(Source) and

Output Direction

(sink).

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

.................................................................................................................................................................................................

Repeat from

Step 10

to Enable Membership for each Tributary at each VCG in each add/drop node in the configuration.

.................................................................................................................................................................................................................................

11-252 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-33: Provision LCAS, add/enable/remove tributaries

14

15

16

17

18

19

20

In a multipoint configuration, it is suggested that tributary membership be added at both ends on one link before moving to the next link.

END OF STEPS FOR ENABLING TRIBUTARIES.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Service hits may occur if the proper sequence is not followed when removing tributaries from an LCAS enabled system.

REMOVING TRIBUTARIES

Use the WaveStar

®

CIT to log in to the near-end Metropolis

®

DMX shelf, as required.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

From the System View menu, use the

Configuration

→

Equipment

command from the System View menu, select the Ethernet circuit pack, select the VCG port, then select the tributary (Trib) being removed. Click

Select

.

Or, use the

ed-vcgtrib

TL1 command to provision parameters.

.................................................................................................................................................................................................

In the Tributary provisioning screen, select

Disabled

for the

VCG Membership

for the

Input Direction

(Source).

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to the far-end Metropolis

®

DMX shelf terminating the link.

.................................................................................................................................................................................................

From the System View menu, use the

Configuration

→

Equipment

command from the System View menu, select the Ethernet circuit pack, select the VCG port, then select the tributary (Trib) being removed. Click

Select

.

Or, use the

ed-vcgtrib

TL1 command to provision parameters.

.................................................................................................................................................................................................

In the Tributary provisioning screen, select

Disabled

for the

VCG Membership

for both the

Output Direction

(Sink) and

Input Direction

(source).

.................................................................................................................................................................................................

Use the WaveStar

®

which you started.

CIT to log back in to the near-end Metropolis

®

DMX shelf in

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-253

Ethernet/Data network provisioning procedures Procedure 11-33: Provision LCAS, add/enable/remove tributaries

21

22

23

24

.................................................................................................................................................................................................

From the System View menu, use the

Configuration

→

Equipment

command from the System View menu, select the Ethernet circuit pack, select the VCG port, then select the tributary (Trib) being removed. Click

Select

.

Or, use the

ed-vcgtrib

TL1 command to provision parameters.

.................................................................................................................................................................................................

In the Tributary provisioning screen, select

Disabled

for the

VCG Membership

for the

Output Direction

(Sink).

.................................................................................................................................................................................................

If you are removing tributaries in a multipoint configuration, repeat from

Step 14

for each link having tributaries removed. Repeat these steps for all other tributaries being removed.

.................................................................................................................................................................................................

If required, remove all pass-through and terminating cross-connections relating to the removed tributaries.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

11-254 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-33: Provision LCAS, add/enable/remove tributaries

Figure 11-50 2-way cross-connections on a UPSR

Node 1

DMX OC-48

Node 2

DMX OC-48

M 1 M 2 M 1 M 2

Ring 1 IN

OUT

IN

Ring 2

OUT

IN OUT

A

V2

1 2

V1

GbE

B C D G

A B

C

D

G

2-Way Point-to-Point, Through cross-connections

UPSR Ring Add/Drop cross-connections: m1-1-(1-21) to a1-v1-(1-21)

OUT

IN

IN

OUT

M 2

Node 5

DMX OC-48

M 1

OUT

IN

IN

OUT

M 2

Node 4

DMX OC-48

M 1

OUT

IN

A B C D G

2-Way Point-to-Point, Through cross-connections

A

V2 V1

GbE

1 2

B C D G

UPSR Ring Add/Drop cross-connections: m1-1-(1-21) to a1-v1-(1-21)

Example: Pass through cross-connections at Nodes 2,3,5, and 6: m1-1-(1-21),m2-1-(1-21)

NC-DMX-086-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-255

Ethernet/Data network provisioning procedures Procedure 11-33: Provision LCAS, add/enable/remove tributaries

Figure 11-51 Multipoint GbE cross-connections on a UPSR

Node 1

DMX OC-48

Node 2

DMX OC-48

M 1 M 2 M 1 M 2

Ring 1 IN OUT IN

Ring 2

OUT

IN OUT

OUT

IN

A

V1 V2

GbE

1 2

B C D G

A B C D G

2-Way Point-to-Point, Through cross-connections m1-1-(1-21),m2-1-(1-21)

Multipoint (unswitched) cross-connections: m1-1-(1-21) to a1-v1-(1-21) m2-1-(1-21) to a1-v2-(1-21)

IN

OUT

M 2

Node 5

DMX OC-48

M 1

OUT

IN

IN

OUT

M 2

Node 4

DMX OC-48

M 1

OUT

IN

A

V2 V1

GbE

1 2

B C D G

A

V2 V1

GbE

1 2

B C D G

Multipoint (unswitched) cross-connections: m1-1-(1-21) to a1-v1-(1-21) m2-1-(1-21) to a1-v2-(1-21)

NC-DMX-084-2

.................................................................................................................................................................................................................................

11-256 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-34: Establish LNW74 10/100-T/F enhanced Fast

Ethernet private line service on UPSR

.................................................................................................................................................................................................................................

Overview

This procedure provides examples for:

•

Configuring point-to-point UPSR protected fast Ethernet private line service using the LNW74 10/100-T/F Enhanced Private Line Ethernet circuit pack. See

Figure

11-52, “Point-to-Point 10/100-T/F private line service, three STS1s” (p. 11-262) ,

Figure 11-53, “Two point-to-point 10/100-T/F private line services, STS1 and

STS3c” (p. 11-262) , and

Figure 11-54, “Two point-to-point 10/100-T/F private line services, STS3c and VT1.5” (p. 11-263)

for examples.

–

Figure 11-52, “Point-to-Point 10/100-T/F private line service, three STS1s”

(p. 11-262)

illustrates a UPSR protected point-to-point private line service using three STS-1 cross-connections.

–

Figure 11-53, “Two point-to-point 10/100-T/F private line services, STS1 and

STS3c” (p. 11-262)

illustrates two UPSR protected point-to-point private line services using STS1 and STS3c cross-connections.

–

Figure 11-54, “Two point-to-point 10/100-T/F private line services, STS3c and

VT1.5” (p. 11-263)

illustrates two UPSR protected point-to-point private line services using VT Virtual Concatenation and STS3c and VT1.5

cross-connections.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data

Provisioning Wizard to perform the provisioning in this procedure. From the System

View menu, select

Configuration

→

Ethernet Service

to invoke the wizard.

Important! If the LNW74 10/100-T/F circuit pack is being used in Function groups A, B, or C and the Main slots are equipped with LNW26B OC-48 OLIUs or functionally equivalent OLIUs with PWDM compatible optics, then only 24

STS-1s are available for cross-connections.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-257

Ethernet/Data network provisioning procedures Procedure 11-34: Establish LNW74 10/100-T/F enhanced

Fast Ethernet private line service on UPSR

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

Step

1

2

3

4

5

Use this procedure as an example for configuring fast Ethernet private line service. See

Figures for examples.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes, if not already performed.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

and/or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

This command may take several minutes to complete depending on the size of the network.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the service to be established.

.................................................................................................................................................................................................

Verify that the Ethernet circuit packs have been installed into the required slot 1 of the

Function Unit or Growth group (A, B, C, D, or G) at each NE providing Ethernet service.

.................................................................................................................................................................................................................................

11-258 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-34: Establish LNW74 10/100-T/F enhanced

Fast Ethernet private line service on UPSR

6

7

8

9

Important! When the LNW74 is installed in Growth group slot 1, only optical ports 17-24 may be used.

Reference:

Procedure 4-12: “Install 10/100 Ethernet circuit packs” (p. 4-50)

.................................................................................................................................................................................................

Important! If the Ethernet circuit pack is already in service, the existing VT

Virtual Concatenation mode cannot be changed without removing all existing VCG

VT1.5 cross-connections.

CONFIGURE VT VIRTUAL CONCATENATION MODE

Determine the existing VT Virtual Concatenation mode for the circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the

System View menu, select the CP, then click

Select

. Note the VT Virtual

Concatenation mode.

.................................................................................................................................................................................................

If required, use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu, select the circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Verify/Select the

VT Virtual Concatenation

mode (

0

or

12

). Click

OK

, read the warning message, then click

Yes

to execute the command.

When

12

is selected as the VT Virtual Concatenation mode, 12 STS-1s are reserved for VT1.5 concatenation. Up to 336 VT1.5s may be assigned to the circuit pack with between 0 and 63 assigned to any VCG. Only 36 STS-1s are then available for STS-1 concatenation or STS-3Cs.

When 0 is selected as the VT Virtual Concatenation mode, there is no VT mapping and all 48 STS-1s are available for STS-1 concatenation or STS-3Cs.

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary cross-connections to be made at each terminating and non terminating node in the network.

Important! The LNW74 supports tributary rates of VT1.5 VCAT, STS-1, or

STS-3c cross-connections independently to each VCG. Up to 63 VT1.5s may be assigned to any VCG if VT Virtual Concatenation mode is set to 12. Any VCG may be assigned 1, 2 or 3 STS-1s. Any VCG may be assigned an STS-3c up to a maximum of 16 for the circuit pack. Ports may be provisioned until all the available 48 STS-1 equivalents (including 336 VT1.5s) are used.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-259

Ethernet/Data network provisioning procedures Procedure 11-34: Establish LNW74 10/100-T/F enhanced

Fast Ethernet private line service on UPSR

10

11

12

13

.................................................................................................................................................................................................

One at a time at each non terminating node in the network, use the TL1

ent-crs-sts1

,

ent-crs-vt1

, or

ent-crs-sts3c

command to provision the pass-through cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard at each of the nodes in the network to provision the cross-connections.

Important! Note that cross-connections at the terminating nodes are add/drop and cross-connections at the non terminating nodes are pass-through.

Reference:

(p. 11-195)

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

One at a time at each terminating node in the network, use the TL1

ent-crs-sts1

,

ent-crs-vt1

, or

ent-crs-sts3c

command to provision the add/drop cross-connections. Or, select

Configuration

→

Cross-Connections

from the System

View menu to start the Cross-Connection Wizard. Use the Cross-Connection Wizard at each of the nodes in the network to provision the cross-connections.

Reference:

(p. 11-195)

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connections have been made.

.................................................................................................................................................................................................

Important! For LNW70/74 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG.

Use the TL1

ed-vcgtrib

command to enable tributaries, or from the System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

.................................................................................................................................................................................................................................

11-260 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

14

15

16

17

18

19

Procedure 11-34: Establish LNW74 10/100-T/F enhanced

Fast Ethernet private line service on UPSR

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

PROVISION LAN PORTS

Use the TL1

ed-eport

command to provision the LAN port parameters, or select

Configuration

→

Equipment

from the System View menu. Expand the details for the circuit pack, highlight the LAN Port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

Click

Apply

. Read the warning message, then click

Yes

to execute the command.

.................................................................................................................................................................................................

PROVISION VCGS

Use the

ed-vcg

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, if window is not already open from the prevision step. Expand the details for the circuit pack, highlight the

VCG port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

.................................................................................................................................................................................................

Click

Apply

. Read the warning message, then click

Yes

to execute the command.

Click

Close

to exit or repeat from

Step 16

for other port provisioning.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-261

Ethernet/Data network provisioning procedures Procedure 11-34: Establish LNW74 10/100-T/F enhanced

Fast Ethernet private line service on UPSR

Figure 11-52 Point-to-Point 10/100-T/F private line service, three STS1s

Node A Node B

M 1

M 2

OUT IN

M 1 M 2

OUT IN

V1

V13

13

D

V24

UPSR Ring Add/Drop cross-connections: m1-1-(1-3) to d1-v13-(1-3)

2-Way Point-to-Point, Through cross-connections m1-1-(1-3),m2-1-(1-3)

Example of 10/100-T/F UPSR Ring Add/Drop cross-connections using three STS1s for point-to-point private line service

M 2

Node D

M 1

OUT

IN

V24

...

V13 V1

D

13

UPSR Ring Add/Drop cross-connections: m1-1-(1-3) to d1-v13-(1-3)

IN

OUT

M 2

Node C

M 1

2-Way Point-to-Point, Through cross-connections m1-1-(1-3),m2-1-(1-3)

MA-DMX-411-2

.................................................................................................................................................................................................................................

11-262 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-34: Establish LNW74 10/100-T/F enhanced

Fast Ethernet private line service on UPSR

Figure 11-53 Two point-to-point 10/100-T/F private line services, STS1 and STS3c

Node A

M 1 M 2

OUT IN

M 1

Node B

M 2

OUT IN

V1

1

V13

13

D

...V24

STS3c and STS1

UPSR Ring Add/Drop cross-connections:

STS3: m1-1-4 to d1-v13-1

STS1: m1-1-1 to d1-v1-1

2-Way Point-to-Point, Through cross-connections:

STS3: m1-1-4 to m2-1-4

STS1: m1-1-1 to m2-1-1

Example: 10/100-PL UPSR Ring Add/Drop cross-connections, two point-to-point private line services, STS3c and STS1

M 2

Node D

M 1

OUT

IN

V24 ...

V13

13

V1

D

UPSR Ring Add/Drop cross-connections:

STS3: m1-1-4 to d1-v13-1

2-Way Point-to-Point, Through cross-connections:

STS1: m1-1-1 to m2-1-1

IN

OUT

M 2

Node C

M 1

V24...

V13

V1

D

1

UPSR Ring Add/Drop cross-connections:

STS1: m1-1-1 to d1-v1-1

2-Way Point-to-Point, Through cross-connections:

STS3: m1-1-4 to m2-1-4

MA-DMX-413-2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-263

Ethernet/Data network provisioning procedures Procedure 11-34: Establish LNW74 10/100-T/F enhanced

Fast Ethernet private line service on UPSR

Figure 11-54 Two point-to-point 10/100-T/F private line services, STS3c and

VT1.5

Node A

M 1 M 2 Node B

OUT

IN

M 1 M 2

IN

V1

V13

1 13

VT Virtual Concatenation = 12

D

V24

UPSR Ring Add/Drop cross-connections

STS3c : m1-1-13,d1-v13-1

VT1.5: m1-1-{1-n}-{1-7}-{1-4},d1-v1-vt{1-63}

OUT

2-Way Point-to-Point, Through cross-connections

STS3c: m1-1-13,m2-1-13

VT1.5: m1-1-{1-n}-{1-7}-{1-4},m2-1-{1-n}-{1-7}-{1-4}

Example: 10/100-T/F UPSR Ring Add/Drop cross-connections, two point-to-point private line services, STS3c and VT1.5

M 2

Node D

M 1

OUT

IN

V24 ...

V13 V1

D

13

UPSR Ring Add/Drop cross-connections

STS3c: m1-1-13,d1-v13-1

2-Way Point-to-Point, Through cross-connections

VT1.5: m1-1-{1-n}-{1-7}-{1-4},m2-1-{1-n}-{1-7}-{1-4}

M 2

Node C

M 1

IN

OUT

V24...

V13

V1

D

1

VT Virtual Concatenation = 12

UPSR Ring Add/Drop cross-connections

VT1.5: m1-1-{1-n}-{1-7}-{1-4},d1-v1-vt{1-63}

2-Way Point-to-Point, Through cross-connections

STS3c: m1-1-13,m2-1-13

MA-DMX-412-2

.................................................................................................................................................................................................................................

11-264 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-35: Establish LNW73/LNW73C FC-DPORT SAN transport service on UPSR

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring SAN transport service using the

LNW73/LNW73C circuit pack.

Figure 11-55, “Point-to-point Fibre Channel service”

(p. 11-270)

illustrates a two-way point to point Fibre Channel service transport over a

SONET UPSR ring.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters.

Important! If the LNW73/LNW73C FC-DPORT circuit pack is being used in

Function groups A, B, or C and the Main slots are equipped with LNW26B OC-48

OLIUs or functionally equivalent OLIUs with PWDM compatible optics, then only

24 STS-1s are available for cross-connections.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

Step

1

Use this procedure as an example for configuring SAN transport service. See Figure for example.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to the terminating nodes, if not already performed.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

2

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

and/or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-265

Ethernet/Data network provisioning procedures Procedure 11-35: Establish LNW73/LNW73C FC-DPORT

SAN transport service on UPSR

3

4

5

6

7

8

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

This command may take several minutes to complete depending on the size of the network.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the service to be established.

.................................................................................................................................................................................................

Verify that the Fibre Channel (FC) circuit packs have been installed into the required slot 1 of the Function Unit or Growth group (A, B, C, D, or G) at each NE providing service.

Reference:

Procedure 4-17: “Install Fibre Channel circuit packs” (p. 4-74)

.................................................................................................................................................................................................

Verify that the correct pluggable transmission modules have been installed for the ports being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the System View menu, expand the details for the Fibre Channel (FC) circuit pack. Select the pluggable transmission modules for the port being provisioned, then click

Select

.

Reference:

Procedure 4-15: “Install pluggable transmission modules” (p. 4-62)

.................................................................................................................................................................................................

Important! If the LNW73/LNW73C Fibre Channel circuit pack is already in service, the existing Data Type cannot be changed without removing all existing

VCG cross-connections.

PROVISION CIRCUIT PACK DATA TYPE

Determine the existing Data Type for the circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the System View menu, select the CP, then click

Select

. Note the Data Type.

.................................................................................................................................................................................................

If required, use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu, select the circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................................................

11-266 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-35: Establish LNW73/LNW73C FC-DPORT

SAN transport service on UPSR

9

10

11

12

13

14

Reference:

Procedure 11-36: “Provision LNW73/LNW73C FC-DPORT circuit pack parameters” (p. 11-271)

.................................................................................................................................................................................................

Verify/Select the

Data Type

(

FC-FICON

or

ESCON

). Click

Apply

, click

Close

to exit.

.................................................................................................................................................................................................

PROVISION CIRCUIT PACK PORT(S)

Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu, expand details for the circuit pack being provisioned.

Select the port being provisioned, then click

Select

. Provision port parameters as required.

Reference:

(p. 11-273)

Procedure 11-37: “Provision FC-DPORT DATA port parameters”

.................................................................................................................................................................................................

Click

Apply

, then click

Yes

to the warning message to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................

PROVISION VCGS

Use the

ed-vcg-data

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, if window is not already open from the previous step. Expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-38: “Provision FC-DPORT VCG parameters” (p. 11-277)

.................................................................................................................................................................................................

Click

Apply

, then click

Yes

, if required, to the warning message to execute the command. Click

Close

to exit.

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary cross-connections to be made at each terminating and non terminating node in the network.

Important! The rate and type of cross-connections made depend on the circuit pack Data Type setting (FC-FICON or ESCON) or the port GFP Enscapsulation

Type setting (FC, FICON, or ASYNC-FC) when the circuit pack Data Type setting is set to FC-FICON.

Virtual Concatenation Mode

must be

Enabled

for each VCG requiring more than one cross-connection.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-267

Ethernet/Data network provisioning procedures Procedure 11-35: Establish LNW73/LNW73C FC-DPORT

SAN transport service on UPSR

15

16

17

18

Reference:

Procedure 11-38: “Provision FC-DPORT VCG parameters” (p. 11-277)

Reference:

“Cross-Connections for LNW73/LNW73C FC-DPORT” (p. 11-282)

.................................................................................................................................................................................................

One at a time at each non terminating node in the network, use the TL1

ent-crs-sts1

,

ent-crs-sts3c

, or

ent-crs-sts12c

command to provision the pass-through cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard at each of the nodes in the network to provision the cross-connections.

Important! Note that cross-connections at the terminating nodes are add/drop and cross-connections at the non terminating nodes are pass-through.

Reference:

Procedure 11-39: “Make cross-connections for LNW73/LNW73C

FC-DPORT SAN transport service” (p. 11-280)

.................................................................................................................................................................................................

One at a time at each terminating node in the network, use the TL1

ent-crs-sts1

,

ent-crs-sts3c

, or

ent-crs-sts12c

command to provision the add/drop cross-connections. Or, select

Configuration

→

Cross-Connections

from the

System View menu to start the Cross-Connection Wizard. Use the Cross-Connection

Wizard at each of the nodes in the network to provision the cross-connections.

Reference:

Procedure 11-39: “Make cross-connections for LNW73/LNW73C

FC-DPORT SAN transport service” (p. 11-280)

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connections have been made.

.................................................................................................................................................................................................

Important! Each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG.

Use the TL1

ed-vcgtrib

command to enable tributaries, or from the System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

.................................................................................................................................................................................................................................

11-268 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

19

20

Procedure 11-35: Establish LNW73/LNW73C FC-DPORT

SAN transport service on UPSR

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-269

Ethernet/Data network provisioning procedures Procedure 11-35: Establish LNW73/LNW73C FC-DPORT

SAN transport service on UPSR

Figure 11-55 Point-to-point Fibre Channel service

Node A

M 1 M 2 M 1

OUT

IN

Node B

M 2

IN

OUT

D

V1 V2

V3

V4

LNW73

3

Circuit Pack Data Type = FC-FICON

Port 3 GFP Encapsulation Type = FC

Line Rate = 1G

UPSR Ring Add/Drop cross-connections m1-1-(1-19),d1-v3-(1-19)

2-Way Point-to-Point, Through cross-connections m1-1-(1-19),m2-1-(1-19)

2-Way UPSR Ring Add/Drop STS-1 cross-connections for point-to-point Fibre Channel (FC) service

M 2

Node D

M 1

OUT

IN

V1 V2

V3 V4

D

LNW73

3

Circuit Pack Data Type = FC-FICON

Port 3 GFP Encapsulation Type = FC

Line Rate = 1G

UPSR Ring Add/Drop cross-connections m1-1-(1-19),d1-v3-(1-19)

IN

M 2

Node C

M 1

OUT

2-Way Point-to-Point, Through cross-connections m1-1-(1-19),m2-1-(1-19)

MA-DMX-428-2

.................................................................................................................................................................................................................................

11-270 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-36: Provision LNW73/LNW73C FC-DPORT circuit pack parameters

.................................................................................................................................................................................................................................

Overview

This procedure provides a list of provisionable parameters for Data circuit packs.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating nodes.

•

The values to be set for each parameter.

Step

1

2

Use this procedure as a reference for provisioning Data circuit pack parameters.

.................................................................................................................................................................................................

Use the

ed-eqpt

TL1 command or select

Configuration

→

Equipment

from the

System View menu. Select the FC Data circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Use

Table 11-9, “ED-EQPT command provisionable parameters” (p. 11-272)

as reference to provision the necessary parameters from your work instructions.

E

N D O F

S

T E P S

ED-EQPT command parameters

Table 11-9, “ED-EQPT command provisionable parameters” (p. 11-272)

lists the provisionable parameters for the Data circuit packs:

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-271

Ethernet/Data network provisioning procedures Procedure 11-36: Provision LNW73/LNW73C FC-DPORT circuit pack parameters

Parameter

datatype

Table 11-9 ED-EQPT command provisionable parameters

Description

Data Type

.

Sets the protocol data type for the circuit pack.

Values for

Data Type

:

•

FC-FICON

— Fibre Channel (FC) and Fiber Connection

(FICON). In this mode, data ports can be configured individually for FC or FICON.

•

ESCON

— Enterprise Systems Connection (ESCON). In this mode, all ports on the circuit pack are set for ESCON.

Changing the value of datatype will cause the target data circuit pack to reset, which may take up to several minutes to complete.

Until the pack reset is complete, subsequent provisioning commands directed toward the pack may not complete and may cause a transient pack failure.

This parameter cannot be changed if there are any existing cross connections or loopbacks.

This parameter applies only to the LNW73/LNW73C circuit pack.

.................................................................................................................................................................................................................................

11-272 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-37: Provision FC-DPORT DATA port parameters

.................................................................................................................................................................................................................................

Overview

This procedure provides a list of provisionable parameters for the LNW73/LNW73C

FC-DPORT ports.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating nodes.

•

The values to be set for each parameter.

Step

1

2

3

Use this procedure as a reference for provisionable DATA port parameters.

.................................................................................................................................................................................................

Use the

ed-dport

TL1 command or select

Configuration

→

Equipment

from the

System View menu for the majority of parameters. Expand the details for the circuit pack, select (highlight) the DATA Port, then click

Select

.

Result:

Exceptions to provisioning parameters from the

Configuration

→

Equipment

command will be noted in this procedure.

Reference:

Appendix A, “Provisionable parameters”

.................................................................................................................................................................................................

Use

Table 11-10, “ED-DPORT command provisionable parameters” (p. 11-274)

as reference to provision the necessary DATA port parameters from your work instructions.

Important! Some of the parameters may have already been provisioned from earlier procedures for establishing service.

.................................................................................................................................................................................................

Use

Procedure 6-10: “Assign alarm severity assignment profile” (p. 6-41)

as a reference to provision ASAPs.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-273

Ethernet/Data network provisioning procedures Procedure 11-37: Provision FC-DPORT DATA port parameters

ED-DPORT command parameters

Table 11-10, “ED-DPORT command provisionable parameters” (p. 11-274)

lists the provisionable parameters for the

ed-dport

command:

Parameter

epmode eppm tcamd lnrate

Table 11-10 ED-DPORT command provisionable parameters

Description

Port Monitoring Mode

may have one of the following values:

•

AUTO (initial value)

•

NMON (not monitored)

When a port is provisioned in the AUTO state, it will automatically transition to the in-service (IS) state upon detection on the port of a valid input.

Data Port PM Enable

. Use the

Performance

→

Prov PM Settings

command from the System View menu to set this performance monitoring parameter to one of the following values:

•

Enable (initial value)

•

Disable

This parameter controls whether performance monitoring is enabled or disabled for the specified port.

TCA Monitoring Mode

. This parameter specifies whether performance monitoring Threshold Crossing Alert reporting is enabled or disabled for the port. Use the

Performance

→

Prov PM

Settings

command from the System View menu to set this performance monitoring parameter to one of the following values:

•

Enable

•

Disable (initial value)

TCA reporting will not begin until tcamd is enabled and port monitoring mode is enabled (eppm = Enabled), and the port is in service (epmode = IS).

Line Rate

. This parameter sets the line rate of the addressed port(s).

This parameter is valid when the circuit pack

Data Type

is set to

FC-FICON

.

Values:

•

1G

- 1.0625 Gbps (initial value)

•

2G

- 2.1250 Gbps.

2G rate is only supported on ports 1 and 3. In order to set port 1 to

2G, port 2 must not have a cross-connection and is unused. In order to set port 3 to 2G, port 4 must not have a cross-connection and is unused.

.................................................................................................................................................................................................................................

11-274 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-37: Provision FC-DPORT DATA port parameters

Parameter

admin rcf rcf-linkdown gfptype

Table 11-10 ED-DPORT command provisionable parameters (continued)

Description

Port Administration Control

. This parameter is used to enable/disable a port. It will enable/disable all frames to and from a port. Values:

•

ENABLE - Enables frames to/from port.

•

DISABLE - Disables frames to/from port.

Remote Client Fail

. This parameter enables/disables Remote Client

Fail message detection and generation.

Values:

•

ENABLE - Enables Remote Client Fail message (Initial Value)

•

DISABLE - Disables Remote Client Fail message.

This parameter must be enabled at both ends of the circuit in order to function.

Remote Client Fail Link Shutdown

. When rcf is enabled, this parameter controls link shutdown by Remote Client Fail message reception.

Values:

•

ENABLE - Enables link shutdown (Initial Value)

•

DISABLE - Disables link shutdown.

Link Loss Return (LLR) is a feature on some external equipment.

External equipment with LLR enabled will stop sending link pulses back to the LNW73/LNW73C if the LNW73/LNW73C has stopped transmitting link pulses to the external equipment due to a link shutdown performed by the Remote Client Fail Link Shutdown feature. Therefore, when the LNW73/LNW73C is connected to equipment that has the Link Loss Return feature enabled, the

Remote Client Fail Link Shutdown (rcf-linkdown) option should be disabled to avoid a link shutdown locking problem. Customers planning to use the CSF feature with RCF-Linkdown enabled should disable LLR on the external equipment.

GFP Encapsulation Type

. This parameter sets the User Payload

Identifier for GFP Client Frames. This parameter is valid when the circuit pack

Data Type

is set to

FC-FICON

.

Values:

•

FC

- Transparent Fibre Channel (initial value) Used for synchronous full rate

•

FICON

- Transparent FICON. Used for synchronous full rate.

•

ASYNC-FC

- Asynchronous Transparent Fibre Channel. Used for full and sub-rate rate, supports distance extension.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-275

Ethernet/Data network provisioning procedures Procedure 11-37: Provision FC-DPORT DATA port parameters

Parameter

sync_ping compr

Table 11-10 ED-DPORT command provisionable parameters (continued)

Description

Synchronous Ping

. This parameter enables/disables WAN ping in synchronous GFP. This parameter is valid when portgfptype is set to

FC

or

FICON

or when the circuit pack

Data Type

is set to

ESCON

.

Values:

•

Enabled

- Enables pinging. Enabling this parameter allows the measurement of the WAN propagation delay. Delay is retrievable by prop_delay in RTRV-DPORT or by Propagation

Delay in

View

→

Data

→

Ethernet/Data/VCG Port

.

•

Disabled

- Disables pinging (initial value).

Data Compression

. This parameter enables/disables data compression provisioning on an LNW73C port. This parameter is valid when port gfptype is set to

async-FC

.

Values:

•

Enable

- Enables data compression. Note: Data Compression is operational if both ends are provisioned for compression, cross-connections are provisioned across the network, and vcgtribs are enabled in both directions. The data compression operational status,

compro

, will only become enabled when the

VCG is operational between both ends (Data Port Status [pstat] value is

TRANS

[Transparent Operation] or

PRT-LNK-INIT

[Port

Link Initialization]).

•

Disable

- Disables data compression (initial value).

.................................................................................................................................................................................................................................

11-276 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-38: Provision FC-DPORT VCG parameters

.................................................................................................................................................................................................................................

Overview

This procedure provides a list of provisionable parameters for virtual concatenation groups (VCGs) on the LNW73/LNW73C FC-DPORT circuit pack.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating nodes.

•

The values to be set for each parameter.

Step

1

2

Use this procedure as a reference for provisioning VCG parameters.

.................................................................................................................................................................................................

Use the

ed-vcg-data

TL1 command or select

Configuration

→

Equipment

from the

System View menu for the majority of parameters. Expand the details for the circuit pack, select (highlight) the VCG port, then click

Select

.

Result:

Exceptions to provisioning parameters from the

Configuration

→

Equipment

command will be noted in this procedure.

Reference:

Appendix A, “Provisionable parameters”

.................................................................................................................................................................................................

Use

Table 11-11, “ED-VCG-DATA command provisionable parameters” (p. 11-278)

as reference to provision the necessary parameters from your work instructions.

Important! Some of the parameters may have already been provisioned from earlier procedures for establishing service or packet rings.

E

N D O F

S

T E P S

ED-VCG-DATA command parameters

Table 11-11, “ED-VCG-DATA command provisionable parameters” (p. 11-278)

lists the provisionable parameters for the ed-vcg-data command:

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-277

Ethernet/Data network provisioning procedures Procedure 11-38: Provision FC-DPORT VCG parameters

Parameter

vmode vpm lcasmd htmr wtr

Table 11-11 ED-VCG-DATA command provisionable parameters

Description

VCG Monitoring Mode

may have one of the following values:

•

AUTO - port automatically goes in-service (IS) when a valid input is received. Initial value.

•

NMON (not monitored)

VCG PM Enable

. This parameter controls when performance monitoring is enabled for the specified VCG. Use the

Performance

→

Prov PM

Settings

command from the System View menu to set this performance monitoring parameter to one of the following values:

•

Enable (initial value)

•

Disable

LCAS Mode

. This parameter controls whether LCAS (Link Capacity

Adjustment Scheme) is enabled for the specified VCG. When enabled, the LCAS protocol allows for hitless changes to the provisioned size of the VCG.

Values for LCAS Mode include:

•

ENABLE

•

DISABLE (initial value)

Note that ENABLE is valid only when

gfptype

(in RTRV-DPORT) is

ASYNC-FC

.

Hold-Off Timer

. This parameter, which is only in effect if

lcasmd

=

ENABLE, specifies the delay between when a tributary is detected faulty and when it is automatically removed from the VCG. It allows underlying protection, if any, to react first. It applies to all tributaries in the specified VCG.

Values:

•

0 to 10,000 ms (10 sec), in 100 millisecond steps

•

99,999 ms (representing infinity)

Initial value is 200 milliseconds.

Wait-to-Restore

. This parameter, which is only in effect if

lcasmd

=

ENABLE, specifies the delay between when a tributary, previously removed from the VCG because of fault, is detected to be normal and when it is automatically returned to the VCG. It applies to all tributaries in the specified VCG.

Values: 0 to 3600 seconds in 1 second steps. Initial value = 5.

.................................................................................................................................................................................................................................

11-278 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-38: Provision FC-DPORT VCG parameters

Parameter

vcat

Table 11-11 ED-VCG-DATA command provisionable parameters (continued)

Description

Virtual Concatenation Mode

. Specifies whether H4 is inserted/monitored for the specified VCG. It has effect only when a single trib, not VT, is cross-connected to the VCG, to allow interworking with non-VCAT equipment.

Valid values are

•

ENABLE (default)

•

DISABLE

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-279

Ethernet/Data network provisioning procedures

Procedure 11-39: Make cross-connections for LNW73/LNW73C

FC-DPORT SAN transport service

.................................................................................................................................................................................................................................

Overview

This procedure provides examples for making cross-connections for SAN transport service using the LNW73/LNW73C circuit pack.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Step

1

Use this procedure as an example for making cross-connections for SAN transport service.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

2

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Neighbor Map

command and note the NEs connected to Main 1 and Main 2.

Access each of the NEs identified and select the

Administration

→

OSI Neighbor

Map

command and note the NEs connected to Main 1 and Main 2.

Repeat the above until the backbone ring can be sketched.

For BLSR rings, you can select

View

→

Rings

→

Ring Map

from the System View menu, then select the 2F BLSR port protection group and click

Select

. Select

NVMRING in the Ring Map Source selection box. You may also Display Ring Map

Graph using this command.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

Result:

The OSI Neighbor Map window opens if the

Administration

→

OSI

Neighbor Map

command was used.

A list of NEs and NE neighbors is displayed if the

View

→

Rings

→

Ring Map

command was used.

.................................................................................................................................................................................................

3

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................................................

11-280 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-39: Make cross-connections for

LNW73/LNW73C FC-DPORT SAN transport service

4

5

6

7

8

9

10

.................................................................................................................................................................................................

From your work instructions, determine the cross-connections to be made at each node associated with the service to be established.

Although

Figure 11-59, “Point-to-point Fibre Channel service” (p. 11-285)

illustrates the use of TL1 commands, the cross-connection rate, type, and STSn AID addresses remain the same when using the Cross-Connection Wizard.

.................................................................................................................................................................................................

Starting at one of the nodes in the ring for the circuit being established, select

View

→

Cross-Connections

at each node in the ring to verify that the cross-connections specified on the work instructions may be made.

If cross-connections are already assigned or improperly assigned, refer trouble to the provisioning organization. Improperly assigned cross-connections may have to be deleted, or a different timeslot must be selected for the service being selected.

.................................................................................................................................................................................................

One at a time, at each non terminating node, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection

Wizard. Use the Cross-Connection Wizard at all non terminating nodes in the network to provision the STSn pass-through cross-connections for the Ethernet service being provided.

Reference:

“Cross-Connections for LNW73/LNW73C FC-DPORT” (p. 11-282)

.................................................................................................................................................................................................

One at a time, at each terminating node, select

Configuration

→

Cross-Connections

from the

System View

menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard at all terminating nodes in the network to provision the STSn add/drop cross-connections.

Reference:

“Cross-Connections for LNW73/LNW73C FC-DPORT” (p. 11-282)

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

at each node to verify that the proper connections have been made.

.................................................................................................................................................................................................

After all cross-connections are made, click on the

Alarm List

button on the System

View window and verify no alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-281

Ethernet/Data network provisioning procedures Procedure 11-39: Make cross-connections for

LNW73/LNW73C FC-DPORT SAN transport service

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

Cross-Connections for LNW73/LNW73C FC-DPORT

The rate and type of VCG cross-connections made depend on the circuit pack Data

Type setting (FC-FICON or ESCON) or the port GFP Enscapsulation Type setting (FC,

FICON, or ASYNC-FC) when the circuit pack Data Type setting is set to FC-FICON.

Data Type

:

ESCON

Whan Data Type is set to

ESCON

(Enterprise Systems Connection) all ports on the circuit pack support only ESCON.

ESCON mode supports only full-rate service requiring a minimum of 4 STS-1s (6

STS-1s may be required for other vendor equipment), or 2 STS-3c, or 1 STS-12c cross-connections. The ports will not carry any traffic end-to-end unless the full rate is provisioned.

Data Type

:

FC-FICON

When Data Type is set to

FC-FICON

, individual port

GFP Encapsulation Type

may be provisioned to support three separate data protocols:

•

FC

(Fibre Channel) - Supports full-rate 1Gbs (

1G

) or 2Gbs (

2G

) service using STS-1 or STS-3c cross-connections. The ports will not carry any traffic end-to-end unless the full rate is provisioned.

–

Line Rate

:

1G

- Full-rate 1G service requires a minimum of 19 STS-1s or 6

STS-3c (7 STS-3c may be required for other vendor equipment) cross-connections.

–

Line Rate

:

2G

- Full-rate 2G service requires a minimum of 37 STS-1s (38

STS-1s may be required for other vendor equipment) or 12 STS-3c (13 STS-3c may be required for other vendor equipment) cross-connections.

.................................................................................................................................................................................................................................

11-282 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-39: Make cross-connections for

LNW73/LNW73C FC-DPORT SAN transport service

The 2G rate only applies to ports 1 and 3. If 2G is selected for port 1(or 3), then port 2(or 4) cannot be used for service. For example, if 2G is selected for port 1 then port 2 is unused, and ports 3 and 4 could be 1G for either of the port gfptypes (FC, FICON, or ASYNC-FC).

•

FICON

(Fibre Connection) - Supports full-rate 1Gbs (

1G

) or 2Gbs (

2G

) service using

STS-1 or STS-3c cross-connections. The ports will not carry any traffic end-to-end unless the full rate is provisioned.

–

Line Rate

:

1G

- Full-rate 1G service requires a minimum of 19 STS-1s or 6

STS-3c (7 STS-3c may be required for other vendor equipment) cross-connections.

–

Line Rate

:

2G

- Full-rate 2G service requires a minimum of 37 STS-1s (38

STS-1s may be required for other vendor equipment) or 12 STS-3c (13 STS-3c may be required for other vendor equipment) cross-connections.

The 2G rate only applies to ports 1 and 3. If 2G is selected for port 1(or 3), then port 2(or 4) cannot be used for service. For example, if 2G is selected for port 3 then port 4 is unused, and ports 1 and 2 could be 1G for either of the port gfptypes (FC, FICON, or ASYNC-FC).

•

ASYNC-FC

(Asynchronous Fibre Channel) - Supports full-rate or partial-rate 1Gbs

(

1G

) or 2Gbs (

2G

) service using STS-1, STS-3c, or STS-12c cross-connections.

Service starts as soon as any end-to-end paths are established in both directions.

–

Line Rate

:

1G

- Full-rate 1G service requires a minimum of 19 STS-1s or 6

STS-3c (7 STS-3c may be required for other vendor equipment) cross-connections. If STS-12c is used, then only one STS-12c cross-connection is allowed.

If the compression feature of the LNW73C is used, it typically would take only

9 STS-1s to transport the equivalent of 1Gbs full rate service. The actual compression saving depends on the data transported.

–

Line Rate

:

2G

- Full-rate 2G service requires a minimum of 37 STS-1s (38

STS-1s may be required for other vendor equipment) or 12 STS-3c (13 STS-3c may be required for other vendor equipment) cross-connections. If STS-12c is used, then only one STS-12c cross-connection is allowed.

The 2G rate only applies to ports 1 and 3. If 2G is selected for port 1(or 3), then port 2(or 4) cannot be used for service. For example, if 2G is selected for port 1 then port 2 is unused, and ports 3 and 4 could be 1G for either of the port gfptypes (FC, FICON, or ASYNC-FC).

If the compression feature of the LNW73C is used, it typically would take only

18 STS-1s to transport the equivalent of 2Gbs full rate service. The actual compression saving depends on the data transported.

Cross-connections

Add/drop or pass-through cross-connections are established between the source and destination in a ring.

Figure 11-56, “2-Way Point-to-Point, Through cross-connection”

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-283

Ethernet/Data network provisioning procedures Procedure 11-39: Make cross-connections for

LNW73/LNW73C FC-DPORT SAN transport service

(p. 11-284)

illustrates a 2-way pass-through cross-connection from one side of the ring to the other.

Figure 11-56 2-Way Point-to-Point, Through cross-connection

2-Way Point-to-Point, Through

Main 1 (m1) Main 2 (m2)

NC-DMX-085-2

Figure 11-57, “UPSR Ring Add/Drop cross-connection” (p. 11-284)

illustrates an add/drop cross-connection on a UPSR ring.

Figure 11-57 UPSR Ring Add/Drop cross-connection

UPSR Ring Add/Drop

Main 1 (m1) Main 2 (m2)

VCG-n

A, B, C, D, G -1

A, B, C, D, G -2

EMPTY

NC-DMX-077-2

.................................................................................................................................................................................................................................

11-284 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-39: Make cross-connections for

LNW73/LNW73C FC-DPORT SAN transport service

Figure 11-58, “2F BLSR Add/Drop cross-connection” (p. 11-285)

illustrates an add/drop cross-connection on a BLSR ring.

Figure 11-58 2F BLSR Add/Drop cross-connection

M 1(2)

M 2(1)

A, B, C, D, G-1

VCGn

Solid lines depict normal working tributaries

Dashed lines depict protection tributaries when BLSR protection is active nc-dmx-235

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-285

Ethernet/Data network provisioning procedures Procedure 11-39: Make cross-connections for

LNW73/LNW73C FC-DPORT SAN transport service

Figure 11-59 Point-to-point Fibre Channel service

Node A

M 1 M 2 M 1

OUT

IN

Node B

M 2

IN

OUT

D

V1 V2

V3

V4

LNW73

3

Circuit Pack Data Type = FC-FICON

Port 3 GFP Encapsulation Type = FC

Line Rate = 1G

UPSR Ring Add/Drop cross-connections m1-1-(1-19),d1-v3-(1-19)

2-Way Point-to-Point, Through cross-connections m1-1-(1-19),m2-1-(1-19)

2-Way UPSR Ring Add/Drop STS-1 cross-connections for point-to-point Fibre Channel (FC) service

M 2

Node D

M 1

OUT

IN

V1 V2

V3 V4

D

LNW73

3

Circuit Pack Data Type = FC-FICON

Port 3 GFP Encapsulation Type = FC

Line Rate = 1G

UPSR Ring Add/Drop cross-connections m1-1-(1-19),d1-v3-(1-19)

IN

M 2

Node C

M 1

OUT

2-Way Point-to-Point, Through cross-connections m1-1-(1-19),m2-1-(1-19)

MA-DMX-428-2

.................................................................................................................................................................................................................................

11-286 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-40: Establish video multi-channel broadcast network on UPSR/BLSR (NOTAG mode)

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for configuring a distributed video broadcast network on a UPSR/BLSR ring using NOTAG tagging mode on the Ethernet circuit packs. See examples in

Figure 11-60, “Provisioning cross-connections for video broadcast on UPSR ring” (p. 11-295)

and

Figure 11-61, “Provisioning cross-connections for video broadcast on BLSR ring” (p. 11-295) .

Frames sent from the head end source node must be Multicast frames.

This procedure uses WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters.

This procedure assumes that the UPSR/BLSR SONET ring network configuration has already been established and no alarms are present.

Important! On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a

Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The shelf slots, circuit packs, ports, and VCGs being provisioned.

•

The number and type of cross-connections to be made at each node.

Important! This procedure is typically performed at full rate Gigabit service; full rate Gigabit service requires 21 STS-1 cross-connections. Ensure that you have a sufficient number of STS-1s available.

Ethernet circuit packs available for use with the NOTAG mode include the

LNW63, LNW67/68, LNW70, LNW71, and LNW74. This procedure illustrates applications of a multi-channel broadcast network using 1 GbE rate (21 STS1s or equivalent) which requires the use of the LNW63, LNW67/68 or LNW70 circuit

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-287

Ethernet/Data network provisioning procedures Procedure 11-40: Establish video multi-channel broadcast network on UPSR/BLSR (NOTAG mode) packs. Applications using lower bandwidth may be provisioned similarly using the

LNW71 or LNW74 circuit packs which support 2 to 3 STS1s. All circuit packs involved in the network must support the same cross-connection types and rate being used.

Step

1

2

3

4

5

Use this procedure as an example for configuring a multi-channel video broadcast network.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to one of the terminating nodes, if not already performed.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

and/or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

This command may take several minutes to complete depending on the size of the network.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the terminating nodes, circuit packs, LAN ports, WAN (VCG) ports, and cross-connections associated with the service being established.

.................................................................................................................................................................................................

Verify that the Ethernet circuit packs have been installed into the required slot 1 of the

Function Unit or Growth group (A, B, C, D, or G) at each NE providing Ethernet service.

.................................................................................................................................................................................................................................

11-288 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-40: Establish video multi-channel broadcast network on UPSR/BLSR (NOTAG mode)

6

Reference:

Procedure 4-13: “Install Gigabit Ethernet circuit packs” (p. 4-54)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

If the Ethernet circuit pack is already providing service, changing tagging mode will take down any existing service. The existing tagging mode cannot be changed without removing all existing cross-connections and virtual switch provisioning.

CONFIGURE TAGGING MODE

At each NE providing this Ethernet service, determine the existing tagging mode for the Ethernet circuit pack being provisioned. Use the TL1

rtrv-eqpt

command or select

View

→

Equipment

from the System View menu, select the CP, then click

Select

. Note the VLAN Tagging Mode and other parameter values.

The VLAN Tagging Mode for the LNW67/68/70 circuit packs must be set to

NOTAG

.

The VLAN Tagging Mode for the LNW63/71/74 circuit packs is

NOTAG

only and does not require setting.

Important! When GbE circuit packs are installed in the shelf, the default

″

NOTAG

″ mode is assigned to the circuit pack.

.................................................................................................................................................................................................

7

If...

the tagging mode and all parameters are set correctly, the tagging mode is set correctly but other parameters are not correct, the tagging mode is NOT set correctly,

Then...

Proceed to

Step 13 .

Proceed to

Step 10 .

Continue with

Step 8 .

8

.................................................................................................................................................................................................

If you are going to change the VLAN Tagging Mode that presently exists AND cross-connections already exist, you must remove service and delete the existing cross-connections before changing the tagging mode.

Determine if cross-connections exist for the circuit packs being used. Use the TL1

rtrv-crs

command or select the

View

→

Cross-Connections

command from the

System View menu, select the circuit pack being provisioned, then click

Select

. Note if cross-connections exist.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-289

Ethernet/Data network provisioning procedures Procedure 11-40: Establish video multi-channel broadcast network on UPSR/BLSR (NOTAG mode)

9

10

11

12

13

14

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once cross-connections and a virtual switch is created and service has been established on the circuit pack, you cannot delete the cross-connections/virtual switch without interrupting service.

If required, remove existing service, then use the TL1

dlt-crs

command or select the

Configuration

→

Cross-Connections

command from the System View menu to start the Cross-Connection Wizard. Use the Cross-Connection Wizard to delete all cross-connections on the circuit pack.

.................................................................................................................................................................................................

Provision circuit pack parameters. Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu, select the circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Verify/Select the tagging mode (

NOTAG

) in the VLAN Tagging Mode box.

.................................................................................................................................................................................................

Verify/Enter other parameter values (for example,

Burst Size

,

Credit Interval

[LNW67/68],

Ethernet Cross Connect Mode

and

Port Configuration

[LNW70]), as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

END OF STEPS TO PROVISION CIRCUIT PACKS

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary STS-1 or equivalent cross-connections to be made at the head end node, each Ethernet terminating node, and any pass through cross-connections to be made at any non terminating nodes in the network. See

Figure 11-60, “Provisioning cross-connections for video broadcast on UPSR ring” (p. 11-295)

and

Figure 11-61,

“Provisioning cross-connections for video broadcast on BLSR ring” (p. 11-295)

for examples.

.................................................................................................................................................................................................

One at a time at each node in the network, select

Configuration

→

Cross-

Connections

from the System View menu to start the Cross-Connection Wizard.

Select

Create a new Cross-Connections

, then click

Next

at the bottom of the screen.

.................................................................................................................................................................................................................................

11-290 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-40: Establish video multi-channel broadcast network on UPSR/BLSR (NOTAG mode)

15

16

17

18

19

Reference:

(p. 11-195) .

Procedure 11-24: “Make cross-connections for Ethernet service”

.................................................................................................................................................................................................

Use the Cross-Connection Wizard at each non terminating node to provision the

2-Way

Point-to-Point, Through

cross-connections for a UPSR ring or

1-Way Point-to-Point,

Through

cross-connections for a BLSR ring.

.................................................................................................................................................................................................

Use the Cross-Connection Wizard at the head end source node to provision the

Ethernet one-way (

1-Way Point-to-Point

) cross-connections.

.................................................................................................................................................................................................

Use the Cross-Connection Wizard at the remote terminating nodes to provision the

1-Way Path Protected Drop from a UPSR Ring

cross-connections from a UPSR ring, or

1-Way Point-to-Point

cross-connections from a BLSR ring, and

2-Way

Point-to-Point, Through

cross-connections for a UPSR ring or

1-Way Point-to-Point,

Through

cross-connections for a BLSR ring.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

to verify that the proper cross-connections have been made.

.................................................................................................................................................................................................

Important! For LNW63/70/74 circuit packs, each tributary cross-connected to a

VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been Enabled in the Input or Ouput Direction, as required.

If required, use the TL1

ed-vcgtrib

command to enable tributaries, or from the

System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-291

Ethernet/Data network provisioning procedures

20

21

22

23

24

Procedure 11-40: Establish video multi-channel broadcast network on UPSR/BLSR (NOTAG mode)

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

After all cross-connections are made at each node in the ring, click on the

Alarm List

button on the System View window and verify no new alarms are present.

.................................................................................................................................................................................................

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

VERIFY PORT MONITORING MODE

After all cross-connections have been made at each node in the ring, verify that the

WAN (VCG) Ports being used have gone in service (IS) at each terminating node.

From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Important! Note that the VCG port at the head end source node will not show in-service since it is not provisioned to receive packets.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Click on the

Fault/Alarms

tab. Verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, click

Close

to exit then proceed to

Step 25 .

•

If the VCG Monitoring Mode is

NMON

(Not Monitored),

.................................................................................................................................................................................................................................

11-292 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-40: Establish video multi-channel broadcast network on UPSR/BLSR (NOTAG mode)

25

26

Perform the following:

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

Fault/Alarms

tab, select

AUTO

for the

VCG Monitoring Mode

.

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 22 .

•

If the VCG Monitoring Mode is

AUTO

:

Verify that the VCG Trib Membership provisioning is correct. Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

If proper cross-connections have been made, then indications are that either the far end or near end circuit pack at each end of the span has failed or must be reset. If

the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Select

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far end and near end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

PROVISION LAN PORTS

Use the TL1

ed-eport

command to provision the LAN port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the LAN Port (for example, Port 1), then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

PROVISION VCGS

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-293

Ethernet/Data network provisioning procedures Procedure 11-40: Establish video multi-channel broadcast network on UPSR/BLSR (NOTAG mode)

Use the

ed-vcg

TL1 command to provision the WAN (VCG) port parameters, or select

Configuration

→

Equipment

from the System View menu, expand the details for the circuit pack, highlight the VCG port, then click

Select

. Provision the parameters as required.

Reference:

Procedure 11-12: “Provision Ethernet VCG parameters” (p. 11-86)

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

11-294 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-40: Establish video multi-channel broadcast network on UPSR/BLSR (NOTAG mode)

Figure 11-60 Provisioning cross-connections for video broadcast on UPSR ring

Head End Source

Node A

M 2 M 1

GbE

1

V1

D

Cross-Connection Wizard commands

Type of Connections: 1-Way Point-to-Point

Source AID: d1-v1-1+, Destination AID: m1-1-1+

Source AID: d1-v1-1+, Destination AID: m2-1-1+

Rate: STS1

Range: 21 (STS1s)

M 1

Node B

M 2

M 1

Node X

M 2

M 1

Node C

M 2

GbE

V1

C

1

V2

D

2

STS1 2-Way Point-to-Point, Through

Source AID: m1-1-1, Destination AID: m2-1-1

Range: 21 (STS1s)

Nodes B

Cross-Connection Wizard commands

Type of Cross-connections: 1-Way Path Protected Drop from a UPSR Ring

Source AID: m1-1-1+, Destination AID: c1-v1-1+

Source AID: m1-1-1+, Destination AID: d1-v2-1+

Rate: STS1

Range: 21 (STS1s)

V1

GbE

1 2

V2

Cross-Connection Wizard commands

D

Type of Cross-connections: 1-Way Path Protected Drop from a UPSR Ring

Source AID: m1-1-1+, Destination AID: d1-v1-1+

Source AID: m1-1-1+, Destination AID: d1-v2-1+

Rate: STS1

Range: 21 (STS1s)

Type of Cross-connection: 2-Way Point-to-Point, Through

Source AID: m1-1-1+, Destination AID: m2-1-1+

Rate: STS1

Range: 21 (STS1s)

Type of Cross-connection: 2-Way Point-to-Point, Through

Source AID: m1-1-1+, Destination AID: m2-1-1+

Rate: STS1

Range: 21 (STS1s)

MA-DMX-444

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-295

Ethernet/Data network provisioning procedures Procedure 11-40: Establish video multi-channel broadcast network on UPSR/BLSR (NOTAG mode)

Figure 11-61 Provisioning cross-connections for video broadcast on BLSR ring

Head End Source

Node A

M 2 M 1

M 1

Node B

M 2

V1 V2 V3 V4

D

GbE

1 2

Cross-Connection Wizard commands

Type of Cross-connection: 1-Way

Point-to-Point

Source AID: d1-v1-1+

Destination AID: m2-1-1+

Rate: STS1

Range: 21 (STS1s)

Circuit Identifier: If required

Destination NE Name: NodeC

Video Broadcast Ring

M 1

Node X

M 2

M 1

Node C

M 2

D

GbE

V1

1

V2

V3

2

V4

Cross-Connection Wizard commands

Type of Cross-connections: 1-Way

Point-to-Point

Source AID: m1-1-1+, Destination AID: d1-v1-1+

Source AID: m1-1-1+, Destination AID: d1-v3-1+

STS1 1-Way Point-to-Point, Through m1-1-(1-21),m2-1-(1-21)

Source NE Name: NodeA

Destination NE Name: NodeC

Rate: STS1

Range: 21 (STS1s)

VT Accessed: NO

Rate: STS1

Range: 21 (STS1s)

Circuit Identifier: If required

Source NE Name: NodeA

Type of Cross-connection: 1-Way Point-to-Point, Through

Source AID: m1-1-1+, Destination AID: m2-1-1+

Rate: STS1

Range: 21 (STS1s)

Circuit Identifier: If required

Source NE Name: NodeA

Destination NE Name: NodeC

VT Accessed: NO

D

V1 V2

GbE 1

V3 V4

2

Cross-Connection Wizard commands

Type of Cross-connection: 1-Way

Point-to-Point

Source AID: m1-1-1+, Destination AID: d1-v1-1+

Rate: STS1

Range: 21 (STS1s)

Circuit Identifier: If required

Source NE Name: NodeA

MA-DMX-443

.................................................................................................................................................................................................................................

11-296 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-41: Provision Resilient Packet Ring

(RPR)-capable VCG parameters

.................................................................................................................................................................................................................................

Overview

This procedure provides a list of provisionable parameters for a Resilient Packet Ring

(RPR)-capable VCG port.

RPR Span VCGs may be either VCG v1 or VCG v2. The RPR IF VCG is VCG v1.

The

ed-vcg-rpr

TL1 command is used to modify (edit) the RPR-capable properties of a port. An RPR instance consists of an Interface (IF) containing the common part (IF), and two directional Spans.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The values to be set for each parameter.

Step

1

2

Use this procedure as a reference for provisioning parameters for a Resilient Packet

Ring (RPR)-capable VCG port.

.................................................................................................................................................................................................

Use the

ed-vcg-rpr

TL1 command or select

Configuration

→

Equipment

from the

System View menu. Expand the details of the LNW78 100/1G-FSR circuit pack, select the VCG being provisioned, then click

Select

.

.................................................................................................................................................................................................

Use

Table 11-12, “ED-VCG-RPR command provisionable parameters” (p. 11-298)

as reference to provision the necessary parameters from your work instructions.

All parameters are for the RPR IF (VCG v1) unless indicated as an RPR span (VCG v1 or VCG v2) parameter.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-297

Ethernet/Data network provisioning procedures Procedure 11-41: Provision Resilient Packet Ring

(RPR)-capable VCG parameters

ED-VCG-RPR command parameters

Table 11-12, “ED-VCG-RPR command provisionable parameters” (p. 11-298)

lists the provisionable parameters for a Resilient Packet Ring (RPR)-capable VCG port:

Parameter

mtu_size vmode tagfilter vcat ifmode

Table 11-12 ED-VCG-RPR command provisionable parameters

Description

MTU size (bytes)

. This parameter specifies the MTU (Maximum

Transmission Unit) size supported on the port, addressed by the aid.

This is the size of the payload in the Ethernet frame, excluding

Source and Destination Address, Type and CRC field, but including all VLAN tags. Value: An integer in the range 46 to 10222. The initial value is 1508.

VCG Monitoring Mode

. May have one of the following values:

•

AUTO - port automatically goes in-service (IS) when a valid input is received.

•

NMON (not monitored)

This is an RPR Span parameter.

Tag Filtering

. The Tag Filter parameter is used to enable tag filtering. Valid value is ENABLE (filters tags allowed on the port).

Virtual Concatenation Mode

. Specifies whether vcat overhead information is inserted/monitored for the specified VCG. It has effect only when a single trib is cross-connected to the VCG, to allow interworking with non-VCAT equipment.

Valid values are:

•

ENABLE (default)

•

DISABLE vcat cannot be set to DISABLE if more than one tributary cross-connection exists on the VCG.

This is an RPR Span parameter.

RPR IF Monitoring Mode

. May have one of the following values:

•

AUTO - port automatically goes in-service (IS) when a valid input is received on at least one associated span.

•

NMON - not monitored

.................................................................................................................................................................................................................................

11-298 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-41: Provision Resilient Packet Ring

(RPR)-capable VCG parameters

Parameter

addporttag delporttag vpm ethertype

Table 11-12 ED-VCG-RPR command provisionable parameters (continued)

Description

Add Port Tag

. Composite list of Port Tag values to be added. Up to

55 Port Tag values can be provisioned in a single command.

Values: An ampersand-separated list of Port Tag identifiers, where each Port Tag identifier is an integer in the range 1 to 4093. The initial status of this list is empty.

Either the

addporttag

or

delporttag

parameters can be provisioned by this command, but not both. They must be provisioned in separate command instances.

This parameter is valid when

vlantagmd

is set to SWITCHED (see

ED-EQPT) and the port belongs to a virtual switch with

tagmd

set to TRANS). To be able to delete a port tag, MAC+tag address provisioning must be removed first from the port.

Delete Port Tag

. Composite list of Port Tag values to be deleted. Up to 55 Port Tag values can be provisioned in a single command.

Values: An ampersand-separated list of Port Tag identifiers, where each Port Tag identifier is an integer in the range 1 to 4093. The initial status of this list is empty.

Either the

addporttag

or

delporttag

parameters can be provisioned by this command, but not both. They must be provisioned in separate command instances.

This parameter is valid when

vlantagmd

is set to SWITCHED (see

ED-EQPT) and the port belongs to a virtual switch with

tagmd

set to TRANS). To be able to delete a port tag, MAC+tag address provisioning must be removed first from the port.

VCG Performance Monitoring (PM)

. This parameter controls whether performance monitoring is enabled for the specified VCG. It controls the IF and both spans. Values:

Values:

•

ENABLE (initial value)

•

DISABLE

Ethernet Type field (TPID)

. Used to interwork with other vendors’ equipment using stacked VLAN. This parameter is valid only when

vlantagmd

is set to SWITCHED and the port belongs to a virtual switch with

tagmd

set to TRANS.

Value: A hexadecimal string in the range 0601 to FFFF. The initial value is FFFF (hexadecimal).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-299

Ethernet/Data network provisioning procedures Procedure 11-41: Provision Resilient Packet Ring

(RPR)-capable VCG parameters

Parameter

qsz qminthldy qmaxthldy qminthldg qdropwt1 qdropwt2 qdropwt3

Table 11-12 ED-VCG-RPR command provisionable parameters (continued)

Description

Port queue size

. This parameter applies to the A, B, and C add queues.

Value: An integer in the range 0 to 256, representing Kbytes. Initial value is 256.

Minimum drop threshold for yellow packets

. This parameter is used by the drop algorithm. It is expressed as a percentage of the queue size,

qsz

. Value: an integer between 0 and 100. The initial value is

33.

qminthldy

must be

≤

qmaxthldy

.

Maximum drop threshold for yellow packets

. This parameter is used by the drop algorithm. It is expressed as a percentage of the queue size,

qsz

. Value: an integer between 0 and 100. The initial value is

50.

qmaxthldy

must be

≥

qminthldy

and

≤

qminthldg

.

Minimum drop threshold for green packets

. This parameter is used by the drop algorithm. It is expressed as a percentage of the queue size,

qsz

. Value: an integer between 0 and 100. The initial value is

90.

qminthldg

must be

≥

qmaxthldy

.

Maximum drop probability mark for CoS 1 (Class C) packets

. This parameter is used by the drop algorithm. It is expressed as a percentage. Value: an integer between 0 and 100. The initial value is 100.

qdropwt1

must be

≥

qdropwt2

>=

qdropwt3

.

Maximum drop probability mark for CoS 2 (Class B) packets

. This parameter is used by the drop algorithm. It is expressed as a percentage. Value: an integer between 0 and 100. The initial value is 100.

qdropwt1

must be

≥

qdropwt2

≥

qdropwt3

.

Maximum drop probability mark for CoS 3 (Class A) packets

. This parameter is used by the drop algorithm. It is expressed as a percentage. Value: an integer between 0 and 100. The initial value is 50.

qdropwt1

must be >=

qdropwt2

>=

qdropwt3

.

.................................................................................................................................................................................................................................

11-300 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-42: Provision Resilient Packet Ring

(RPR)-specific VCG parameters

.................................................................................................................................................................................................................................

Overview

This procedure provides a list of provisionable Resilient Packet Ring (RPR)-specific parameters for a VCG port.

RPR Span VCGs may be either VCG v1 or VCG v2. The RPR IF VCG is VCG v1.

The

ed-rpr

TL1 command is used to modify (edit) the RPR-specific properties of a port. An RPR instance consists of an Interface (IF) containing the common part (IF), and two directional Spans.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the terminating Ethernet nodes.

•

The values to be set for each parameter.

Step

1

2

Use this procedure as a reference for provisioning Resilient Packet Ring (RPR)-specific parameters for a VCG port.

.................................................................................................................................................................................................

Use the

ed-rpr

TL1 command or select

Configuration

→

Equipment

from the

System View menu. Expand the details of the LNW78 100/1G-FSR circuit pack, select the VCG being provisioned, then click

Select

.

.................................................................................................................................................................................................

Use

Table 11-13, “ED-RPR command provisionable parameters” (p. 11-302)

as reference to provision the necessary parameters from your work instructions.

All parameters are for the RPR IF (VCG v1) unless indicated as an RPR span (VCG v1 or VCG v2) parameter.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-301

Ethernet/Data network provisioning procedures Procedure 11-42: Provision Resilient Packet Ring

(RPR)-specific VCG parameters

ED-RPR command parameters

Table 11-13, “ED-RPR command provisionable parameters” (p. 11-302)

lists the

Resilient Packet Ring (RPR) provisionable parameters for a port:

Parameter

enh_brdgmd

Table 11-13 ED-RPR command provisionable parameters

Description

Enhanced Bridging Mode.

Values are:

•

ENABLE (initial value). When enabled, the RPR bridge learns

RPR node addresses to obtain spatial reuse.

•

DISABLE. When disabled, 802.17 “basic” bridging is used.

ptqsize stqsize

Primary Transit Queue Size (bytes)

. Value: an integer in the range

2000 to 51200, in number of bytes. Initial value is 5000.

Secondary Transit Queue Size (bytes)

. Value: an integer in the range 2000 to 4194304, in number of bytes. Initial value is

1800000.

stqfullthr prot_wtr prot_fasttmr prot_slowtmr prot_katmr

Secondary Transit Queue Full Threshold (bytes)

. The STQ occupancy above which secondary transit traffic has priority over any add traffic. Value: an integer in the range 2000 - 4194304, in number of bytes. Initial value is 1795000.

RPR Protection Wait-to-Restore (sec)

. After a fault clears, the protected state is maintained for the duration of this timer.

Value: an integer in the range of 0 to 1440 representing seconds.

The initial value is 0.

RPR Protection Fast Timer (msec)

. The interval between fast

Topology and Protection messages.

Value: an integer in the range of 1 to 20 representing milliseconds.

The initial value is 10.

RPR Protection Slow Timer (50 msec unit)

. The interval between slow Topology and Protection messages.

Value: an integer in the range of 1 to 200 representing 50 milliseconds. The initial value is 20, which equals to 1 second.

RPR Protection Keep Alive Timer (msec)

. The timer after which a span is declared failed if no Single-Choke Fairness message is received.

Value: an integer in the range of 2 to 50 representing milliseconds.

The initial value is 3.

.................................................................................................................................................................................................................................

11-302 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-42: Provision Resilient Packet Ring

(RPR)-specific VCG parameters

Parameter

atd_tmr tstab_tmr fair_ramp fair_lp fair_advert fair_stqhi fair_stqlo fair_agec

Table 11-13 ED-RPR command provisionable parameters (continued)

Description

Attribute Discovery (ATD) Timer (50 msec unit)

. The period between

ATD messages.

Value: an integer in the range of 1 to 200 representing 50 milliseconds units. The initial value is 20, which equals to 1 second.

Topology Stability Timer (msec)

. The period for determining topology stabilization.

Value: an integer in the range of 10 to 100 representing milliseconds. The initial value is 40.

Fairness Ramp Coefficient

. The coefficient for ramping up an allowed rate.

Value: an integer in the range of 4 to 9 representing the logarithm of the actual coefficient. The initial value is 6.

Fairness Low Pass Coefficient

. The relative weight of the low-pass filter rate counters in successive aging intervals.

Value: an integer in the range of 4 to 11 representing the logarithm of the actual coefficient. The initial value is 6.

Fairness Advertisement Ratio (units of 0.00025)

. The ratio between bandwidth for fairness control messages and total link capacity.

Value: an integer in the range of 1 to 40 in units of 0.00025. The initial value is 5.

Fairness STQ High Threshold

. Maximum STQ occupancy above which fairness-elegible add frames are no longer admitted to the ring.

Value: an integer in the range of 0 to 1000 representing tenths of percent of

stqfullthr

. The initial value is 250.

Fairness STQ Low Threshold

. STQ occupancy above which congestion of the outbound link is imminent.

Value: an integer in the range of 0 to 1000 representing tenths of percent of

fair_stqhi

. The initial value is 500.

Fairness Aging Coefficient

. Controls the amount of history kept in a rate estimator.

Value: an integer in the range of 0 to 4 representing the logarithm of the actual coefficient. The initial value is 2.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-303

Ethernet/Data network provisioning procedures Procedure 11-42: Provision Resilient Packet Ring

(RPR)-specific VCG parameters

Parameter

rsv_a rsv_b

Table 11-13 ED-RPR command provisionable parameters (continued)

Description

Reserved Class A Add Rate (Mb/sec)

. The maximum rate at which

Class A traffic is allowed to be added to each ringlet. It controls the Class A shaper. This is an RPR Span parameter.

Value: an integer in the range of 0 to 1200 in units of Mb/s. The initial value is 0.

Reserved Class B Add Rate (Mb/sec)

. The maximum rate at which

Class B traffic is allowed to be added to each ringlet. It controls the Class B shaper. This is an RPR Span parameter.

Value: an integer in the range of 0 to 1200 in units of Mb/s. The initial value is 0.

.................................................................................................................................................................................................................................

11-304 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-43: Bridge and roll Ethernet cross-connections

.................................................................................................................................................................................................................................

Overview

CAUTION

Service disruption hazard

Service interruption of up to 10 ms for STS cross-connections or 25 ms for VT cross-connections may occur when an existing source is rolled to a new source. In cases involving roll procedures from Main 2 cross-connections to function slot ports, the service interruption may be as high as 200 ms.

Use this procedure to move traffic to another circuit path. Traffic can be moved from the existing tributary to another tributary on:

• the same set of interconnecting facilities.

• a different set of interconnecting facilities.

Traffic is moved using a coordinated sequence of bridging and rolling cross-connection legs at the terminating (add/drop) nodes and provisioning new cross-connections at pass-through nodes (UPSRs/BLSRs only).

At the head-end terminating node of a 1-way circuit, the existing add cross-connection leg is bridged to the new destination tributary allowing traffic to be added to the new circuit path.

At the tail-end terminating node of the 1-way circuit, the existing drop cross-connection leg is rolled to the new source tributary allowing traffic to be switched to the new circuit path.

For 2-way circuits, traffic in one direction of transmission is moved to the new circuit path, then the traffic in the opposite direction of transmission is moved to the new circuit path.

Bridging cross-connection legs

Cross-connection legs are bridged at the head-end terminating node of a 1-way circuit to move traffic to the new circuit path. Bridged cross-connection legs allow a single source tributary to be cross-connected to multiple destination tributaries at the same rate.

At the head-end terminating node of a 1-way circuit, the existing add cross-connection leg is bridged using 1-Way Point-to-Point or 1-Way Path Protected Drop from a UPSR

Ring cross-connections.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-305

Ethernet/Data network provisioning procedures Procedure 11-43: Bridge and roll Ethernet cross-connections

Rolling cross-connection legs

Cross-connection legs are rolled at the tail-end terminating node of a 1-way circuit to switch traffic from the existing circuit path to the new circuit path. The source tributary of the existing drop cross-connection is switched to the new source tributary at the same rate.

Guidelines for provisioning the circuit ID parameter

When bridging/rolling cross-connection legs use the following guidelines to provision the circuit ID parameter.

•

If an existing cross-connection has (or does not have) a circuitid value, and you want the new circuit to have a different or new circuitid value

(circuitid=some_other_value), then specify circuitid=some_other_value in the bridge command. Then, specify the same circuitid=some_other_value in the roll command.

•

If an existing cross-connection does not have a circuitid value, and you do not want the new circuit to have a circuitid value, then do not specify a circuitid value in the bridge command. Then, do not specify a circuitid value in the roll command.

•

If an existing cross-connection has a circuitid value and you want the new circuit to have the same circuitid value, then specify the same circuitid value in the bridged cross-connection. Then, do not specify a circuitid value in the roll command.

•

If an existing cross-connection has a circuitid value and you do not want the new circuit to have a circuitid value, then do not specify a circuitid value in the bridge command. Then, specify a null value for the circuitid (circuitid=

″″

) in the roll command.

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Before you begin this procedure, you must:

1. Refer to

“Before you begin” (p. 10-2)

and

“Required equipment” (p. 10-2)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure.

.................................................................................................................................................................................................................................

11-306 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-43: Bridge and roll Ethernet cross-connections

4. Verify that the work instructions specify the existing circuit path including terminating (add/drop) nodes, pass-through nodes (UPSRs/BLSRs only), cross-connections, and port/tributary addresses.

5. Verify that the work instructions specify the new circuit path including port/tributary addresses, cross-connections, and pass-through nodes (UPSRs/BLSRs only).

Step

1

2

3

4

Complete the following steps to move traffic to another circuit path.

.................................................................................................................................................................................................

Important! For 2-way circuits, traffic in one direction of transmission is moved to the new circuit path, then the traffic in the opposite direction of transmission is moved to the new circuit path.

Using the work instructions, determine whether the circuit to be moved is 1-way or

2-way. If the circuit to be moved is 2-way, identify the direction of transmission to be moved first.

.................................................................................................................................................................................................

Identify and log in to the terminating (add/drop) nodes.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Identify and record the existing interconnecting facilities and the new interconnecting facilities (if required). If required, at the terminating (add/drop) nodes select

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the interconnecting facilities is not provided with the work instructions, it is recommended that you draw a simple diagram and list each node’s TID.

.................................................................................................................................................................................................

Important! If the Port Monitoring Mode parameter is AUTO, the port automatically transitions to the in service state if a valid signal is detected and the port is monitored/alarmed. If the Port Monitoring Mode is NMON, the port is not monitored/alarmed, and the port will not automatically transition to the in service state if a valid signal is detected. No alarm reporting creates the possibility of service degradation or service outage if the new circuit path has a defect.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-307

Ethernet/Data network provisioning procedures Procedure 11-43: Bridge and roll Ethernet cross-connections

5

At each terminating (add/drop) and pass-through node (UPSRs/BLSRs only), select

View

→

Equipment

and verify that all circuit packs, pluggable transmission modules, ports, and protection groups have been provisioned at each node.

If required, refer to

Chapter 4, “Install and provision circuit packs/OLIUs procedures”

to perform additional installation and provisioning.

.................................................................................................................................................................................................

Important! Before moving traffic to the new circuit path, new cross-connections must be created at pass-through nodes (UPSRs/BLSRs only).

If moving a...

1-way circuit,

2-way circuit,

Then at each pass-through node

(UPSRs/BLSRs only)...

select

Configuration

→

Cross-Connections

to access the Cross-Connection Wizard and create the required new

1-Way

Point-to-Point, Through

cross-connection.

select

Configuration

→

Cross-Connections

to access the Cross-Connection Wizard and create the required new

2-Way

Point-to-Point, Through

cross-connection.

6

7

8

.................................................................................................................................................................................................

At each pass-through node (UPSRs/BLSRs only), select

View

→

Cross-Connections

to access the cross-connection list and verify that the required pass-through cross-connection was created.

.................................................................................................................................................................................................

Important! If the Tributary Monitoring Mode parameter is AUTO, the tributary automatically transitions to the in service state if a valid signal is detected and the tributary is monitored/alarmed. If the Tributary Monitoring Mode is NMON, the tributary is not monitored/alarmed, and the tributary will not automatically transition to the in service state if a valid signal is detected.

At each pass-through node (UPSRs/BLSRs only), select

View

→

Equipment

and verify the new Tributary parameters.

If required, use

Configuration

→

Equipment

and refer to

Chapter 4, “Install and provision circuit packs/OLIUs procedures”

to perform additional provisioning.

.................................................................................................................................................................................................

Important! At the head-end terminating node of the 1-way circuit, the traffic to be moved must be bridged to the new tributary. In UPSRs, the traffic to be moved

.................................................................................................................................................................................................................................

11-308 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-43: Bridge and roll Ethernet cross-connections must be bridged to the same new tributary on Main/Function/Growth 1 and

Main/Function/Growth 2.

At the head-end node of the 1-way circuit, select

Configuration

→

Cross-

Connections

to access the Cross-Connection Wizard. Select

Bridge a crossconnection from a source to multiple destinations

and follow the directions to bridge the add cross-connection leg to the required new destination tributary(ies).

The following figure shows an example of an add cross-connection leg bridged to new destination tributaries within a UPSR.

Existing tributary New tributary

Bridge

M2

M1

MA-DMX-309

9

10

11

.................................................................................................................................................................................................

At the head-end node of the 1-way circuit, select

View

→

Cross-Connections

to access the cross-connection list and verify that the required add cross-connection leg was bridged to the new destination tributary(ies).

.................................................................................................................................................................................................

Important! If the Tributary Monitoring Mode parameter is AUTO, the tributary automatically transitions to the in service state if a valid signal is detected and the tributary is monitored/alarmed. If the Tributary Monitoring Mode is NMON, the tributary is not monitored/alarmed, and the tributary will not automatically transition to the in service state if a valid signal is detected.

At the head-end node of the 1-way circuit, select

View

→

Equipment

and verify the new Tributary parameters.

If required, use

Configuration

→

Equipment

and refer to

Chapter 4, “Install and provision circuit packs/OLIUs procedures”

to perform additional provisioning.

.................................................................................................................................................................................................

At each terminating (add/drop) and pass-through node (UPSRs/BLSRs only), click the

Alarm List

button or select

Fault

→

NE Alarm List

from the System View menu to obtain an NE Alarm List and verify that no alarms are present. Clear all alarms before continuing this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-309

Ethernet/Data network provisioning procedures

12

Procedure 11-43: Bridge and roll Ethernet cross-connections

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Service interruption of up to 10 ms for STS cross-connections or 25 ms for VT cross-connections may occur when performing the following roll procedures. In cases involving roll procedures from Main 2 cross-connections to Function slot ports, the service interruption may be as high as 200 ms.

CAUTION

Service disruption hazard

Service outage will occur if all new cross-connections are not properly made before performing the following roll procedures.

Important! It is suggested that you use a Command Mode (cmdmde) of

NORM

when rolling a cross-connection input to a SONET interface. If the new input is being monitored and it is faulty, the command will not complete. A Command

Mode of

FRCD

allows the command to complete even if the new input is faulty.

When rolling a cross-connection input to a non-SONET interface, the new input is not monitored and the Command Mode must be set to

FRCD

.

At the tail-end terminating node of the 1-way circuit, the traffic to be moved must be rolled to the new tributary. In UPSRs, the traffic to be moved must be bridged to the same new tributary on Main/Function/Growth 1 and Main/Function/Growth

2.

At the tail-end node of the 1-way circuit, select

Configuration

→

Cross-Connections

to access the Cross-Connection Wizard. Select

Roll a cross-connection from a source to a new source

and follow the directions to roll the drop cross-connection leg(s) to the required new source tributary(ies).

.................................................................................................................................................................................................................................

11-310 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-43: Bridge and roll Ethernet cross-connections

If a new Circuit Identifier (circuitid) is not specified, then the circuitid parameter value of the resultant cross-connection is inherited from the original cross-connection. If a new Circuit Identifier (circuitid) is null (circuitid=

″″

), then the circuitid parameter value of the resultant cross-connection is cleared.

The following figure shows an example of drop cross-connection legs rolled to new source tributaries within a UPSR.

Existing tributary New tributary

M1

M2

Roll

MA-DMX-313

13

14

15

16

.................................................................................................................................................................................................

At the tail-end node of the 1-way circuit, select

View

→

Cross-Connections

to access the cross-connection list and verify that the required drop cross-connection leg(s) was rolled to the new source tributary(ies).

.................................................................................................................................................................................................

Important! If the Tributary Monitoring Mode parameter is AUTO, the tributary automatically transitions to the in service state if a valid signal is detected and the tributary is monitored/alarmed. If the Tributary Monitoring Mode is NMON, the tributary is not monitored/alarmed, and the tributary will not automatically transition to the in service state if a valid signal is detected.

At the tail-end node of the 1-way circuit, select

View

→

Equipment

and verify the new Tributary parameters.

If required, use

Configuration

→

Equipment

and refer to

Chapter 4, “Install and provision circuit packs/OLIUs procedures”

to perform additional provisioning.

.................................................................................................................................................................................................

If moving a 2-way circuit, repeat

Step 8

through

Step 14

to move the traffic in the opposite direction of transmission to the new circuit path; otherwise, continue with the next step.

.................................................................................................................................................................................................

At each terminating (add) and pass-through node (UPSRs/BLSRs only), select

Configuration

→

Cross-Connections

to access the Cross-Connection Wizard. Select

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-311

Ethernet/Data network provisioning procedures Procedure 11-43: Bridge and roll Ethernet cross-connections

Delete leg(s) of an existing cross-connection

and follow the directions to delete the original cross-connections in the original circuit path.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

11-312 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-44: Establish Resilient Packet Ring (RPR) on a

UPSR

.................................................................................................................................................................................................................................

Overview

This procedure provides an example for establishing a Resilient Packet Ring (RPR) on a unidirectional path switched ring (UPSR) or a bidirectional line switched ring

(BLSR) with nonpreemptible unprotected traffic (NUT) access.

This procedure assumes that the UPSR/BLSR ring network configuration has already been established and no alarms are present.

This procedure uses TL1 commands and specific WaveStar

®

CIT menu selections to illustrate the detailed provisioning parameters. For examples, see

Figure 11-62,

“Resilient packet ring (RPR) on a UPSR” (p. 11-320) ,

Figure 11-63, “Resilient packet ring (RPR) with multiple RPR circuit packs in same node” (p. 11-320) , and

Figure

11-64, “Resilient packet ring (RPR) on a BLSR” (p. 11-321) .

Privilege level

You must login as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The network configuration and the nodes participating in the packet ring network.

•

The shelf slots, circuit packs, ports, and VCGs involved in the packet ring network.

•

The number and type of cross-connections to be made at each node.

•

The tagging mode (Transparent or 802.1TAG), virtual switch ID, and RPR IF and

Span parameters.

Step

1

Use this procedure as an example to establish a Resilient Packet Ring (RPR) with

Transparent VLAN Tagging Mode.

.................................................................................................................................................................................................

Use the WaveStar

®

performed.

CIT to log in to one of the terminating nodes, if not already

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-313

Ethernet/Data network provisioning procedures Procedure 11-44: Establish Resilient Packet Ring (RPR) on a UPSR

2

3

4

5

6

7

8

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

On the System View menu, select

Administration

→

OSI Routing Map

or

Administration

→

OSI Neighbor Map

to retrieve a node-to-node listing of every node in the network.

Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node’s TID.

This command may take several minutes to complete depending on the size of the network.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

.................................................................................................................................................................................................

Verify that the system configuration is the same as specified on your work instructions.

.................................................................................................................................................................................................

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the packet ring being established.

.................................................................................................................................................................................................

Verify that the LNW78 100/1G-FSR circuit packs have been installed into the required slot 1 of the Function Unit or Growth groups (A, B, C, D, or G) at each NE providing service.

Reference:

Procedure 4-13: “Install Gigabit Ethernet circuit packs” (p. 4-54)

.................................................................................................................................................................................................

Use the TL1

ed-eqpt

command or select the

Configuration

→

Equipment

command from the System View menu, select the circuit pack being provisioned, then click

Select

.

.................................................................................................................................................................................................

Verify/Enter

Ethernet Cross Connect Mode

, as required, then click

Apply

. Read the warning message, then click

OK

to make your changes. Click

Close

to exit.

Reference:

(p. 11-96)

Procedure 11-13: “Provision Ethernet circuit pack parameters”

.................................................................................................................................................................................................

ESTABLISH SONET CROSS-CONNECTIONS

.................................................................................................................................................................................................................................

11-314 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-44: Establish Resilient Packet Ring (RPR) on a UPSR

9

10

11

Determine the necessary cross-connections to be made at each terminating node and any pass-through cross-connections to be made at any non terminating nodes in the network.

Three or more STS-1s or equivalent must be assigned to this service up to the maximum of 24 STS-1s for each VCG. The LNW78 in STS1 Ethernet Cross

Connect Mode supports STS1 cross-connections. In STS12c Ethernet Cross

Connect Mode, only STS3c and STS12c cross-connections are supported.

.................................................................................................................................................................................................

One at a time at each node in the network, use the TL1

ent-crs-sts1

command to provision the cross-connections. Or, select

Configuration

→

Cross-Connections

from the System View menu to start the Cross-Connection Wizard. Use the

Cross-Connection Wizard at each non terminating node to provision the

2-Way

Point-to-Point, Through

pass-through cross-connections. Use the Cross-Connection

Wizard at each terminating node to provision the Ethernet

Multipoint

(unswitched) cross-connections. For example, see

Figure 11-62, “Resilient packet ring (RPR) on a

UPSR” (p. 11-320) ,

Figure 11-63, “Resilient packet ring (RPR) with multiple RPR circuit packs in same node” (p. 11-320) , and

Figure 11-64, “Resilient packet ring

(RPR) on a BLSR” (p. 11-321) .

In nodes with RPR supported across multiple RPR circuit packs, cross-connections are made from VCG v1 on one pack to main-1 or fn/growth-1 tribs and VCG v2 on the other pack is connected to main-2 or fn/growth-2 tribs. VCG v2 on the first pack and VCG v1 on the second pack are connected through hairpin cross-connections as shown in

Figure 11-63, “Resilient packet ring (RPR) with multiple RPR circuit packs in same node” (p. 11-320) .

Reference:

Refer to

Procedure 11-24: “Make cross-connections for Ethernet service” (p. 11-195)

for cross-connection examples.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Cross-Connections

to verify that the proper connections have been made.

.................................................................................................................................................................................................

Important! Each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select

View

→

Data

→

Ethernet/Data/VCG Port

to verify that VCG Membership has been Enabled in both

Input and Output Direction.

If required, use the TL1

ed-vcgtrib

command to enable tributaries, or from the

System View menu at each node, select

Configuration

→

Equipment

. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click

Select

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-315

Ethernet/Data network provisioning procedures

12

13

14

Procedure 11-44: Establish Resilient Packet Ring (RPR) on a UPSR

Select

Enabled

for the

VCG Membership

in both the Input and Output Direction.

Click

Apply

, read the warning message, then click

Yes

to execute the command.

Repeat this step for each tributary being enabled. Click Close to exit.

When Input VCG Membership (source) (

inmbs

) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When

Output VCG Membership (sink) (

outmbs

) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-33: “Provision LCAS, add/enable/remove tributaries”

(p. 11-249)

.................................................................................................................................................................................................

Important! At least one tributary at each terminating end of the circuit must be

Enabled in order for the VCG to go in service.

After all cross-connections have been made, verify that the WAN (VCG) Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select

View

→

Data

→

Ethernet/Data/VCG Port

.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

.................................................................................................................................................................................................

Expand the details for the circuit pack being used. Select the required

VCG v( )

port, then click

Select

at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

.................................................................................................................................................................................................

Click on the

VCG Data

tab. Under the

Fault/Alarms

section of the parameter display, verify the

VCG Monitoring Mode

is

IS

(in service). If the

VCG Monitoring Mode

is

IS

, proceed to

Step 15 .

•

If the VCG Monitoring Mode is

NMON

(Not Monitored),

1. Click

Close

to exit this window. From the System View menu, select

Configuration

→

Equipment

. Expand the details for the circuit pack being used, then select the required

VCG v( )

port and click

Select

at the bottom of the window.

2. In the parameters display area, click the

VCG Data

tab. Under the

Fault

section, select

AUTO

for the

VCG Monitoring Mode

.

3. Click

Apply

at the bottom of the window then click

Yes

in the warning message to execute the command.

4. Click

Close

to exit the window, then repeat this procedure from

Step 12 .

•

If the VCG Monitoring Mode is

AUTO

:

Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

.................................................................................................................................................................................................................................

11-316 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-44: Establish Resilient Packet Ring (RPR) on a UPSR

15

If proper cross-connections have been made, then indications are that either the far-end or near-end circuit pack at each end of the span has failed or must be reset.

If the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

– Log in to the NE at the far end of the span that connects to the near-end VCG not in service. Select the

Fault

→

Reset

→

Smart Pack

command from the

System View menu, then select the circuit pack to be reset. Click

Apply

. Read the warning message, then click

Yes

. Wait until the alarms clear, then check the

VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (

IS

), then reset the near-end circuit pack and check the VCG Monitoring

Mode.

– If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far-end and near-end circuit packs.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service.

If the service you are establishing in this procedure is a second service on an existing circuit pack with all LAN/WAN ports in the same virtual switch, then the existing virtual switch ID must be retained or the ports not in service must be removed from the existing virtual switch and added to a new virtual switch ID.

Create a virtual switch using the

ent-vrtsw

TL1 command or

Configuration

→

Data

→

Create Virtual Switch

command from the System View menu. Select the circuit pack and provision the following parameters:

•

Virtual Switch ID

(

vrtswid

) - Value in the range of 1-8 for the LNW78 circuit packs.

•

Virtual LAN Tagging Mode

(

tagmd

) - Value of

802.1TAG

or

Transparent

.

•

Ethernet (LAN) Ports

(

eplst

) - List or selection of LAN ports associated with the virtual switch ID.

•

VCG (WAN) Ports

(

vcglst

) - List or selection of VCG ports associated with the virtual switch ID.

In this release, the only VCG allowed is the RPR IF VCG (v1).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-317

Ethernet/Data network provisioning procedures Procedure 11-44: Establish Resilient Packet Ring (RPR) on a UPSR

16

17

18

.................................................................................................................................................................................................

Perform one of the following:

•

If the

VLAN Tagging Mode

is set to

802.1TAG

:

Use the TL1

ent-vlan

command to assign the default VLAN ID for customer untagged frames or the customer VLAN ID for tagged frames to the associated

Ethernet (LAN) Ports and VCG (WAN) Ports. Or, select

Configuration

→

Data

→

Create VLAN

command from the CIT System View menu. Highlight the circuit pack being provisioned, then click

Select

. Provision the parameters as required.

Click

Apply

, then click

Yes

to the warning message. Click

Close

to exit.

•

If the

VLAN Tagging Mode

is set to

Transparent

:

Use the TL1

ed-eport

and

ed-vcg

commands to assign port tags to the associated

Ethernet (LAN) Ports and VCG (WAN) Ports. Or, select

Configuration

→

Data

→

Create Port Tag

command from the CIT System View menu. Highlight the circuit pack being provisioned, then click

Select

. Provision the parameters as required.

Click

Apply

, then click

Yes

to the warning message. Click

Close

to exit.

.................................................................................................................................................................................................

PROVISION LAN (Ethernet) PORTS

If not already performed, use the TL1

ed-eport

command to provision parameters for the LAN port being provisioned. Or, select

Configuration

→

Equipment

from the

System View menu, expand the details for the circuit pack, highlight the LAN port, then click

Select

. Provision the parameters as required.

Click

Apply

, then click

Yes

to execute the command. Click

Close

to exit.

Reference:

Procedure 11-11: “Provision Ethernet LAN port parameters” (p. 11-72)

.................................................................................................................................................................................................

Provision RPR IF VCG and RPR Span VCG parameters, as required.

Use the

ed-rpr

and/or the

ed-vcg-rpr

TL1 commands or select

Configuration

→

Equipment

from the System View menu. Expand the details for the circuit pack, select the VCG being provisioned, then click

Select

. Provision the parameters as required.

VCG v1 is a RPR IF VCG and a RPR Span VCG. VCG v2 is a Span VCG.

The

ed-rpr

TL1 command is used to modify (edit) the RPR-specific properties of a port. An RPR instance consists of an Interface (IF) containing the common part

(IF), and two directional Spans.

The

ed-vcg-rpr

TL1 command is used to modify (edit) the properties of an

RPR-capable virtual concatenation group (VCG).

Reference:

Procedure 11-41: “Provision Resilient Packet Ring (RPR)-capable

VCG parameters” (p. 11-297)

Procedure 11-42: “Provision Resilient Packet Ring (RPR)-specific VCG parameters” (p. 11-301)

.................................................................................................................................................................................................................................

11-318 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-44: Establish Resilient Packet Ring (RPR) on a UPSR

19

20

.................................................................................................................................................................................................

Verify the RPR ring is closed and no RPR related alarms are present. Use the

rtrv-map-rpr

TL1 command, or from the System View menu, select

View

→

Rings

→

Ring Map

, select the RPR Ring, then click

Select

. Verify that the

Topology Type

Status

indicates

CLOSED

and the Number of Nodes is reported correctly. Click

Close

to exit.

Click the

Alarm List

button and verify no RPR alarms are present.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Provision Ethernet Quality of Service (QoS) parameters, as required.

Reference:

(p. 11-323)

Procedure 11-45: “Provision Ethernet quality of service (QoS) - RPR”

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-319

Ethernet/Data network provisioning procedures Procedure 11-44: Establish Resilient Packet Ring (RPR) on a UPSR

Figure 11-62 Resilient packet ring (RPR) on a UPSR

Node A

West East

M 1 M 2

Ringlet 0 Ringlet 0

M1

Node B

M2

Ringlet 1 Ringlet 1

V1 V2

D

V1 V2

D

RPR IF

1

Default Port Tag=55

RPR IF

1

Default Port Tag=55

VLAN Tagging Mode=SWITCHED (LNW78)

Cross Connect Mode=STS1

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=switched,eccmode=sts1

Virtual Switch ID = 1 (LNW78)

Virtual LAN Tagging Mode=Transparent or 802.1TAG (LNW78)

Ent-vrtsw:tid:fn-d-1:ctag::1:eplst=d1-1,vcglst=d1-v1,tagmd=Trans

Cross-Connection Wizard Multipoint Cross-connections:

Source AID: m1-1-(1-24),Destination AID: d1-v1-(1-24)

Source AID: m2-1-(1-24),Destination AID: d1-v2-(1-24)

Create Port Tag ed-eport-1ge:tid:d1-1:ctag:::dftporttag=55 ed-vcg:tid:d1-v1:ctag:::addporttag=55

M2

Node D

M1 M2

Node C

M1

Ringlet 1

Ringlet 0

V2 V1

D

STS1 2-Way Point-to-Point Through cross-connections m1-1-(1-24),m2-1-(1-24)

Resilient Packet Ring (RPR) on UPSR using multipoint (unswitched) cross-connections

RPR IF

1

Default Port Tag=55

MA-DMX-447

.................................................................................................................................................................................................................................

11-320 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-44: Establish Resilient Packet Ring (RPR) on a UPSR

Figure 11-63 Resilient packet ring (RPR) with multiple RPR circuit packs in same node

Node A Node B

West

M 1 M 2

East

M1 M2

Ringlet 0

Ringlet 0

Ringlet 1

Ringlet 1

V1 V2

D

RPR IF

STS1 2-Way Point-to-Point Through cross-connections m1-1-(1-24),m2-1-(1-24)

1

Default Port Tag=55

Cross-Connection Wizard Multipoint Cross-connections:

Source AID: m1-1-(1-24),Destination AID: d1-v1-(1-24)

Source AID: m2-1-(1-24),Destination AID: d1-v2-(1-24)

Resilient Packet Ring (RPR) on UPSR using multiple RPR circuit packs in the same node

M2

Node D

M1 M2

Ringlet 1

Node C

M1

Ringlet 0

STS1 2-Way Point-to-Point Through cross-connections m1-1-(1-24),m2-1-(1-24)

VLAN Tagging Mode=SWITCHED only (LNW78)

Configuration > Equipment

Cross Connect Mode=STS1

Ed-eqpt:tid:aid:ctag::ETHPK:vlantagmd=switched,eccmode=sts1

Configuration > Data > Create Virtual Switch (LNW78)

Virtual Switch ID = 1

Virtual LAN Tagging Mode=Transparent or 802.1TAG (LNW78)

Ent-vrtsw:tid:aid:ctag::1:eplst=d1-1,vcglst=d1-v1,tagmd=Trans

Configuration > Data > Create Port Tag ed-eport-1ge:tid:aid:ctag:::dftporttag=55 ed-vcg:tid:aid:ctag:::addporttag=55

D

V2 V1 V2 V1

G

RPR IF RPR IF

1 1

Default Port Tag=55

Cross-Connection Wizard Multipoint Cross-connections:

Source AID: m1-1-(1-24),Destination AID: g1-v1-(1-24)

Source AID: m2-1-(1-24),Destination AID: d1-v2-(1-24)

Cross-Connection Wizard 2-Way Hairpin Cross-connections:

Source AID: d1-v1-(1-24),Destination AID: g1-v2-(1-24)

MA-DMX-448

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-321

Ethernet/Data network provisioning procedures Procedure 11-44: Establish Resilient Packet Ring (RPR) on a UPSR

Figure 11-64 Resilient packet ring (RPR) on a BLSR

Node A

West

Ringlet 0

M 1 M 2

East

Ringlet 0

M1

Node B

M2

Ringlet 1

Ringlet 1

V1 V2

D

V1 V2

D

RPR IF

1

Default Port Tag=55

Multipoint (unswitched) cross-connections: m1-1-(1-24) to d1-v1-(1-24) m2-1-(1-24) to d1-v2-(1-24)

RPR IF

1

Default Port Tag=55

Multipoint (unswitched) cross-connections: m1-1-(1-24) to d1-v1-(1-24) m2-1-(1-24) to d1-v2-(1-24)

Resilient Packet Ring (RPR) on BLSR with NUT using multipoint (unswitched) cross-connections

Node D Node C

M2 M1 M2 M1

Ringlet 1

Ringlet 0

V2 V1

D

2-Way Point-to-Point, Through Cross-connections m1-1-(1-24),m2-1-(1-24)

Source NE=Node A

Destination NE=Node C

RPR IF

1

Default Port Tag=55

Multipoint (unswitched) cross-connections: m1-1-(1-24) to d1-v1-(1-24) m2-1-(1-24) to d1-v2-(1-24)

VLAN Tagging Mode=SWITCHED (LNW78)

Cross Connect Mode=STS1

Ed-eqpt:tid:fn-d-1:ctag::ETHPK:vlantagmd=switched,eccmode=sts1

Virtual Switch ID = 1 (LNW78)

Virtual LAN Tagging Mode=Transparent or 802.1TAG (LNW78)

Ent-vrtsw:tid:fn-d-1:ctag::1:eplst=d1-1,vcglst=d1-v1,tagmd=Trans

NUT Value for cross-connections:

Configuration > Equipment, select Ptn Grp, select BLSR protection group, click Select. Provision NUT Protection Attribute to “Not Protected” for all timeslots being used.

Cross-Connection Wizard Multipoint Cross-connections:

Source AID: m1-1-(1-24),Destination AID: d1-v1-(1-24)

Source AID: m2-1-(1-24),Destination AID: d1-v2-(1-24)

Create Port Tag ed-eport-1ge:tid:d1-1:ctag:::dftporttag=55 ed-vcg:tid:d1-v1:ctag:::addporttag=55

MA-DMX-449

.................................................................................................................................................................................................................................

11-322 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures

Procedure 11-45: Provision Ethernet quality of service (QoS) -

RPR

.................................................................................................................................................................................................................................

Overview

Use this procedure as a reference to provision Ethernet Quality of Service (QoS). Refer to the section at the end of these steps for a detailed overview.

Important! This procedure applies only to LNW78 circuit packs.

To provision Ethernet Quality of Service for an LNW70, refer to

Procedure 11-31:

“Provision Ethernet quality of service (QoS)” (p. 11-238) .

Privilege level

You must login at least as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 11-4)

and

“Required equipment” (p. 11-4)

in this chapter and you must have complete work instructions for this procedure that detail:

•

The shelf slots, circuit packs, ports, being provisioned.

•

The type of QoS service being provisioned and all the related parameter values.

All the required regular Ethernet service parameters must have already been provisioned using the procedures in this chapter. This includes any packet rings, vlan tagging modes, customer vlan/port tags, virtual switches, and related LAN and VCG port parameters.

Step

1

2

Use the following to provision a QoS service.

.................................................................................................................................................................................................

Use the WaveStar

®

CIT to log in to the Metropolis

®

DMX shelf.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Use the

Configuration

→

Equipment

command from the System View menu, select the circuit pack, then select the VCG port being provisioned. Click on the

Queue

Management

tab. Provision the queue management parameters, as required. Click on the

RPR Span

tab. Provision the RPR shaper parameters, as required. Or, use the

ed-eport/ed-vcg-rpr/ed-rpr

TL1 commands to provision the parameters.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-323

Ethernet/Data network provisioning procedures Procedure 11-45: Provision Ethernet quality of service

(QoS) - RPR

3

4

5

6

Repeat this step for each port in the network service.

Queue Management parameters apply to VCG v1 only. RPR Span parameters apply to both VCG v1 and v2.

References:

(p. 11-72)

Procedure 11-11: “Provision Ethernet LAN port parameters”

Procedure 11-41: “Provision Resilient Packet Ring (RPR)-capable VCG parameters” (p. 11-297)

Procedure 11-42: “Provision Resilient Packet Ring (RPR)-specific VCG parameters” (p. 11-301)

.................................................................................................................................................................................................

Use the

Configuration

→

Data

→

Provision QoS Service

command from the System

View menu, select the circuit pack, then select the port being provisioned. Or, use the

ed-erate

TL1 command to provision the parameters for the QoS service.

Reference:

Procedure 11-32: “Provision Ethernet QoS parameters” (p. 11-244)

.................................................................................................................................................................................................

Select the

Port Type

as

Boundary

(Interior ports are not provisionable in this release.)

Select the

Traffic Management Mode

.

.................................................................................................................................................................................................

Provision the parameters as required from your work order for the traffic management mode selected.

.................................................................................................................................................................................................

Verify your settings, then click

Apply

. Read the warning message, then click

Yes

to execute the command. Click Close to exit.

E

N D O F

S

T E P S

Ethernet QoS

Use as a reference to provision Ethernet Quality of Service (QoS).

The Metropolis

®

DMX uses the differentiated services (DiffServ) model for the QoS feature. Traffic flow to the network is regulated only at the ingress ports.

The DiffServ model has two types of ports:

•

Boundary port - port at the edge of the DiffServ domain.

•

Interior port - port internal to the DiffServ domain.

An LNW78 LAN/VCG port may be a boundary only.

.................................................................................................................................................................................................................................

11-324 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-45: Provision Ethernet quality of service

(QoS) - RPR

Selection of these port parameters may be done using the

ed-eport

and

ed-vcg_rpr

TL1 commands, or

Configuration

→

Data

→

Provision QoS Service

from the

WaveStar

®

CIT system menu, selecting the port, then select

Port Type

.

QoS Services/Traffic Management Modes

A basic QoS service is defined as a particular traffic flow that uses a single traffic conditioner. A number of services can be provisioned at a Boundary port. The configuration of these services is defined as one of two traffic management modes

(

trafmgmtmd

). The mode specifies how the packets will be divided into traffic flows and the services that can be provided at the port. All services at one port must be in the same traffic management mode. The total number of QoS services on the LNW78 circuit pack is 400.

The traffic management modes are defined as follows:

•

PORT mode - Allowed in all VLAN tagging modes. One QoS service per port.

•

COSPORT mode - Allowed only in 802.1TAG mode. One QoS service and one TC for each Class of Service (CoS) at the port.

Selection of these port parameters may be done using the

ed-eport

and

ed-vcg-rpr

TL1 commands, or

Configuration

→

Data

→

Provision QoS Service

from the

WaveStar

®

CIT system menu, selecting the port, then select

Traffic Management

Mode

.

Classes of Service

Data packets classified at the ingress port result in unique traffic flows. Multiple flows can be mapped into a single Class of Service (COS). There may be up to three classes of service (CoS level 3, 2, and 1) corresponding to RPR classes A, B, and C, respectively. Class A has guaranteed bandwidth and lowest latency. Class B can have guaranteed bandwidth and bounded latency and can also have access to opportunistic bandwidth. Class C has no guarantees and only access to opportunistic bandwidth.

Selection of these parameters may be done using the

ent/ed-erate

TL1 commands, or

Configuration

→

Data

→

Provision QoS Service

from the WaveStar

®

CIT system menu, selecting the port, then selecting

Traffic Management Mode

.

Traffic Conditioning

Traffic conditioning is performed on the ingress packets at Boundary Ports by metering the packets and either marking or policing as appropriate. This is used to enforce the guarantees and limitations specified in a Service Level Agreement (SLA). Within the network, queueing and scheduling functions provide a network that is engineered to satisfy all of the attached customers’ SLA requirements.

Traffic Conditioner Parameters

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-325

Ethernet/Data network provisioning procedures Procedure 11-45: Provision Ethernet quality of service

(QoS) - RPR

Traffic Conditioner (TC) parameters include PIR, CIR, PBS, and CBS.

•

PIR - Peak Information Rate. This is the peak information rate of the traffic conditioner function in Mbps. This is the PIR for the service addressed by the trafmgmtmd, port aid, tagid and cos. Value is from 0 to 1000. A value of 0 means that the PIR function is bypassed and there is no policing of the traffic. The value of PIR must be greater than or equal to CIR. PIR does not apply to CoS Level 3.

•

CIR - Committed Information Rate. This is the committed information rate of the traffic conditioner function in Mbps for the service addressed by the trafmgmtmd, port aid, tagid, and cos. Value is from 0 to 1000. The value of cir must be less than or equal to pir. A value of 0 means that there is no network commitment on incoming traffic. All traffic will be considered excess traffic. CIR does not apply to

CoS Level 1.

•

PBS - Peak Burst Size. This is the peak burst size in kilobytes for the service addressed by the trafmgmtmd, port aid, tagid, and cos. Value is from 0 to

1024.PBS does not apply to CoS Level 3.

•

CBS - Committed Burst Size. This is the committed burst size in kilobytes for the service addressed by the trafmgmtmd, port aid, tagid, and cos. Value is from 1 to

1024. The value of CBS must be less than or equal to PBS. In case of Private Line

(vlantagmd set to NOTAG), the CBS value cannot be set (it inherits the PBS value). CBS does not apply to CoS Level 1.

Selection of these parameters may be done using the

ent/ed-erate

TL1 commands, or

Configuration

→

Data

→

Provision QoS Service

from the WaveStar

®

CIT system menu, then selecting the port.

Metering, Policing, and Color Marking

Metering measures the data rate with conformance levels determined by three color markers:

•

Red - data rates greater than the PIR or PBS.

•

Yellow - data rates less than or equal to PIR or PBS, but greater than CIR or CBS.

•

Green - data rates less than or equal to CIR or CBS.

Policing discards red packets at the boundary ports. The remaining yellow and green packets determine drop precedence (DP).

Packets ingressing at boundary ports are remarked. Packets user priority is altered to reflect COS and DP. In COSPORT mode, user priority bit values map to the specified

COS value as specified in IEEE 802.17a-2004.

In PORT mode, the traffic class is set for all packets that ingress the port and the COS value is set based on the default priority of the port. The COS value is inserted into the packet prior to egressing the NE.

.................................................................................................................................................................................................................................

11-326 365-372-301 R6.0

Issue 15, January 2006

Ethernet/Data network provisioning procedures Procedure 11-45: Provision Ethernet quality of service

(QoS) - RPR

Selection of these parameters may be done using the

ent/ed-erate

TL1 commands, or

Configuration

→

Data

→

Provision QoS Service

from the WaveStar

®

CIT system menu, then selecting the port.

Queue Management

Each port supports configurable thresholds expressed as a percentage of the total queue allocation. Each queue is controlled by setting the size of the queues, the queue weights and the drop thresholds for yellow and green packets. The performance of each CoS level is controlled by setting the dropping probabilities for each CoS level.

Traffic that was admitted into the network within the terms of a Service Level

Agreement (SLA) can be differentiated and given preferential treatment at the queue in order to satisfy the SLA service guarantees.

Provisioning of these port parameters may be done using the

ed-eport

and

ed-vcg-rpr

TL1 commands, or

Configuration

→

Equipment

from the WaveStar

®

CIT system menu, selecting the port, then selecting

Queue Management

.

The following TL1 command (WaveStar

®

CIT) parameters determine the maximum queue size and the minimum and maximum dropping thresholds for yellow and green packets:

• qsz - Maximum queue size.

Total Queue Size (in Kbytes)

• qminthldg - Minimum dropping threshold for green packets.

Green Packet Min

Drop Threshold (in %)

• qmaxthldy - Maximum dropping threshold for yellow packets.

Yellow Packet Max

Drop Threshold (in %)

• qminthldy - Minimum dropping threshold for yellow packets.

Yellow Packet Min

Drop Threshold (in %)

The following TL1 command (WaveStar

®

drop probability for COS 1, 2, 3 packets:

CIT) parameters determine the maximum

• qdropwt1 - Specifies maximum drop probability for COS 1 packets.

CoS 1

Packets Drop Probability Mark (in %)

• qdropwt2 - Specifies maximum drop probability for COS 2 packets.

CoS 2

Packets Drop Probability Mark (in %)

• qdropwt3 - Specifies maximum drop probability for COS 3 packets.

CoS 3

Packets Drop Probability Mark (in %)

RPR traffic shapers

RPR shapers govern the aggregate amount of class A and class B traffic ingressing on the RPR ring, and should typically be set to at least the sum of the CIR’s for each class from all the LAN ports.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

11-327

Ethernet/Data network provisioning procedures Procedure 11-45: Provision Ethernet quality of service

(QoS) - RPR

Provisioning of these port parameters may be done using the

ed-rpr

TL1 command, or

Configuration

→

Equipment

from the WaveStar

®

CIT system menu, selecting the port, then selecting

RPR Span

.

The following TL1 command (WaveStar

®

CIT) parameters determine the maximum rate that Class A or B traffic is allowed to be added to each ringlet:

• rsv_a - Specifies the maximum rate that Class A traffic can be added to each ringlet. It controls the Class A shaper.

Reserved Class A Add Rate (Mb/sec):

• rsv_b - Specifies the maximum rate that Class B traffic can be added to each ringlet. It controls the Class B shaper.

Reserved Class B Add Rate (Mb/sec):

.................................................................................................................................................................................................................................

11-328 365-372-301 R6.0

Issue 15, January 2006

12

12

procedures

Overview

.................................................................................................................................................................................................................................

Purpose

This chapter includes procedures used to:

•

Upgrade rings

•

Back out ring upgrades

•

Suspend ring upgrades temporarily

•

Upgrade transmission circuit packs at a node

•

Upgrade/Replace the SYSCTL circuit pack

Contents

Before you begin

Procedure 12-1: Upgrade high-speed OC-48 OLIUs in UPSR/BLSR network

Procedure 12-2: Back out high-speed OC-48 OLIU upgrade

Procedure 12-3: Upgrade OC-3 UPSR to OC-12 UPSR

Procedure 12-4: Back out OC-3 UPSR to OC-12 UPSR upgrade

Procedure 12-5: Upgrade OC-12 UPSR to OC-48 UPSR

Procedure 12-6: Back out OC-12 UPSR to OC-48 UPSR upgrade

Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

Procedure 12-8: Upgrade OC-48 UPSR to OC-192 UPSR

Procedure 12-9: Back out OC-48 UPSR to OC-192 UPSR upgrade

Procedure 12-10: Suspend OC-48 UPSR to OC-192 UPSR upgrade

Procedure 12-11: Upgrade OC-48 BLSR to OC-192 BLSR

Procedure 12-12: Back out OC-48 BLSR to OC-192 BLSR upgrade

12-3

12-4

12-19

12-32

12-42

12-52

12-93

12-130

12-144

12-182

12-214

12-223

12-262

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-1

Ring and circuit pack upgrade procedures Overview

Procedure 12-13: Suspend OC-48 BLSR to OC-192 BLSR upgrade

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a Metropolis

®

OC-48/192 UPSR

DMX

Procedure 12-15: Upgrade low-speed electrical circuit packs

Procedure 12-16: Upgrade or replace SYSCTL (LNW2) circuit pack

12-294

12-303

12-318

12-325

.................................................................................................................................................................................................................................

12-2 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Before you begin

.................................................................................................................................................................................................................................

Before you begin

Prior to performing any procedures in this chapter,

1. If not previously completed, install generic and WaveStar

®

CIT software on the PC.

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

2. Connect PC and establish a WaveStar

®

CIT session.

Refer to

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24) .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-3

Ring and circuit pack upgrade procedures

Procedure 12-1: Upgrade high-speed OC-48 OLIUs in

UPSR/BLSR network

.................................................................................................................................................................................................................................

Overview

Use this procedure to upgrade the in-service high-speed OC-48 OLIU circuit packs at nodes in a UPSR/BLSR network with OC-48 OLIU circuit packs equipped with larger

VT switch fabrics.

This procedure supports upgrading LNW26B, LNW28, LNW77, or LNW121B-159B

OC-48 OLIUs to LNW27, LNW29, LNW32, LNW76, or LNW221-259 OC-48 OLIUs.

The LNW27, LNW29, LNW32, LNW76, and LNW221-259 OC-48 OLIU circuit packs can cross-connect VT1.5 signals in up to 48 STS-1 signals.

The LNW26B, LNW28, LNW77, and LNW121B-159B OC-48 OLIU circuit packs can cross-connect VT1.5 signals in up to 6 STS-1 signals or 12 STS-1 signals. If the

Normal/Enhanced jumper is in the Normal position, the circuit pack can cross-connect

VT1.5 signals in up to 6 STS-1 signals. If the Normal/Enhanced jumper is in the

Enhanced position, the circuit pack can cross-connect VT1.5 signals in up to 12 STS-1 signals.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

The following equipment is required to perform this procedure:

•

Wrist strap

•

Optical power meter

•

Two replacement OC-48 OLIU circuit packs for the OC-48 OLIU circuit packs in the Main slots

Release 4.0 or later software is required to support the LNW32 OC-48 OLIU circuit packs.

Release 2.1 or later software is required to support the LNW27, LNW29, LNW76, and

LNW221-259 OC-48 OLIU circuit packs.

Release 2.0 or later software is required to support the LNW26B, LNW28, LNW77, and LNW121B-159B OC-48 OLIU circuit packs.

Release 2.1 or later software is required to support the LNW26B, LNW28, LNW77, and LNW121B-159B OC-48 OLIU circuit packs with the Normal/Enhanced jumper in the Enhanced position.

.................................................................................................................................................................................................................................

12-4 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-1: Upgrade high-speed OC-48 OLIUs in

UPSR/BLSR network

LC-type lightguide buildouts

The following lightguide buildouts are required for attenuating the OC-48 OLIUs.

Code

ABLCS-05.0

ABLCS-10.0

ABLCS-15.0

Comcode

108279381

108279431

108279480

Loss (dB) Fiber Type

5

10

15

SM

SM

SM

Color

Yellow

Yellow

Yellow

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Obtain the work instructions for this procedure.

3. Review the applicable office records and verify that each fiber span is capable of supporting the replacement circuit pack. Refer to Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 OLIU circuit packs.

4. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this upgrade procedure.

5. If the provisioned Timing Source is external, verify that both timing references

(REF-1 and REF-2) are in-service (IS) before beginning this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-5

Ring and circuit pack upgrade procedures Procedure 12-1: Upgrade high-speed OC-48 OLIUs in

UPSR/BLSR network

6. If the LNW26B, LNW28, LNW77, or LNW121B-159B OC-48 OLIU circuit packs are being installed, verify that the Normal/Enhanced jumper is in the Enhanced

.

position. Refer to

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

7. If the LNW121B-159B or LNW221-259 OC-48 OLIU circuit packs are being installed, verify that the channel selection jumper is in the required position. Refer to

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7) .

Step

1

Complete the following steps to upgrade the in-service high-speed OC-48 OLIU circuit packs at nodes in a UPSR/BLSR network.

.................................................................................................................................................................................................

Determine the high-speed network configuration (UPSR or BLSR) using the work instructions and/or office records.

2

.................................................................................................................................................................................................

If upgrading the high-speed

OC-48 OLIU circuit packs at nodes in a...

UPSR network,

Then proceed to and perform...

BLSR network,

Procedure 12-1.1: “Upgrade high-speed OC-48

OLIUs in UPSR network” (p. 12-7)

Procedure 12-1.2: “Upgrade high-speed OC-48

OLIUs in BLSR network” (p. 12-13)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-6 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-1.1: Upgrade high-speed OC-48 OLIUs in UPSR network

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-1: “Upgrade high-speed OC-48 OLIUs in UPSR/BLSR network” (p. 12-4) .

Step

1

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade the in-service high-speed OC-48 OLIU circuit packs at nodes in a UPSR network.

.................................................................................................................................................................................................

Log in to the node where the OC-48 OLIU circuit packs are to be replaced.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

2

3

.................................................................................................................................................................................................

Click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the NE Alarm List and verify that no alarms are present.

Refer to the appropriate trouble clearing procedures to clear all existing alarms before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

To verify that no loopbacks, protection switch lockouts, or protection switches are present, select

View

→

Rolling Events

. Under the line reading

RTRV-COND-ALL determine if any loopbacks, protection switch lockouts, or protection switches are displayed.

Remove all existing loopbacks, protection switch lockouts, or protection switches before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

4

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and verify that no test access sessions exist.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-7

Ring and circuit pack upgrade procedures

5

Procedure 12-1.1: Upgrade high-speed OC-48 OLIUs in

UPSR network

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and delete all existing test access sessions.

Reference:

•

Procedure 14-27: “View test access session(s)” (p. 14-130)

•

Procedure 14-26: “Delete test access session” (p. 14-129)

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 13 .

Continue with

Step 6 .

6

7

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

.................................................................................................................................................................................................................................

12-8 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-1.1: Upgrade high-speed OC-48 OLIUs in

UPSR network

8

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 6

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for timing.

9

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-48 OLIU circuit pack in Main slot

M1

.

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m1-()-() paths supported by the circuit pack in Main slot

M1

(Ring

1). Record the active paths supported by the circuit pack in Main slot

M1

(Ring 1).

Click

Close

.

.................................................................................................................................................................................................

10

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M1

. In UPSRs, each path supported by the circuit pack in Main slot

M1

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 12 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

11

Repeat

Step 10

for each path supported by the circuit pack in Main slot

M1

. Click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-9

Ring and circuit pack upgrade procedures Procedure 12-1.1: Upgrade high-speed OC-48 OLIUs in

UPSR network

12

13

.................................................................................................................................................................................................

If required, repeat

Step 9

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for transmission.

.................................................................................................................................................................................................

Important! The OC-48 OLIU circuit pack in Main slot

M1

must be replaced first.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the replacement OC-48 OLIU circuit pack.

Result:

Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M1

. If active through traffic exists on the circuit pack in Main slot

M1

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected CP type alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

14

15

.................................................................................................................................................................................................

Measure the optical receive power of the receive fiber using an optical power meter.

Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 OLIU circuit packs.)

.................................................................................................................................................................................................

Clean all fiber connectors, and connect the transmit and receive optical fibers to the replacement OC-48 OLIU circuit pack in Main slot

M1

.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

16

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The replacement OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system performs an automatic path protection switch. Transmission hits (less than 60 ms) occur as active traffic is automatically switched from the circuit pack

.................................................................................................................................................................................................................................

12-10 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-1.1: Upgrade high-speed OC-48 OLIUs in

UPSR network

17

18

19

20

in Main slot

M2

to the circuit pack in Main slot

M1

. All traffic is now active on the circuit pack in Main slot

M1

.

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an unexpected CP type alarm for Main slot

M2

.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the replacement OC-48 OLIU circuit pack.

Result:

The replacement OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M2

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

Measure the optical receive power of the receive fiber using an optical power meter.

Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 OLIU circuit packs.)

.................................................................................................................................................................................................

Clean all fiber connectors, and connect the transmit and receive optical fibers to the replacement OC-48 OLIU circuit pack in Main slot

M2

.

Result:

All alarms clear and service is restored.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Important! It is recommended that the network element database be backed up to a remote OS (for example, the Navis

®

Optical Element Management System) after an upgrade. This creates a current backup copy that includes the replacement circuit packs. The remote OS could use this backup copy to restore the network element database in the event of a catastrophic failure. Attempts to restore the network element database using a backup copy created prior to the upgrade may result in circuit pack failures.

Back up the network element database using the

Configuration

→

Software

→

Remote Backup

command.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-11

Ring and circuit pack upgrade procedures Procedure 12-1.1: Upgrade high-speed OC-48 OLIUs in

UPSR network

21

Reference:

•

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123)

•

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135)

•

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150)

.................................................................................................................................................................................................

This completes the circuit pack upgrade at the local node. If other nodes in the UPSR are to be upgraded, repeat

Step 1

through

Step 20

at each node beginning at the adjacent node connected to the circuit pack in Main slot

M2

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-12 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-1.2: Upgrade high-speed OC-48 OLIUs in BLSR network

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-1: “Upgrade high-speed OC-48 OLIUs in UPSR/BLSR network” (p. 12-4) .

Step

1

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade the in-service high-speed OC-48 OLIU circuit packs at nodes in a BLSR network.

.................................................................................................................................................................................................

Log in to the node where the OC-48 OLIU circuit packs are to be replaced.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

2

3

.................................................................................................................................................................................................

Click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the NE Alarm List and verify that no alarms are present.

Refer to the appropriate trouble clearing procedures to clear all existing alarms before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

To verify that no loopbacks, protection switch lockouts, or protection switches are present, select

View

→

Rolling Events

. Under the line reading

RTRV-COND-ALL determine if any loopbacks, protection switch lockouts, or protection switches are displayed.

Remove all existing loopbacks, protection switch lockouts, or protection switches before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

4

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and verify that no test access sessions exist.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-13

Ring and circuit pack upgrade procedures

5

Procedure 12-1.2: Upgrade high-speed OC-48 OLIUs in

BLSR network

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and delete all existing test access sessions.

Reference:

•

Procedure 14-27: “View test access session(s)” (p. 14-130)

•

Procedure 14-26: “Delete test access session” (p. 14-129)

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 11 .

Continue with

Step 6 .

6

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than 60 ms) will occur. If desired, perform this step to determine the transmission and timing state of the OC-48 OLIU circuit pack in

Main slot

M1

.

At the System View select

Reports

→

Status Lists

→

Pack

. Click Shelf and

Select

.

Observe the value of the Switch State parameter for the main-1 circuit pack. If the

Switch State parameter is ACTIVE-TIMING, all Function units are selecting timing from the main-1 circuit pack, and some Function units are receiving traffic from the

main-1 circuit pack. If the Switch State parameter is ACTIVE, some Function units are receiving traffic from the main-1 circuit pack. Click

Close

.

.................................................................................................................................................................................................................................

12-14 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-1.2: Upgrade high-speed OC-48 OLIUs in

BLSR network

7

8

9

10

11

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 6

to determine the transmission and timing state of the OC-48

OLIU circuit pack in Main slot

M1

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, an optional manual switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 10 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Click on 2F BLSR main-1-1 and

Select

. Select the West Direction and Manual to

Protection, Ring Switch Type, and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and

Close

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the Alarm List shows the

Protection Switch, OC48 Port, Manual Switch, MSR, 2F condition

(Not Alarmed).

.................................................................................................................................................................................................

If required, repeat

Step 6

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for transmission.

.................................................................................................................................................................................................

Important! The OC-48 OLIU circuit pack in Main slot

M1

must be replaced first.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-15

Ring and circuit pack upgrade procedures Procedure 12-1.2: Upgrade high-speed OC-48 OLIUs in

BLSR network

12

13

14

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the replacement OC-48 OLIU circuit pack.

Result:

Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M1

. If active through traffic exists on the circuit pack in Main slot

M1

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected CP type alarm and a

Line Automatic Switch condition for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

Measure the optical receive power of the receive fiber using an optical power meter.

Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 OLIU circuit packs.)

.................................................................................................................................................................................................

Clean all fiber connectors, and connect the transmit and receive optical fibers to the replacement OC-48 OLIU circuit pack in Main slot

M1

.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The replacement OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned,

The system performs an automatic line protection switch. Transmission hits (less than 60 ms) occur as active traffic is automatically switched from the circuit pack in Main slot

M2

to the circuit pack in Main slot

M1

. All traffic is now active on the circuit pack in Main slot

M1

.

The unexpected CP type alarm and

Line Automatic Switch condition for Main slot

M1

clear, and the system reports an unexpected CP type alarm and a

Line

Automatic Switch condition for Main slot

M2

.

.................................................................................................................................................................................................................................

12-16 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-1.2: Upgrade high-speed OC-48 OLIUs in

BLSR network

15

16

17

18

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the replacement OC-48 OLIU circuit pack.

Result:

The replacement OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M2

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

Measure the optical receive power of the receive fiber using an optical power meter.

Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 OLIU circuit packs.)

.................................................................................................................................................................................................

Clean all fiber connectors, and connect the transmit and receive optical fibers to the replacement OC-48 OLIU circuit pack in Main slot

M2

.

Result:

All alarms clear and service is restored. The

Line Automatic Switch condition clears after the provisionable wait-to-restore interval elapses. (The default is 5 minutes.) This applies to the local node and the adjacent node connected to the circuit pack in Main slot

M2

.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Important! It is recommended that the network element database be backed up to a remote OS (for example, the Navis

®

Optical Element Management System) after an upgrade. This creates a current backup copy that includes the replacement circuit packs. The remote OS could use this backup copy to restore the network element database in the event of a catastrophic failure. Attempts to restore the network element database using a backup copy created prior to the upgrade may result in circuit pack failures.

Back up the network element database using the

Configuration

→

Software

→

Remote Backup

command.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-17

Ring and circuit pack upgrade procedures Procedure 12-1.2: Upgrade high-speed OC-48 OLIUs in

BLSR network

19

Reference:

•

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123)

•

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135)

•

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150)

.................................................................................................................................................................................................

This completes the circuit pack upgrade at the local node. If other nodes in the BLSR are to be upgraded, repeat

Step 1

through

Step 18

at each node beginning at the adjacent node connected to the circuit pack in Main slot

M2

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-18 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-2: Back out high-speed OC-48 OLIU upgrade

.................................................................................................................................................................................................................................

Overview

Important! Do not use this procedure to downgrade a node if the upgrade has been completed and additional VT1.5 cross-connections have been provisioned (and even subsequently deleted). The system will not recognize the original OC-48 OLIU circuit pack as an allowable type.

Use this procedure to back out of an in-service high-speed OC-48 OLIU circuit pack upgrade (in progress) at a node in a unidirectional path switched ring (UPSR) or bidirectional line-switched ring (BLSR) network.

Backing out of an upgrade in progress returns the node to the pre-upgrade state.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

The following equipment is required to perform this procedure:

•

Wrist strap

•

Original OC-48 OLIU circuit packs and LBOs for the node to be backed out

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-19

Ring and circuit pack upgrade procedures Procedure 12-2: Back out high-speed OC-48 OLIU upgrade

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Obtain the work instructions for this procedure.

3. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this back out procedure.

Step

1

Complete the following steps to back out an in-service high-speed OC-48 OLIU circuit pack upgrade (in progress) at a node in a UPSR or BLSR network.

.................................................................................................................................................................................................

Determine the high-speed network configuration (UPSR or BLSR) using the work instructions and/or office records.

2

.................................................................................................................................................................................................

If backing out of a high-speed

OC-48 OLIU circuit pack upgrade at a node in a...

UPSR network,

Then proceed to and perform...

BLSR network,

Procedure 12-2.1: “Back out high-speed OC-48

OLIU upgrade in UPSR network” (p. 12-21)

Procedure 12-2.2: “Back out high-speed OC-48

OLIU upgrade in BLSR network” (p. 12-26)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-20 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-2.1: Back out high-speed OC-48 OLIU upgrade in UPSR network

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-2: “Back out high-speed OC-48 OLIU upgrade”

(p. 12-19) .

Step

1

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an in-service high-speed OC-48 OLIU circuit pack upgrade (in progress) at a node in a UPSR network.

.................................................................................................................................................................................................

Determine the status of the in-service high-speed OC-48 OLIU circuit pack upgrade.

If...

If the original OC-48 OLIU circuit pack in Main slot

M1

has been replaced and the

Configuration

→

Update System

→

Update All

command has not been performed,

If the original OC-48 OLIU circuit pack in Main slot

M1

has been replaced and the

Configuration

→

Update System

→

Update All

command has been performed,

If the original OC-48 OLIU circuit pack in Main slot

M2

has been replaced,

Then...

Continue with

Step 2 .

Proceed to

Step 4 .

Proceed to

Step 9 .

.................................................................................................................................................................................................

2

Important! The original OC-48 OLIU circuit pack in Main slot

M1

has been replaced and the

Configuration

→

Update System

→

Update All

command has

not been performed. The system reports an unexpected CP type alarm for Main slot

M1

.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the original OC-48 OLIU circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-21

Ring and circuit pack upgrade procedures

3

4

5

Procedure 12-2.1: Back out high-speed OC-48 OLIU upgrade in UPSR network

Result:

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

Obtain the original LBO, clean all fiber connectors, and connect the transmit and receive optical fibers to the original OC-48 OLIU circuit pack in Main slot

M1

.

Result:

All alarms clear and service is restored.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

STOP!

End of Procedure. This completes the back out procedure at the local node.

If other nodes are to be backed out, go to the adjacent node connected to the circuit pack in Main slot

M1

and return to

Step 1 .

.................................................................................................................................................................................................

Important! The original OC-48 OLIU circuit pack in Main slot

M1

has been replaced and the

Configuration

→

Update System

→

Update All

command has been performed. The replacement OC-48 OLIU circuit pack in Main slot

M1

has been autoprovisioned, and the system has performed an automatic path protection switch. All traffic is now active on the circuit pack in Main slot

M1

. The unexpected CP type unexpected CP type alarm for Main slot alarm for Main slot

M1

M2

.

clears, and the system reports an

From the WaveStar

®

CIT System View select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

Alarm List shows the Ring Upgrade mode as Not Alarmed.

CIT

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this procedure.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The original OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned. The system performs an automatic protection switch, and all traffic is now active on the circuit pack in Main slot

M2

.

Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in Main slot

M1

to the circuit pack in Main slot

M2

.

.................................................................................................................................................................................................................................

12-22 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

6

7

8

9

Procedure 12-2.1: Back out high-speed OC-48 OLIU upgrade in UPSR network

The unexpected CP type alarm for Main slot

M2

clears, and the system reports an unexpected CP type alarm for Main slot

M1

.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the original OC-48 OLIU circuit pack.

Result:

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

Obtain the original LBO, clean all fiber connectors, and connect the transmit and receive optical fibers to the original OC-48 OLIU circuit pack in Main slot

M1

.

Result:

All alarms clear and service is restored.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

At the System View select

Configuration

→

Normal Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode is removed from the WaveStar

®

CIT alarm list.

STOP!

End of Procedure. This completes the back out procedure at the local node.

If other nodes are to be backed out, go to the adjacent node connected to the circuit pack in Main slot

M1

and return to

Step 1 .

.................................................................................................................................................................................................

Important! The original OC-48 OLIU circuit pack in Main slot

M2

has been replaced, and the unexpected CP type alarm for Main slot

M2

clears.

At the WaveStar

®

CIT System View select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

Alarm List shows the Ring Upgrade mode as Not Alarmed.

CIT

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-23

Ring and circuit pack upgrade procedures Procedure 12-2.1: Back out high-speed OC-48 OLIU upgrade in UPSR network

10

11

12

13

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the original OC-48 OLIU circuit pack.

Result:

Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M2

. If active through traffic exists on the circuit pack in Main slot

M2

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected CP type alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

Obtain the original LBO, clean all fiber connectors, and connect the transmit and receive optical fibers to the original OC-48 OLIU circuit pack in Main slot

M2

.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this procedure.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The original OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned. The system performs an automatic protection switch, and all traffic is now active on the circuit pack in Main slot

M2

.

Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in Main slot

M1

to the circuit pack in Main slot

M2

.

The unexpected CP type alarm for Main slot

M2

clears, and the system reports an unexpected CP type alarm for Main slot

M1

.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the original OC-48 OLIU circuit pack.

.................................................................................................................................................................................................................................

12-24 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

14

15

Procedure 12-2.1: Back out high-speed OC-48 OLIU upgrade in UPSR network

Result:

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

Obtain the original LBO, clean all fiber connectors, and connect the transmit and receive optical fibers to the original OC-48 OLIU circuit pack in Main slot

M1

.

Result:

All alarms clear and service is restored.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

At the System View select

Configuration

→

Normal Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode is removed from the WaveStar

®

CIT alarm list.

STOP!

End of Procedure. This completes the back out procedure at the local node.

If other nodes are to be backed out, go to the adjacent node connected to the circuit pack in Main slot

M1

and return to

Step 1 .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-25

Ring and circuit pack upgrade procedures

Procedure 12-2.2: Back out high-speed OC-48 OLIU upgrade in BLSR network

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-2: “Back out high-speed OC-48 OLIU upgrade”

(p. 12-19) .

Step

1

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an in-service high-speed OC-48 OLIU circuit pack upgrade (in progress) at a node in a BLSR network.

.................................................................................................................................................................................................

Determine the status of the in-service high-speed OC-48 OLIU circuit pack upgrade.

If...

If the original OC-48 OLIU circuit pack in Main slot

M1

has been replaced and the

Configuration

→

Update System

→

Update All

command has not been performed,

If the original OC-48 OLIU circuit pack in Main slot

M1

has been replaced and the

Configuration

→

Update System

→

Update All

command has been performed,

If the original OC-48 OLIU circuit pack in Main slot

M2

has been replaced,

Then...

Continue with

Step 2 .

Proceed to

Step 4 .

Proceed to

Step 9 .

.................................................................................................................................................................................................

2

Important! The original OC-48 OLIU circuit pack in Main slot

M1

has been replaced and the

Configuration

→

Update System

→

Update All

command has

not been performed. The system reports an unexpected CP type alarm and

Line

Automatic Switch condition for Main slot

M1

.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the original OC-48 OLIU circuit pack.

.................................................................................................................................................................................................................................

12-26 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

3

4

5

Procedure 12-2.2: Back out high-speed OC-48 OLIU upgrade in BLSR network

Reference:

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

Obtain the original LBO, clean all fiber connectors, and connect the transmit and receive optical fibers to the original OC-48 OLIU circuit pack in Main slot

M1

.

Result:

All alarms clear and service is restored. The

Line Automatic Switch condition clears after the provisionable wait-to-restore interval elapses. (The default is 5 minutes.) This applies to the local node and the adjacent node connected to the circuit pack in Main slot

M1

.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

STOP!

End of Procedure. This completes the back out procedure at the local node.

If other nodes are to be backed out, go to the adjacent node connected to the circuit pack in Main slot

M1

and return to

Step 1 .

.................................................................................................................................................................................................

Important! The original OC-48 OLIU circuit pack in Main slot

M1

has been replaced and the

Configuration

→

Update System

→

Update All

command has been performed. The replacement OC-48 OLIU circuit pack in Main slot

M1

has been autoprovisioned, and the system has performed an automatic line protection switch. All traffic is now active on the circuit pack in Main slot

M1

.

The unexpected CP type alarm and

Line Automatic Switch condition for Main slot

M1

clear, and the system reports an unexpected CP type alarm and

Line

Automatic Switch condition for Main slot

M2

.

From the WaveStar

®

CIT System View select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

Alarm List shows the Ring Upgrade mode as Not Alarmed.

CIT

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this procedure.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-27

Ring and circuit pack upgrade procedures Procedure 12-2.2: Back out high-speed OC-48 OLIU upgrade in BLSR network

6

7

8

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The original OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned. The system performs an automatic line protection switch, and all traffic is now active on the circuit pack in Main slot

M2

.

Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in Main slot

M1

to the circuit pack in Main slot

M2

.

The unexpected CP type alarm and

Line Automatic Switch condition for Main slot

M2

clear, and the system reports an unexpected CP type alarm and

Line

Automatic Switch condition for Main slot

M1

.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the original OC-48 OLIU circuit pack.

Result:

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

Obtain the original LBO, clean all fiber connectors, and connect the transmit and receive optical fibers to the original OC-48 OLIU circuit pack in Main slot

M1

.

Result:

All alarms clear and service is restored. The

Line Automatic Switch condition clears after the provisionable wait-to-restore interval elapses. (The default is 5 minutes.) This applies to the local node and the adjacent node connected to the circuit pack in Main slot

M1

.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

At the System View select

Configuration

→

Normal Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode is removed from the WaveStar

®

CIT alarm list.

.................................................................................................................................................................................................................................

12-28 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-2.2: Back out high-speed OC-48 OLIU upgrade in BLSR network

9

10

11

12

STOP!

End of Procedure. This completes the back out procedure at the local node.

If other nodes are to be backed out, go to the adjacent node connected to the circuit pack in Main slot

M1

and return to

Step 1 .

.................................................................................................................................................................................................

Important! The original OC-48 OLIU circuit pack in Main slot

M2

has been replaced, and the unexpected CP type alarm for Main slot

M2

clears.

At the WaveStar

®

CIT System View select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

CIT

Alarm List shows the Ring Upgrade mode as Not Alarmed.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the original OC-48 OLIU circuit pack.

Result:

Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M2

. If active through traffic exists on the circuit pack in Main slot

M2

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected CP type alarm and a

Line Automatic Switch condition for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

Obtain the original LBO, clean all fiber connectors, and connect the transmit and receive optical fibers to the original OC-48 OLIU circuit pack in Main slot

M2

.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this procedure.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-29

Ring and circuit pack upgrade procedures Procedure 12-2.2: Back out high-speed OC-48 OLIU upgrade in BLSR network

13

14

15

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The original OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned. The system performs an automatic line protection switch, and all traffic is now active on the circuit pack in Main slot

M2

.

Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in Main slot

M1

to the circuit pack in Main slot

M2

.

The unexpected CP type alarm and

Line Automatic Switch condition for Main slot

M2

clear, and the system reports an unexpected CP type alarm and

Line

Automatic Switch condition for Main slot

M1

.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the original OC-48 OLIU circuit pack.

Result:

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

Obtain the original LBO, clean all fiber connectors, and connect the transmit and receive optical fibers to the original OC-48 OLIU circuit pack in Main slot

M1

.

Result:

All alarms clear and service is restored. The

Line Automatic Switch condition clears after the provisionable wait-to-restore interval elapses. (The default is 5 minutes.) This applies to the local node and the adjacent node connected to the circuit pack in Main slot

M1

.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

At the System View select

Configuration

→

Normal Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode is removed from the WaveStar

®

CIT alarm list.

.................................................................................................................................................................................................................................

12-30 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-2.2: Back out high-speed OC-48 OLIU upgrade in BLSR network

STOP!

End of Procedure. This completes the back out procedure at the local node.

If other nodes are to be backed out, go to the adjacent node connected to the circuit pack in Main slot

M1

and return to

Step 1 .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-31

Ring and circuit pack upgrade procedures

Procedure 12-3: Upgrade OC-3 UPSR to OC-12 UPSR

.................................................................................................................................................................................................................................

Overview

Important! The Metropolis

®

DMX product family does not support upgrading a

UPSR where all nodes are connected to the UPSR using port pairs in the

Function/Growth slots. Currently, Metropolis

®

DMX does not support OC-3 OLIU circuit packs in Main slots. Therefore, at least one Metropolis

®

DMXtend or

Metropolis

®

DMXplore node must be connected to the OC-3 UPSR using the Main slots and this node must be the starting node.

Use this procedure to upgrade an in-service OC-3 UPSR to an OC-12 UPSR.

Important! The UPSR must be equipped with Metropolis

®

DMX, Metropolis

®

DMXtend, and/or Metropolis

®

DMXplore nodes only. This upgrade procedure does

not support upgrading UPSRs equipped with nodes other than Metropolis

®

Metropolis

®

DMXtend, and/or Metropolis

®

DMXplore.

DMX,

This procedure assumes that one or more Metropolis

®

DMX nodes are interconnected in an OC-3 UPSR using a port pair in the Function/Growth slots with:

•

Metropolis

®

DMXtend: Metropolis

®

DMXtend nodes may be connected to the

UPSR using the Main slots or a port pair in the Function/Growth slots.

•

Metropolis

®

DMXplore: Metropolis

®

DMXplore nodes may be connected to the

UPSR using Main slots only.

At nodes connected to the UPSR using the Main slots, the OC-3 circuit packs in the

Main slots are replaced with OC-12 circuit packs. At nodes connected to the UPSR using a port pair in the Function/Growth slots, traffic is bridged/rolled to an OC-12 port pair in a different Function/Growth group.

This procedure assumes that in the UPSR, the circuit pack in Main/Function/Growth slot 1 is always connected to the circuit pack in Main/Function/Growth slot 2 at the adjacent node. (Refer to the

“UPSR example” (p. 12-35)

at the end of the procedure.)

If other network connections exist, for example, the circuit pack in Main slot 2 is connected to the circuit pack in Function/Growth slot 2 at the adjacent node, modify this procedure as required.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

The following equipment is required to perform this procedure:

•

Wrist strap

•

Optical power meter

.................................................................................................................................................................................................................................

12-32 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-3: Upgrade OC-3 UPSR to OC-12 UPSR

•

As optical spans are upgraded around the UPSR, ensure that technicians are available at each end of an optical span as it is upgraded.

•

At each Metropolis

®

DMX and Metropolis

®

DMXtend node connected to the

UPSR using a port pair in the Function/Growth slots, an OC-12 port pair on an

LNW46 or LNW49 OC-12 OLIU circuit pack pair in a different Function/Growth group

If required, install the OC-12 OLIU circuit packs/pluggable transmission modules in the Function/Growth group and provision the OC-12 port and DCC termination parameters. Refer to

Chapter 4, “Install and provision circuit packs/OLIUs procedures” .

The replacement OC-12 port pair must have compatible optics. For example, do not replace a port pair that has long reach optics with a port pair that has intermediate reach optics. Refer to the Metropolis

®

DMX Access Multiplexer Applications and

Planning Guide, 365-372-300 for the SONET optical specifications.

•

Refer to the Metropolis

®

DMXtend Access Multiplexer User Operations Guide,

365-372-325 for the circuit packs required at Metropolis

®

DMXtend nodes connected to the UPSR using the Main slots.

•

Refer to the Metropolis

®

DMXplore Access Multiplexer User Operations Guide,

365-372-332 for the circuit packs required at Metropolis

®

DMXplore nodes connected to the UPSR using the Main slots.

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-33

Ring and circuit pack upgrade procedures Procedure 12-3: Upgrade OC-3 UPSR to OC-12 UPSR

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Obtain the work instructions for this procedure.

3. Review the applicable office records and verify that each fiber span in the UPSR is capable of supporting higher rate (OC-12) traffic. Refer to the Metropolis

®

DMX

Access Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-12 OLIU circuit packs. If required, refer to the

Metropolis

®

DMXtend Access Multiplexer Applications and Planning Guide,

365-372-324 and Metropolis

®

DMXplore Access Multiplexer Applications and

Planning Guide, 365-372-331.

4. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this upgrade procedure. If required, refer to the Metropolis

®

DMXtend Access Multiplexer

Software Release Description and Metropolis

®

DMXplore Access Multiplexer

Software Release Description.

5. Review the Metropolis

®

DMXtend Access Multiplexer User Operations Guide,

365-372-325 and Metropolis

®

DMXplore Access Multiplexer User Operations

Guide, 365-372-332 for procedures or cautions that may apply to this upgrade procedure.

Step

1

2

Complete the following steps to upgrade an in-service OC-3 UPSR to an OC-12

UPSR.

.................................................................................................................................................................................................

From office records and work instructions, determine the current network configuration. Note how the nodes are connected in the ring and make a drawing of the ring to reference during this upgrade.

.................................................................................................................................................................................................

Important! Because the starting node must be connected to the UPSR using the

Main slots and Metropolis

®

DMX does not support OC-3 OLIU circuit packs in the

Main slots, the starting node must be a Metropolis

®

DMXtend or Metropolis

®

DMXplore node.

.................................................................................................................................................................................................................................

12-34 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-3: Upgrade OC-3 UPSR to OC-12 UPSR

If the starting node is a...

Metropolis

®

DMXtend,

Metropolis

®

DMXplore,

Then proceed to and perform...

Procedure 12-1: Upgrade OC-3 UPSR to

OC-12 UPSR in the Metropolis

®

DMXtend

Access Multiplexer User Operations

Guide, 365-372-325 to upgrade an in-service OC-3 UPSR to an OC-12

UPSR.

Procedure 12-3: Upgrade OC-3 UPSR to

OC-12 UPSR in the Metropolis

®

DMXplore Access Multiplexer User

Operations Guide, 365-372-332 to upgrade an in-service OC-3 UPSR to an

OC-12 UPSR.

E

N D O F

S

T E P S

UPSR example

Starting Node

: Metropolis

®

UPSR using the Main Slots

DMXtend or Metropolis

®

DMXplore connected to the

Starting Circuit Pack

: Main-2 at the Starting Node

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-35

Ring and circuit pack upgrade procedures Procedure 12-3: Upgrade OC-3 UPSR to OC-12 UPSR

Direction of Upgrade

: Clockwise around UPSR from Main-2 at the Starting Node to

Main/Function/Growth slot 1 at the adjacent node

Node C

DMX or DMXtend

MAIN-1 MAIN-2

FN-x-1 or

Growth-1

FN-x-2 or

Growth-2

Node B

DMX

plore

or

DMX

tend

or

Other

DMXplore

MAIN-2

(physical)

MAIN-1

(physical)

OC3/OC12

MAIN-2

(virtual)

DS1

FN-A-2

(virtual)

DS3

FN-B-2

(virtual)

Node A

OC3/OC12

MAIN-1

(virtual)

DS1

FN-A-1

(virtual)

DS3

FN-B-1

(virtual)

DMX = Metropolis DMX Access Multiplexer

DMX

DMX

plore tend

= Metropolis DMX

plore

= Metropolis DMX

tend

Access Multiplexer

Access Multiplexer

Node D

DMX

plore

or

DMX

tend

or

Other

MA-DMXplore-046

.................................................................................................................................................................................................................................

12-36 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-3.1: Upgrade low-speed OC-3 UPSR connections at node

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by another procedure.

When upgrading connections to a UPSR using a port pair in the Function/Growth slots, the node is not required to be in the provisioned Ring Upgrade mode.

Step

1

2

3

4

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade the in-service UPSR connections at a

Metropolis

®

DMX node that is connected to the UPSR using a port pair in the

Function/Growth slots.

.................................................................................................................................................................................................

Important! An OC-12 port pair must be available in a different Function/Growth group.

Provision the required OC-12 port pair according to the work instructions using the

Configuration

→

Equipment

command.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

To verify that the OC-12 port parameters were provisioned correctly, select

View

→

Equipment

and expand the required circuit pack. Click on the required port and

Select

to obtain the port parameters. Click

Close

.

.................................................................................................................................................................................................

Provision the required OC-12 port DCC parameters according to the work instructions using the

Configuration

→

DCC Terminations

command.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

To verify that the OC-12 port DCC parameters were provisioned correctly, select

View

→

DCC Terminations

to obtain the DCC channel status. Click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-37

Ring and circuit pack upgrade procedures Procedure 12-3.1: Upgrade low-speed OC-3 UPSR connections at node

5

6

7

.................................................................................................................................................................................................

Important! All cross-connections at this node that are associated with the existing

OC-3 UPSR must be identified so that traffic can be moved to the OC-12 UPSR.

Select

View

→

Cross-Connections

. Expand the required OC-3 OLIU circuit pack in slot 1 of the Function/Growth group that is currently connected to the OC-3 UPSR.

Click on the required OC-3 port and

Select

to obtain the current list of cross-connections. Identify and record all through, add, drop, and UPSR Dual Ring

Interworking cross-connections. Click

Close

to exit.

Important! A UPSR Dual Ring Interworking cross-connection consists of a 1-way add, a 1-way through, and a 1-way path protected drop cross-connection. To verify that a cross-connection leg is part of a UPSR Dual Ring Interworking cross-connection, click on the cross-connection leg in the list of cross-connections and click

View Graphic

.

For additional information about UPSR Dual Ring Interworking cross-connections, refer to

Procedure 10-11: “Establish dual ring interworking (DRI) connections”

(p. 10-56) .

.................................................................................................................................................................................................

For each UPSR Dual Ring Interworking cross-connection identified in

Step 5 , select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to delete the UPSR Dual Ring Interworking cross-connections. Then use the Cross-Connection

Wizard to create the same UPSR Dual Ring Interworking cross-connections on the required OC-12 port pair in the other Function/Growth group.

Result:

Transmission hits (less than 60 ms) may occur. Alarms may be reported at other nodes in the ring.

Reference:

Procedure 10-11: “Establish dual ring interworking (DRI) connections”

(p. 10-56)

.................................................................................................................................................................................................

Important! Do not perform this step for a 1-way through cross-connection associated with a UPSR Dual Ring Interworking cross-connection.

For each through cross-connection identified in

Step 5

that is not part of a UPSR Dual

Ring Interworking cross-connection, select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to create the same through cross-connections on the required OC-12 port pair in the other Function/Growth group.

.................................................................................................................................................................................................................................

12-38 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-3.1: Upgrade low-speed OC-3 UPSR connections at node

8

Reference:

Procedure 10-5: “Make VT1.5 or STS-n cross-connections, single

OC-3/OC-12 UPSR configuration” (p. 10-16)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Removal of wrong fiber connections will result in a service interruption.

Ensure that you remove only the fiber connections for the optical span being upgraded.

9

10

Disconnect the transmit and receive optical fibers from the required OC-3 port on the

OC-3 OLIU circuit pack in slot 1 of the Function/Growth group.

Result:

The system still reports an inc. OC3 LOS alarm for the OC-3 port.

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the

OC-12 port on the OC-12 OLIU circuit pack in slot 1 of the other Function/Growth group and the required OC-12 circuit pack/port at the opposite end of the upgraded

OC-12 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-12 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! Do not perform this step for a 1-way add cross-connection associated with a UPSR Dual Ring Interworking cross-connection.

For each add cross-connection identified in

Step 5

that is not part of a UPSR Dual

Ring Interworking cross-connection, select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to bridge the add cross-connections to the required

OC-12 port on the OC-12 OLIU circuit pack in slot 1 of the other Function/Growth group.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-39

Ring and circuit pack upgrade procedures Procedure 12-3.1: Upgrade low-speed OC-3 UPSR connections at node

11

12

Reference:

Procedure 10-10: “Bridge and roll cross-connections” (p. 10-48)

.................................................................................................................................................................................................

Important! Do not perform this step for a 1-way path protected drop cross-connection associated with a UPSR Dual Ring Interworking cross-connection.

For each drop cross-connection identified in

Step 5

that is not part of a UPSR Dual

Ring Interworking cross-connection, select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to roll the drop cross-connections to the required

OC-12 port on the OC-12 OLIU circuit pack in slot 1 of the other Function/Growth group.

Reference:

Procedure 10-10: “Bridge and roll cross-connections” (p. 10-48)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Removal of wrong fiber connections will result in a service interruption.

Ensure that you remove only the fiber connections for the optical span being upgraded.

Important! Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-3 circuit pack is upgraded at each end of the optical span.

Disconnect the transmit and receive optical fibers from the required OC-3 port on the

OC-3 OLIU circuit pack in slot 2 of the Function/Growth group.

Result:

The system reports inc. OC3 LOS alarms for the original OC-3 ports.

Alarms may also be reported at other nodes in the ring.

STOP!

To complete the UPSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-40 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-3.2: Place holder

.................................................................................................................................................................................................................................

Step

1

.................................................................................................................................................................................................

This is a place holder for a future procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-41

Ring and circuit pack upgrade procedures

Procedure 12-4: Back out OC-3 UPSR to OC-12 UPSR upgrade

.................................................................................................................................................................................................................................

Overview

CAUTION

Service disruption hazard

If a node has been taken out of the Ring Upgrade mode, the node cannot be returned to the original pre-upgrade state without affecting service.

All nodes in the ring must be in the provisioned Ring Upgrade mode.

Use this procedure to back out an OC-3 UPSR to OC-12 UPSR upgrade.

Backing out of an upgrade in progress returns all nodes in the ring to their pre-upgrade state.

To temporarily stop (suspend) the upgrade refer to Metropolis

®

DMXtend Access

Multiplexer User Operations Guide, 365-372-325 or Metropolis

®

DMXplore Access

Multiplexer User Operations Guide, 365-372-332. The upgrade cannot be suspended at a Metropolis

®

DMX node. Suspending an upgrade at a node connected to the UPSR using port pairs in the Function/Growth slots is not supported.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

The following equipment is required to perform this procedure:

•

Wrist strap

•

Original OC-3 OLIU circuit packs/port pairs for each node to be backed out

•

As the upgrade is backed out around the UPSR, ensure that technicians are available at each end of an optical span as the upgrade is backed out.

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

.................................................................................................................................................................................................................................

12-42 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-4: Back out OC-3 UPSR to OC-12 UPSR upgrade

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this back out procedure. If required, refer to the Metropolis

®

DMXtend Access Multiplexer

Software Release Description and Metropolis

®

DMXplore Access Multiplexer

Software Release Description.

3. Review the Metropolis

®

DMXtend Access Multiplexer User Operations Guide,

365-372-325 and Metropolis

®

DMXplore Access Multiplexer User Operations

Guide, 365-372-332 for procedures or cautions that may apply to this backout procedure.

Step

1

Important! This procedure starts at the last node upgraded.

Complete the following steps to back out of an OC-3 UPSR to OC-12 UPSR upgrade.

.................................................................................................................................................................................................

From office records and work instructions, determine the current network configuration and status of the upgrade.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-43

Ring and circuit pack upgrade procedures

2

Procedure 12-4: Back out OC-3 UPSR to OC-12 UPSR upgrade

.................................................................................................................................................................................................

Important! Because the starting node must be connected to the UPSR using the

Main slots and Metropolis

®

DMX does not support OC-3 OLIU circuit packs in the

Main slots, the starting node must be a Metropolis

®

DMXtend or Metropolis

®

DMXplore node.

If the starting node is a...

Metropolis

®

DMXtend,

Metropolis

®

DMXplore,

Then proceed to and perform...

Procedure 12-2: Back out OC-3 UPSR to

OC-12 UPSR upgrade in the Metropolis

®

DMXtend Access Multiplexer User

Operations Guide, 365-372-325 to back out of an OC-3 UPSR to OC-12 UPSR upgrade.

Procedure 12-4: Back out OC-3 UPSR to

OC-12 UPSR upgrade in the Metropolis

®

DMXplore Access Multiplexer User

Operations Guide, 365-372-332 to back out of an OC-3 UPSR to OC-12 UPSR upgrade.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

12-44 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

UPSR example

Procedure 12-4: Back out OC-3 UPSR to OC-12 UPSR upgrade

Node C

DMX or DMXtend

MAIN-1 MAIN-2

FN-x-1 or

Growth-1

FN-x-2 or

Growth-2

Node B

DMX

plore

or

DMX

tend

or

Other

DMXplore

MAIN-2

(physical)

MAIN-1

(physical)

OC3/OC12

MAIN-2

(virtual)

DS1

FN-A-2

(virtual)

DS3

FN-B-2

(virtual)

Node A

OC3/OC12

MAIN-1

(virtual)

DS1

FN-A-1

(virtual)

DS3

FN-B-1

(virtual)

DMX = Metropolis DMX Access Multiplexer

DMX

DMX

plore tend

= Metropolis DMX

plore

= Metropolis DMX

tend

Access Multiplexer

Access Multiplexer

Node D

DMX

plore

or

DMX

tend

or

Other

MA-DMXplore-046

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-45

Ring and circuit pack upgrade procedures

Procedure 12-4.1: Back out low-speed OC-3 to OC-12 UPSR upgrade at node

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by another procedure.

Step

1

Important! This procedure assumes that the Metropolis

®

DMX node is still equipped with the original OC-3 OLIU circuit packs/pluggable transmission modules.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-3 UPSR to OC-12 UPSR upgrade at a

Metropolis

®

DMX node connected to the UPSR using a port pair in the

Function/Growth slots.

.................................................................................................................................................................................................

Determine the current status of the upgrade at the node.

If the port in...

both Function/Growth slot 1 and 2 have been upgraded to OC-12 ports, only Function/Growth slot 1 has been upgraded to an OC-12 port,

Then...

Continue with

Step 2 .

Proceed to

Step 12 .

2

3

.................................................................................................................................................................................................

To verify that the original OC-3 port parameters are provisioned correctly, select

View

→

Equipment

and expand the required circuit pack. Click on the original port and

Select

to obtain the port parameters. Click

Close

.

If required, provision the original OC-3 port pair according to the office records using the

Configuration

→

Equipment

command.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

To verify that the original OC-3 port DCC parameters are provisioned correctly, select

View

→

DCC Terminations

to obtain the DCC channel status. Click

Close

.

.................................................................................................................................................................................................................................

12-46 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-4.1: Back out low-speed OC-3 to OC-12

UPSR upgrade at node

If required, provision the original OC-3 port DCC parameters according to the office records using the

Configuration

→

DCC Terminations

command.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

4

5

6

Important! All cross-connections at this node that are associated with the OC-12

UPSR must be identified so that traffic can be moved back to the original OC-3

UPSR.

Select

View

→

Cross-Connections

. Expand the required OC-12 OLIU circuit pack in slot 2 of the Function/Growth group that is currently connected to the UPSR. Click on the required OC-12 port and

Select

to obtain the current list of cross-connections.

Identify and record all through, add, drop, and UPSR Dual Ring Interworking cross-connections. Click

Close

to exit.

Important! A UPSR Dual Ring Interworking cross-connection consists of a 1-way add, a 1-way through, and a 1-way path protected drop cross-connection. To verify that a cross-connection leg is part of a UPSR Dual Ring Interworking cross-connection, click on the cross-connection leg in the list of cross-connections and click

View Graphic

.

For additional information about UPSR Dual Ring Interworking cross-connections, refer to

Procedure 10-11: “Establish dual ring interworking (DRI) connections”

(p. 10-56) .

.................................................................................................................................................................................................

Repeat

Step 4

to obtain a current list of cross-connections for the original OC-3 port in slot 2 of the other Function/Growth group. Compare the original OC-3 port cross-connection list with the upgrade OC-12 port cross-connection list.

.................................................................................................................................................................................................

For each UPSR Dual Ring Interworking cross-connection identified in

Step 4 , select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to delete the UPSR Dual Ring Interworking cross-connections. Then use the Cross-Connection

Wizard to create the same UPSR Dual Ring Interworking cross-connections on the original OC-3 port pair in the other Function/Growth group.

Result:

Transmission hits (less than 60 ms) may occur. Alarms may be reported at other nodes in the ring.

Reference:

Procedure 10-11: “Establish dual ring interworking (DRI) connections”

(p. 10-56)

.................................................................................................................................................................................................

7

Important! Refer to the cross-connection list obtained in

Step 4

when performing this step.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-47

Ring and circuit pack upgrade procedures Procedure 12-4.1: Back out low-speed OC-3 to OC-12

UPSR upgrade at node

8

Do not perform this step for a 1-way through cross-connection associated with a

UPSR Dual Ring Interworking cross-connection.

If required, select

Configuration

→

Cross-Connections

and use the Cross-Connection

Wizard to create the required through cross-connections on the original OC-3 port pair.

Reference:

Procedure 10-5: “Make VT1.5 or STS-n cross-connections, single

OC-3/OC-12 UPSR configuration” (p. 10-16)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Removal of wrong fiber connections will result in a service interruption.

Ensure that you remove only the fiber connections for the optical span being upgraded.

9

10

Disconnect the transmit and receive optical fibers from the upgrade OC-12 port on the

OC-12 OLIU circuit pack in slot 2 of the Function/Growth group.

Result:

The system still reports an inc. OC12 LOS alarm for the OC-12 port.

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-3 port on the OC-3 OLIU circuit pack in slot 2 of the other

Function/Growth group and the required OC-3 circuit pack/port at the opposite end of the original OC-3 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-3 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! Refer to the cross-connection list obtained in

Step 4

when performing this step.

Do not perform this step for a 1-way add cross-connection associated with a UPSR

Dual Ring Interworking cross-connection.

.................................................................................................................................................................................................................................

12-48 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

11

12

Procedure 12-4.1: Back out low-speed OC-3 to OC-12

UPSR upgrade at node

If required, select

Configuration

→

Cross-Connections

and use the Cross-Connection

Wizard to bridge the required add cross-connections to the original OC-3 port on the

OC-3 OLIU circuit pack in slot 2 of the other Function/Growth group.

Reference:

Procedure 10-10: “Bridge and roll cross-connections” (p. 10-48)

.................................................................................................................................................................................................

Important! Refer to the cross-connection list obtained in

Step 4

when performing this step.

Do not perform this step for a 1-way path protected drop cross-connection associated with a UPSR Dual Ring Interworking cross-connection.

Select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to roll the required drop cross-connections to the original OC-3 port on the OC-3 OLIU circuit pack in slot 2 of the other Function/Growth group.

Reference:

Procedure 10-10: “Bridge and roll cross-connections” (p. 10-48)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Removal of wrong fiber connections will result in a service interruption.

Ensure that you remove only the fiber connections for the optical span being upgraded.

13

14

Important! Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-12 circuit pack is backed out at each end of the optical span.

Disconnect the transmit and receive optical fibers from the upgrade OC-12 port on the

OC-12 OLIU circuit pack in slot 1 of the Function/Growth group.

Result:

The system reports inc. LOS alarms for the upgrade OC-12 ports and the original OC-3 port on the OC-3 OLIU circuit pack in slot 1 of the Function/Growth group. Alarms may also be reported at other nodes in the ring.

.................................................................................................................................................................................................

Select

Configuration

→

Update System

→

Update All

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The inc. OC12 LOS alarms for the upgrade OC-12 ports clear.

.................................................................................................................................................................................................

Select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to delete the remaining add and through cross-connections to the upgrade OC-12 ports.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-49

Ring and circuit pack upgrade procedures Procedure 12-4.1: Back out low-speed OC-3 to OC-12

UPSR upgrade at node

STOP!

To complete backing out the UPSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-50 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-4.2: Place holder

.................................................................................................................................................................................................................................

Step

1

.................................................................................................................................................................................................

This is a place holder for a future procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-51

Ring and circuit pack upgrade procedures

Procedure 12-5: Upgrade OC-12 UPSR to OC-48 UPSR

.................................................................................................................................................................................................................................

Overview

Important! Metropolis

®

DMX product family does not support upgrading a UPSR where all nodes are connected to the UPSR using port pairs in the Function/Growth slots. At least one node must be connected to the UPSR using the Main slots and this node must be the starting node.

Use this procedure to upgrade an in-service OC-12 UPSR to an OC-48 UPSR.

Important! The UPSR must be equipped with Metropolis

®

DMX and/or

Metropolis

®

DMXtend nodes only. This upgrade procedure does not support upgrading UPSRs equipped with nodes other than Metropolis

®

Metropolis

®

DMXtend.

DMX and/or

This procedure assumes that one or more Metropolis

®

DMX nodes are interconnected in an OC-12 UPSR using the Main slots or a port pair in the Function/Growth slots with Metropolis

®

DMXtend. Metropolis

®

DMXtend nodes may be connected to the

UPSR using the Main slots or a port pair in the Function/Growth slots.

At Metropolis

®

DMX nodes connected to the UPSR using the Main slots, the OC-12

OLIU circuit packs in the Main slots are replaced with the following OC-48 OLIU circuit packs:

•

LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIU circuit packs at one or more nodes.

These OC-48 OLIU circuit packs have different optics and transmit at different wavelengths. However, these circuit packs have the same circuit pack type and a

small VT cross-connection fabric. There are no differences between these circuit packs for the purposes of ring upgrades.

•

LNW27, LNW29, LNW32, LNW76, and/or LNW221-259 OC-48 OLIU circuit packs at all nodes.

These OC-48 OLIU circuit packs have different optics and transmit at different wavelengths. However, these circuit packs have the same circuit pack type and a

large VT cross-connection fabric. There are no differences between these circuit packs for the purposes of ring upgrades.

At nodes connected to the UPSR using a port pair in the Function/Growth slots, traffic is bridged/rolled to an OC-48 port pair in a different Function/Growth group.

This procedure assumes that in the UPSR, the circuit pack in Main/Function/Growth slot 1 is always connected to the circuit pack in Main/Function/Growth slot 2 at the adjacent node. If other network connections exist, for example, the circuit pack in

Main slot 2 is connected to the circuit pack in Function/Growth slot 2 at the adjacent node, modify this procedure as required.

.................................................................................................................................................................................................................................

12-52 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-5: Upgrade OC-12 UPSR to OC-48 UPSR

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

The following equipment is required to perform this procedure:

•

Optical power meter

•

Wrist strap

•

As optical spans are upgraded around the UPSR, ensure that technicians are available at each end of an optical span as it is upgraded.

•

At the Metropolis

®

DMX starting node, 1 LNW26B OC-48 OLIU circuit pack with the enhanced/normal jumper set to enhanced (temporarily required if the starting node is to be upgraded with LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIU circuit packs).

An LNW28, LNW77, or LNW121B-159B OC-48 OLIU circuit pack may also be used as the temporary replacement circuit pack. However, the temporary replacement circuit pack must have compatible optics. For example, do not replace a circuit pack that has long reach optics with a circuit pack that has intermediate reach optics. Refer to Metropolis

®

DMX Access Multiplexer Applications and

Planning Guide, 365-372-300 for the SONET optical specifications.

•

At each Metropolis

®

DMX node connected to the UPSR using the Main slots, 2 replacement LNW26B, LNW27, LNW28, LNW29, LNW32, LNW76, LNW77

LNW121B-159B, or LNW221-259 OC-48 OLIU circuit packs.

The replacement circuit packs must have compatible optics. For example, do not replace a circuit pack that has long reach optics with a circuit pack that has intermediate reach optics. Refer to Metropolis

®

DMX Access Multiplexer

Applications and Planning Guide, 365-372-300 for the SONET optical specifications.

•

At each node connected to the UPSR using a port pair in the Function/Growth slots, an OC-48 port pair on an LNW31 or LNW421-459 OC-48 OLIU circuit pack pair in a different Function/Growth group.

If required, install the OC-48 OLIU circuit packs in the Function/Growth group and provision the OC-48 port and DCC termination parameters. Refer to

Procedure 4-3:

“Install OLIU circuit packs in Function slots” (p. 4-14) .

The replacement circuit packs must have compatible optics. For example, do not replace a circuit pack that has long reach optics with a circuit pack that has intermediate reach optics. Refer to Metropolis

®

DMX Access Multiplexer

Applications and Planning Guide, 365-372-300 for the SONET optical specifications.

•

Refer to the Metropolis

®

DMXtend Access Multiplexer User Operations Guide,

365-372-325 for the circuit packs required at Metropolis

®

DMXtend nodes connected to the UPSR using the Main slots.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-53

Ring and circuit pack upgrade procedures Procedure 12-5: Upgrade OC-12 UPSR to OC-48 UPSR

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Obtain the work instructions for this procedure.

3. Review the applicable office records and verify that each fiber span in the UPSR is capable of supporting higher rate (OC-48) traffic. Refer to the Metropolis

®

DMX

Access Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 OLIU circuit packs. If required, refer to the

Metropolis

®

DMXtend Access Multiplexer Applications and Planning Guide,

365-372-324.

4. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this upgrade procedure. If required, refer to the Metropolis

®

DMXtend Access Multiplexer

Software Release Description.

5. Review the Metropolis

®

DMXtend Access Multiplexer User Operations Guide,

365-372-325 for procedures or cautions that may apply to this upgrade procedure.

.................................................................................................................................................................................................................................

12-54 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Step

Procedure 12-5: Upgrade OC-12 UPSR to OC-48 UPSR

1

2

3

4

Complete the following steps to upgrade an in-service OC-12 UPSR to an OC-48

UPSR.

.................................................................................................................................................................................................

From office records and work instructions, determine the current network configuration. Note how the nodes are connected in the ring and make a drawing of the ring to reference during this upgrade procedure.

.................................................................................................................................................................................................

Important! The starting node must be connected to the OC-12 UPSR using the

Main slots. This procedure assumes that the starting node is a Metropolis

®

DMX.

If one or more Metropolis

®

DMX nodes connected to the UPSR using the Main slots are to be upgraded with LNW26B, LNW28, LNW77, and/or LNW121B-159B

OC-48 OLIU circuit packs, it is recommended that one of these nodes be designated the starting node.

Identify and log in to the Metropolis

®

DMX starting node.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the NE Alarm List and verify that no alarms are present.

Refer to the appropriate trouble clearing procedures to clear all existing alarms before continuing with this procedure.

Reference:

•

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble Clearing

Guide, 365-372-302

•

Metropolis

®

DMXtend Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-326

.................................................................................................................................................................................................

To verify that no loopbacks, protection switch lockouts, or protection switches are present, select

View

→

Rolling Events

. Under the line reading

RTRV-COND-ALL determine if any loopbacks, protection switch lockouts, or protection switches are displayed.

Remove all existing loopbacks, protection switch lockouts, or protection switches before continuing with this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-55

Ring and circuit pack upgrade procedures Procedure 12-5: Upgrade OC-12 UPSR to OC-48 UPSR

5

6

7

Reference:

•

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble Clearing

Guide, 365-372-302

•

Metropolis

®

DMXtend Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-326

.................................................................................................................................................................................................

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and verify that no test access sessions exist.

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and delete all existing test access sessions.

Reference:

•

Procedure 14-27: “View test access session(s)” (p. 14-130)

•

Procedure 14-26: “Delete test access session” (p. 14-129)

.................................................................................................................................................................................................

If Ethernet service is provisioned with spanning tree protection, verify that the spanning tree states are correct by selecting

View

→

Data

→

Spanning Tree Group

.

Expand the required circuit pack, select the appropriate spanning tree and click

Select

.

Observe the VCG Status. All VCGs should be forwarding (FWG) packets, except for one VCG that should be discarding (DCD) packets. If this is not the case, contact

Technical Support Services (TSS) for assistance in correcting the spanning tree states before continuing with this procedure.

.................................................................................................................................................................................................

At each of the remaining nodes in the UPSR, log in to the node and repeat

Step 3

through

Step 6 . Then continue with the next step.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

8

If ...

all Metropolis

®

DMX nodes connected to the UPSR using the

Main slots are to be upgraded with

LNW27, LNW29, LNW32,

LNW76, and/or LNW221-259

OC-48 OLIU circuit packs,

Then proceed to and perform...

Procedure 12-5.1: “Upgrade OC-12 UPSR to

OC-48 UPSR using LNW27, LNW29, LNW32,

LNW76, and/or LNW221-259 OC-48 OLIUs at all nodes using Main slots” (p. 12-58)

.................................................................................................................................................................................................................................

12-56 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-5: Upgrade OC-12 UPSR to OC-48 UPSR

If ...

one or more Metropolis

®

DMX nodes connected to the UPSR using the Main slots are to be upgraded with LNW26B, LNW28,

LNW77, and/or LNW121B-159B

OC-48 OLIU circuit packs,

Then proceed to and perform...

Procedure 12-5.2: “Upgrade OC-12 UPSR to

OC-48 UPSR using LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIUs at one or more nodes using Main slots” (p. 12-69)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-57

Ring and circuit pack upgrade procedures

Procedure 12-5.1: Upgrade OC-12 UPSR to OC-48 UPSR using

LNW27, LNW29, LNW32, LNW76, and/or LNW221-259

OC-48 OLIUs at all nodes using Main slots

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by another procedure.

Step

1

2

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade an in-service OC-12 UPSR to an OC-48

UPSR using LNW27, LNW29, LNW32, LNW76, and/or LNW221-259 OC-48 OLIU circuit packs at all Metropolis

®

DMX nodes connected to the UPSR using the Main slots.

.................................................................................................................................................................................................

Important! The starting node must be connected to the OC-12 UPSR using the

Main slots. This procedure assumes that the starting node is a Metropolis

®

DMX.

Identify and log in to the Metropolis

®

DMX starting node (refer to the

“UPSR example” (p. 12-68)

at the end of the procedure).

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The Ring Upgrade mode allows cross-connections/ data to be mapped to the new circuit pack and prohibits provisioning new cross-connections.

At the WaveStar

®

CIT System View, select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

Alarm List shows the Ring Upgrade mode as Not Alarmed.

CIT

.................................................................................................................................................................................................................................

12-58 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-5.1: Upgrade OC-12 UPSR to OC-48

UPSR using LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs at all nodes using Main slots

The node remains in the Ring Upgrade mode until manually provisioned back to the Normal mode. While in the Ring Upgrade mode, the upgrade may be temporarily suspended or backed out. To prevent errors in the upgraded ring, keep the nodes connected to the UPSR using the Main slots in Ring Upgrade mode until all nodes have been upgraded.

.................................................................................................................................................................................................

3

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-12 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 11 .

Continue with

Step 4 .

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-12 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-59

Ring and circuit pack upgrade procedures Procedure 12-5.1: Upgrade OC-12 UPSR to OC-48

UPSR using LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs at all nodes using Main slots

If the OC-12 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

6

.................................................................................................................................................................................................

If required, repeat

Step 4

to verify that the OC-12 OLIU circuit pack in Main slot

M1

is now the active circuit pack for timing.

7

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M2

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-12 OLIU circuit pack in Main slot

M2

.

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m2-()-() paths supported by the circuit pack in Main slot

M2

(Ring

2). Record the active paths supported by the circuit pack in Main slot

M2

(Ring 2).

Click

Close

.

.................................................................................................................................................................................................

8

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M2

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M2

. In UPSRs, each path supported by the circuit pack in Main slot

M2

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-12 OLIU circuit pack in Main slot

M2

is not the active circuit pack for transmission, proceed to

Step 10 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

9

Repeat

Step 8

for each path supported by the circuit pack in Main slot

M2

. Click

Close

.

.................................................................................................................................................................................................................................

12-60 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-5.1: Upgrade OC-12 UPSR to OC-48

UPSR using LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs at all nodes using Main slots

.................................................................................................................................................................................................

10

If required, repeat

Step 7

to verify that the OC-12 OLIU circuit pack in Main slot is now the active circuit pack for transmission.

M1

.................................................................................................................................................................................................

11

Important! Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-12 circuit pack is upgraded at each end of the optical span.

At the starting node, the OC-12 OLIU circuit pack in Main slot

M2

must be first replaced with the temporary replacement OC-48 OLIU circuit pack. The temporary replacement OC-48 OLIU circuit pack maintains traffic while slot

M1

and the other nodes in the ring are upgraded. As a final step, this temporary replacement OC-48

OLIU circuit pack is upgraded.

Open a faceplate latch on the OC-12 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-12 OLIU circuit pack in Main slot

M2

. Then replace the OC-12 OLIU circuit pack in Main slot

M2

with the temporary replacement OC-48 OLIU circuit pack.

Result:

The temporary replacement OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned. Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M2

. If active through traffic exists on the circuit pack in Main slot

M2

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected circuit pack type condition and an inc.

OC48 LOS alarm for Main slot

M2

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

This completes the first phase of the upgrade at the starting node. The starting node upgrade will be completed after all the other nodes in the ring are upgraded.

12

.................................................................................................................................................................................................

Log in to the adjacent node connected to Main/Function/Growth slot 2 (refer to the

“UPSR example” (p. 12-68)

at the end of the procedure).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-61

Ring and circuit pack upgrade procedures Procedure 12-5.1: Upgrade OC-12 UPSR to OC-48

UPSR using LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs at all nodes using Main slots

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

13

.................................................................................................................................................................................................

Determine how the node is connected to the UPSR and upgrade the UPSR connections.

If ...

Metropolis

®

DMX connected to the

UPSR using the circuit packs in the

Main slots,

Metropolis

®

DMX connected to the

UPSR using the circuit packs in the

Function/Growth slots,

Metropolis

®

DMXtend connected to the UPSR using the circuit packs in the Main slots,

Metropolis

®

DMXtend connected to the UPSR using the circuit packs in the Function/Growth slots,

Then ...

Upgrade the high-speed UPSR connections using

Procedure 12-5.3: “Upgrade high-speed UPSR connections at node using LNW27, LNW29,

LNW32, LNW76, and/or LNW221-259 OC-48

OLIUs” (p. 12-79) . Then continue with

Step 14 .

Upgrade the low-speed UPSR connections using

Procedure 12-5.5: “Upgrade low-speed OC-12

UPSR connections at node” (p. 12-89) . Then

continue with

Step 14 .

Upgrade the high-speed UPSR connections using

Procedure 12-4.2: Upgrade high-speed OC-12

UPSR connections at node in Metropolis

®

.

DMXtend Access Multiplexer User Operations

Guide, 365-372-325. Then continue with

Step 14

Upgrade the low-speed UPSR connections using

Procedure 12-4.1: Upgrade low-speed OC-12

UPSR connections at node in Metropolis

®

.

DMXtend Access Multiplexer User Operations

Guide, 365-372-325. Then continue with

Step 14

14

.................................................................................................................................................................................................

Except for the starting node, have all nodes in the UPSR been upgraded.

If...

No

Yes

Then...

Repeat

Step 12

and

Step 13

as required at the next node (refer to the

“UPSR example”

(p. 12-68)

at the end of the procedure).

Continue with

Step 15 .

.................................................................................................................................................................................................................................

12-62 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-5.1: Upgrade OC-12 UPSR to OC-48

UPSR using LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs at all nodes using Main slots

.................................................................................................................................................................................................

15

Log in to the starting node (refer to the procedure).

“UPSR example” (p. 12-68)

at the end of the

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

16

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M2

clears, and the system reports an unexpected circuit pack type condition for Main slot

M1

.

.................................................................................................................................................................................................

17

Important! Local operating procedures for removing a circuit pack may vary. One method is to simply remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-12 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then remove the circuit pack,

Then...

Proceed to

Step 21 .

Continue with

Step 18 .

18

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-12 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-63

Ring and circuit pack upgrade procedures Procedure 12-5.1: Upgrade OC-12 UPSR to OC-48

UPSR using LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs at all nodes using Main slots

.................................................................................................................................................................................................

19

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the temporary replacement OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

20

21

.................................................................................................................................................................................................

If required, repeat

Step 18

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-12 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-12 OLIU circuit pack in Main slot

M1

. Then replace the OC-12 OLIU circuit pack in Main slot

M1

with the replacement OC-48 OLIU circuit pack.

Result:

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an unexpected CP type alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

22

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the replacement OC-48 OLIU circuit pack in Main slot

M1

and the required OC-48 circuit pack/port at the opposite end of the OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

.................................................................................................................................................................................................................................

12-64 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-5.1: Upgrade OC-12 UPSR to OC-48

UPSR using LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs at all nodes using Main slots

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

23

24

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The replacement OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system performs an automatic path protection switch, and all traffic is now active on Main slot

M1.

Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in the Main slot

M2

to the circuit pack in Main slot

M1

.

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an unexpected CP type alarm for Main slot

M2

.

.................................................................................................................................................................................................

Open a faceplate latch on the temporary replacement OC-48 OLIU circuit pack in

Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the temporary replacement OC-48 OLIU circuit pack in Main slot

M2

. Then replace the temporary replacement OC-48 OLIU circuit pack in Main slot

M2

with the replacement

OC-48 OLIU circuit pack.

Result:

The replacement OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M2

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M2

. Alarms may also be reported at other nodes in the ring.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-65

Ring and circuit pack upgrade procedures Procedure 12-5.1: Upgrade OC-12 UPSR to OC-48

UPSR using LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs at all nodes using Main slots

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

25

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the replacement OC-48 OLIU circuit pack in Main slot

M2

and the required OC-48 circuit pack/port at the opposite end of the OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC48 LOS alarms clear. Transmission is now supported on the upgraded optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

26

27

.................................................................................................................................................................................................

Important! At nodes connected to the UPSR using the Main slots, the system reports the ring upgrade mode standing condition (not alarmed) in the NE Alarm

List until the node is manually provisioned back to the Normal mode.

At nodes connected to the UPSR using the Main slots, click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the

NE Alarm List and verify that no alarms or standing conditions are present (except ring upgrade mode and

ABN condition

).

Refer to the appropriate trouble clearing procedures to clear all existing alarms and standing conditions (except ring upgrade mode and

ABN condition

) before continuing with this procedure.

Reference:

•

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble Clearing

Guide, 365-372-302

•

Metropolis

®

DMXtend Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-326

.................................................................................................................................................................................................

At each node connected to the UPSR using a port pair in the Function/Growth slots, select

Configuration

→

Update System

→

Update All

.

.................................................................................................................................................................................................................................

12-66 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-5.1: Upgrade OC-12 UPSR to OC-48

UPSR using LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs at all nodes using Main slots

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The inc. OC12 LOS alarms clear on the original OC-12 ports.

.................................................................................................................................................................................................

28

At each node connected to the UPSR using a port pair in the Function/Growth slots, select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to delete the remaining add and through cross-connections to the original OC-12 ports.

.................................................................................................................................................................................................

29

Important! The UPSR network must be alarm free with normal transmission before manually provisioning the nodes back to the Normal mode. After a node is manually provisioned back to the Normal mode, the node cannot be returned to the pre-upgrade state using the back out procedure.

At each node connected to the UPSR using the Main slots, select

Configuration

→

Normal Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode will be removed from the WaveStar

®

CIT alarm list.

.................................................................................................................................................................................................

30

Important! It is recommended that the network element database be backed up to a remote OS (for example, the Navis

®

Optical Element Management System) after an upgrade. This creates a current backup copy that includes the replacement circuit packs/port pairs. The remote OS could use this backup copy to restore the network element database in the event of a catastrophic failure. Attempts to restore the network element database using a backup copy created prior to the upgrade may result in circuit pack failures.

At each node in the UPSR, back up the network element database using the

Configuration

→

Software

→

Remote Backup

command.

Reference:

•

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123)

•

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135)

•

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150)

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-67

Ring and circuit pack upgrade procedures Procedure 12-5.1: Upgrade OC-12 UPSR to OC-48

UPSR using LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs at all nodes using Main slots

UPSR example

Starting Node

: Metropolis

®

DMX connected to the UPSR using the Main Slots (Node

N)

Starting Circuit Pack

: Main-2 at the Starting Node

Direction of Upgrade

: Clockwise around UPSR from Main-2 at the Starting Node to

Main/Function/Growth slot 1 at the adjacent node

DMX or DMXtend

N

(Starting Node)

MAIN-1 MAIN-2

DMX or DMXtend

DMX or DMXtend

N+3

N+1

DMX or DMXtend

FN-n-2-n or

Growth-2-n

N+2

FN-n-1-n or

Growth-1-n

DMX = Metropolis DMX Access Multiplexer

DMX

tend

= Metropolis DMX

tend

Access Multiplexer

MA-DMX-404

.................................................................................................................................................................................................................................

12-68 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-5.2: Upgrade OC-12 UPSR to OC-48 UPSR using

LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48

OLIUs at one or more nodes using Main slots

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by another procedure.

Step

1

2

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade an in-service OC-12 UPSR to an OC-48

UPSR using LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIU circuit packs at one or more Metropolis

®

DMX nodes connected to the UPSR using the Main slots.

.................................................................................................................................................................................................

Important! The starting node must be connected to the OC-12 UPSR using the

Main slots and upgraded with LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIU circuit packs. This procedure assumes that the starting node is a Metropolis

®

DMX.

Identify and log in to the Metropolis

®

DMX starting node (refer to the

“UPSR example” (p. 12-78)

at the end of the procedure).

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The Ring Upgrade mode allows cross-connections/ data to be mapped to the new circuit pack and prohibits provisioning new cross-connections.

At the WaveStar

®

CIT System View select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

CIT

Alarm List shows the Ring Upgrade mode as Not Alarmed.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-69

Ring and circuit pack upgrade procedures Procedure 12-5.2: Upgrade OC-12 UPSR to OC-48

UPSR using LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIUs at one or more nodes using Main slots

The node remains in the Ring Upgrade mode until manually provisioned back to the Normal mode. While in the Ring Upgrade mode, the upgrade may be temporarily suspended or backed out. To prevent errors in the upgraded ring, keep the nodes connected to the UPSR using the Main slots in the Ring Upgrade mode until all nodes have been upgraded.

.................................................................................................................................................................................................

3

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-12 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 11 .

Continue with

Step 4 .

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-12 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

.................................................................................................................................................................................................................................

12-70 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-5.2: Upgrade OC-12 UPSR to OC-48

UPSR using LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIUs at one or more nodes using Main slots

If the OC-12 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

6

.................................................................................................................................................................................................

If required, repeat

Step 4

to verify that the OC-12 OLIU circuit pack in Main slot

M1

is now the active circuit pack for timing.

7

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M2

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-12 OLIU circuit pack in Main slot

M2

.

Select

Reports

→

Path Protection List

and observe the value of the

Current Role

parameter for the

m2-()-()

paths supported by the circuit pack in Main slot

M2

(

Ring

2

). Record the active paths supported by the circuit pack in Main slot

M2

(

Ring 2

).

Click

Close

.

.................................................................................................................................................................................................

8

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M2

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M2

. In UPSRs, each path supported by the circuit pack in Main slot

M2

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-12 OLIU circuit pack in Main slot

M2

is not the active circuit pack for transmission, proceed to

Step 10 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

9

Repeat

Step 8

for each path supported by the circuit pack in Main slot

M2

. Click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-71

Ring and circuit pack upgrade procedures Procedure 12-5.2: Upgrade OC-12 UPSR to OC-48

UPSR using LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIUs at one or more nodes using Main slots

.................................................................................................................................................................................................

10

If required, repeat

Step 7

to verify that the OC-12 OLIU circuit pack in Main slot is now the active circuit pack for transmission.

M1

.................................................................................................................................................................................................

11

Important! Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-12 circuit pack is upgraded at each end of the optical span.

Open a faceplate latch on the OC-12 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-12 OLIU circuit pack in Main slot

M2

. Then replace the OC-12 OLIU circuit pack in Main slot

M2

with the replacement OC-48 OLIU circuit pack.

Result:

The replacement OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned. Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M2

. If active through traffic exists on the circuit pack in Main slot

M2

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected circuit pack type condition and an inc.

OC48 LOS alarm for Main slot

M2

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

This completes the first phase of the upgrade at the starting node. The starting node upgrade will be completed after all the other nodes in the ring are upgraded.

12

.................................................................................................................................................................................................

Log in to the adjacent node connected to Main/Function/Growth slot 2 (refer to the

“UPSR example” (p. 12-78)

at the end of the procedure).

.................................................................................................................................................................................................................................

12-72 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Reference:

Procedure 12-5.2: Upgrade OC-12 UPSR to OC-48

UPSR using LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIUs at one or more nodes

using Main slots

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

13

.................................................................................................................................................................................................

Determine how the node is connected to the UPSR and the type of upgrade circuit pack to be used, and then upgrade the UPSR connections.

If ...

Metropolis

®

DMX connected to the

UPSR using the circuit packs in the

Main slots and LNW27, LNW29,

LNW32, LNW76, and/or

LNW221-259 OC-48 OLIU circuit packs are to be used,

Metropolis

®

DMX connected to the

UPSR using the circuit packs in the

Main slots and LNW26B, LNW28,

LNW77, and/or LNW121B-159B

OC-48 OLIU circuit packs are to be used,

Metropolis

®

DMX connected to the

UPSR using the circuit packs in the

Function/Growth slots,

Then ...

Upgrade the high-speed UPSR connections using

Procedure 12-5.3: “Upgrade high-speed UPSR connections at node using LNW27, LNW29,

LNW32, LNW76, and/or LNW221-259 OC-48

OLIUs” (p. 12-79) . Then continue with

Step 14 .

Upgrade the high-speed UPSR connections using

Procedure 12-5.4: “Upgrade high-speed UPSR connections at node using LNW26B, LNW28,

LNW77, and/or LNW121B-159B OC-48 OLIUs”

(p. 12-83) . Then continue with

Step 14 .

Metropolis

the UPSR using the circuit packs in the Main slots,

Metropolis

®

®

DMXtend connected to

DMXtend connected to the UPSR using the circuit packs in the Function/Growth slots,

Upgrade the low-speed UPSR connections using

Procedure 12-5.5: “Upgrade low-speed OC-12

UPSR connections at node” (p. 12-89) . Then

continue with

Step 14 .

Upgrade the high-speed UPSR connections using

Procedure 12-4.2: Upgrade high-speed OC-12

UPSR connections at node in Metropolis

®

.

DMXtend Access Multiplexer User Operations

Guide, 365-372-325. Then continue with

Step 14

Upgrade the low-speed UPSR connections using

Procedure 12-4.1: Upgrade low-speed OC-12

UPSR connections at node in Metropolis

®

.

DMXtend Access Multiplexer User Operations

Guide, 365-372-325. Then continue with

Step 14

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-73

Ring and circuit pack upgrade procedures Procedure 12-5.2: Upgrade OC-12 UPSR to OC-48

UPSR using LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIUs at one or more nodes using Main slots

.................................................................................................................................................................................................

14

Except for the starting node, have all nodes in the UPSR been upgraded.

If...

No

Yes

Then...

Repeat

Step 12

and

Step 13

as required at the next node (refer to the

“UPSR example”

(p. 12-78)

at the end of the procedure).

Continue with

Step 15 .

15

16

17

.................................................................................................................................................................................................

Log in to the starting node (refer to the

“UPSR example” (p. 12-78)

at the end of the procedure).

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View, select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M2

clears, and the system reports an unexpected circuit pack type condition for Main slot

M1

.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-12 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 21 .

.................................................................................................................................................................................................................................

12-74 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

If the local operating procedures specify

{ verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Procedure 12-5.2: Upgrade OC-12 UPSR to OC-48

UPSR using LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIUs at one or more nodes using Main slots

Then...

Continue with

Step 18 .

18

19

20

21

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-12 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 18

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-12 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-12 OLIU circuit pack in Main slot

M1

. Then replace the OC-12 OLIU circuit pack in Main slot

M1

with the replacement OC-48 OLIU circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-75

Ring and circuit pack upgrade procedures

Result:

Procedure 12-5.2: Upgrade OC-12 UPSR to OC-48

UPSR using LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIUs at one or more nodes using Main slots

The replacement OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

22

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the replacement OC-48 circuit pack in Main slot

M1

and the required OC-48 circuit pack/port at the opposite end of the upgraded OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC48 LOS alarms clear. Transmission is now supported on the upgraded optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

23

Important! At nodes connected to the UPSR using the Main slots, the system reports the ring upgrade mode standing condition (not alarmed) in the NE Alarm

List until the node is manually provisioned back to the Normal mode.

At nodes connected to the UPSR using the Main slots, click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the

NE Alarm List and verify that no alarms or standing conditions are present (except ring upgrade mode and

ABN condition

).

Refer to the appropriate trouble clearing procedures to clear all existing alarms and standing conditions (except ring upgrade mode and

ABN condition

) before continuing with this procedure.

Reference:

•

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble Clearing

Guide, 365-372-302

•

Metropolis

®

DMXtend Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-326

.................................................................................................................................................................................................................................

12-76 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-5.2: Upgrade OC-12 UPSR to OC-48

UPSR using LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIUs at one or more nodes using Main slots

.................................................................................................................................................................................................

24

At each node connected to the UPSR using a port pair in the Function/Growth slots, select

Configuration

→

Update System

→

Update All

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The inc. OC12 LOS alarms clear on the original OC-12 ports.

25

.................................................................................................................................................................................................

At each node connected to the UPSR using a port pair in the Function/Growth slots, select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to delete the remaining add and through cross-connections to the original OC-12 ports.

.................................................................................................................................................................................................

26

Important! The network must be alarm free with normal transmission before manually provisioning the nodes back to the Normal mode. After a node is manually provisioned back to the Normal mode, the node cannot be returned to the pre-upgrade state using the back out procedure.

At each node connected to the UPSR using the Main slots, select

Configuration

→

Normal Mode

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode will be removed from the WaveStar

®

CIT alarm list.

.................................................................................................................................................................................................

27

Important! It is recommended that the network element database be backed up to a remote OS (for example, the Navis

®

Optical Element Management System) after an upgrade. This creates a current backup copy that includes the replacement circuit packs/port pairs. The remote OS could use this backup copy to restore the network element database in the event of a catastrophic failure. Attempts to restore the network element database using a backup copy created prior to the upgrade may result in circuit pack failures.

At each node in the UPSR, back up the network element database using the

Configuration

→

Software

→

Remote Backup

command.

Reference:

•

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123)

•

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135)

•

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150)

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-77

Ring and circuit pack upgrade procedures Procedure 12-5.2: Upgrade OC-12 UPSR to OC-48

UPSR using LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIUs at one or more nodes using Main slots

UPSR example

Starting Node

: Metropolis

®

DMX connected to the UPSR using the Main Slots (Node

N)

Starting Circuit Pack

: Main-2 at the Starting Node

Direction of Upgrade

: Clockwise around UPSR from Main-2 at the Starting Node to

Main/Function/Growth slot 1 at the adjacent node

DMX or DMXtend

N

(Starting Node)

MAIN-1 MAIN-2

DMX or DMXtend

DMX or DMXtend

N+3

N+1

DMX or DMXtend

FN-n-2-n or

Growth-2-n

N+2

FN-n-1-n or

Growth-1-n

DMX = Metropolis DMX Access Multiplexer

DMX

tend

= Metropolis DMX

tend

Access Multiplexer

MA-DMX-404

.................................................................................................................................................................................................................................

12-78 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-5.3: Upgrade high-speed UPSR connections at node using LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by another procedure.

Step

1

2

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade the in-service high-speed UPSR connections at a Metropolis

®

DMX node using LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIU circuit packs in the Main slots.

.................................................................................................................................................................................................

Important! The Ring Upgrade mode allows cross-connections/ data to be mapped to the new circuit pack and prohibits provisioning new cross-connections.

At the System View, select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

Alarm List shows the Ring Upgrade mode as Not Alarmed.

CIT

The node remains in the Ring Upgrade mode until manually provisioned back to the Normal mode. While in the Ring Upgrade mode, the upgrade may be temporarily suspended or backed out. To prevent errors in the upgraded ring, keep the nodes connected to the UPSR using the Main slots in Ring Upgrade mode until all nodes have been upgraded.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-79

Ring and circuit pack upgrade procedures Procedure 12-5.3: Upgrade high-speed UPSR connections at node using LNW27, LNW29, LNW32,

LNW76, and/or LNW221-259 OC-48 OLIUs

Determine the local operating procedures for removing a circuit pack before removing the OC-12 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

Continue with

Step 3 .

3

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-12 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-12 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the OC-12 OLIU circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

12-80 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-5.3: Upgrade high-speed UPSR connections at node using LNW27, LNW29, LNW32,

LNW76, and/or LNW221-259 OC-48 OLIUs

.................................................................................................................................................................................................

6

Open a faceplate latch on the OC-12 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-12 OLIU circuit pack in Main slot

M1

. Then replace the OC-12 OLIU circuit pack in Main slot

M1

with the replacement OC-48 OLIU circuit pack.

Result:

The system reports an unexpected CP type alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

7

8

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the replacement OC-48 circuit pack in Main slot

M1

and the required OC-48 circuit pack/port at the opposite end of the upgraded OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The replacement OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system performs an automatic path protection switch, and all traffic is now active on Main slot

M1.

Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in the Main slot

M2

to the circuit pack in Main slot

M1

.

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an unexpected CP type alarm for Main slot

M2

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-81

Ring and circuit pack upgrade procedures Procedure 12-5.3: Upgrade high-speed UPSR connections at node using LNW27, LNW29, LNW32,

LNW76, and/or LNW221-259 OC-48 OLIUs

.................................................................................................................................................................................................

9

Important! Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-12 circuit pack is upgraded at each end of the optical span.

Open a faceplate latch on the OC-12 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-12 OLIU circuit pack in Main slot

M2

. Then replace the OC-12 OLIU circuit pack in Main slot

M2

with the replacement OC-48 OLIU circuit pack.

Result:

The replacement OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M2

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M2

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

STOP!

To complete the UPSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-82 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-5.4: Upgrade high-speed UPSR connections at node using LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIUs

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by another procedure.

Step

1

2

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade the in-service high-speed UPSR connections at a Metropolis

®

DMX node using LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIU circuit packs in the Main slots.

.................................................................................................................................................................................................

Important! The Ring Upgrade mode allows cross-connections/ data to be mapped to the new circuit pack and prohibits provisioning new cross-connections.

At the System View, select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

Alarm List shows the Ring Upgrade mode as Not Alarmed.

CIT

The node remains in the Ring Upgrade mode until manually provisioned back to the Normal mode. While in the Ring Upgrade mode, the upgrade may be temporarily suspended or backed out. To prevent errors in the upgraded ring, keep the nodes connected to the UPSR using the Main slots in Ring Upgrade mode until all nodes have been upgraded.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-83

Ring and circuit pack upgrade procedures Procedure 12-5.4: Upgrade high-speed UPSR connections at node using LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIUs

Determine the local operating procedures for removing a circuit pack before removing the OC-12 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

Continue with

Step 3 .

3

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-12 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-12 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the OC-12 OLIU circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

12-84 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-5.4: Upgrade high-speed UPSR connections at node using LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIUs

.................................................................................................................................................................................................

6

Open a faceplate latch on the OC-12 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-12 OLIU circuit pack in Main slot

M1

. Then replace the OC-12 OLIU circuit pack in Main slot

M1

with the replacement OC-48 OLIU circuit pack.

Result:

The replacement OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system reports an unexpected circuit pack type condition and an inc.

OC48 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

7

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the replacement OC-48 circuit pack in Main slot

M1

and the required OC-48 circuit pack/port at the opposite end of the upgraded OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC48 LOS alarms clear. Transmission is now supported on the upgraded optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

8

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an unexpected circuit pack type condition for Main slot

M2

.

.................................................................................................................................................................................................

9

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-85

Ring and circuit pack upgrade procedures Procedure 12-5.4: Upgrade high-speed UPSR connections at node using LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIUs method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-12 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 17 .

Continue with

Step 10 .

10

11

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-12 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

.................................................................................................................................................................................................................................

12-86 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-5.4: Upgrade high-speed UPSR connections at node using LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIUs

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

12

13

.................................................................................................................................................................................................

If required, repeat

Step 10

to verify that the OC-48 OLIU circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M2

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-12 OLIU circuit pack in Main slot

M2

.

Select

Reports

→

Path Protection List

and observe the value of the

Current Role

parameter for the

m2-()-()

paths supported by the circuit pack in Main slot

M2

(

Ring

2

). Record the active paths supported by the circuit pack in Main slot

M2

(

Ring 2

).

Click

Close

.

.................................................................................................................................................................................................

14

15

16

Important! This step is optional. If the OC-12 OLIU circuit pack in Main slot

M2

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M2

. In UPSRs, each path supported by the circuit pack in Main slot

M2

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-12 OLIU circuit pack in Main slot

M2

is not the active circuit pack for transmission, proceed to

Step 16 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

Repeat

Step 14

for each path supported by the circuit pack in Main slot

M2

. Click

Close

.

.................................................................................................................................................................................................

If required, repeat

Step 13

to verify that the OC-48 OLIU circuit pack in Main slot

M1

is now the active circuit pack for transmission.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-87

Ring and circuit pack upgrade procedures Procedure 12-5.4: Upgrade high-speed UPSR connections at node using LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIUs

.................................................................................................................................................................................................

17

Important! Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-12 circuit pack is upgraded at each end of the optical span.

Open a faceplate latch on the OC-12 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-12 OLIU circuit pack in Main slot

M2

. Then replace the OC-12 OLIU circuit pack in Main slot

M2

with the replacement OC-48 OLIU circuit pack.

Result:

The replacement OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected circuit pack type condition for Main slot

M2

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M2

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

STOP!

To complete the UPSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-88 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-5.5: Upgrade low-speed OC-12 UPSR connections at node

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by another procedure.

When upgrading connections to a UPSR using a port pair in the Function/Growth slots, the node is not required to be in the provisioned Ring Upgrade mode.

Step

1

2

3

4

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade the in-service UPSR connections at a

Metropolis

®

DMX node that is connected to the UPSR using a port pair in the

Function/Growth slots.

.................................................................................................................................................................................................

Important! An OC-48 port pair must be available in a different Function/Growth group.

Provision the required OC-48 port pair according to the work instructions using the

Configuration

→

Equipment

command.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

To verify that the OC-48 port parameters were provisioned correctly, select

View

→

Equipment

and expand the required circuit pack. Click on the required port and

Select

to obtain the port parameters. Click

Close

.

.................................................................................................................................................................................................

Provision the required OC-48 port DCC parameters according to the work instructions using the

Configuration

→

DCC Terminations

command.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

To verify that the OC-48 port DCC parameters were provisioned correctly, select

View

→

DCC Terminations

to obtain the DCC channel status. Click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-89

Ring and circuit pack upgrade procedures Procedure 12-5.5: Upgrade low-speed OC-12 UPSR connections at node

5

6

7

.................................................................................................................................................................................................

Important! All cross-connections at this node that are associated with the existing

OC-12 UPSR must be identified so that traffic can be moved to the OC-48 UPSR.

Select

View

→

Cross-Connections

. Expand the required OC-12 OLIU circuit pack in slot 1 of the Function/Growth group that is currently connected to the OC-12 UPSR.

Click on the required OC-12 port and

Select

to obtain the current list of cross-connections. Identify and record all through, add, drop, and UPSR Dual Ring

Interworking cross-connections. Click

Close

to exit.

Important! A UPSR Dual Ring Interworking cross-connection consists of a 1-way add, a 1-way through, and a 1-way path protected drop cross-connection. To verify that a cross-connection leg is part of a UPSR Dual Ring Interworking cross-connection, click on the cross-connection leg in the list of cross-connections and click

View Graphic

.

For additional information about UPSR Dual Ring Interworking cross-connections, refer to

Procedure 10-11: “Establish dual ring interworking (DRI) connections”

(p. 10-56) .

.................................................................................................................................................................................................

For each UPSR Dual Ring Interworking cross-connection identified in

Step 5 , select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to delete the UPSR Dual Ring Interworking cross-connections. Then use the Cross-Connection

Wizard to create the same UPSR Dual Ring Interworking cross-connections on the required OC-48 port pair in the other Function/Growth group.

Result:

Transmission hits (less than 60 ms) may occur. Alarms may be reported at other nodes in the ring.

Reference:

Procedure 10-11: “Establish dual ring interworking (DRI) connections”

(p. 10-56)

.................................................................................................................................................................................................

Important! Do not perform this step for a 1-way through cross-connection associated with a UPSR Dual Ring Interworking cross-connection.

For each through cross-connection identified in

Step 5

that is not part of a UPSR Dual

Ring Interworking cross-connection, select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to create the same through cross-connections on the required OC-48 port pair in the other Function/Growth group.

.................................................................................................................................................................................................................................

12-90 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-5.5: Upgrade low-speed OC-12 UPSR connections at node

8

Reference:

Procedure 10-5: “Make VT1.5 or STS-n cross-connections, single

OC-3/OC-12 UPSR configuration” (p. 10-16)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Removal of wrong fiber connections will result in a service interruption.

Ensure that you remove only the fiber connections for the optical span being upgraded.

9

10

Disconnect the transmit and receive optical fibers from the required OC-12 port on the

OC-12 OLIU circuit pack in slot 1 of the Function/Growth group.

Result:

The system still reports an inc. OC12 LOS alarm for the OC-12 port.

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the

OC-48 port on the OC-48 OLIU circuit pack in slot 1 of the other Function/Growth group and the required OC-48 circuit pack/port at the opposite end of the upgraded

OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! Do not perform this step for a 1-way add cross-connection associated with a UPSR Dual Ring Interworking cross-connection.

For each add cross-connection identified in

Step 5

that is not part of a UPSR Dual

Ring Interworking cross-connection, select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to bridge the add cross-connections to the required

OC-48 port on the OC-48 OLIU circuit pack in slot 1 of the other Function/Growth group.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-91

Ring and circuit pack upgrade procedures Procedure 12-5.5: Upgrade low-speed OC-12 UPSR connections at node

11

12

Reference:

Procedure 10-10: “Bridge and roll cross-connections” (p. 10-48)

.................................................................................................................................................................................................

Important! Do not perform this step for a 1-way path protected drop cross-connection associated with a UPSR Dual Ring Interworking cross-connection.

For each drop cross-connection identified in

Step 5

that is not part of a UPSR Dual

Ring Interworking cross-connection, select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to roll the drop cross-connections to the required

OC-48 port on the OC-48 OLIU circuit pack in slot 1 of the other Function/Growth group.

Reference:

Procedure 10-10: “Bridge and roll cross-connections” (p. 10-48)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Removal of wrong fiber connections will result in a service interruption.

Ensure that you remove only the fiber connections for the optical span being upgraded.

Important! Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-12 circuit pack is upgraded at each end of the optical span.

Disconnect the transmit and receive optical fibers from the required OC-12 port on the

OC-12 OLIU circuit pack in slot 2 of the Function/Growth group.

Result:

The system reports inc. OC12 LOS alarms for the original OC-12 ports.

Alarms may also be reported at other nodes in the ring.

STOP!

To complete the UPSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-92 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-6: Back out OC-12 UPSR to OC-48 UPSR upgrade

.................................................................................................................................................................................................................................

Overview

CAUTION

Service disruption hazard

If a node has been taken out of the Ring Upgrade mode, the node cannot be returned to the original pre-upgrade state without affecting service.

All nodes connected to the UPSR using the Main slots must be in the provisioned Ring

Upgrade mode.

Use this procedure to back out an OC-12 UPSR to OC-48 upgrade with:

•

LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIU circuit packs installed at one or more upgraded Metropolis

®

DMX nodes using the Main slots.

These OC-48 OLIU circuit packs have different optics and transmit at different wavelengths. However, these circuit packs have the same circuit pack type and a

small VT cross-connection fabric. There are no differences between these circuit packs for the purposes of ring backouts.

•

LNW27, LNW29, LNW32, LNW76, and/or LNW221-259 OC-48 OLIU circuit packs installed at all upgraded Metropolis

®

DMX nodes using the Main slots.

These OC-48 OLIU circuit packs have different optics and transmit at different wavelengths. However, these circuit packs have the same circuit pack type and a

large VT cross-connection fabric. There are no differences between these circuit packs for the purposes of ring backouts.

Backing out of an upgrade in progress returns all nodes in the ring to their pre-upgrade state.

To temporarily stop the upgrade refer to

Procedure 12-7: “Suspend OC-12 UPSR to

OC-48 UPSR upgrade” (p. 12-130) .

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

The following equipment is required to perform this procedure:

•

Wrist strap

•

Original OC-12 OLIU circuit packs/port pairs for each node to be backed out

•

As the upgrade is backed out around the UPSR, ensure that technicians are available at each end of an optical span as the upgrade is backed out.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-93

Ring and circuit pack upgrade procedures Procedure 12-6: Back out OC-12 UPSR to OC-48 UPSR upgrade

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this back out procedure. If required, refer to the Metropolis

®

DMXtend Access Multiplexer

Software Release Description.

3. If required, review the Metropolis

®

DMXtend Access Multiplexer User Operations

Guide, 365-372-325 for procedures or cautions that may apply to this backout procedure.

Step

1

Important! This procedure starts at the last node upgraded.

Complete the following steps to back out an OC-12 UPSR to OC-48 UPSR upgrade.

.................................................................................................................................................................................................

From office records and work instructions, determine the current network configuration and status of the upgrade.

.................................................................................................................................................................................................................................

12-94 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-6: Back out OC-12 UPSR to OC-48 UPSR upgrade

.................................................................................................................................................................................................

2

If ...

all upgraded Metropolis

®

DMX nodes connected to the UPSR using the

Main slots are equipped with LNW27,

LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIU circuit packs,

one or more upgraded Metropolis

®

DMX nodes connected to the UPSR using the Main slots are equipped with LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIU circuit packs,

Then proceed to and perform...

Procedure 12-6.1: “Back out OC-12 UPSR to

OC-48 UPSR upgrade when all upgraded nodes using Main slots are equipped with

LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs ” (p. 12-96)

Procedure 12-6.2: “Back out OC-12 UPSR to

OC-48 UPSR upgrade when one or more upgraded nodes using Main slots are equipped with LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIUs” (p. 12-106)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-95

Ring and circuit pack upgrade procedures

Procedure 12-6.1: Back out OC-12 UPSR to OC-48 UPSR upgrade when all upgraded nodes using Main slots are equipped with LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by another procedure.

Step

CAUTION

Service disruption hazard

If a node has been taken out of the Ring Upgrade mode, the node cannot be returned to the original pre-upgrade state without affecting service.

All nodes connected to the UPSR using the Main slots must be in the provisioned Ring

Upgrade mode.

1

Important! This procedure starts at the last node upgraded.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-12 UPSR to OC-48 UPSR upgrade with LNW27, LNW29, LNW32, LNW76, and/or LNW221-259 OC-48 OLIU circuit packs installed at all upgraded Metropolis

®

DMX nodes using the Main slots.

.................................................................................................................................................................................................

Identify the last node that was upgraded.

If the last node upgraded is...

the Metropolis

®

DMX starting node, and the ring upgrade is complete (all nodes connected to the UPSR using the

Main slots are in the Ring Upgrade mode), not the Metropolis

®

DMX starting node,

Then...

Log in to the Metropolis

®

DMX starting node (refer to the

“UPSR example”

(p. 12-105)

at the end of the procedure) and continue with

Step 2 .

Log in to the last node upgraded (refer to the

“UPSR example” (p. 12-105)

at the end of the procedure) and proceed to

Step 15 .

.................................................................................................................................................................................................................................

12-96 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Reference:

Procedure 12-6.1: Back out OC-12 UPSR to OC-48

UPSR upgrade when all upgraded nodes using Main slots are equipped with LNW27, LNW29, LNW32, LNW76,

and/or LNW221-259 OC-48 OLIUs

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

2

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 10 .

Continue with

Step 3 .

3

4

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-97

Ring and circuit pack upgrade procedures Procedure 12-6.1: Back out OC-12 UPSR to OC-48

UPSR upgrade when all upgraded nodes using Main slots are equipped with LNW27, LNW29, LNW32, LNW76,

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

5

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

6

7

8

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-48 OLIU circuit pack in Main slot

M2

.

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m2-()-() paths supported by the circuit pack in Main slot

M2

(Ring

2). Record the active paths supported by the circuit pack in Main slot

M2

(Ring 2).

Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M2

. In UPSRs, each path supported by the circuit pack in Main slot

M2

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is not the active circuit pack for transmission, proceed to

Step 9 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

Repeat

Step 7

for each path supported by the circuit pack in Main slot

M2

. Click

Close

.

.................................................................................................................................................................................................................................

12-98 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-6.1: Back out OC-12 UPSR to OC-48

UPSR upgrade when all upgraded nodes using Main slots are equipped with LNW27, LNW29, LNW32, LNW76, and/or LNW221-259 OC-48 OLIUs

.................................................................................................................................................................................................

9

If required, repeat

Step 6

to verify that the circuit pack in Main slot active circuit pack for transmission.

M1

is now the

.................................................................................................................................................................................................

10

Important! At the starting node, the OC-48 OLIU circuit pack in Main slot

M2

must be first replaced with the temporary replacement OC-48 OLIU circuit pack.

The temporary replacement OC-48 OLIU circuit pack maintains traffic while backing out of the upgrade. As a final step in backing out the ring upgrade, this temporary replacement OC-48 OLIU circuit pack is replaced with the original

OC-12 OLIU circuit pack.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the temporary replacement OC-48 OLIU circuit pack.

Result:

Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M2

. If active through traffic exists on the circuit pack in Main slot

M2

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected CP type alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

11

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the temporary replacement OC-48 OLIU circuit pack in Main slot

M2

and the required

OC-48 circuit pack/port at the opposite end of the upgraded OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

12

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-99

Ring and circuit pack upgrade procedures Procedure 12-6.1: Back out OC-12 UPSR to OC-48

UPSR upgrade when all upgraded nodes using Main slots are equipped with LNW27, LNW29, LNW32, LNW76,

At the System View select

Configuration

→ and/or LNW221-259 OC-48 OLIUs

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The temporary replacement OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The system performs an automatic path protection switch, and all traffic is now active on Main slot

M2

. Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in Main slot

M1

to the circuit pack in Main slot

M2

.

The unexpected CP type alarm for Main slot

M2

clears, and the system reports an unexpected CP type alarm for Main slot

M1

.

.................................................................................................................................................................................................

13

Important! Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-48 circuit pack is backed out at each end of the optical span.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the original OC-12 OLIU circuit pack.

Result:

The original OC-12 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M1

clears. The system reports an unexpected circuit pack type condition and an inc. OC12 LOS alarm for Main slot

M1

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

This completes the first phase of the back out at the starting node. The back out at the starting node will be completed after backing out of all the other nodes in the ring.

14

.................................................................................................................................................................................................

Log in to the adjacent node connected to Main/Function/Growth slot 1 (refer to the

“UPSR example” (p. 12-105)

at the end of the procedure).

.................................................................................................................................................................................................................................

12-100 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Reference:

Procedure 12-6.1: Back out OC-12 UPSR to OC-48

UPSR upgrade when all upgraded nodes using Main slots are equipped with LNW27, LNW29, LNW32, LNW76,

and/or LNW221-259 OC-48 OLIUs

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

15

.................................................................................................................................................................................................

Determine how the node is connected to the UPSR and back out the upgrade at the node.

If ...

Metropolis

®

DMX connected to the

UPSR using the circuit packs in the Main slots,

Metropolis

®

DMX connected to the

UPSR using the circuit packs in the Function/Growth slots,

Metropolis

®

DMXtend connected to the UPSR using the circuit packs in the Main slots,

Metropolis

®

DMXtend connected to the UPSR using the circuit packs in the Function/Growth slots,

Then ...

Back out the UPSR upgrade using

Procedure

12-6.3: “Back out high-speed UPSR upgrade at node (LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs installed)”

(p. 12-115) . Then continue with

Step 16 .

Back out the UPSR upgrade using

Procedure

12-6.5: “Back out low-speed OC-12 to OC-48

UPSR upgrade at node” (p. 12-125) . Then

continue with

Step 16 .

Back out the UPSR upgrade using Procedure

12-5.2: Back out high-speed OC-12 UPSR to

OC-48 UPSR upgrade at node in Metropolis

®

DMXtend Access Multiplexer User Operations

Guide, 365-372-325. Then continue with

Step 16 .

Back out the UPSR upgrade using Procedure

12-5.1: Back out low-speed OC-12 UPSR to

OC-48 UPSR upgrade at node in Metropolis

®

DMXtend Access Multiplexer User Operations

Guide, 365-372-325. Then continue with

Step 16 .

16

.................................................................................................................................................................................................

Except for the starting node, has the upgrade been backed out of all nodes in the

UPSR.

If...

No,

Yes,

Then...

Repeat

Step 14

and

Step 15 , as required, at the

next node (refer to the

“UPSR example”

(p. 12-105)

at the end of the procedure).

Continue with

Step 17 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-101

Ring and circuit pack upgrade procedures Procedure 12-6.1: Back out OC-12 UPSR to OC-48

UPSR upgrade when all upgraded nodes using Main slots are equipped with LNW27, LNW29, LNW32, LNW76, and/or LNW221-259 OC-48 OLIUs

.................................................................................................................................................................................................

17

Log in to the starting node (refer to the procedure).

“UPSR example” (p. 12-105)

at the end of the

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

18

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 22 .

Continue with

Step 19 .

19

20

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

.................................................................................................................................................................................................................................

12-102 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-6.1: Back out OC-12 UPSR to OC-48

UPSR upgrade when all upgraded nodes using Main slots are equipped with LNW27, LNW29, LNW32, LNW76, and/or LNW221-259 OC-48 OLIUs

If the OC-12 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

21

.................................................................................................................................................................................................

If required, repeat

Step 19

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

22

23

.................................................................................................................................................................................................

Open a faceplate latch on the temporary replacement OC-48 OLIU circuit pack in

Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the temporary replacement OC-48 OLIU circuit pack in Main slot

M2

. Then replace the temporary replacement OC-48 OLIU circuit pack in Main slot

M2

with the original

OC-12 OLIU circuit pack.

Result:

The original OC-12 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The system reports an unexpected circuit pack type condition for both Main slot

M1

and Main slot

M2

, and an inc. OC12 LOS alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-12 OLIU circuit pack in Main slot

M2

and the required OC-12 OLIU circuit pack/port at the opposite end of the original OC-12 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-12 circuit packs.)

3. Clean and connect the receive fibers.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-103

Ring and circuit pack upgrade procedures

Result:

Procedure 12-6.1: Back out OC-12 UPSR to OC-48

UPSR upgrade when all upgraded nodes using Main slots are equipped with LNW27, LNW29, LNW32, LNW76, and/or LNW221-259 OC-48 OLIUs

The inc. OC12 LOS alarms clear. Transmission is now supported on the original OC-12 optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

24

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type conditions for both Main slot

M1

and Main slot

M2

clear.

.................................................................................................................................................................................................

25

Important! At nodes connected to the UPSR using the Main slots, the system reports the ring upgrade mode standing condition (not alarmed) in the NE Alarm

List until the node is manually provisioned back to the Normal mode.

At nodes connected to the UPSR using the Main slots, click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the

NE Alarm List and verify that no alarms or standing conditions are present (except ring upgrade mode and

ABN condition

).

Refer to the appropriate trouble clearing procedures to clear all existing alarms and standing conditions (except ring upgrade mode and

ABN condition

) before continuing with this procedure.

Reference:

•

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble Clearing

Guide, 365-372-302

•

Metropolis

®

DMXtend Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-326

.................................................................................................................................................................................................

26

Important! This completes the back out procedure, except for taking the nodes connected to the UPSR using the Main slots out of the Ring Upgrade mode. The decision to take these nodes out of the Ring Upgrade mode or leave them depends on the reason the back out was necessary, and what is required before again starting the upgrade. In the Ring Upgrade mode, UPSR cross-connections cannot be created or removed.

If required at each node connected to the UPSR using the Main slots, select

Configuration

→

Normal Mode

.

.................................................................................................................................................................................................................................

12-104 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Result:

Procedure 12-6.1: Back out OC-12 UPSR to OC-48

UPSR upgrade when all upgraded nodes using Main slots are equipped with LNW27, LNW29, LNW32, LNW76, and/or LNW221-259 OC-48 OLIUs

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode will be removed from the WaveStar

®

CIT alarm list.

E

N D O F

S

T E P S

UPSR example

DMX or DMXtend

N

(Starting Node)

MAIN-1 MAIN-2

DMX or DMXtend

DMX or DMXtend

N+3

N+1

DMX or DMXtend

FN-n-2-n or

Growth-2-n

N+2

FN-n-1-n or

Growth-1-n

DMX = Metropolis DMX Access Multiplexer

DMX

tend

= Metropolis DMX

tend

Access Multiplexer

MA-DMX-404

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-105

Ring and circuit pack upgrade procedures

Procedure 12-6.2: Back out OC-12 UPSR to OC-48 UPSR upgrade when one or more upgraded nodes using Main slots are equipped with LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIUs

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by another procedure.

Step

CAUTION

Service disruption hazard

If a node has been taken out of the Ring Upgrade mode, the node cannot be returned to the original pre-upgrade state without affecting service.

All nodes connected to the UPSR using the Main slots must be in the provisioned Ring

Upgrade mode.

1

Important! This procedure starts at the last node upgraded.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-12 UPSR to OC-48 UPSR upgrade with LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIU circuit packs installed at one or more upgraded Metropolis

®

DMX nodes using the Main slots.

.................................................................................................................................................................................................

Identify the last node that was upgraded.

If the last node upgraded is...

the Metropolis

®

DMX starting node, and the ring upgrade is complete (all nodes connected to the UPSR using the Main slots are in the Ring Upgrade mode), not the Metropolis

®

DMX starting node,

Then...

Log in to the Metropolis

®

DMX starting node

(refer to the

“UPSR example” (p. 12-114)

at the end of the procedure) and continue with

Step 2 .

Log in to the last node upgraded (refer to the

“UPSR example” (p. 12-114)

at the end of the procedure) and proceed to

Step 12 .

.................................................................................................................................................................................................................................

12-106 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Reference:

Procedure 12-6.2: Back out OC-12 UPSR to OC-48

UPSR upgrade when one or more upgraded nodes using

Main slots are equipped with LNW26B, LNW28, LNW77,

and/or LNW121B-159B OC-48 OLIUs

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

2

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 10 .

Continue with

Step 3 .

3

4

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-107

Ring and circuit pack upgrade procedures Procedure 12-6.2: Back out OC-12 UPSR to OC-48

UPSR upgrade when one or more upgraded nodes using

Main slots are equipped with LNW26B, LNW28, LNW77,

To perform an optional manual timing switch, select and/or LNW121B-159B OC-48 OLIUs

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

5

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for timing.

6

7

8

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-48 OLIU circuit pack in Main slot

M1

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m1-()-() paths supported by the circuit pack in Main slot

M1

(Ring

1). Record the active paths supported by the circuit pack in Main slot

M1

(Ring 1).

Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M1

. In UPSRs, each path supported by the circuit pack in Main slot

M1

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 9 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

Repeat

Step 7

for each path supported by the circuit pack in Main slot

M1

. Click

Close

.

.................................................................................................................................................................................................................................

12-108 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-6.2: Back out OC-12 UPSR to OC-48

UPSR upgrade when one or more upgraded nodes using

Main slots are equipped with LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIUs

.................................................................................................................................................................................................

9

If required, repeat

Step 6

to verify that the circuit pack in Main slot active circuit pack for transmission.

M2

is now the

.................................................................................................................................................................................................

10

Important! Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-48 circuit pack is backed out at each end of the optical span.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the original OC-12 OLIU circuit pack.

Result:

The original OC-12 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned. Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M1

. If active through traffic exists on the circuit pack in Main slot

M1

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected circuit pack type condition and an inc.

OC12 LOS alarm for Main slot

M1

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

This completes the first phase of the back out at the starting node. The back out at the starting node will be completed after backing out of all the other nodes in the ring.

11

.................................................................................................................................................................................................

Log in to the adjacent node connected to Main/Function/Growth slot 1 (refer to the

“UPSR example” (p. 12-114)

at the end of the procedure).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-109

Ring and circuit pack upgrade procedures

Reference:

Procedure 12-6.2: Back out OC-12 UPSR to OC-48

UPSR upgrade when one or more upgraded nodes using

Main slots are equipped with LNW26B, LNW28, LNW77,

and/or LNW121B-159B OC-48 OLIUs

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

12

.................................................................................................................................................................................................

Determine how the node is connected to the UPSR and back out the upgrade at the node.

If ...

Metropolis

®

DMX connected to the

UPSR using LNW27, LNW29,

LNW32, LNW76, and/or

LNW221-259 OC-48 OLIU circuit packs in the Main slots,

Metropolis

®

DMX connected to the

UPSR using LNW26B, LNW28,

LNW77, and/or LNW121B-159B

OC-48 OLIU circuit packs in the

Main slots,

Metropolis

®

DMX connected to the

UPSR using circuit packs in the

Function/Growth slots,

Metropolis

to the UPSR using circuit packs in the Main slots,

Metropolis

®

®

DMXtend connected

DMXtend connected to the UPSR using circuit packs in the Function/Growth slots,

Then ...

Back out the UPSR upgrade using

Procedure

12-6.3: “Back out high-speed UPSR upgrade at node (LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs installed)”

(p. 12-115) . Then continue with

Step 13 .

Back out the UPSR upgrade using

Procedure

12-6.4: “Back out high-speed UPSR upgrade at node (LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIUs installed)”

(p. 12-119) . Then continue with

Step 13 .

Back out the UPSR upgrade using

Procedure

12-6.5: “Back out low-speed OC-12 to OC-48

UPSR upgrade at node” (p. 12-125) . Then

continue with

Step 13 .

Back out the UPSR upgrade using Procedure

12-5.2: Back out high-speed OC-12 UPSR to

OC-48 UPSR upgrade at node in Metropolis

®

DMXtend Access Multiplexer User Operations

Guide, 365-372-325. Then continue with

Step 13 .

Back out the UPSR upgrade using Procedure

12-5.1: Back out low-speed OC-12 UPSR to

OC-48 UPSR upgrade at node in Metropolis

®

DMXtend Access Multiplexer User Operations

Guide, 365-372-325. Then continue with

Step 13 .

.................................................................................................................................................................................................................................

12-110 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-6.2: Back out OC-12 UPSR to OC-48

UPSR upgrade when one or more upgraded nodes using

Main slots are equipped with LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIUs

.................................................................................................................................................................................................

13

Except for the starting node, has the upgrade been backed out of all nodes in the

UPSR.

If...

No,

Yes,

Then...

Repeat

Step 11

and

Step 12 , as required, at the

next node (refer to the

“UPSR example”

(p. 12-114)

at the end of the procedure).

Continue with

Step 14 .

14

15

16

.................................................................................................................................................................................................

Log in to the starting node (refer to the

“UPSR example” (p. 12-114)

at the end of the procedure).

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this procedure.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an unexpected circuit pack type condition for Main slot

M2

.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 20 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-111

Ring and circuit pack upgrade procedures

If the local operating procedures specify

{ verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Procedure 12-6.2: Back out OC-12 UPSR to OC-48

UPSR upgrade when one or more upgraded nodes using

Main slots are equipped with LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIUs

Then...

Continue with

Step 17 .

17

18

19

20

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-12 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 17

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the original OC-12 OLIU circuit pack.

.................................................................................................................................................................................................................................

12-112 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Result:

Procedure 12-6.2: Back out OC-12 UPSR to OC-48

UPSR upgrade when one or more upgraded nodes using

Main slots are equipped with LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIUs

The original OC-12 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected circuit pack type condition for Main slot

M2

clears, and the system reports an inc. OC12 LOS alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

21

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-12 circuit pack in Main slot

M2

and the required OC-12 circuit pack/port at the opposite end of the original OC-12 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-12 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC12 LOS alarms clear. Transmission is now supported on the original OC-12 optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

22

Important! At nodes connected to the UPSR using the Main slots, the system reports the ring upgrade mode standing condition (not alarmed) in the NE Alarm

List until the node is manually provisioned back to the Normal mode.

At nodes connected to the UPSR using the Main slots, click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the

NE Alarm List and verify that no alarms or standing conditions are present (except ring upgrade mode and

ABN condition

).

Refer to the appropriate trouble clearing procedures to clear all existing alarms and standing conditions (except ring upgrade mode and

ABN condition

) before continuing with this procedure.

Reference:

•

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble Clearing

Guide, 365-372-302

•

Metropolis

®

DMXtend Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-326

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-113

Ring and circuit pack upgrade procedures Procedure 12-6.2: Back out OC-12 UPSR to OC-48

UPSR upgrade when one or more upgraded nodes using

Main slots are equipped with LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIUs

.................................................................................................................................................................................................

23

Important! This completes the back out procedure, except for taking the nodes connected to the UPSR using the Main slots out of the Ring Upgrade mode. The decision to take these nodes out of the Ring Upgrade mode or leave them depends on the reason the back out was necessary, and what is required before again starting the upgrade. In the Ring Upgrade mode, UPSR cross-connections cannot be created or removed.

If required at each node connected to the UPSR using the Main slots, select

Configuration

→

Normal Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode will be removed from the WaveStar

®

CIT alarm list.

E

N D O F

S

T E P S

UPSR example

DMX or DMXtend

N

(Starting Node)

MAIN-1 MAIN-2

DMX or DMXtend

DMX or DMXtend

N+3

N+1

DMX or DMXtend

FN-n-2-n or

Growth-2-n

N+2

FN-n-1-n or

Growth-1-n

DMX = Metropolis DMX Access Multiplexer

DMX

tend

= Metropolis DMX

tend

Access Multiplexer

MA-DMX-404

.................................................................................................................................................................................................................................

12-114 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-6.3: Back out high-speed UPSR upgrade at node

(LNW27, LNW29, LNW32, LNW76, and/or LNW221-259

OC-48 OLIUs installed)

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by another procedure.

Step

1

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-12 UPSR to OC-48 UPSR upgrade at a Metropolis

®

DMX node with LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIU circuit packs installed in the Main slots.

.................................................................................................................................................................................................

Determine the current status of the upgrade at the node.

If...

both Main slots have been upgraded with OC-48 OLIU circuit packs, only Main slot

M1

has been upgraded with an OC-48 OLIU circuit pack,

Then...

Continue with

Step 2 .

Proceed to

Step 8 .

2

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-115

Ring and circuit pack upgrade procedures

If the local operating procedures specify

{ verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Procedure 12-6.3: Back out high-speed UPSR upgrade at node (LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs installed)

Then...

Continue with

Step 3 .

3

4

5

6

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the original OC-12 OLIU circuit pack.

.................................................................................................................................................................................................................................

12-116 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-6.3: Back out high-speed UPSR upgrade at node (LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs installed)

Result:

The system reports an unexpected CP type alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

7

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-12 OLIU circuit pack in Main slot

M2

and the required OC-12 circuit pack/port at the opposite end of the original OC-12 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-12 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

8

9

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The original OC-12 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The system performs an automatic path protection switch, and all traffic is now active on Main slot

M2

. Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in Main slot

M1

to the circuit pack in Main slot

M2

.

The unexpected CP type alarm for Main slot

M2

clears, and the system reports an unexpected CP type alarm for Main slot

M1

.

.................................................................................................................................................................................................

Important! Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-48 circuit pack is backed out at each end of the optical span.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the original OC-12 OLIU circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-117

Ring and circuit pack upgrade procedures Procedure 12-6.3: Back out high-speed UPSR upgrade at node (LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIUs installed)

Result:

The original OC-12 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an inc. OC12 LOS alarm for Main slot

M1

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

STOP!

To complete backing out the UPSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-118 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-6.4: Back out high-speed UPSR upgrade at node

(LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48

OLIUs installed)

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by another procedure.

Step

1

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-12 UPSR to OC-48 UPSR upgrade at a Metropolis

®

DMX node with LNW26B, LNW28, LNW77, and/or LNW121B-159B

OC-48 OLIU circuit packs installed in the Main slots.

.................................................................................................................................................................................................

Determine the current status of the upgrade at the node.

If...

both Main slots have been upgraded with OC-48 OLIU circuit packs, only Main slot

M1

has been upgraded with an OC-48 OLIU circuit pack,

Then...

Continue with

Step 2 .

Proceed to

Step 8 .

2

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-119

Ring and circuit pack upgrade procedures

If the local operating procedures specify

{ verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Procedure 12-6.4: Back out high-speed UPSR upgrade at node (LNW26B, LNW28, LNW77, and/or LNW121B-159B

OC-48 OLIUs installed)

Then...

Continue with

Step 3 .

3

4

5

6

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the original OC-12 OLIU circuit pack.

.................................................................................................................................................................................................................................

12-120 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-6.4: Back out high-speed UPSR upgrade at node (LNW26B, LNW28, LNW77, and/or LNW121B-159B

OC-48 OLIUs installed)

Result:

The original OC-12 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The system reports an unexpected circuit pack type condition and an inc.

OC12 LOS alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

7

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-12 circuit pack in Main slot

M2

and the required OC-12 circuit pack/port at the opposite end of the original OC-12 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-12 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC12 LOS alarms clear. Transmission is now supported on the original OC-12 optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

8

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M2

clears, and the system reports an unexpected circuit pack type condition for Main slot

M1

.

.................................................................................................................................................................................................

9

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-121

Ring and circuit pack upgrade procedures Procedure 12-6.4: Back out high-speed UPSR upgrade at node (LNW26B, LNW28, LNW77, and/or LNW121B-159B

OC-48 OLIUs installed)

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 17 .

Continue with

Step 10 .

10

11

12

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-12 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 10

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

12-122 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-6.4: Back out high-speed UPSR upgrade at node (LNW26B, LNW28, LNW77, and/or LNW121B-159B

OC-48 OLIUs installed)

.................................................................................................................................................................................................

13

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-48 OLIU circuit pack in Main slot

M1

.

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m1-()-() paths supported by the circuit pack in Main slot

M1

(Ring

1). Record the active paths supported by the circuit pack in Main slot

M1

(Ring 1).

Click

Close

.

.................................................................................................................................................................................................

14

15

16

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M1

. In UPSRs, each path supported by the circuit pack in Main slot

M1

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 16 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

Repeat

Step 14

for each path supported by the circuit pack in Main slot

M1

. Click

Close

.

.................................................................................................................................................................................................

If required, repeat

Step 13

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for transmission.

.................................................................................................................................................................................................

17

Important! Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-48 circuit pack is backed out at each end of the optical span.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-123

Ring and circuit pack upgrade procedures Procedure 12-6.4: Back out high-speed UPSR upgrade at node (LNW26B, LNW28, LNW77, and/or LNW121B-159B

OC-48 OLIUs installed) in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the original OC-12 OLIU circuit pack.

Result:

The original OC-12 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an inc. OC12 LOS alarm for Main slot

M1

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

STOP!

To complete backing out the UPSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-124 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-6.5: Back out low-speed OC-12 to OC-48 UPSR upgrade at node

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by another procedure.

Step

1

Important! This procedure assumes that the Metropolis

®

DMX node is still equipped with the original OC-12 OLIU circuit packs/pluggable transmission modules.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-12 UPSR to OC-48 UPSR upgrade at a Metropolis

®

DMX node connected to the UPSR using a port pair in the

Function/Growth slots.

.................................................................................................................................................................................................

Determine the current status of the upgrade at the node.

If the port in...

both Function/Growth slot 1 and 2 have been upgraded to OC-48 ports, only Function/Growth slot 1 has been upgraded to an OC-48 port,

Then...

Continue with

Step 2 .

Proceed to

Step 12 .

2

3

.................................................................................................................................................................................................

To verify that the original OC-12 port parameters are provisioned correctly, select

View

→

Equipment

and expand the required circuit pack. Click on the original port and

Select

to obtain the port parameters. Click

Close

.

If required, provision the original OC-12 port pair according to the office records using the

Configuration

→

Equipment

command.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

To verify that the original OC-12 port DCC parameters are provisioned correctly, select

View

→

DCC Terminations

to obtain the DCC channel status. Click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-125

Ring and circuit pack upgrade procedures Procedure 12-6.5: Back out low-speed OC-12 to OC-48

UPSR upgrade at node

If required, provision the original OC-12 port DCC parameters according to the office records using the

Configuration

→

DCC Terminations

command.

Reference:

Procedure 6-4: “Provision DCC terminations” (p. 6-13)

.................................................................................................................................................................................................

4

5

6

Important! All cross-connections at this node that are associated with the OC-48

UPSR must be identified so that traffic can be moved back to the original OC-12

UPSR.

Select

View

→

Cross-Connections

. Expand the required OC-48 OLIU circuit pack in slot 2 of the Function/Growth group that is currently connected to the UPSR. Click on the required OC-48 port and

Select

to obtain the current list of cross-connections.

Identify and record all through, add, drop, and UPSR Dual Ring Interworking cross-connections. Click

Close

to exit.

Important! A UPSR Dual Ring Interworking cross-connection consists of a 1-way add, a 1-way through, and a 1-way path protected drop cross-connection. To verify that a cross-connection leg is part of a UPSR Dual Ring Interworking cross-connection, click on the cross-connection leg in the list of cross-connections and click

View Graphic

.

For additional information about UPSR Dual Ring Interworking cross-connections, refer to

Procedure 10-11: “Establish dual ring interworking (DRI) connections”

(p. 10-56) .

.................................................................................................................................................................................................

Repeat

Step 4

to obtain a current list of cross-connections for the original OC-12 port in slot 2 of the other Function/Growth group. Compare the original OC-12 port cross-connection list with the upgrade OC-48 port cross-connection list.

.................................................................................................................................................................................................

For each UPSR Dual Ring Interworking cross-connection identified in

Step 4 , select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to delete the UPSR Dual Ring Interworking cross-connections. Then use the Cross-Connection

Wizard to create the same UPSR Dual Ring Interworking cross-connections on the original OC-12 port pair in the other Function/Growth group.

Result:

Transmission hits (less than 60 ms) may occur. Alarms may be reported at other nodes in the ring.

Reference:

Procedure 10-11: “Establish dual ring interworking (DRI) connections”

(p. 10-56)

.................................................................................................................................................................................................

7

Important! Refer to the cross-connection list obtained in

Step 4

when performing this step.

.................................................................................................................................................................................................................................

12-126 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-6.5: Back out low-speed OC-12 to OC-48

UPSR upgrade at node

8

Do not perform this step for a 1-way through cross-connection associated with a

UPSR Dual Ring Interworking cross-connection.

If required, select

Configuration

→

Cross-Connections

and use the Cross-Connection

Wizard to create the required through cross-connections on the original OC-12 port pair.

Reference:

Procedure 10-5: “Make VT1.5 or STS-n cross-connections, single

OC-3/OC-12 UPSR configuration” (p. 10-16)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Removal of wrong fiber connections will result in a service interruption.

Ensure that you remove only the fiber connections for the optical span being upgraded.

9

10

Disconnect the transmit and receive optical fibers from the upgrade OC-48 port on the

OC-48 OLIU circuit pack in slot 2 of the Function/Growth group.

Result:

The system still reports an inc. OC48 LOS alarm for the OC-48 port.

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-12 port on the OC-12 OLIU circuit pack in slot 2 of the other

Function/Growth group and the required OC-12 circuit pack/port at the opposite end of the original OC-12 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-12 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! Refer to the cross-connection list obtained in

Step 4

when performing this step.

Do not perform this step for a 1-way add cross-connection associated with a UPSR

Dual Ring Interworking cross-connection.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-127

Ring and circuit pack upgrade procedures

11

12

Procedure 12-6.5: Back out low-speed OC-12 to OC-48

UPSR upgrade at node

If required, select

Configuration

→

Cross-Connections

and use the Cross-Connection

Wizard to bridge the required add cross-connections to the original OC-12 port on the

OC-12 OLIU circuit pack in slot 2 of the other Function/Growth group.

Reference:

Procedure 10-10: “Bridge and roll cross-connections” (p. 10-48)

.................................................................................................................................................................................................

Important! Refer to the cross-connection list obtained in

Step 4

when performing this step.

Do not perform this step for a 1-way path protected drop cross-connection associated with a UPSR Dual Ring Interworking cross-connection.

Select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to roll the required drop cross-connections to the original OC-12 port on the OC-12 OLIU circuit pack in slot 2 of the other Function/Growth group.

Reference:

Procedure 10-10: “Bridge and roll cross-connections” (p. 10-48)

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Removal of wrong fiber connections will result in a service interruption.

Ensure that you remove only the fiber connections for the optical span being upgraded.

13

14

Important! Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-48 circuit pack is backed out at each end of the optical span.

Disconnect the transmit and receive optical fibers from the upgrade OC-48 port on the

OC-48 OLIU circuit pack in slot 1 of the Function/Growth group.

Result:

The system reports inc. LOS alarms for the upgrade OC-48 ports and the original OC-12 port on the OC-3 OLIU circuit pack in slot 1 of the

Function/Growth group. Alarms may also be reported at other nodes in the ring.

.................................................................................................................................................................................................

Select

Configuration

→

Update System

→

Update All

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The inc. OC48 LOS alarms for the upgrade OC-48 ports clear.

.................................................................................................................................................................................................

Select

Configuration

→

Cross-Connections

and use the Cross-Connection Wizard to delete the remaining add and through cross-connections to the upgrade OC-48 ports.

.................................................................................................................................................................................................................................

12-128 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-6.5: Back out low-speed OC-12 to OC-48

UPSR upgrade at node

STOP!

To complete backing out the UPSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-129

Ring and circuit pack upgrade procedures

Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

.................................................................................................................................................................................................................................

Overview

CAUTION

Service disruption hazard

If a node has been taken out of the Ring Upgrade mode, the node cannot be returned to the original pre-upgrade state without affecting service.

All nodes connected to the UPSR using the Main slots must be in the provisioned Ring

Upgrade mode.

Important! This procedure starts at the last node upgraded. The last node upgraded must be connected to the UPSR using the Main slots. Suspending an upgrade at a node connected to the UPSR using port pairs in the Function/Growth slots is not supported.

This procedure assumes that the last node upgraded is a Metropolis

®

DMX.

However, the Metropolis

®

DMXtend can also be connected to a UPSR using the

Main slots. If the upgrade is suspended at a Metropolis

®

the Metropolis

®

DMXtend node, refer to

DMXtend Access Multiplexer User Operations Guide, 365-372-325,

Procedure 12-6: Suspend OC-12 UPSR to OC-48 UPSR upgrade.

Use this procedure to temporarily suspend an OC-12 UPSR to OC-48 UPSR upgrade at a Metropolis

®

DMX node.

Suspending an upgrade in progress temporarily stops the upgrade.

To return all nodes in the ring to their pre-upgrade state, refer to

Procedure 12-6:

“Back out OC-12 UPSR to OC-48 UPSR upgrade” (p. 12-93) .

When the ring upgrade is temporarily suspended before completion, some spans are operating at the OC-12 line rate and some at the OC-48 line rate. This requires two nodes that are equipped with an OC-12 OLIU circuit pack in one Main slot and an

OC-48 OLIU circuit pack in the other Main slot. These nodes are the starting node and the last node upgraded. These nodes must be connected to the UPSR using the Main slots. Suspending an upgrade at a node connected to the UPSR using port pairs in the

Function/Growth slots is not supported.

To continue to operate temporarily with different circuit packs in the Main slots, the starting node and the nodes that have been upgraded must remain in the Ring Upgrade mode.

.................................................................................................................................................................................................................................

12-130 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

The following equipment is required to perform this procedure:

•

Wrist strap

•

One original OC-12 OLIU circuit pack if the upgrade is suspended at a node where both Main slots are equipped with LNW26B, LNW28, LNW77, and/or

LNW121B-159B OC-48 OLIU circuit packs

•

One LNW26B OC-48 OLIU circuit packs (temporarily required if the upgrade is suspended at a node equipped with an LNW27, LNW29, LNW32, LNW76, and/or

LNW221-259 OC-48 OLIU circuit pack)

The LNW28, LNW77, and/or LNW121B-159B OC-48 OLIU circuit packs may also be used as the temporary replacement circuit packs. However, the temporary replacement circuit packs must have compatible optics. For example, do not replace a circuit pack that has long range optics with a circuit pack that has intermediate reach optics. Refer to the Metropolis

®

DMX Access Multiplexer Applications and

Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48

OLIU circuit packs.

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-131

Ring and circuit pack upgrade procedures Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this back out procedure.

Step

1

Important! This procedure starts at the last node upgraded. This procedure assumes that the last node upgraded is a Metropolis

®

DMX.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to temporarily suspend an OC-12 to OC-48 UPSR upgrade at a Metropolis

®

DMX.

.................................................................................................................................................................................................

Identify the last node that was upgraded.

If...

both Main slots have been upgraded with LNW27, LNW29,

LNW32, LNW76, and/or

LNW221-259 OC-48 OLIU circuit packs, both Main slots have been upgraded with LNW26B, LNW28,

LNW77, and/or LNW121B-159B

OC-48 OLIU circuit packs, one Main slot has been upgraded with an LNW27, LNW29,

LNW32, LNW76, and/or

LNW221-259 OC-48 OLIU circuit pack, one Main slot has been upgraded with an LNW26B, LNW28,

LNW77, and/or LNW121B-159B

OC-48 OLIU circuit pack,

Then log in to the...

last node upgraded (refer to the

“UPSR example”

(p. 12-143)

at the end of the procedure) and continue with

Step 2 .

last node upgraded (refer to the

“UPSR example”

(p. 12-143)

at the end of the procedure) and proceed to

Step 11 .

last node upgraded (refer to the

“UPSR example”

(p. 12-143)

at the end of the procedure) and proceed to

Step 17 .

last node upgraded (refer to the

“UPSR example”

(p. 12-143)

at the end of the procedure) and proceed to

Step 28 .

.................................................................................................................................................................................................................................

12-132 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

2

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! Both Main slots have been upgraded with LNW27, LNW29, LNW32,

LNW76, and/or LNW221-259 OC-48 OLIU circuit packs. The

Configuration

→

Update System

→

Update All

command has been performed and all traffic is now active on Main slot

M1

. The system is reporting an inc. OC48 LOS alarm for Main slot

M2

.

Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

Continue with

Step 3 .

3

4

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-133

Ring and circuit pack upgrade procedures Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

5

6

7

8

If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Replace the OC-48 OLIU circuit pack in Main slot

M2

with the original OC-12 OLIU circuit pack.

Result:

The inc. OC48 LOS alarm for Main slot

M2

clears, and system reports an unexpected CP type alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span, perform the following to connect the original OC-12

OLIU circuit pack in Main slot

M2

and the required OC-12 circuit pack/port at the opposite end of the original OC-12 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-12 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

.................................................................................................................................................................................................................................

12-134 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

9

10

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The original OC-12 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The system performs an automatic path protection switch, and all traffic is now active on Main slot

M2

. Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in Main slot

M1

to the circuit pack in Main slot

M2

.

The unexpected CP type alarm for Main slot

M2

clears, and the system reports an unexpected CP type alarm for Main slot

M1

.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with a temporary replacement OC-48 OLIU circuit pack.

Result:

The temporary replacement OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M1

clears. The system reports an unexpected circuit pack type condition and an inc. OC48 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span, perform the following to connect the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

and the required OC-48 circuit pack/port at the opposite end of the OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-135

Ring and circuit pack upgrade procedures

11

Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

Result:

The inc. OC48 LOS alarm for Main slot

M1

clears, and the system still reports an unexpected circuit pack type condition for Main slot

M1

.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

STOP!

End of Procedure. The upgrade procedure is now temporarily suspended and traffic is supported to the adjacent nodes.

To resume the upgrade, replace the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

with the upgrade OC-48 OLIU circuit pack, perform a system update, and replace the OC-12 OLIU circuit pack in Main slot

M2

with the upgrade

OC-48 OLIU circuit pack. Refer to

Procedure 12-5: “Upgrade OC-12 UPSR to

OC-48 UPSR” (p. 12-52) .

To back out the upgrade, refer to

Procedure 12-6: “Back out OC-12 UPSR to

OC-48 UPSR upgrade” (p. 12-93) .

.................................................................................................................................................................................................

Important! Both Main slots have been upgraded with LNW26B, LNW28,

LNW77, and/or LNW121B-159B OC-48 OLIU circuit packs. The

Configuration

→

Update System

→

Update All

command has been performed and all traffic is now active on Main slot M1. The system is reporting an inc. OC48 LOS alarm for

Main slot

M2

.

Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 15 .

Continue with

Step 12 .

.................................................................................................................................................................................................

12

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system

.................................................................................................................................................................................................................................

12-136 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

13

14

15

performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 12

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Replace the OC-48 OLIU circuit pack in Main slot

M2

with the original OC-12 OLIU circuit pack.

Result:

The OC-12 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The inc. OC48 LOS alarm for Main slot

M2

clears. The system reports an unexpected circuit pack type condition and an inc. OC12 LOS alarm for Main slot

M2

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-137

Ring and circuit pack upgrade procedures Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

16

17

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span, perform the following to connect the original OC-12

OLIU circuit pack in Main slot

M2

and the required OC-12 circuit pack/port at the opposite end of the original OC-12 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-12 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC12 LOS alarm for Main slot

M2

clears, and the system still reports an unexpected circuit pack type condition for Main slot

M2

.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

STOP!

End of Procedure. The upgrade procedure is now temporarily suspended and traffic is supported to the adjacent nodes.

To resume the upgrade, replace the OC-12 OLIU circuit pack in Main slot

M2

with the upgrade OC-48 OLIU circuit pack. Refer to

Procedure 12-5: “Upgrade OC-12

UPSR to OC-48 UPSR” (p. 12-52) .

To back out the upgrade, refer to

Procedure 12-6: “Back out OC-12 UPSR to

OC-48 UPSR upgrade” (p. 12-93) .

.................................................................................................................................................................................................

Important! Main slot

M1

has been upgraded with an LNW27, LNW29, LNW32,

LNW76, and/or LNW221-259 OC-48 OLIU circuit pack. The

Configuration

→

Update System

→

Update All

command has been performed and all traffic is now active on Main slot

M1

.

Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

.................................................................................................................................................................................................................................

12-138 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 25 .

Continue with

Step 18 .

18

19

20

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-12 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 18

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-139

Ring and circuit pack upgrade procedures Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

21

22

23

24

25

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-48 OLIU circuit pack in Main slot

M1

.

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m1-()-() paths supported by the circuit pack in Main slot

M1

(Ring

1). Record the active paths supported by the circuit pack in Main slot

M1

(Ring 1).

Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M1

. In UPSRs, each path supported by the circuit pack in Main slot

M1

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 24 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

Repeat

Step 22

for each path supported by the circuit pack in Main slot

M1

. Click

Close

.

.................................................................................................................................................................................................

If required, repeat

Step 21

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for transmission.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the temporary replacement OC-48 OLIU circuit pack.

.................................................................................................................................................................................................................................

12-140 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

26

27

Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

Result:

The system reports an unexpected CP type alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span, perform the following to connect the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

and the required OC-48 circuit pack/port at the opposite end of the OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The temporary replacement OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system performs an automatic path protection switch, and all traffic is now active on Main slot

M1

. Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in the Main slot

M2

to the circuit pack in Main slot

M1

.

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an unexpected circuit pack type condition for Main slot

M2

.

STOP!

End of Procedure. The upgrade procedure is now temporarily suspended and traffic is supported to the adjacent nodes.

To resume the upgrade, replace the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

with the upgrade OC-48 OLIU circuit pack, perform a system update, and replace the OC-12 OLIU circuit pack in Main slot

M2

with the upgrade

OC-48 OLIU circuit pack. Refer to

Procedure 12-5: “Upgrade OC-12 UPSR to

OC-48 UPSR” (p. 12-52) .

To back out the upgrade, refer to

Procedure 12-6: “Back out OC-12 UPSR to

OC-48 UPSR upgrade” (p. 12-93) .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-141

Ring and circuit pack upgrade procedures Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

28

.................................................................................................................................................................................................

Important! Main slot

M1

has been upgraded with an LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIU circuit pack.

If an unexpected circuit pack type condition is reported for Main slot

M1

, select

Configuration

→

Update System

→

Update All

, then select

main-1

(default) as the

Ring Upgrade Choice and click

OK

. Otherwise, the node is already in the proper suspend configuration and no further action is required.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an unexpected circuit pack type condition for Main slot

M2

.

STOP!

End of Procedure. The upgrade procedure is now temporarily suspended and traffic is supported to the adjacent nodes.

To resume the upgrade, replace the OC-12 OLIU circuit pack in Main slot

M2

with the OC-48 OLIU circuit pack. Refer to

Procedure 12-5: “Upgrade OC-12 UPSR to

OC-48 UPSR” (p. 12-52) .

To back out the upgrade, refer to

Procedure 12-6: “Back out OC-12 UPSR to

OC-48 UPSR upgrade” (p. 12-93) .

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

12-142 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

UPSR example

DMX or DMXtend

N

(Starting Node)

MAIN-1 MAIN-2

DMX or DMXtend

N+3

Procedure 12-7: Suspend OC-12 UPSR to OC-48 UPSR upgrade

DMX or DMXtend

N+1

DMX or DMXtend

FN-n-2-n or

Growth-2-n

N+2

FN-n-1-n or

Growth-1-n

DMX = Metropolis DMX Access Multiplexer

DMX

tend

= Metropolis DMX

tend

Access Multiplexer

MA-DMX-404

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-143

Ring and circuit pack upgrade procedures

Procedure 12-8: Upgrade OC-48 UPSR to OC-192 UPSR

.................................................................................................................................................................................................................................

Overview

Important! The UPSR must be equipped with Metropolis

®

DMX nodes only. This upgrade procedure does not support upgrading UPSRs equipped with nodes other than Metropolis

®

DMX.

Use this procedure to upgrade an in-service OC-48 UPSR with:

•

LNW26B, LNW27 (pre Series 1:6), LNW28, LNW29 (pre Series 1:6), LNW76

(pre Series 1:6), LNW77, LNW121B-159B, and/or LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs at all nodes to an OC-192 UPSR.

These OC-48 OLIU circuit packs have different optics and transmit at different wavelengths. However, these circuit packs have the same circuit pack type and a

small VT cross-connection fabric. There are no differences between these circuit packs for the purposes of ring upgrades.

These OC-48 OLIU circuit packs and the OC-192 OLIU circuit packs have

incompatible VT cross-connection fabrics.

•

LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76

(Series 1:6 and later), and/or LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs at one or more nodes to an OC-192 UPSR.

These OC-48 OLIU circuit packs have different optics and transmit at different wavelengths. However, these circuit packs have the same circuit pack type and a

large VT cross-connection fabric. There are no differences between these circuit packs for the purposes of ring upgrades.

These OC-48 OLIU circuit packs and the OC-192 OLIU circuit packs have

compatible VT cross-connection fabrics.

The OC-48 OLIU circuit packs in the Main slots are upgraded at each node.

Low-speed OC-48 UPSR upgrades are not supported in this release. Currently,

Metropolis

®

DMX does not support OC-192 OLIU circuit packs in the

Function/Growth slots.

This procedure assumes that in the UPSR, the circuit pack in the Main slot

M1

is always connected to the circuit pack in the Main slot

M2

of the adjacent node.

Important! Transmission hits will occur during this procedure whenever an OLIU circuit pack with a different line rate is installed or removed from a Main slot. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

Privilege level

You must log in as a Privileged user to complete this procedure.

.................................................................................................................................................................................................................................

12-144 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-8: Upgrade OC-48 UPSR to OC-192 UPSR

Required equipment

The following equipment is required to perform this procedure:

•

Optical power meter

•

Wrist strap

•

As optical spans are upgraded around the UPSR, ensure that technicians are available at each end of an optical span as it is upgraded.

•

If the first node to be upgraded is equipped with LNW27 (pre Series 1:6), LNW29

(pre Series 1:6), LNW76 (pre Series 1:6), and/or LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs, 1 Series 1:6 or later version of the same OC-48 OLIU circuit pack type is temporarily required. For example if the first node to be upgraded is equipped with pre Series 1:6 LNW27 OC-48 OLIU circuit packs, then

1 Series 1:6 or later LNW27 OC-48 OLIU circuit pack is temporarily required.

•

If the first node to be upgraded is equipped with LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIU circuit packs, 1 LNW27 (Series 1:6 and later) or LNWUPG OC-48 OLIU circuit pack is temporarily required.

The LNWUPG OC-48 OLIU circuit pack is a special LNW27 OC-48 OLIU circuit pack that is intended for use only as the temporary transition circuit pack. There are no differences between the LNW27 (Series 1:6 and later) and LNWUPG circuit packs with respect to in-service upgrades.

An LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and/or

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit pack may also be used as the temporary replacement circuit pack. However, the temporary replacement circuit pack must have compatible optics. For example, do not replace a circuit pack that has long reach optics with a circuit pack that has intermediate reach optics. Refer to the Metropolis

®

DMX Access Multiplexer Applications and Planning Guide,

365-372-300 for the SONET optical specifications of the OC-48 OLIU circuit packs.

•

2 replacement LNW56, LNW57, LNW58, LNW60, LNW523, LNW527, LNW554, or LNW555 OC-192 OLIU circuit packs for each node

The replacement circuit packs must have compatible optics. For example, do not replace a circuit pack that has long reach optics with a circuit pack that has intermediate reach optics. Refer to the Metropolis

®

DMX Access Multiplexer

Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-192 OLIU circuit packs.

Important! Release 2.1.2 or later software is required to support the OC-192 OLIU circuit packs.

Release 3.0 or later software is required to support LNW555 OC-192 OLIU circuit packs.

Release 4.0 or later software is required to support LNW57, LNW523, LNW527, and LNW554 OC-192 OLIU circuit packs.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-145

Ring and circuit pack upgrade procedures Procedure 12-8: Upgrade OC-48 UPSR to OC-192 UPSR

Release 5.1 or later software is required to support LNW60 OC-192 OLIU circuit packs.

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Obtain the work instructions for this procedure.

3. Review the applicable office records and verify that each fiber span in the UPSR is capable of supporting higher rate (OC-192) traffic. Verify that the fiber span does not exceed 40 kilometers. Refer to the Metropolis

®

DMX Access Multiplexer

Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-192 OLIU circuit packs.

4. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this upgrade procedure.

Step

Complete the following steps to upgrade an in-service OC-48 UPSR to an OC-192

UPSR.

.................................................................................................................................................................................................

1

From office records and work instructions, determine the current network configuration. Note how the nodes are connected in the ring and make a drawing of the ring to reference during this upgrade procedure.

.................................................................................................................................................................................................................................

12-146 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-8: Upgrade OC-48 UPSR to OC-192 UPSR

2

3

4

5

6

.................................................................................................................................................................................................

Log in to a node in the UPSR to be upgraded.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the NE Alarm List and verify that no alarms are present.

Refer to the appropriate trouble clearing procedures to clear all existing alarms before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

To verify that no loopbacks, protection switch lockouts, or protection switches are present, select

View

→

Rolling Events

. Under the line reading

RTRV-COND-ALL determine if any loopbacks, protection switch lockouts, or protection switches are displayed.

Remove all existing loopbacks, protection switch lockouts, or protection switches before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and verify that no test access sessions exist.

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and delete all existing test access sessions.

Reference:

•

Procedure 14-27: “View test access session(s)” (p. 14-130)

•

Procedure 14-26: “Delete test access session” (p. 14-129)

.................................................................................................................................................................................................

If Ethernet service is provisioned with spanning tree protection, verify that the spanning tree states are correct by selecting

View

→

Data

→

Spanning Tree Group

.

Expand the required circuit pack, select the appropriate spanning tree and click

Select

.

Observe the VCG Status. All VCGs should be forwarding (FWG) packets, except for one VCG that should be discarding (DCD) packets. If this is not the case, contact

Technical Support Services (TSS) for assistance in correcting the spanning tree states before continuing with this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-147

Ring and circuit pack upgrade procedures Procedure 12-8: Upgrade OC-48 UPSR to OC-192 UPSR

7

.................................................................................................................................................................................................

At each of the remaining nodes in the UPSR, log in to the node and repeat

Step 3

through

Step 6 . Then continue with the next step.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

8

If upgrading an OC-48 UPSR with...

LNW27 (pre Series 1:6), LNW29

(pre Series 1:6), LNW76 (pre

Series 1:6), and/or LNW221-259

(pre Series 1:6) OC-48 OLIU circuit packs at all nodes to an

OC-192 UPSR,

Then...

Proceed to and perform the following:

1.

Procedure 12-8.5: “Replace pre Series 1:6

LNW27, 29, 76, 221-259 OC-48 OLIU at first node to be upgraded” (p. 12-178)

2.

Procedure 12-8.2: “Upgrade OC-48 UPSR

(compatible OC-48 OLIUs at one or more nodes) to OC-192 UPSR” (p. 12-159)

Proceed to and perform

Procedure 12-8.1:

“Upgrade OC-48 UPSR (incompatible OC-48

OLIUs at all nodes) to OC-192 UPSR”

(p. 12-149) .

LNW26B, LNW27 (pre Series 1:6),

LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, and/or

LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs at all nodes to an OC-192 UPSR,

LNW27 (Series 1:6 and later),

LNW29 (Series 1:6 and later),

LNW32, LNW76 (Series 1:6 and later), and/or LNW221-259 (Series

1:6 and later) OC-48 OLIU circuit packs at one or more nodes to an

OC-192 UPSR,

Procedure 12-8.2: “Upgrade OC-48 UPSR

(compatible OC-48 OLIUs at one or more nodes) to OC-192 UPSR” (p. 12-159)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-148 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-8.1: Upgrade OC-48 UPSR (incompatible OC-48

OLIUs at all nodes) to OC-192 UPSR

.................................................................................................................................................................................................................................

.

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-8: “Upgrade OC-48 UPSR to OC-192 UPSR” (p. 12-144)

Step

1

2

Important! Incompatible OC-48 OLIU circuit packs include the LNW26B, LNW27

(pre Series 1:6), LNW28, LNW29 (pre Series 1:6), LNW76 (pre Series 1:6),

LNW77, LNW121B-159B, and LNW221-259 (pre Series 1:6) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade an in-service OC-48 UPSR (equipped with incompatible OC-48 OLIU circuit packs at all nodes) to an OC-192 UPSR.

.................................................................................................................................................................................................

Important! The starting node must be equipped with LNW26B, LNW28, LNW32,

LNW77, or LNW121B-159B OC-48 OLIU circuit packs in the Main slots.

Identify and log in to the starting node (refer to the

“UPSR example” (p. 12-158)

at the end of the procedure). Verify that the Main slots are equipped with LNW26B,

LNW28, LNW32, LNW77, or LNW121B-159B OC-48 OLIU circuit packs using

Reports

→

Equipment Lists

→

Packs

. Click Shelf and

Select

. Observe the

Apparatus Code of the main-1 and main-2 circuit packs. Click

Close

.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The Ring Upgrade mode allows cross-connections/ data to be mapped to the new circuit pack and prohibits provisioning new cross-connections.

At the WaveStar

®

CIT System View, select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

CIT

Alarm List shows the Ring Upgrade mode as Not Alarmed.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-149

Ring and circuit pack upgrade procedures Procedure 12-8.1: Upgrade OC-48 UPSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 UPSR

3

The node remains in the Ring Upgrade mode until manually provisioned back to the Normal mode. While in the Ring Upgrade mode, the upgrade may be temporarily suspended or backed out. To prevent errors in the upgraded ring, keep all nodes in Ring Upgrade mode until all nodes have been upgraded.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 11 .

Continue with

Step 4 .

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

.................................................................................................................................................................................................................................

12-150 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

6

7

8

9

Procedure 12-8.1: Upgrade OC-48 UPSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 UPSR

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 4

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-48 OLIU circuit pack in Main slot

M1

.

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m1-()-() paths supported by the circuit pack in Main slot

M1

(Ring

1). Record the active paths supported by the circuit pack in Main slot

M1

(Ring 1).

Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M1

. In UPSRs, each path supported by the circuit pack in Main slot

M1

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 10 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

Repeat

Step 8

for each path supported by the circuit pack in Main slot

M1

. Click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-151

Ring and circuit pack upgrade procedures Procedure 12-8.1: Upgrade OC-48 UPSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 UPSR

10

11

12

13

.................................................................................................................................................................................................

If required, repeat

Step 7

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for transmission.

.................................................................................................................................................................................................

Important! At the starting node, the OC-48 OLIU circuit pack in Main slot

M1

must be first replaced with the temporary replacement OC-48 OLIU circuit pack.

(Refer to

“Required equipment” (p. 12-145)

for a list of acceptable temporary replacement OC-48 OLIU circuit packs.) The temporary replacement OC-48 OLIU circuit pack maintains traffic with the last node to be upgraded while slot

M2

and the other nodes in the ring are upgraded. As a final step, this temporary replacement OC-48 OLIU circuit pack is upgraded.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the temporary replacement OC-48 OLIU circuit pack.

Result:

Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M1

. If active through traffic exists on the circuit pack in Main slot

M1

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected CP type alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

and the required

OC-48 circuit pack/port at the opposite end of the OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

.................................................................................................................................................................................................................................

12-152 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

14

Procedure 12-8.1: Upgrade OC-48 UPSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 UPSR

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The temporary replacement OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system performs an automatic path protection switch, and all traffic is now active on Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an unexpected CP type alarm for Main slot

M2

.

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-48 OLIU circuit pack is upgraded at each end of the optical span.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the replacement OC-192 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-192 OLIU circuit pack is inserted. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The replacement OC-192 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The system reports an unexpected circuit pack type condition and an

OC192

LOS alarm for Main slot

M2

. Alarms may also be reported at other nodes in the ring.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-153

Ring and circuit pack upgrade procedures Procedure 12-8.1: Upgrade OC-48 UPSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 UPSR

15

16

17

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

This completes the first phase of the upgrade at the starting node. The starting node upgrade will be completed after all the other nodes in the ring are upgraded.

.................................................................................................................................................................................................

Log in to the adjacent node connected to Main slot

M2

(refer to the

“UPSR example”

(p. 12-158)

at the end of the procedure).

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Upgrade the incompatible OC-48 OLIU circuit packs in the Main slots.

Reference:

Procedure 12-8.3: “Upgrade high-speed UPSR connections at node equipped with incompatible OC-48 OLIUs” (p. 12-168)

.................................................................................................................................................................................................

Except for the starting node, have all nodes in the UPSR been upgraded.

If...

No,

Yes,

Then...

Repeat

Step 15

and

Step 16

as required at the next node (refer to the

“UPSR example”

(p. 12-158)

at the end of the procedure).

Continue with

Step 18 .

18

19

.................................................................................................................................................................................................

Log in to the starting node (refer to the

“UPSR example” (p. 12-158)

at the end of the procedure).

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View, select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M2

clears, and the system reports an unexpected circuit pack type condition for Main slot

M1

.

.................................................................................................................................................................................................................................

12-154 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-8.1: Upgrade OC-48 UPSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 UPSR

20

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 24 .

Continue with

Step 21 .

21

22

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-155

Ring and circuit pack upgrade procedures Procedure 12-8.1: Upgrade OC-48 UPSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 UPSR

23

24

25

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 21

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Open a faceplate latch on the temporary replacement OC-48 OLIU circuit pack in

Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

. Then replace the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

with the replacement

OC-192 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-192 OLIU circuit pack is inserted. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The replacement OC-192 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an inc. OC192 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the replacement OC-192 OLIU circuit pack in Main slot

M1

and the required OC-192 circuit pack/port at the opposite end of the upgraded OC-192 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-192 circuit packs.)

3. Clean and connect the receive fibers.

.................................................................................................................................................................................................................................

12-156 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-8.1: Upgrade OC-48 UPSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 UPSR

Result:

The inc. OC192 LOS alarms clear. Transmission is now supported on the upgraded optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

26

Important! At nodes connected to the UPSR using the Main slots, the system reports the ring upgrade mode standing condition (not alarmed) in the NE Alarm

List until the node is manually provisioned back to the Normal mode.

At nodes connected to the UPSR using the Main slots, click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the

NE Alarm List and verify that no alarms or standing conditions are present (except ring upgrade mode and

ABN condition

).

Refer to the appropriate trouble clearing procedures to clear all existing alarms and standing conditions (except ring upgrade mode and

ABN condition

) before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

27

Important! The network must be alarm free with normal transmission before manually provisioning the nodes back to the Normal mode. After a node is manually provisioned back to the Normal mode, the node cannot be returned to the pre-upgrade state using the back out procedure.

At each node in the UPSR, select

Configuration

→

Normal Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode will be removed from the WaveStar

®

CIT alarm list.

.................................................................................................................................................................................................

28

Important! It is recommended that the network element database be backed up to a remote OS (for example, the Navis

®

Optical Element Management System) after an upgrade. This creates a current backup copy that includes the replacement circuit packs. The remote OS could use this backup copy to restore the network element database in the event of a catastrophic failure. Attempts to restore the network element database using a backup copy created prior to the upgrade may result in circuit pack failures.

At each node in the UPSR, back up the network element database using the

Configuration

→

Software

→

Remote Backup

command.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-157

Ring and circuit pack upgrade procedures Procedure 12-8.1: Upgrade OC-48 UPSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 UPSR

Reference:

•

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123)

•

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135)

•

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150)

E

N D O F

S

T E P S

UPSR example

Starting Node

: Metropolis

®

DMX Node N

Starting Circuit Pack

: Main-2 at the Starting Node (a temporary replacement OC-48 circuit pack must be installed in Main-1)

Direction of Upgrade

: Clockwise around UPSR from Main-2 at the Starting Node to

Main/Function/Growth slot 1 at the adjacent node

N

(Starting Node)

MAIN-1 MAIN-2

N+3

N+1

MAIN-2

N+2

MAIN-1 nc-dmx-255

.................................................................................................................................................................................................................................

12-158 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-8.2: Upgrade OC-48 UPSR (compatible OC-48

OLIUs at one or more nodes) to OC-192 UPSR

.................................................................................................................................................................................................................................

.

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-8: “Upgrade OC-48 UPSR to OC-192 UPSR” (p. 12-144)

Step

1

2

Important! Compatible OC-48 OLIU circuit packs include LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade an in-service OC-48 UPSR (equipped with compatible OC-48 OLIU circuit packs at one or more nodes) to an OC-192 UPSR.

.................................................................................................................................................................................................

Important! The starting node must be equipped with LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), or

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs in the Main slots.

Identify and log in to the starting node (refer to the

“UPSR example” (p. 12-167)

at the end of the procedure). Verify that the Main slots are equipped with compatible

OC-48 OLIU circuit packs using

Reports

→

Equipment Lists

→

Packs

. Click Shelf and

Select

. Observe the Apparatus Code of the main-1 and main-2 circuit packs. Click

Close

.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The Ring Upgrade mode allows cross-connections/ data to be mapped to the new circuit pack and prohibits provisioning new cross-connections.

At the WaveStar

®

CIT System View, select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

CIT

Alarm List shows the Ring Upgrade mode as Not Alarmed.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-159

Ring and circuit pack upgrade procedures Procedure 12-8.2: Upgrade OC-48 UPSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 UPSR

3

The node remains in the Ring Upgrade mode until manually provisioned back to the Normal mode. While in the Ring Upgrade mode, the upgrade may be temporarily suspended or backed out. To prevent errors in the upgraded ring, keep all nodes in Ring Upgrade mode until all nodes have been upgraded.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 11 .

Continue with

Step 4 .

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

.................................................................................................................................................................................................................................

12-160 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

6

7

8

9

Procedure 12-8.2: Upgrade OC-48 UPSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 UPSR

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 4

to verify that the OC-48 OLIU circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-48 OLIU circuit pack in Main slot

M2

.

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m2-()-() paths supported by the circuit pack in Main slot

M2

(Ring

2). Record the active paths supported by the circuit pack in Main slot

M2

(Ring 2).

Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M2

. In UPSRs, each path supported by the circuit pack in Main slot

M2

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is not the active circuit pack for transmission, proceed to

Step 10 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

Repeat

Step 8

for each path supported by the circuit pack in Main slot

M2

. Click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-161

Ring and circuit pack upgrade procedures Procedure 12-8.2: Upgrade OC-48 UPSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 UPSR

10

11

.................................................................................................................................................................................................

If required, repeat

Step 7

to verify that the OC-48 OLIU circuit pack in Main slot

M1

is now the active circuit pack for transmission.

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-48 OLIU circuit pack is upgraded at each end of the optical span.

12

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the replacement OC-192 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-192 OLIU circuit pack is inserted. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The replacement OC-192 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned. Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M2

. If active through traffic exists on the circuit pack in Main slot

M2

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected circuit pack type condition and an inc.

OC192 LOS alarm for Main slot

M2

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

This completes the first phase of the upgrade at the starting node. The starting node upgrade will be completed after all the other nodes in the ring are upgraded.

.................................................................................................................................................................................................

Log in to the adjacent node connected to Main slot

M2

(refer to the

“UPSR example”

(p. 12-167)

at the end of the procedure).

.................................................................................................................................................................................................................................

12-162 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-8.2: Upgrade OC-48 UPSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 UPSR

13

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Determine the type of OC-48 OLIU circuit packs in the Main slots, and then upgrade the node.

If the node is equipped with...

LNW26B, LNW27 (pre Series 1:6),

LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, and/or

LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs in the

Main slots,

LNW27 (Series 1:6 and later),

LNW29 (Series 1:6 and later),

LNW32, LNW76 (Series 1:6 and later), and/or LNW221-259 (Series

1:6 and later) OC-48 OLIU circuit packs in the Main slots,

Then upgrade the high-speed UPSR connections using...

Procedure 12-8.3: “Upgrade high-speed UPSR connections at node equipped with incompatible

OC-48 OLIUs” (p. 12-168)

Step 14 .

. Then continue with

Procedure 12-8.4: “Upgrade high-speed UPSR connections at node equipped with compatible

OC-48 OLIUs” (p. 12-172) . Then continue with

Step 14 .

14

.................................................................................................................................................................................................

Except for the starting node, have all nodes in the UPSR been upgraded.

If...

No

Yes

Then...

Repeat

Step 12

and

Step 13

as required at the next node (refer to the

“UPSR example”

(p. 12-167)

at the end of the procedure).

Continue with

Step 15 .

15

16

.................................................................................................................................................................................................

Log in to the starting node (refer to the

“UPSR example” (p. 12-167)

at the end of the procedure).

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-163

Ring and circuit pack upgrade procedures

17

Procedure 12-8.2: Upgrade OC-48 UPSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 UPSR

At the System View, select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M2

clears, and the system reports an unexpected circuit pack type condition for Main slot

M1

.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 21 .

Continue with

Step 18 .

18

19

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

.................................................................................................................................................................................................................................

12-164 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-8.2: Upgrade OC-48 UPSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 UPSR

20

21

22

If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 18

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the replacement OC-192 OLIU circuit pack.

Result:

A transmission hit may occur after the OC-48 OLIU circuit pack is removed. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The replacement OC-192 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an inc. OC192 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the replacement OC-192 OLIU circuit pack in Main slot

M1

and the required OC-192 circuit pack/port at the opposite end of the upgraded OC-192 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-OC-192 circuit packs.)

3. Clean and connect the receive fibers.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-165

Ring and circuit pack upgrade procedures Procedure 12-8.2: Upgrade OC-48 UPSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 UPSR

Result:

The inc. OC192 LOS alarms clear. Transmission is now supported on the upgraded optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

23

Important! At nodes connected to the UPSR using the Main slots, the system reports the ring upgrade mode standing condition (not alarmed) in the NE Alarm

List until the node is manually provisioned back to the Normal mode.

At nodes connected to the UPSR using the Main slots, click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the

NE Alarm List and verify that no alarms or standing conditions are present (except ring upgrade mode and

ABN condition

).

Refer to the appropriate trouble clearing procedures to clear all existing alarms and standing conditions (except ring upgrade mode and

ABN condition

) before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

24

Important! The network must be alarm free with normal transmission before manually provisioning the nodes back to the Normal mode. After a node is manually provisioned back to the Normal mode, the node cannot be returned to the pre-upgrade state using the back out procedure.

At each node in the UPSR, select

Configuration

→

Normal Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode will be removed from the WaveStar

®

CIT alarm list.

.................................................................................................................................................................................................

25

Important! It is recommended that the network element database be backed up to a remote OS (for example, the Navis

®

Optical Element Management System) after an upgrade. This creates a current backup copy that includes the replacement circuit packs. The remote OS could use this backup copy to restore the network element database in the event of a catastrophic failure. Attempts to restore the network element database using a backup copy created prior to the upgrade may result in circuit pack failures.

At each node in the UPSR, back up the network element database using the

Configuration

→

Software

→

Remote Backup

command.

.................................................................................................................................................................................................................................

12-166 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-8.2: Upgrade OC-48 UPSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 UPSR

Reference:

•

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123)

•

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135)

•

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150)

E

N D O F

S

T E P S

UPSR example

Starting Node

: Metropolis

®

DMX Node N

Starting Circuit Pack

: Main-2 at the Starting Node

Direction of Upgrade

: Clockwise around UPSR from Main-2 at the Starting Node to

Main/Function/Growth slot 1 at the adjacent node

N

(Starting Node)

MAIN-1 MAIN-2

N+3 N+1

MAIN-2

N+2

MAIN-1 nc-dmx-255

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-167

Ring and circuit pack upgrade procedures

Procedure 12-8.3: Upgrade high-speed UPSR connections at node equipped with incompatible OC-48 OLIUs

.................................................................................................................................................................................................................................

.

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-8: “Upgrade OC-48 UPSR to OC-192 UPSR” (p. 12-144)

Step

1

2

Important! Incompatible OC-48 OLIU circuit packs include the LNW26B, LNW27

(pre Series 1:6), LNW28, LNW29 (pre Series 1:6), LNW76 (pre Series 1:6),

LNW77, LNW121B-159B, and LNW221-259 (pre Series 1:6) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade the in-service high-speed UPSR connections at a node equipped with incompatible OC-48 OLIU circuit packs in the Main slots.

.................................................................................................................................................................................................

Important! The Ring Upgrade mode allows cross-connections/ data to be mapped to the new circuit pack and prohibits provisioning new cross-connections.

At the System View, select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

CIT

Alarm List shows the Ring Upgrade mode as Not Alarmed.

The node remains in the Ring Upgrade mode until manually provisioned back to the Normal mode. While in the Ring Upgrade mode, the upgrade may be temporarily suspended or backed out. To prevent errors in the upgraded ring, keep all nodes in Ring Upgrade mode until all nodes have been upgraded.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

.................................................................................................................................................................................................................................

12-168 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-8.3: Upgrade high-speed UPSR connections at node equipped with incompatible OC-48

OLIUs

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

Continue with

Step 3 .

3

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-169

Ring and circuit pack upgrade procedures Procedure 12-8.3: Upgrade high-speed UPSR connections at node equipped with incompatible OC-48

OLIUs

.................................................................................................................................................................................................

6

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the replacement OC-192 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-192 OLIU circuit pack is inserted. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in the Main slot

M1

.

The system reports an unexpected CP type alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

7

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the replacement OC-192 OLIU circuit pack in Main slot

M1

and the required OC-192 circuit pack/port at the opposite end of the upgraded OC-192 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-192 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

8

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The replacement OC-192 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system performs an automatic path protection switch, and all traffic is now active on Main slot

M1

. Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in the Main slot

M2

to the circuit pack in Main slot

M1

.

.................................................................................................................................................................................................................................

12-170 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-8.3: Upgrade high-speed UPSR connections at node equipped with incompatible OC-48

OLIUs

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an unexpected CP type alarm for Main slot

M2

.

9

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-48 OLIU circuit pack is upgraded at each end of the optical span.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the replacement OC-192 OLIU circuit pack.

Result:

The replacement OC-192 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M2

clears, and the system reports an inc. OC192 LOS alarm for Main slot

M2

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

STOP!

To complete the UPSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-171

Ring and circuit pack upgrade procedures

Procedure 12-8.4: Upgrade high-speed UPSR connections at node equipped with compatible OC-48 OLIUs

.................................................................................................................................................................................................................................

.

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-8: “Upgrade OC-48 UPSR to OC-192 UPSR” (p. 12-144)

Step

1

2

Important! Compatible OC-48 OLIU circuit packs include LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade the in-service high-speed UPSR connections at a node equipped with compatible OC-48 OLIU circuit packs in the Main slots.

.................................................................................................................................................................................................

Important! The Ring Upgrade mode allows cross-connections/ data to be mapped to the new circuit pack and prohibits provisioning new cross-connections.

At the System View, select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

Alarm List shows the Ring Upgrade mode as Not Alarmed.

CIT

The node remains in the Ring Upgrade mode until manually provisioned back to the Normal mode. While in the Ring Upgrade mode, the upgrade may be temporarily suspended or backed out. To prevent errors in the upgraded ring, keep all nodes in Ring Upgrade mode until all nodes have been upgraded.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

.................................................................................................................................................................................................................................

12-172 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-8.4: Upgrade high-speed UPSR connections at node equipped with compatible OC-48

OLIUs

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

Continue with

Step 3 .

3

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-173

Ring and circuit pack upgrade procedures Procedure 12-8.4: Upgrade high-speed UPSR connections at node equipped with compatible OC-48

OLIUs

.................................................................................................................................................................................................

6

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the replacement OC-192 OLIU circuit pack.

Result:

A transmission hit may occur after the OC-192 OLIU circuit pack is inserted. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The replacement OC-192 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system reports an unexpected circuit pack type condition and an inc.

OC192 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

7

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the replacement OC-192 OLIU circuit pack in Main slot

M1

and the required OC-192 circuit pack/port at the opposite end of the upgraded OC-192 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-OC-192 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC192 LOS alarms clear. Transmission is now supported on the upgraded optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

8

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an unexpected circuit pack type condition for Main slot

M2

.

.................................................................................................................................................................................................................................

12-174 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-8.4: Upgrade high-speed UPSR connections at node equipped with compatible OC-48

OLIUs

.................................................................................................................................................................................................

9

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 17 .

Continue with

Step 10 .

10

11

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-175

Ring and circuit pack upgrade procedures Procedure 12-8.4: Upgrade high-speed UPSR connections at node equipped with compatible OC-48

OLIUs

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

12

13

.................................................................................................................................................................................................

If required, repeat

Step 10

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-48 OLIU circuit pack in Main slot

M2

.

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m2-()-() paths supported by the circuit pack in Main slot

M2

(Ring

2). Record the active paths supported by the circuit pack in Main slot

M2

(Ring 2).

Click

Close

.

.................................................................................................................................................................................................

14

15

16

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M2

. In UPSRs, each path supported by the circuit pack in Main slot

M2

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is not the active circuit pack for transmission, proceed to

Step 16 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

Repeat

Step 14

for each path supported by the circuit pack in Main slot

M2

. Click

Close

.

.................................................................................................................................................................................................

If required, repeat

Step 13

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for transmission.

.................................................................................................................................................................................................................................

12-176 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

17

Procedure 12-8.4: Upgrade high-speed UPSR connections at node equipped with compatible OC-48

OLIUs

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-48 OLIU circuit pack is upgraded at each end of the optical span.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the replacement OC-192 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-48 OLIU circuit pack is removed. The transmission hit is the result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The replacement OC-192 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected circuit pack type condition for Main slot

M2

clears, and the system reports an inc. OC192 LOS alarm for Main slot

M2

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

STOP!

To complete the UPSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-177

Ring and circuit pack upgrade procedures

Procedure 12-8.5: Replace pre Series 1:6 LNW27, 29, 76,

221-259 OC-48 OLIU at first node to be upgraded

.................................................................................................................................................................................................................................

.

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-8: “Upgrade OC-48 UPSR to OC-192 UPSR” (p. 12-144)

Step

1

2

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to replace a pre Series 1:6 LNW27, 29, 76, 221-259

OC-48 OLIU circuit pack with a Series 1:6 or later version of the same OC-48 OLIU circuit pack type at the first node to be upgraded.

.................................................................................................................................................................................................

Identify and log in to the starting node.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 10 .

Continue with

Step 3 .

.................................................................................................................................................................................................................................

12-178 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-8.5: Replace pre Series 1:6 LNW27, 29,

76, 221-259 OC-48 OLIU at first node to be upgraded

3

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

4

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

5

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................

6

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-48 OLIU circuit pack in Main slot

M1

.

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m1-()-() paths supported by the circuit pack in Main slot

M1

(Ring

1). Record the active paths supported by the circuit pack in Main slot

M1

(Ring 1).

Click

Close

.

.................................................................................................................................................................................................

7

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M1

. In UPSRs, each path

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-179

Ring and circuit pack upgrade procedures Procedure 12-8.5: Replace pre Series 1:6 LNW27, 29,

76, 221-259 OC-48 OLIU at first node to be upgraded

8

9

10

supported by the circuit pack in Main slot

M1

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 9 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

Repeat

Step 7

for each path supported by the circuit pack in Main slot

M1

. Click

Close

.

.................................................................................................................................................................................................

If required, repeat

Step 6

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for transmission.

.................................................................................................................................................................................................

Important! At the starting node, the pre Series 1:6 LNW27, 29, 76, 221-259

OC-48 OLIU circuit pack in Main slot

M1

must be first replaced with a Series 1:6 or later version of the same LNW27, 29, 76, 221-259 OC-48 OLIU circuit pack type. For example, a pre Series 1:6 LNW27 OC-48 OLIU circuit pack must be replaced with a Series 1:6 or later LNW27 OC-48 OLIU circuit pack. The Series

1:6 or later OC-48 OLIU circuit pack maintains traffic with the last node to be upgraded while slot

M2

and the other nodes in the ring are upgraded. As a final step, The Series 1:6 or later OC-48 OLIU circuit pack is upgraded.

Open a faceplate latch on the pre Series 1:6 LNW27, 29, 76, 221-259 OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the

OC-48 OLIU circuit pack in Main slot

M1

with a Series 1:6 or later version of the same OC-48 OLIU circuit pack type.

.................................................................................................................................................................................................................................

12-180 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-8.5: Replace pre Series 1:6 LNW27, 29,

76, 221-259 OC-48 OLIU at first node to be upgraded

11

12

Result:

Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M1

. If active through traffic exists on the circuit pack in Main slot

M1

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

Measure the optical receive power of the receive fiber using an optical power meter.

Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 OLIU circuit packs.)

.................................................................................................................................................................................................

Clean all fiber connectors, and connect the transmit and receive optical fibers to the replacement OC-48 OLIU circuit pack in Main slot

M1

.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

STOP!

To complete the UPSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-181

Ring and circuit pack upgrade procedures

Procedure 12-9: Back out OC-48 UPSR to OC-192 UPSR upgrade

.................................................................................................................................................................................................................................

Overview

CAUTION

Service disruption hazard

If a node has been taken out of the Ring Upgrade mode, the node cannot be returned to the original pre-upgrade state without affecting service.

All nodes in the ring must be in the provisioned Ring Upgrade mode.

Use this procedure to back out an OC-48 UPSR to OC-192 upgrade with:

•

LNW26B, LNW27 (pre Series 1:6), LNW28, LNW29 (pre Series 1:6), LNW76

(pre Series 1:6), LNW77, LNW121B-159B, and/or LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs originally at all nodes.

These OC-48 OLIU circuit packs have different optics and transmit at different wavelengths. However, these circuit packs have the same circuit pack type and a

small VT cross-connection fabric. There are no differences between these circuit packs for the purposes of ring backouts/suspends.

These OC-48 OLIU circuit packs and the OC-192 OLIU circuit packs have

incompatible VT cross-connection fabrics.

•

LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76

(Series 1:6 and later), and/or LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs originally at one or more nodes.

These OC-48 OLIU circuit packs have different optics and transmit at different wavelengths. However, these circuit packs have the same circuit pack type and a

large VT cross-connection fabric. There are no differences between these circuit packs for the purposes of ring backouts/suspends.

These OC-48 OLIU circuit packs and the OC-192 OLIU circuit packs have

compatible VT cross-connection fabrics.

Backing out of an upgrade in progress returns all nodes in the ring to their pre-upgrade state.

To temporarily stop the upgrade refer to

Procedure 12-10: “Suspend OC-48 UPSR to

OC-192 UPSR upgrade” (p. 12-214) .

Important! Transmission hits will occur during this procedure whenever an OLIU circuit pack with a different line rate is installed or removed from a Main slot. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

.................................................................................................................................................................................................................................

12-182 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-9: Back out OC-48 UPSR to OC-192 UPSR upgrade

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

The following equipment is required to perform this procedure:

•

Wrist strap

•

Original OC-48 OLIU circuit packs for each node to be backed out

•

As the upgrade is backed out around the UPSR, ensure that technicians are available at each end of an optical span as the upgrade is backed out.

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this back out procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-183

Ring and circuit pack upgrade procedures

Step

Procedure 12-9: Back out OC-48 UPSR to OC-192 UPSR upgrade

1

Important! This procedure starts at the last node upgraded.

Complete the following steps to back out an OC-48 UPSR to OC-192 UPSR upgrade.

.................................................................................................................................................................................................

From office records and work instructions, determine the current network configuration and status of the upgrade.

2

.................................................................................................................................................................................................

If backing out an OC-48 UPSR to OC-192 UPSR upgrade with...

LNW26B, LNW27 (pre Series 1:6),

LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, and/or

LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs originally at all nodes,

LNW27 (Series 1:6 and later),

LNW29 (Series 1:6 and later),

LNW32, LNW76 (Series 1:6 and later), and/or LNW221-259 (Series

1:6 and later) OC-48 OLIU circuit packs originally at one or more nodes,

Then proceed to and perform...

Procedure 12-9.1: “Back out OC-48 UPSR to

OC-192 UPSR upgrade (incompatible OC-48

OLIUs originally at all nodes)” (p. 12-185)

Procedure 12-9.2: “Back out OC-48 UPSR to

OC-192 UPSR upgrade (compatible OC-48

OLIUs originally at one or more nodes)”

(p. 12-195)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-184 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-9.1: Back out OC-48 UPSR to OC-192 UPSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-9: “Back out OC-48 UPSR to OC-192 UPSR upgrade”

(p. 12-182) .

Step

CAUTION

Service disruption hazard

If a node has been taken out of the Ring Upgrade mode, the node cannot be returned to the original pre-upgrade state without affecting service.

All nodes in the ring must be in the provisioned Ring Upgrade mode.

1

Important! This procedure starts at the last node upgraded.

Incompatible OC-48 OLIU circuit packs include the LNW26B, LNW27 (pre Series

1:6), LNW28, LNW29 (pre Series 1:6), LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, and LNW221-259 (pre Series 1:6) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-48 to OC-192 UPSR upgrade

(incompatible OC-48 OLIU circuit packs originally at all nodes).

.................................................................................................................................................................................................

Identify the last node that was upgraded.

If the last node upgraded is...

the starting node, and the ring upgrade is complete (all nodes are in the Ring

Upgrade mode), not the starting node,

Then...

Log in to the starting node (refer to the

“UPSR example” (p. 12-194)

at the end of the procedure) and continue with

Step 2 .

Log in to the last node upgraded (refer to the

“UPSR example” (p. 12-194)

at the end of the procedure) and proceed to

Step 12 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-185

Ring and circuit pack upgrade procedures Procedure 12-9.1: Back out OC-48 UPSR to OC-192

UPSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

2

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 10 .

Continue with

Step 3 .

3

4

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-192 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

.................................................................................................................................................................................................................................

12-186 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-9.1: Back out OC-48 UPSR to OC-192

UPSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

5

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for timing.

6

7

8

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-192 OLIU circuit pack in Main slot

M1

.

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m1-()-() paths supported by the circuit pack in Main slot

M1

(Ring

1). Record the active paths supported by the circuit pack in Main slot

M1

(Ring 1).

Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M1

. In UPSRs, each path supported by the circuit pack in Main slot

M1

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 9 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

Repeat

Step 7

for each path supported by the circuit pack in Main slot

M1

. Click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-187

Ring and circuit pack upgrade procedures Procedure 12-9.1: Back out OC-48 UPSR to OC-192

UPSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

.................................................................................................................................................................................................

9

If required, repeat

Step 6

to verify that the circuit pack in Main slot active circuit pack for transmission.

M2

is now the

10

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-192 OLIU circuit pack is backed out at each end of the optical span.

Important! At the starting node, the OC-192 OLIU circuit pack in Main slot

M1

must be first replaced with the temporary replacement OC-48 OLIU circuit pack.

The temporary replacement OC-48 OLIU circuit pack maintains traffic while backing out of the upgrade. As a final step in backing out the ring upgrade, this temporary replacement OC-48 OLIU circuit pack is replaced with the original

OC-48 OLIU circuit pack.

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M1

. Then replace the OC-192 OLIU circuit pack in Main slot

M1

with the temporary replacement OC-48 OLIU circuit pack.

Result:

A transmission hit will occur after the temporary replacement OC-48

OLIU circuit pack is inserted in the slot. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two

Main slots.

The temporary replacement OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned. Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M1

. If active through traffic exists on the circuit pack in Main slot

M1

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected circuit pack type condition and an inc.

OC48 LOS alarm for Main slot

M1

. Alarms may also be reported at other nodes in the ring.

.................................................................................................................................................................................................................................

12-188 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-9.1: Back out OC-48 UPSR to OC-192

UPSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

This completes the first phase of the back out at the starting node. The back out at the starting node will be completed after backing out of all the other nodes in the ring.

11

.................................................................................................................................................................................................

Log in to the adjacent node connected to Main slot

M1

(refer to the

“UPSR example”

(p. 12-194)

at the end of the procedure).

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

12

.................................................................................................................................................................................................

Back out the upgrade at the node using the original incompatible OC-48 OLIU circuit packs.

Reference:

Procedure 12-9.3: “Back out high-speed UPSR upgrade at node originally equipped with incompatible OC-48 OLIUs” (p. 12-204)

13

.................................................................................................................................................................................................

Except for the starting node, has the upgrade been backed out of all nodes in the

UPSR.

If...

No,

Yes,

Then...

Repeat

Step 11

and

Step 12

as required at the next node (refer to the

“UPSR example”

(p. 12-194)

at the end of the procedure).

Continue with

Step 14 .

14

15

.................................................................................................................................................................................................

Log in to the starting node (refer to the

“UPSR example” (p. 12-194)

at the end of the procedure).

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-189

Ring and circuit pack upgrade procedures Procedure 12-9.1: Back out OC-48 UPSR to OC-192

UPSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an unexpected circuit pack type condition for Main slot

M2

.

.................................................................................................................................................................................................

16

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 20 .

Continue with

Step 17 .

17

18

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-192 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

.................................................................................................................................................................................................................................

12-190 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-9.1: Back out OC-48 UPSR to OC-192

UPSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

19

.................................................................................................................................................................................................

If required, repeat

Step 17

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

20

21

22

.................................................................................................................................................................................................

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M2

. Then replace the OC-192 OLIU circuit pack in Main slot

M2

with the original OC-48 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-192 OLIU circuit pack is removed. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The system reports an unexpected CP type alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-48 circuit pack in Main slot

M2

and the required OC-48 circuit pack/port at the opposite end of the original OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-191

Ring and circuit pack upgrade procedures Procedure 12-9.1: Back out OC-48 UPSR to OC-192

UPSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

23

The original OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The system performs an automatic path protection switch, and all traffic is now active on Main slot

M2

. Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in Main slot

M1

to the circuit pack in Main slot

M2

.

The unexpected CP type alarm for Main slot

M2

clears, and the system reports an unexpected CP type alarm for Main slot

M1

.

.................................................................................................................................................................................................

Open a faceplate latch on the temporary replacement OC-48 OLIU circuit pack in

Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

. Then replace the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

with the original

OC-48 OLIU circuit pack.

Result:

The original OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

24

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-48 circuit pack in Main slot

M1

and the required OC-48 circuit pack/port at the opposite end of the original OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

.................................................................................................................................................................................................................................

12-192 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-9.1: Back out OC-48 UPSR to OC-192

UPSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

Result:

The inc. OC48 LOS alarms clear. Transmission is now supported on the original OC-48 optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

25

Important! At nodes connected to the UPSR using the Main slots, the system reports the ring upgrade mode standing condition (not alarmed) in the NE Alarm

List until the node is manually provisioned back to the Normal mode.

At nodes connected to the UPSR using the Main slots, click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the

NE Alarm List and verify that no alarms or standing conditions are present (except ring upgrade mode and

ABN condition

).

Refer to the appropriate trouble clearing procedures to clear all existing alarms and standing conditions (except ring upgrade mode and

ABN condition

) before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

26

.................................................................................................................................................................................................

Important! This completes the back out procedure, except for taking the nodes out of the Ring Upgrade mode. The decision to take the nodes out of the Ring Upgrade mode or leave them depends on the reason the back out was necessary, and what is required before again starting the upgrade. In the Ring Upgrade mode, UPSR cross-connections cannot be created or removed.

If required at each node in the UPSR, select

Configuration

→

Normal Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode will be removed from the WaveStar

®

CIT alarm list.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-193

Ring and circuit pack upgrade procedures

UPSR example

N

(Starting Node)

MAIN-1 MAIN-2

Procedure 12-9.1: Back out OC-48 UPSR to OC-192

UPSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

N+3 N+1

MAIN-2

N+2

MAIN-1 nc-dmx-255

.................................................................................................................................................................................................................................

12-194 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-9.2: Back out OC-48 UPSR to OC-192 UPSR upgrade (compatible OC-48 OLIUs originally at one or more nodes)

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-9: “Back out OC-48 UPSR to OC-192 UPSR upgrade”

(p. 12-182) .

Step

CAUTION

Service disruption hazard

If a node has been taken out of the Ring Upgrade mode, the node cannot be returned to the original pre-upgrade state without affecting service.

All nodes in the ring must be in the provisioned Ring Upgrade mode.

1

Important! This procedure starts at the last node upgraded.

Compatible OC-48 OLIU circuit packs include LNW27 (Series 1:6 and later),

LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-48 UPSR to OC-192 UPSR upgrade

(compatible OC-48 OLIU circuit packs originally at one or more nodes).

.................................................................................................................................................................................................

Identify the last node that was upgraded.

If the last node upgraded is...

the starting node, and the ring upgrade is complete (all nodes are in the Ring

Upgrade mode), not the starting node,

Then log in to the...

starting node (refer to the

“UPSR example”

(p. 12-203)

at the end of the procedure) and continue with

Step 2 .

last node upgraded (refer to the

“UPSR example” (p. 12-203)

at the end of the procedure) and proceed to

Step 12 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-195

Ring and circuit pack upgrade procedures Procedure 12-9.2: Back out OC-48 UPSR to OC-192

UPSR upgrade (compatible OC-48 OLIUs originally at one or more nodes)

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

2

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 10 .

Continue with

Step 3 .

3

4

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-192 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

.................................................................................................................................................................................................................................

12-196 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-9.2: Back out OC-48 UPSR to OC-192

UPSR upgrade (compatible OC-48 OLIUs originally at one or more nodes)

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

5

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for timing.

6

7

8

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-192 OLIU circuit pack in Main slot

M1

.

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m1-()-() paths supported by the circuit pack in Main slot

M1

(Ring

1). Record the active paths supported by the circuit pack in Main slot

M1

(Ring 1).

Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M1

. In UPSRs, each path supported by the circuit pack in Main slot

M1

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 9 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

Repeat

Step 7

for each path supported by the circuit pack in Main slot

M1

. Click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-197

Ring and circuit pack upgrade procedures Procedure 12-9.2: Back out OC-48 UPSR to OC-192

UPSR upgrade (compatible OC-48 OLIUs originally at one or more nodes)

.................................................................................................................................................................................................

9

If required, repeat

Step 6

to verify that the circuit pack in Main slot active circuit pack for transmission.

M2

is now the

10

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-192 OLIU circuit pack is backed out at each end of the optical span.

11

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M1

. Then replace the OC-192 OLIU circuit pack in Main slot

M1

with the original OC-48 OLIU circuit pack.

Result:

A transmission hit will occur after the original OC-48 OLIU circuit pack is inserted. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The original OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned. Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M1

. If active through traffic exists on the circuit pack in Main slot

M1

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected circuit pack type condition and an inc.

OC48 LOS alarm for Main slot

M1

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

This completes the first phase of the back out at the starting node. The back out at the starting node will be completed after backing out of all the other nodes in the ring.

.................................................................................................................................................................................................

Log in to the adjacent node connected to Main slot

M1

(refer to the

“UPSR example”

(p. 12-203)

at the end of the procedure).

.................................................................................................................................................................................................................................

12-198 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-9.2: Back out OC-48 UPSR to OC-192

UPSR upgrade (compatible OC-48 OLIUs originally at one or more nodes)

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

12

.................................................................................................................................................................................................

Determine how the node was originally equipped and back out the upgrade.

If the node was originally equipped with...

LNW26B, LNW27 (pre Series 1:6),

LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, and/or

LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs in the

Main slots,

LNW27 (Series 1:6 and later),

LNW29 (Series 1:6 and later),

LNW32, LNW76 (Series 1:6 and later), and/or LNW221-259 (Series

1:6 and later) OC-48 OLIU circuit packs in the Main slots,

Then back out the UPSR upgrade using ...

Procedure 12-9.3: “Back out high-speed UPSR upgrade at node originally equipped with incompatible OC-48 OLIUs” (p. 12-204) . Then

continue with

Step 13 .

Procedure 12-9.4: “Back out high-speed UPSR upgrade at node originally equipped with compatible OC-48 OLIUs” (p. 12-208) . Then

continue with

Step 13 .

13

.................................................................................................................................................................................................

Except for the starting node, has the upgrade been backed out of all nodes in the

UPSR.

If...

No,

Yes,

Then...

Repeat

Step 11

and

Step 12

as required at the next node (refer to the

“UPSR example”

(p. 12-203)

at the end of the procedure).

Continue with

Step 14 .

14

15

.................................................................................................................................................................................................

Log in to the starting node (refer to the

“UPSR example” (p. 12-203)

at the end of the procedure).

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-199

Ring and circuit pack upgrade procedures Procedure 12-9.2: Back out OC-48 UPSR to OC-192

UPSR upgrade (compatible OC-48 OLIUs originally at one or more nodes)

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an unexpected circuit pack type condition for Main slot

M2

.

.................................................................................................................................................................................................

16

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 20 .

Continue with

Step 17 .

17

18

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-192 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

.................................................................................................................................................................................................................................

12-200 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-9.2: Back out OC-48 UPSR to OC-192

UPSR upgrade (compatible OC-48 OLIUs originally at one or more nodes)

If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

19

.................................................................................................................................................................................................

If required, repeat

Step 17

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

20

21

.................................................................................................................................................................................................

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M2

. Then replace the OC-192 OLIU circuit pack in Main slot

M2

with the original OC-48 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-192 OLIU circuit pack is removed. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The original OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected circuit pack type condition for Main slot

M2

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-48 OLIU circuit pack in Main slot

M2

and the required OC-48 OLIU circuit pack/port at the opposite end of the original OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-201

Ring and circuit pack upgrade procedures Procedure 12-9.2: Back out OC-48 UPSR to OC-192

UPSR upgrade (compatible OC-48 OLIUs originally at one or more nodes)

Result:

The inc. OC48 LOS alarms clear. Transmission is now supported on the original OC-48 optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

22

Important! At nodes connected to the UPSR using the Main slots, the system reports the ring upgrade mode standing condition (not alarmed) in the NE Alarm

List until the node is manually provisioned back to the Normal mode.

At nodes connected to the UPSR using the Main slots, click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the

NE Alarm List and verify that no alarms or standing conditions are present (except ring upgrade mode and

ABN condition

).

Refer to the appropriate trouble clearing procedures to clear all existing alarms and standing conditions (except ring upgrade mode and

ABN condition

) before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

23

.................................................................................................................................................................................................

Important! This completes the back out procedure, except for taking the nodes out of the Ring Upgrade mode. The decision to take the nodes out of the Ring Upgrade mode or leave them depends on the reason the back out was necessary, and what is required before again starting the upgrade. In the Ring Upgrade mode, UPSR cross-connections cannot be created or removed.

If required at each node in the UPSR, select

Configuration

→

Normal Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode will be removed from the WaveStar

®

CIT alarm list.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

12-202 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

UPSR example

N

(Starting Node)

MAIN-1 MAIN-2

N+3 N+1

Procedure 12-9.2: Back out OC-48 UPSR to OC-192

UPSR upgrade (compatible OC-48 OLIUs originally at one or more nodes)

MAIN-2

N+2

MAIN-1 nc-dmx-255

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-203

Ring and circuit pack upgrade procedures

Procedure 12-9.3: Back out high-speed UPSR upgrade at node originally equipped with incompatible OC-48 OLIUs

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-9: “Back out OC-48 UPSR to OC-192 UPSR upgrade”

(p. 12-182) .

Step

1

Important! Incompatible OC-48 OLIU circuit packs include the LNW26B, LNW27

(pre Series 1:6), LNW28, LNW29 (pre Series 1:6), LNW76 (pre Series 1:6),

LNW77, LNW121B-159B, and LNW221-259 (pre Series 1:6) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-48 UPSR to OC-192 UPSR upgrade at a node originally equipped with incompatible OC-48 OLIU circuit packs in the Main slots.

.................................................................................................................................................................................................

Determine the current status of the upgrade at the node.

If...

both Main slots have been upgraded with OC-192 OLIU circuit packs, only Main slot

M1

has been upgraded with an OC-192 OLIU circuit pack,

Then...

Continue with

Step 2 .

Proceed to

Step 8 .

2

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

.................................................................................................................................................................................................................................

12-204 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-9.3: Back out high-speed UPSR upgrade at node originally equipped with incompatible OC-48 OLIUs

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

Continue with

Step 3 .

3

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-192 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-205

Ring and circuit pack upgrade procedures Procedure 12-9.3: Back out high-speed UPSR upgrade at node originally equipped with incompatible OC-48 OLIUs

6

7

8

.................................................................................................................................................................................................

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M2

. Then replace the OC-192 OLIU circuit pack in Main slot

M2

with the original OC-48 OLIU circuit pack.

Result:

The system reports an unexpected CP type alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-48 OLIU circuit pack in Main slot

M2

and the required OC-48 circuit pack/port at the opposite end of the original OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The original OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The system performs an automatic path protection switch, and all traffic is now active on Main slot

M2

. Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in Main slot

M1

to the circuit pack in Main slot

M2

.

The unexpected CP type alarm for Main slot

M2

clears, and the system reports an unexpected CP type alarm for Main slot

M1

.

.................................................................................................................................................................................................................................

12-206 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-9.3: Back out high-speed UPSR upgrade at node originally equipped with incompatible OC-48 OLIUs

9

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-192 OLIU circuit pack is backed out at each end of the optical span.

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M1

. Then replace the OC-192 OLIU circuit pack in Main slot

M1

with the original OC-48 OLIU circuit pack.

Result:

The original OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M1

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

STOP!

To complete backing out the UPSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-207

Ring and circuit pack upgrade procedures

Procedure 12-9.4: Back out high-speed UPSR upgrade at node originally equipped with compatible OC-48 OLIUs

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-9: “Back out OC-48 UPSR to OC-192 UPSR upgrade”

(p. 12-182) .

Step

1

Important! Compatible OC-48 OLIU circuit packs include LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-48 UPSR to OC-192 UPSR upgrade at a node originally equipped with compatible OC-48 OLIU circuit packs in the Main slots.

.................................................................................................................................................................................................

Determine the current status of the upgrade at the node.

If...

both Main slots have been upgraded with

OC-192 OLIU circuit packs, only Main slot

M1

has been upgraded with an OC-192 OLIU circuit pack,

Then...

Continue with

Step 2 .

Proceed to

Step 8 .

2

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

.................................................................................................................................................................................................................................

12-208 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-9.4: Back out high-speed UPSR upgrade at node originally equipped with compatible OC-48 OLIUs

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

Continue with

Step 3 .

3

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-192 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-209

Ring and circuit pack upgrade procedures Procedure 12-9.4: Back out high-speed UPSR upgrade at node originally equipped with compatible OC-48 OLIUs

6

7

8

.................................................................................................................................................................................................

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M2

. Then replace the OC-192 OLIU circuit pack in Main slot

M2

with the original OC-48 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-48 OLIU is inserted. The transmission hit is the result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The original OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The system reports an unexpected circuit pack type condition and an inc.

OC48 LOS alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-48 circuit pack in Main slot

M2

and the required OC-48 circuit pack/port at the opposite end of the original OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-3 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC48 LOS alarms clear. Transmission is now supported on the original OC-48 optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M2

clears, and the system reports an unexpected circuit pack type condition for Main slot

M1

.

.................................................................................................................................................................................................................................

12-210 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-9.4: Back out high-speed UPSR upgrade at node originally equipped with compatible OC-48 OLIUs

9

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 17 .

Continue with

Step 10 .

10

11

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-192 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-211

Ring and circuit pack upgrade procedures Procedure 12-9.4: Back out high-speed UPSR upgrade at node originally equipped with compatible OC-48 OLIUs

12

13

14

15

16

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 10

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits

(less than 60 ms) will occur. If desired, perform this step to determine the transmission state of the OC-192 OLIU circuit pack in Main slot

M1

.

Select

Reports

→

Path Protection List

and observe the value of the Current Role parameter for the m1-()-() paths supported by the circuit pack in Main slot

M1

(Ring

1). Record the active paths supported by the circuit pack in Main slot

M1

(Ring 1).

Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, optional manual switches can be performed before replacing the circuit pack in Main slot

M1

. In UPSRs, each path supported by the circuit pack in Main slot

M1

must be switched separately.

Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 16 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Expand Path Protection, click on the required m-1-() path and

Select

. Select the

Manual Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The system reports a manual switch condition for the affected path.

.................................................................................................................................................................................................

Repeat

Step 14

for each path supported by the circuit pack in Main slot

M1

. Click

Close

.

.................................................................................................................................................................................................

If required, repeat

Step 13

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for transmission.

.................................................................................................................................................................................................................................

12-212 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-9.4: Back out high-speed UPSR upgrade at node originally equipped with compatible OC-48 OLIUs

17

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-192 OLIU circuit pack is backed out at each end of the optical span.

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M1

. Then replace the OC-192 OLIU circuit pack in Main slot

M1

with the original OC-48 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-192 OLIU is removed. The transmission hit is the result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The original OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M1

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

STOP!

To complete backing out the UPSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-213

Ring and circuit pack upgrade procedures

Procedure 12-10: Suspend OC-48 UPSR to OC-192 UPSR upgrade

.................................................................................................................................................................................................................................

Overview

CAUTION

Service disruption hazard

If a node has been taken out of the Ring Upgrade mode, the node cannot be returned to the original pre-upgrade state without affecting service.

All nodes in the ring must be in the provisioned Ring Upgrade mode.

Use this procedure to temporarily suspend an OC-48 UPSR to OC-192 UPSR upgrade.

Suspending an upgrade in progress temporarily stops the upgrade.

To return all nodes in the ring to their pre-upgrade state, refer to

Procedure 12-9:

“Back out OC-48 UPSR to OC-192 UPSR upgrade” (p. 12-182) .

When the ring upgrade is temporarily suspended before completion, some spans are operating at the OC-48 line rate and some at the OC-192 line rate. This requires two nodes that are equipped with an OC-48 OLIU circuit pack in one Main slot and an

OC-192 OLIU circuit pack in the other Main slot. These nodes are the starting node and the last node upgraded.

To continue to operate temporarily with different circuit packs in the Main slots, the starting node and the nodes that have been upgraded must remain in the Ring Upgrade mode.

Important! Transmission hits will occur during this procedure whenever an OLIU circuit pack with a different line rate is installed or removed from a Main slot. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

Privilege level

You must log in as a Privileged user to complete this procedure.

.................................................................................................................................................................................................................................

12-214 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-10: Suspend OC-48 UPSR to OC-192

UPSR upgrade

Required equipment

The following equipment is required to perform this procedure:

•

Wrist strap

•

One original OC-48 OLIU circuit pack if the upgrade is suspended at an upgraded node originally equipped with LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and/or LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs

•

One LNW27 (Series 1:6 and later) or LNWUPG OC-48 OLIU circuit pack

(temporarily required if the upgrade is suspended at a partially upgraded node originally equipped with LNW26B, LNW27 (pre Series 1:6), LNW28, LNW29 (pre

Series 1:6), LNW76 (pre Series 1:6), LNW77, LNW121B-159B, and/or

LNW221-259 (pre Series 1:6) OC-48 OLIU circuit packs)

The LNWUPG OC-48 OLIU circuit pack is a special LNW27 OC-48 OLIU circuit pack that is intended for use only as the temporary transition circuit pack. There are no differences between the LNW27 (Series 1:6 and later) and LNWUPG circuit packs with respect to in-service backouts/suspends.

The LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and/or

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs may also be used as the temporary replacement circuit packs. However, the temporary replacement circuit packs must have compatible optics. For example, do not replace a circuit pack that has long range optics with a circuit pack that has intermediate reach optics. Refer to the Metropolis

®

DMX Access Multiplexer Applications and

Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48

OLIU circuit packs.

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-215

Ring and circuit pack upgrade procedures Procedure 12-10: Suspend OC-48 UPSR to OC-192

UPSR upgrade

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this suspend procedure.

Step

1

Important! This procedure starts at the last node upgraded.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to temporarily suspend an OC-48 UPSR to OC-192

UPSR upgrade.

.................................................................................................................................................................................................

Identify the last node that was upgraded.

If...

both Main slots have been upgraded, one Main slot has been upgraded and the node was originally equipped with

LNW26B, LNW27 (pre Series 1:6),

LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, and/or LNW221-259

(pre Series 1:6) OC-48 OLIU circuit packs one Main slot has been upgraded and the node was originally equipped with

LNW27 (Series 1:6 and later), LNW29

(Series 1:6 and later), LNW32, LNW76

(Series 1:6 and later), and/or

LNW221-259 (Series 1:6 and later)

OC-48 OLIU circuit packs

Then log in to the...

last node upgraded (refer to the

“UPSR example” (p. 12-222)

at the end of the procedure) and continue with

Step 2 .

last node upgraded (refer to the

example” (p. 12-222)

at the end of the procedure) and proceed to

Step 8

“UPSR

.

last node upgraded (refer to the

“UPSR example” (p. 12-222)

at the end of the procedure) and proceed to

Step 11 .

.................................................................................................................................................................................................................................

12-216 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-10: Suspend OC-48 UPSR to OC-192

UPSR upgrade

2

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! Both Main slots have been upgraded, and the

Configuration

→

Update System

→

Update All

command has been performed. All traffic is now active on Main slot

M1

, and the system is reporting an inc. OC192 LOS alarm for

Main slot

M2

.

Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

Continue with

Step 3 .

3

4

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-192 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-217

Ring and circuit pack upgrade procedures Procedure 12-10: Suspend OC-48 UPSR to OC-192

UPSR upgrade

5

6

If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M2

.

If the Main slots were originally equipped with...

LNW26B, LNW27 (pre Series 1:6),

LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, or LNW221-259 (pre

Series 1:6) OC-48 OLIUs,

LNW27 (Series 1:6 and later), LNW29

(Series 1:6 and later), LNW32, LNW76

(Series 1:6 and later), or LNW221-259

(Series 1:6 and later) OC-48 OLIUs,

Then replace the OC-192 OLIU circuit pack in Main slot M2 with...

the temporary replacement OC-48 OLIU circuit pack.

the original OC-48 OLIU circuit pack

Result:

The OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The inc. OC192 LOS alarm for Main slot

M2

clears. The system reports an unexpected circuit pack type condition and an inc. OC48 LOS alarm for Main slot

M2

.

.................................................................................................................................................................................................................................

12-218 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-10: Suspend OC-48 UPSR to OC-192

UPSR upgrade

7

8

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span, perform the following to connect the OC-48 OLIU circuit pack in Main slot

M2

and the required OC-48 circuit pack/port at the opposite end of the OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC48 LOS alarm for Main slot

M2

clears, and the system still reports an unexpected circuit pack type condition for Main slot

M2

.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

STOP!

End of Procedure. The upgrade procedure is now temporarily suspended and traffic is supported to the adjacent nodes.

To resume the upgrade, replace the OC-48 OLIU circuit pack in Main slot

M2

with the OC-192 OLIU circuit pack. Refer to

Procedure 12-8: “Upgrade OC-48 UPSR to

OC-192 UPSR” (p. 12-144) .

To back out the upgrade, refer to

Procedure 12-9: “Back out OC-48 UPSR to

OC-192 UPSR upgrade” (p. 12-182) .

.................................................................................................................................................................................................

Important! Main slot

M1

has been upgraded and the node was originally equipped with LNW26B, LNW27 (pre Series 1:6), LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77, LNW121B-159B, and/or LNW221-259 (pre

Series 1:6) OC-48 OLIU circuit packs.

If an unexpected CP type alarm is reported for Main slot

M1

, select

Configuration

→

Update System

→

Update All

, then select

main-1

(default) as the Ring Upgrade

Choice and click

OK

. Otherwise, proceed to the next step.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The OC-192 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system performs an automatic path protection switch, and all traffic is now active on Main slot

M1

. Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in the Main slot

M2

to the circuit pack in Main slot

M1

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-219

Ring and circuit pack upgrade procedures

9

10

Procedure 12-10: Suspend OC-48 UPSR to OC-192

UPSR upgrade

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an unexpected CP type alarm for Main slot

M2

.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the temporary replacement OC-48 OLIU circuit pack.

Result:

The temporary replacement OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M2

clears. The system reports an unexpected circuit pack type condition and an inc. OC48 LOS alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span, perform the following to connect the temporary replacement OC-48 OLIU circuit pack in Main slot

M2

and the required OC-48 circuit pack/port at the opposite end of the OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC48 LOS alarm for Main slot

M2

clears, and the system still reports an unexpected circuit pack type condition for Main slot

M2

.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

STOP!

End of Procedure. The upgrade procedure is now temporarily suspended and traffic is supported to the adjacent nodes.

To resume the upgrade, replace the OC-48 OLIU circuit pack in Main slot

M2

with the OC-192 OLIU circuit pack. Refer to

Procedure 12-8: “Upgrade OC-48 UPSR to

OC-192 UPSR” (p. 12-144) .

To back out the upgrade, refer to

Procedure 12-9: “Back out OC-48 UPSR to

OC-192 UPSR upgrade” (p. 12-182) .

.................................................................................................................................................................................................................................

12-220 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

11

Procedure 12-10: Suspend OC-48 UPSR to OC-192

UPSR upgrade

.................................................................................................................................................................................................

Important! Main slot

M1

has been upgraded and the node was originally equipped with LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32,

LNW76 (Series 1:6 and later), and/or LNW221-259 (Series 1:6 and later) OC-48

OLIU circuit packs.

If an unexpected circuit pack type condition is reported for Main slot

M1

, select

Configuration

→

Update System

→

Update All

, then select

main-1

(default) as the

Ring Upgrade Choice and click

OK

. Otherwise, the node is already in the proper suspend configuration and no further action is required.

Result:

Click

Yes

.

A dialog box appears asking you to confirm executing this command.

The OC-192 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an unexpected circuit pack type condition for Main slot

M2

.

STOP!

End of Procedure. The upgrade procedure is now temporarily suspended and traffic is supported to the adjacent nodes.

To resume the upgrade, replace the OC-48 OLIU circuit pack in Main slot

M2

with the OC-192 OLIU circuit pack. Refer to

Procedure 12-8: “Upgrade OC-48 UPSR to

OC-192 UPSR” (p. 12-144) .

To back out the upgrade, refer to

Procedure 12-9: “Back out OC-48 UPSR to

OC-192 UPSR upgrade” (p. 12-182) .

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-221

Ring and circuit pack upgrade procedures

UPSR example

N

(Starting Node)

MAIN-1 MAIN-2

N+3 N+1

Procedure 12-10: Suspend OC-48 UPSR to OC-192

UPSR upgrade

MAIN-2

N+2

MAIN-1 nc-dmx-255

.................................................................................................................................................................................................................................

12-222 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-11: Upgrade OC-48 BLSR to OC-192 BLSR

.................................................................................................................................................................................................................................

Overview

Important! The BLSR must be equipped with Metropolis

®

DMX nodes only. This upgrade procedure does not support upgrading BLSRs equipped with nodes other than Metropolis

®

DMX.

Use this procedure to upgrade an in-service OC-48 BLSR with:

•

LNW26B, LNW27 (pre Series 1:6), LNW28, LNW29 (pre Series 1:6), LNW76

(pre Series 1:6), LNW77, LNW121B-159B, and/or LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs at all nodes to an OC-192 BLSR.

These OC-48 OLIU circuit packs have different optics and transmit at different wavelengths. However, these circuit packs have the same circuit pack type and a small VT cross-connection fabric. There are no differences between these circuit packs for the purposes of ring upgrades.

These OC-48 OLIU circuit packs and the OC-192 OLIU circuit packs have

incompatible VT cross-connection fabrics.

•

LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76

(Series 1:6 and later), and/or LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs at one or more nodes to an OC-192 BLSR.

These OC-48 OLIU circuit packs have different optics and transmit at different wavelengths. However, these circuit packs have the same circuit pack type and a large VT cross-connection fabric. There are no differences between these circuit packs for the purposes of ring upgrades.

These OC-48 OLIU circuit packs and the OC-192 OLIU circuit packs have

compatible VT cross-connection fabrics.

The OC-48 OLIU circuit packs in the Main slots are upgraded at each node.

Low-speed OC-48 BLSR upgrades are not supported in this release.

This procedure assumes that in the BLSR, the circuit pack in the Main slot

M1

is always connected to the circuit pack in the Main slot

M2

of the adjacent node.

Important! Transmission hits will occur during this procedure whenever an OLIU circuit pack with a different line rate is installed or removed from a Main slot. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

Privilege level

You must log in as a Privileged user to complete this procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-223

Ring and circuit pack upgrade procedures Procedure 12-11: Upgrade OC-48 BLSR to OC-192 BLSR

Required equipment

The following equipment is required to perform this procedure:

•

Optical power meter

•

Wrist strap

•

As optical spans are upgraded around the BLSR, ensure that technicians are available at each end of an optical span as it is upgraded.

•

If the first node to be upgraded is equipped with LNW27 (pre Series 1:6), LNW29

(pre Series 1:6), LNW76 (pre Series 1:6), and/or LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs, 1 Series 1:6 or later version of the same OC-48 OLIU circuit pack type is temporarily required. For example if the first node to be upgraded is equipped with pre Series 1:6 LNW27 OC-48 OLIU circuit packs, then

1 Series 1:6 or later LNW27 OC-48 OLIU circuit pack is temporarily required.

•

If the first node to be upgraded is equipped with LNW26B, LNW28, LNW77, and/or LNW121B-159B OC-48 OLIU circuit packs, 1 LNW27 (Series 1:6 and later) or LNWUPG OC-48 OLIU circuit pack is temporarily required.

The LNWUPG OC-48 OLIU circuit pack is a special LNW27 OC-48 OLIU circuit pack that is intended for use only as the temporary transition circuit pack. There are no differences between the LNW27 (Series 1:6 and later) and LNWUPG circuit packs with respect to in-service upgrades.

An LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and/or

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit pack may also be used as the temporary replacement circuit pack. However, the temporary replacement circuit pack must have compatible optics. For example, do not replace a circuit pack that has long reach optics with a circuit pack that has intermediate reach optics. Refer to the Metropolis

®

DMX Access Multiplexer Applications and Planning Guide,

365-372-300 for the SONET optical specifications of the OC-48 OLIU circuit packs.

•

2 replacement LNW56, LNW57, LNW58, LNW60, LNW523, LNW527, LNW554, or LNW555 OC-192 OLIU circuit packs for each node.

The replacement circuit packs must have compatible optics. For example, do not replace a circuit pack that has long reach optics with a circuit pack that has intermediate reach optics. Refer to the Metropolis

®

DMX Access Multiplexer

Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-192 OLIU circuit packs.

Important! Release 3.0 or later software is required to support the OC-192 OLIU circuit packs.

Release 3.0 or later software is required to support LNW555 OC-192 OLIU circuit packs.

Release 4.0 or later software is required to support LNW57, LNW523, LNW527, and LNW554 OC-192 OLIU circuit packs.

.................................................................................................................................................................................................................................

12-224 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11: Upgrade OC-48 BLSR to OC-192 BLSR

Release 5.1 or later software is required to support LNW60 OC-192 OLIU circuit packs.

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Obtain the work instructions for this procedure.

3. Review the applicable office records and verify that each fiber span in the BLSR is capable of supporting higher rate (OC-192) traffic. Verify that the fiber span does not exceed 40 kilometers. Refer to the Metropolis

®

DMX Access Multiplexer

Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-192 OLIU circuit packs.

4. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this upgrade procedure.

Step

1

Complete the following steps to upgrade an in-service OC-48 BLSR to an OC-192

BLSR.

.................................................................................................................................................................................................

From office records and work instructions, determine the current network configuration.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-225

Ring and circuit pack upgrade procedures Procedure 12-11: Upgrade OC-48 BLSR to OC-192 BLSR

2

3

4

5

6

.................................................................................................................................................................................................

Log in to a node in the BLSR to be upgraded.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Select

View

→

Rings

→

Ring Map

. Click on required Ring ID and

Select

. Click

View

Graphic

and observe the ring map diagram. Note how the nodes are connected in the ring and make a drawing of the ring map diagram to reference during this upgrade procedure.

.................................................................................................................................................................................................

Click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the NE Alarm List and verify that no alarms are present.

Refer to the appropriate trouble clearing procedures to clear all existing alarms before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

To verify that no loopbacks, protection switch lockouts, or protection switches are present, select

View

→

Rolling Events

. Under the line reading

RTRV-COND-ALL determine if any loopbacks, protection switch lockouts, or protection switches are displayed.

Remove all existing loopbacks, protection switch lockouts, or protection switches before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and verify that no test access sessions exist.

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and delete all existing test access sessions.

Reference:

•

Procedure 14-27: “View test access session(s)” (p. 14-130)

•

Procedure 14-26: “Delete test access session” (p. 14-129)

.................................................................................................................................................................................................................................

12-226 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11: Upgrade OC-48 BLSR to OC-192 BLSR

7

8

9

.................................................................................................................................................................................................

If Ethernet service is provisioned with spanning tree protection, verify that the spanning tree states are correct by selecting

View

→

Data

→

Spanning Tree Group

.

Expand the required circuit pack, select the appropriate spanning tree and click

Select

.

Observe the VCG Status. All VCGs should be forwarding (FWG) packets, except for one VCG that should be discarding (DCD) packets. If this is not the case, contact

Technical Support Services (TSS) for assistance in correcting the spanning tree states before continuing with this procedure.

.................................................................................................................................................................................................

Select

View

→

Protection

. Click on 2F BLSR main-1-1 and

Select

. Click on the

Provisionable Parameters tab and observe the Automatic Ring Discovery parameter.

.................................................................................................................................................................................................

Is the Automatic Ring Discovery parameter Enabled or Disabled?

If Automatic Ring Discovery is...

Disabled,

Enabled,

Then...

click

Close

and continue with

Step 10 .

click

Close

and perform the following:

1. Select

Configuration

→

Equipment

.

2. Select the

Ptn Grp

tab and the 2F BLSR main-1-1 protection group. Then click

Select

.

3. Provision the Automatic Ring Discovery parameter to Disabled and click

Apply

. Then click

Close

.

10

.................................................................................................................................................................................................

At each of the remaining nodes in the BLSR, log in to the node and repeat

Step 3

through

Step 9 . Then continue with the next step.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-227

Ring and circuit pack upgrade procedures Procedure 12-11: Upgrade OC-48 BLSR to OC-192 BLSR

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

11

If upgrading OC-48 BLSR with...

Then...

LNW27 (pre Series 1:6), LNW29

(pre Series 1:6), LNW76 (pre

Series 1:6), and/or LNW221-259

(pre Series 1:6) OC-48 OLIU circuit packs at all nodes to an

OC-192 UPSR,

Proceed to and perform the following:

1.

Procedure 12-11.5: “Replace pre Series 1:6

LNW27, 29, 76, 221-259 OC-48 OLIU at first node to be upgraded” (p. 12-258)

2.

Procedure 12-11.2: “Upgrade OC-48 BLSR

(compatible OC-48 OLIUs at one or more nodes) to OC-192 BLSR” (p. 12-238)

Procedure 12-11.1: “Upgrade OC-48 BLSR

(incompatible OC-48 OLIUs at all nodes) to

OC-192 BLSR” (p. 12-229)

LNW26B, LNW27 (pre Series 1:6),

LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, and/or

LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs at all nodes to an OC-192 BLSR,

LNW27 (Series 1:6 and later),

LNW29 (Series 1:6 and later),

LNW32, LNW76 (Series 1:6 and later), and/or LNW221-259 (Series

1:6 and later) OC-48 OLIU circuit packs at one or more nodes to an

OC-192 BLSR,

Procedure 12-11.2: “Upgrade OC-48 BLSR

(compatible OC-48 OLIUs at one or more nodes) to OC-192 BLSR” (p. 12-238)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-228 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-11.1: Upgrade OC-48 BLSR (incompatible OC-48

OLIUs at all nodes) to OC-192 BLSR

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-11: “Upgrade OC-48 BLSR to OC-192 BLSR”

(p. 12-223) .

Step

1

2

Important! Incompatible OC-48 OLIU circuit packs include the LNW26B, LNW27

(pre Series 1:6), LNW28, LNW29 (pre Series 1:6), LNW76 (pre Series 1:6),

LNW77, LNW121B-159B, and LNW221-259 (pre Series 1:6) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade an in-service OC-48 BLSR (equipped with incompatible OC-48 OLIU circuit packs at all nodes) to an OC-192 BLSR.

.................................................................................................................................................................................................

Important! The starting node must be equipped with LNW26B, LNW28, LNW32,

LNW77, or LNW121B-159B OC-48 OLIU circuit packs in the Main slots.

Identify and log in to the starting node (refer to the

“BLSR example” (p. 12-237)

at the end of the procedure). Verify that the Main slots are equipped with LNW26B,

LNW28, LNW32, LNW77, or LNW121B-159B OC-48 OLIU circuit packs using

Reports

→

Equipment Lists

→

Packs

. Click Shelf and

Select

. Observe the

Apparatus Code of the main-1 and main-2 circuit packs. Click

Close

.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The Ring Upgrade mode allows cross-connections/ data to be mapped to the new circuit pack and prohibits provisioning new cross-connections.

At the starting node, select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

CIT alarm list shows that the shelf is in the Ring Upgrade mode.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-229

Ring and circuit pack upgrade procedures Procedure 12-11.1: Upgrade OC-48 BLSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 BLSR

3

The node remains in the Ring Upgrade mode until manually provisioned back to the Normal mode. While in the Ring Upgrade mode, the upgrade may be temporarily suspended or backed out. To prevent errors in the upgraded ring, keep all nodes in Ring Upgrade mode until all nodes have been upgraded.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 9 .

Continue with

Step 4 .

.................................................................................................................................................................................................

4

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than 60 ms) will occur. If desired, perform this step to determine the transmission and timing state of the OC-48 OLIU circuit pack in

Main slot

M1

.

From the System View select

Reports

→

Status Lists

→

Pack

. Click Shelf and

Select

. Observe the value of the Switch State parameter for the main-1 circuit pack. If the Switch State parameter is ACTIVE-TIMING, all Function units are selecting timing from the main-1 circuit pack, and some Function units are receiving traffic from the

main-1 circuit pack. If the Switch State parameter is ACTIVE, some Function units are receiving traffic from the main-1 circuit pack. Click

Close

.

.................................................................................................................................................................................................

5

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be

.................................................................................................................................................................................................................................

12-230 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11.1: Upgrade OC-48 BLSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 BLSR

6

7

8

9

performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 4

to determine the transmission and timing state of the OC-48

OLIU circuit pack in Main slot

M1

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, an optional manual switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 8 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Click on 2F BLSR main-1-1 and

Select

. Select the West Direction and Manual to

Protection, Ring Switch Type, and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and

Close

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the Alarm List shows the

Protection Switch, OC48 Port, Manual Switch, MSR, 2F condition (Not Alarmed).

.................................................................................................................................................................................................

If required, repeat

Step 4

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for transmission.

.................................................................................................................................................................................................

Important! At the starting node, the OC-48 OLIU circuit pack in Main slot

M1

must be first replaced with the temporary replacement OC-48 OLIU circuit pack.

(Refer to

“Required equipment” (p. 12-224)

for a list of acceptable temporary replacement OC-48 OLIU circuit packs.) The temporary replacement OC-48 OLIU circuit pack maintains traffic with the last node to be upgraded while Main slot

M2

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-231

Ring and circuit pack upgrade procedures Procedure 12-11.1: Upgrade OC-48 BLSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 BLSR

10

and the other nodes in the ring are upgraded. As a final step, this temporary replacement OC-48 OLIU circuit pack is upgraded.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the temporary replacement OC-48 OLIU circuit pack.

Result:

Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M1

. If active through traffic exists on the circuit pack in Main slot

M1

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected CP type alarm and a

Line Automatic Switch condition for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

and the required

OC-48 circuit pack/port at the opposite end of the OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

11

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The temporary replacement OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system performs an automatic protection switch, and all traffic is now active on Main slot

M1

. Transmission hits (less than 60 ms) occur as traffic switches from the circuit pack in Main slot

M2

to the circuit pack in Main slot

M1

.

.................................................................................................................................................................................................................................

12-232 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

12

Procedure 12-11.1: Upgrade OC-48 BLSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 BLSR

The unexpected CP type alarm and

Line Automatic Switch condition for Main slot

M1

clear. The system reports an unexpected CP type alarm and a

Line

Automatic Switch condition for Main slot

M2

.

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-48 OLIU circuit pack is upgraded at each end of the optical span.

13

14

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the replacement OC-192 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-192 OLIU is inserted. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The replacement OC-192 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The system reports an unexpected circuit pack type condition and an inc.

OC192 LOS

Switch alarm for Main slot condition for Main slot

M2

M2

. The system also reports a

Line Automatic

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

This completes the first phase of the upgrade at the starting node. The starting node upgrade will be completed after all the other nodes in the ring are upgraded.

.................................................................................................................................................................................................

Log in to the adjacent node connected to Main slot

M2

(refer to the

“BLSR example”

(p. 12-237)

at the end of the procedure).

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Upgrade the incompatible OC-48 OLIU circuit packs in the Main slots.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-233

Ring and circuit pack upgrade procedures Procedure 12-11.1: Upgrade OC-48 BLSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 BLSR

15

Reference:

Procedure 12-11.3: “Upgrade high-speed BLSR connections at node equipped with incompatible OC-48 OLIUs” (p. 12-248)

.................................................................................................................................................................................................

Except for the starting node, have all nodes in the BLSR been upgraded.

If...

No,

Yes,

Then...

Repeat

Step 13

and

Step 14

as required at the next node (refer to the

“BLSR example”

(p. 12-237)

at the end of the procedure).

Continue with

Step 16 .

16

17

.................................................................................................................................................................................................

Log in to the starting node (refer to the

“BLSR example” (p. 12-237)

at the end of the procedure).

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Open a faceplate latch on the temporary replacement OC-48 OLIU circuit pack in

Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

. Then replace the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

with the replacement

OC-192 OLIU circuit pack.

Result:

A transmission hit will occur after the temporary replacement OC-48

OLIU circuit pack is removed. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The replacement OC-192 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system reports an unexpected circuit pack type condition for Main slots

M1

and

M2

. The system also reports an inc. OC192 LOS alarm for Main slot

M1

.

.................................................................................................................................................................................................................................

12-234 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11.1: Upgrade OC-48 BLSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 BLSR

18

19

20

21

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the replacement OC-192 OLIU circuit pack in Main slot

M1

and the required OC-192 circuit pack/port at the opposite end of the upgraded OC-192 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-192 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC192 LOS alarms clear. Transmission is now supported on the upgraded optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View, select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slots

M1

and

M2

clears.

.................................................................................................................................................................................................

Important! All BLSR protection switches in the ring must be cleared before any nodes are taken out of the Ring Upgrade mode.

At each node in the BLSR, clear the BLSR protection switches. Select

Fault

→

Protection Switch

. Click on 2F BLSR main-1-1 and

Select

. Select the required

Direction and Clear Switch Type, and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and

Close

.

.................................................................................................................................................................................................

Important! At each node in the BLSR, the system reports the ring upgrade mode standing condition (not alarmed) in the NE Alarm List until the node is manually provisioned back to the Normal mode.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-235

Ring and circuit pack upgrade procedures Procedure 12-11.1: Upgrade OC-48 BLSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 BLSR

At each node in the BLSR, click the

Alarm List

button in the top right corner of the

System View or select

Fault

→

NE Alarm List

to view the NE Alarm List and verify that no alarms or standing conditions are present (except ring upgrade mode and

ABN condition

).

Refer to the appropriate trouble clearing procedures to clear all existing alarms and standing conditions (except ring upgrade mode and

ABN condition

) before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

22

Important! The BLSR network must be alarm free with normal transmission before manually provisioning the nodes back to the Normal mode. After a node is manually provisioned back to the Normal mode, the node can not be returned to the pre-upgrade state using the back out procedure.

At each node in the BLSR, select

Configuration

→

Normal Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode will be removed from the WaveStar

®

CIT alarm list.

.................................................................................................................................................................................................

23

If Automatic Ring

Discovery was...

Disabled,

Then...

not Disabled,

Perform the following to enable Automatic Ring Discovery.

1. Select

Configuration

→

Equipment

.

2. Select the

Ptn Grp

tab and the 2F BLSR main-1-1 protection group. Then click

Select

.

3. Provision the Automatic Ring Discovery parameter to

Enabled and click

Apply

. Then click

Close

.

Repeat this step to enable Automatic Ring Discovery at each node in the BLSR.

Continue with

Step 24 .

24

.................................................................................................................................................................................................

Important! It is recommended that the network element database be backed up to a remote OS (for example, the Navis

®

Optical Element Management System) after an upgrade. This creates a current backup copy that includes the replacement circuit packs. The remote OS could use this backup copy to restore the network element

.................................................................................................................................................................................................................................

12-236 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11.1: Upgrade OC-48 BLSR (incompatible

OC-48 OLIUs at all nodes) to OC-192 BLSR database in the event of a catastrophic failure. Attempts to restore the network element database using a backup copy created prior to the upgrade may result in circuit pack failures.

At each node in the BLSR, back up the network element database using the

Configuration

→

Software

→

Remote Backup

command.

Reference:

•

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123)

•

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135)

•

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150)

E

N D O F

S

T E P S

BLSR example

Starting Node

: Metropolis

®

DMX Node N

Starting Circuit Pack

: Main-2 at the Starting Node (a temporary replacement OC-48 circuit pack must be installed in Main-1)

Direction of Upgrade

: Clockwise around BLSR from Main-2 at the Starting Node to

Main/Function/Growth slot 1 at the adjacent node

N

(Starting Node)

West East

MAIN-1 MAIN-2

East

N+3

West

West

N+1

East

MAIN-2 MAIN-1

East

N+2

West nc-dmx-256

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-237

Ring and circuit pack upgrade procedures

Procedure 12-11.2: Upgrade OC-48 BLSR (compatible OC-48

OLIUs at one or more nodes) to OC-192 BLSR

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-11: “Upgrade OC-48 BLSR to OC-192 BLSR”

(p. 12-223) .

Step

1

2

Important! Compatible OC-48 OLIU circuit packs include LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade an in-service OC-48 BLSR (equipped with compatible OC-48 OLIU circuit packs at one or more nodes) to an OC-192 BLSR.

.................................................................................................................................................................................................

Important! The starting node must be equipped with LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), or

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs in the Main slots.

Identify and log in to the starting node (refer to the

“BLSR example” (p. 12-247)

at the end of the procedure). Verify that the Main slots are equipped with compatible

OC-48 OLIU circuit packs using

Reports

→

Equipment Lists

→

Packs

. Click Shelf and

Select

. Observe the Apparatus Code of the main-1 and main-2 circuit packs. Click

Close

.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The Ring Upgrade mode allows cross-connections/ data to be mapped to the new circuit pack and prohibits provisioning new cross-connections.

At the starting node, select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

CIT alarm list shows that the shelf is in the Ring Upgrade mode.

.................................................................................................................................................................................................................................

12-238 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11.2: Upgrade OC-48 BLSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 BLSR

3

The node remains in the Ring Upgrade mode until manually provisioned back to the Normal mode. While in the Ring Upgrade mode, the upgrade may be temporarily suspended or backed out. To prevent errors in the upgraded ring, keep all nodes in Ring Upgrade mode until all nodes have been upgraded.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 9 .

Continue with

Step 4 .

.................................................................................................................................................................................................

4

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for transmission and timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than 60 ms) will occur. If desired, perform this step to determine the transmission and timing state of the OC-48 OLIU circuit pack in

Main slot

M2

.

From the System View select

Reports

→

Status Lists

→

Pack

. Click on Shelf and

Select

. Observe the value of the Switch State parameter for the main-2 circuit pack. If the Switch State parameter is ACTIVE-TIMING, all Function units are selecting timing from the main-2 circuit pack, and some Function units are receiving traffic from the

main-2 circuit pack. If the Switch State parameter is ACTIVE, some Function units are receiving traffic from the main-2 circuit pack. Click

Close

.

.................................................................................................................................................................................................

5

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-239

Ring and circuit pack upgrade procedures Procedure 12-11.2: Upgrade OC-48 BLSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 BLSR

6

7

8

performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 4

to determine the transmission and timing state of the OC-48

OLIU circuit pack in Main slot

M2

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is an active circuit pack for transmission, an optional manual switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is not the active circuit pack for transmission, proceed to

Step 8 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Click on 2F BLSR main-1-1 and

Select

. Select the East Direction and Manual to

Protection, Ring Switch Type, and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and

Close

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the Alarm List shows the

Protection Switch, OC48 Port, Manual Switch, MSR, 2F condition (Not Alarmed).

.................................................................................................................................................................................................

If required, repeat

Step 4

to verify that the OC-48 OLIU circuit pack in Main slot

M1

is now the active circuit pack for transmission.

.................................................................................................................................................................................................................................

12-240 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11.2: Upgrade OC-48 BLSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 BLSR

9

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-48 OLIU circuit pack is upgraded at each end of the optical span.

10

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the replacement OC-192 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-192 OLIU circuit pack is inserted. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The replacement OC-192 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned. Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M2

. If active through traffic exists on the circuit pack in Main slot

M2

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected circuit pack type condition and an inc.

OC192 LOS

Switch alarm for Main slot condition for Main slot

M2

M2

. The system also reports a

Line Automatic

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

This completes the first phase of the upgrade at the starting node. The starting node upgrade will be completed after all the other nodes in the ring are upgraded.

.................................................................................................................................................................................................

Log in to the adjacent node connected to Main slot

M2

(refer to the

“BLSR example”

(p. 12-247)

at the end of the procedure).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-241

Ring and circuit pack upgrade procedures Procedure 12-11.2: Upgrade OC-48 BLSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 BLSR

11

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Determine the type of OC-48 OLIU circuit packs in the Main slots, and then upgrade the node.

If the node is equipped with...

LNW26B, LNW27 (pre Series 1:6),

LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, and/or

LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs in the

Main slots,

LNW27 (Series 1:6 and later),

LNW29 (Series 1:6 and later),

LNW32, LNW76 (Series 1:6 and later), and/or LNW221-259 (Series

1:6 and later) OC-48 OLIU circuit packs in the Main slots,

Then upgrade the high-speed BLSR connections using...

Procedure 12-11.3: “Upgrade high-speed BLSR connections at node equipped with incompatible

OC-48 OLIUs” (p. 12-248)

Step 12 .

. Then continue with

Procedure 12-11.4: “Upgrade high-speed BLSR connections at node equipped with compatible

OC-48 OLIUs” (p. 12-252) . Then continue with

Step 12 .

12

.................................................................................................................................................................................................

Except for the starting node, have all nodes in the BLSR been upgraded.

If...

No,

Yes,

Then...

Repeat

Step 10

and

Step 11

as required at the next node (refer to the

“BLSR example”

(p. 12-247)

at the end of the procedure).

Continue with

Step 13 .

13

.................................................................................................................................................................................................

Log in to the starting node (refer to the

“BLSR example” (p. 12-247)

at the end of the procedure).

.................................................................................................................................................................................................................................

12-242 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11.2: Upgrade OC-48 BLSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 BLSR

14

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 18 .

Continue with

Step 15 .

15

16

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-243

Ring and circuit pack upgrade procedures

17

18

19

Procedure 12-11.2: Upgrade OC-48 BLSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 BLSR

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 15

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the replacement OC-192 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-48 OLIU circuit pack is removed. The transmission hit is the result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The replacement OC-192 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system reports an unexpected circuit pack type condition for Main slots

M1

and

M2

. The system also reports an inc. OC192 LOS alarm and a

Line

Automatic Switch condition for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the replacement OC-192 OLIU circuit pack in Main slot

M1

and the required OC-192 circuit pack/port at the opposite end of the upgraded OC-192 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-192 circuit packs.)

3. Clean and connect the receive fibers.

.................................................................................................................................................................................................................................

12-244 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

20

21

22

23

Procedure 12-11.2: Upgrade OC-48 BLSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 BLSR

Result:

The inc. OC192 LOS alarms and

Line Automatic Switch conditions clear. Transmission is now supported on the upgraded optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View, select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slots

M1

and

M2

clears.

.................................................................................................................................................................................................

Important! All BLSR protection switches in the ring must be cleared before any nodes are taken out of the Ring Upgrade mode.

At each node in the BLSR, clear the BLSR protection switches. Select

Fault

→

Protection Switch

. Click on 2F BLSR main-1-1 and

Select

. Select the required

Direction and Clear Switch Type, and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and

Close

.

.................................................................................................................................................................................................

Important! At each node in the BLSR, the system reports the ring upgrade mode standing condition (not alarmed) in the NE Alarm List until the node is manually provisioned back to the Normal mode.

At each node in the BLSR, click the

Alarm List

button in the top right corner of the

System View or select

Fault

→

NE Alarm List

to view the NE Alarm List and verify that no alarms or standing conditions are present (except ring upgrade mode and

ABN condition

).

Refer to the appropriate trouble clearing procedures to clear all existing alarms and standing conditions (except ring upgrade mode and

ABN condition

) before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Important! The BLSR network must be alarm free with normal transmission before manually provisioning the nodes back to the Normal mode. After a node is

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-245

Ring and circuit pack upgrade procedures Procedure 12-11.2: Upgrade OC-48 BLSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 BLSR manually provisioned back to the Normal mode, the node can not be returned to the pre-upgrade state using the back out procedure.

At each node in the BLSR, select

Configuration

→

Normal Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode will be removed from the WaveStar

®

CIT alarm list.

.................................................................................................................................................................................................

24 If Automatic Ring Discovery was...

Disabled,

Then...

not Disabled,

Perform the following to enable Automatic Ring

Discovery at a node.

1. Select

Configuration

→

Equipment

.

2. Select the

Ptn Grp

tab and the 2F BLSR main-1-1 protection group. Then click

Select

.

3. Provision the Automatic Ring Discovery parameter to Enabled and click

Apply

. Then click

Close

.

Repeat this step to enable Automatic Ring Discovery at each node in the BLSR.

Continue with

Step 25 .

25

.................................................................................................................................................................................................

Important! It is recommended that the network element database be backed up to a remote OS (for example, the Navis

®

Optical Element Management System) after an upgrade. This creates a current backup copy that includes the replacement circuit packs. The remote OS could use this backup copy to restore the network element database in the event of a catastrophic failure. Attempts to restore the network element database using a backup copy created prior to the upgrade may result in circuit pack failures.

At each node in the BLSR, back up the network element database using the

Configuration

→

Software

→

Remote Backup

command.

Reference:

•

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123)

•

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135)

•

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150)

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

12-246 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11.2: Upgrade OC-48 BLSR (compatible

OC-48 OLIUs at one or more nodes) to OC-192 BLSR

BLSR example

Starting Node

: Metropolis

®

DMX Node N

Starting Circuit Pack

: Main-2 at the Starting Node

Direction of Upgrade

: Clockwise around BLSR from Main-2 at the Starting Node to

Main/Function/Growth slot 1 at the adjacent node

N

(Starting Node)

West East

MAIN-1 MAIN-2

East

N+3

West

West

N+1

East

MAIN-2 MAIN-1

East

N+2

West nc-dmx-256

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-247

Ring and circuit pack upgrade procedures

Procedure 12-11.3: Upgrade high-speed BLSR connections at node equipped with incompatible OC-48 OLIUs

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-11: “Upgrade OC-48 BLSR to OC-192 BLSR”

(p. 12-223) .

Step

1

2

Important! Incompatible OC-48 OLIU circuit packs include the LNW26B, LNW27

(pre Series 1:6), LNW28, LNW29 (pre Series 1:6), LNW76 (pre Series 1:6),

LNW77, LNW121B-159B, and LNW221-259 (pre Series 1:6) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade the in-service high-speed BLSR connections at a node equipped with incompatible OC-48 OLIU circuit packs in the Main slots.

.................................................................................................................................................................................................

Important! The Ring Upgrade mode allows cross-connections/ data to be mapped to the new circuit pack and prohibits provisioning new cross-connections.

At the System View, select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

CIT alarm list shows that the shelf is in the Ring Upgrade mode.

The node remains in the Ring Upgrade mode until manually provisioned back to the Normal mode. While in the Ring Upgrade mode, the upgrade may be temporarily suspended or backed out. To prevent errors in the upgraded ring, keep all nodes in Ring Upgrade mode until all nodes have been upgraded.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

.................................................................................................................................................................................................................................

12-248 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11.3: Upgrade high-speed BLSR connections at node equipped with incompatible OC-48

OLIUs

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

Continue with

Step 3 .

3

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-249

Ring and circuit pack upgrade procedures Procedure 12-11.3: Upgrade high-speed BLSR connections at node equipped with incompatible OC-48

OLIUs

.................................................................................................................................................................................................

6

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the replacement OC-192 OLIU circuit pack.

Result:

The system reports an unexpected CP type alarm and a

Line

Automatic Switch condition for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

7

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the replacement OC-192 OLIU circuit pack in Main slot

M1

and the required OC-192 circuit pack/port at the opposite end of the upgraded OC-192 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-192 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

8

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

Click

Yes

.

A dialog box appears asking you to confirm executing this command.

The replacement OC-192 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system performs an automatic protection switch, and all traffic is now active on Main slot

M1

. Transmission hits (less than 60 ms) occur as traffic switches from the circuit pack in Main slot

M2

to the circuit pack in Main slot

M1

.

The unexpected CP type alarm and

Line Automatic Switch condition for Main slot

M1

clear. The system reports an unexpected CP type alarm and a

Line

Automatic Switch condition for Main slot

M2

.

.................................................................................................................................................................................................................................

12-250 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

9

Procedure 12-11.3: Upgrade high-speed BLSR connections at node equipped with incompatible OC-48

OLIUs

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-48 OLIU circuit pack is upgraded at each end of the optical span.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the replacement OC-192 OLIU circuit pack.

Result:

The replacement OC-192 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M2

clears. The system reports an inc. OC192 LOS alarm and a

Line Automatic Switch condition for Main slot

M2

.

Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

STOP!

To complete the BLSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-251

Ring and circuit pack upgrade procedures

Procedure 12-11.4: Upgrade high-speed BLSR connections at node equipped with compatible OC-48 OLIUs

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-11: “Upgrade OC-48 BLSR to OC-192 BLSR”

(p. 12-223) .

Step

1

2

Important! Compatible OC-48 OLIU circuit packs include LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to upgrade the in-service high-speed BLSR connections at a node equipped with compatible OC-48 OLIU circuit packs in the Main slots.

.................................................................................................................................................................................................

Important! The Ring Upgrade mode allows cross-connections/ data to be mapped to the new circuit pack and prohibits provisioning new cross-connections.

At the System View, select

Configuration

→

Ring Upgrade Mode

.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Ring Upgrade mode. Click

Yes

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the WaveStar

®

alarm list shows that the shelf is in the Ring Upgrade mode.

CIT

The node remains in the Ring Upgrade mode until manually provisioned back to the Normal mode. While in the Ring Upgrade mode, the upgrade may be temporarily suspended or backed out. To prevent errors in the upgraded ring, keep all nodes in Ring Upgrade mode until all nodes have been upgraded.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

.................................................................................................................................................................................................................................

12-252 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11.4: Upgrade high-speed BLSR connections at node equipped with compatible OC-48

OLIUs

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

Continue with

Step 3 .

3

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-48 OLIU circuit pack in Main slot

M1

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click on

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-253

Ring and circuit pack upgrade procedures Procedure 12-11.4: Upgrade high-speed BLSR connections at node equipped with compatible OC-48

OLIUs

.................................................................................................................................................................................................

6

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the OC-48 OLIU circuit pack in Main slot

M1

with the replacement OC-192 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-192 OLIU circuit pack is inserted. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The replacement OC-192 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system reports an unexpected circuit pack type and

Line Automatic

Switch condition for Main slot

M1

. The system also reports an inc. OC192 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

7

.................................................................................................................................................................................................

At both ends of the optical span to be upgraded, perform the following to connect the replacement OC-192 OLIU circuit pack in Main slot

M1

and the required OC-192 circuit pack/port at the opposite end of the upgraded OC-192 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-192 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC192 LOS alarms and

Line Automatic Switch conditions clear. Transmission is now supported on the upgraded optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

8

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

Click

Yes

.

A dialog box appears asking you to confirm executing this command.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an unexpected circuit pack type condition for Main slot

M2

.

.................................................................................................................................................................................................................................

12-254 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11.4: Upgrade high-speed BLSR connections at node equipped with compatible OC-48

OLIUs

.................................................................................................................................................................................................

9

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 15 .

Continue with

Step 10 .

10

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for transmission and timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than 60 ms) will occur. If desired, perform this step to determine the transmission and timing state of the OC-48 OLIU circuit pack in

Main slot

M2

.

From the System View select

Reports

→

Status Lists

→

Pack

. Click on Shelf and

Select

. Observe the value of the Switch State parameter for the main-2 circuit pack. If the Switch State parameter is ACTIVE-TIMING, all Function units are selecting timing from the main-2 circuit pack, and some Function units are receiving traffic from the

main-2 circuit pack. If the Switch State parameter is ACTIVE, some Function units are receiving traffic from the main-2 circuit pack. Click

Close

.

.................................................................................................................................................................................................

11

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-255

Ring and circuit pack upgrade procedures Procedure 12-11.4: Upgrade high-speed BLSR connections at node equipped with compatible OC-48

OLIUs

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

12

.................................................................................................................................................................................................

If required, repeat

Step 10

to determine the transmission and timing state of the OC-48

OLIU circuit pack in Main slot

M2

.

.................................................................................................................................................................................................

13

14

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M2

is an active circuit pack for transmission, an optional manual switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is not the active circuit pack for transmission, proceed to

Step 14 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Click on 2F BLSR main-1-1 and

Select

. Select the East Direction and Manual to

Protection, Ring Switch Type, and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and

Close

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the Alarm List shows the

Protection Switch, OC48 Port, Manual Switch, MSR, 2F condition (Not Alarmed).

.................................................................................................................................................................................................

If required, repeat

Step 10

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for transmission.

15

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-48 OLIU circuit pack is upgraded at each end of the optical span.

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or

.................................................................................................................................................................................................................................

12-256 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11.4: Upgrade high-speed BLSR connections at node equipped with compatible OC-48

OLIUs transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the replacement OC-192 OLIU circuit pack.

Result:

A transmission hit will occur when the OC-48 OLIU circuit pack is removed. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The replacement OC-192 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected circuit pack type condition for Main slot

M2

clears. The system reports an inc. OC192 LOS alarm and a

Line Automatic Switch condition for Main slot

M2

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

STOP!

To complete the BLSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-257

Ring and circuit pack upgrade procedures

Procedure 12-11.5: Replace pre Series 1:6 LNW27, 29, 76,

221-259 OC-48 OLIU at first node to be upgraded

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-11: “Upgrade OC-48 BLSR to OC-192 BLSR”

(p. 12-223) .

Step

1

2

Important! When optical fibers are disconnected during this procedure, inc. LOS

, section DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to replace a pre Series 1:6 LNW27, 29, 76, 221-259

OC-48 OLIU circuit pack with a Series 1:6 or later version of the same OC-48 OLIU circuit pack type at the first node to be upgraded.

.................................................................................................................................................................................................

Identify and log in to the starting node.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-48 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 8 .

Continue with

Step 3 .

.................................................................................................................................................................................................................................

12-258 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11.5: Replace pre Series 1:6 LNW27, 29,

76, 221-259 OC-48 OLIU at first node to be upgraded

3

4

5

6

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than 60 ms) will occur. If desired, perform this step to determine the transmission and timing state of the OC-48 OLIU circuit pack in

Main slot

M1

.

At the System View select

Reports

→

Status Lists

→

Pack

. Click Shelf and

Select

.

Observe the value of the Switch State parameter for the main-1 circuit pack. If the

Switch State parameter is ACTIVE-TIMING, all Function units are selecting timing from the main-1 circuit pack, and some Function units are receiving traffic from the

main-1 circuit pack. If the Switch State parameter is ACTIVE, some Function units are receiving traffic from the main-1 circuit pack. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to determine the transmission and timing state of the OC-48

OLIU circuit pack in Main slot

M1

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-48 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, an optional manual switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 7 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-259

Ring and circuit pack upgrade procedures

7

8

9

Procedure 12-11.5: Replace pre Series 1:6 LNW27, 29,

76, 221-259 OC-48 OLIU at first node to be upgraded

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Click on 2F BLSR main-1-1 and

Select

. Select the West Direction and Manual to

Protection, Ring Switch Type, and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and

Close

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the Alarm List shows the

Protection Switch, OC48 Port, Manual Switch, MSR, 2F condition

(Not Alarmed).

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the OC-48 OLIU circuit pack in Main slot

M2

is now the active circuit pack for transmission.

.................................................................................................................................................................................................

Important! At the starting node, the pre Series 1:6 LNW27, 29, 76, 221-259

OC-48 OLIU circuit pack in Main slot

M1

must be first replaced with a Series 1:6 or later version of the same LNW27, 29, 76, 221-259 OC-48 OLIU circuit pack type. For example, a pre Series 1:6 LNW27 OC-48 OLIU circuit pack must be replaced with a Series 1:6 or later LNW27 OC-48 OLIU circuit pack. The Series

1:6 or later OC-48 OLIU circuit pack maintains traffic with the last node to be upgraded while slot

M2

and the other nodes in the ring are upgraded. As a final step, The Series 1:6 or later OC-48 OLIU circuit pack is upgraded.

Open a faceplate latch on the pre Series 1:6 LNW27, 29, 76, 221-259 OC-48 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M1

. Then replace the

OC-48 OLIU circuit pack in Main slot

M1

with a Series 1:6 or later version of the same OC-48 OLIU circuit pack type.

Result:

Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M1

. If active through traffic exists on the circuit pack in Main slot

M1

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

Measure the optical receive power of the receive fiber using an optical power meter.

Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 OLIU circuit packs.)

.................................................................................................................................................................................................................................

12-260 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-11.5: Replace pre Series 1:6 LNW27, 29,

76, 221-259 OC-48 OLIU at first node to be upgraded

10

.................................................................................................................................................................................................

Clean all fiber connectors, and connect the transmit and receive optical fibers to the replacement OC-48 OLIU circuit pack in Main slot

M1

.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

STOP!

To complete the BLSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-261

Ring and circuit pack upgrade procedures

Procedure 12-12: Back out OC-48 BLSR to OC-192 BLSR upgrade

.................................................................................................................................................................................................................................

Overview

CAUTION

Service disruption hazard

If a node has been taken out of the Ring Upgrade mode, the node cannot be returned to the original pre-upgrade state without affecting service.

All nodes in the ring must be in the provisioned Ring Upgrade mode.

Use this procedure to back out an OC-48 BLSR to OC-192 BLSR upgrade with:

•

LNW26B, LNW27 (pre Series 1:6), LNW28, LNW29 (pre Series 1:6), LNW76

(pre Series 1:6), LNW77, LNW121B-159B, and/or LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs originally at all nodes.

These OC-48 OLIU circuit packs have different optics and transmit at different wavelengths. However, these circuit packs have the same circuit pack type and a small VT cross-connection fabric. There are no differences between these circuit packs for the purposes of ring backouts/suspends.

These OC-48 OLIU circuit packs and the OC-192 OLIU circuit packs have

incompatible VT cross-connection fabrics.

•

LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76

(Series 1:6 and later), and/or LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs originally at one or more nodes.

These OC-48 OLIU circuit packs have different optics and transmit at different wavelengths. However, these circuit packs have the same circuit pack type and a large VT cross-connection fabric. There are no differences between these circuit packs for the purposes of ring backouts/suspends.

These OC-48 OLIU circuit packs and the OC-192 OLIU circuit packs have

compatible VT cross-connection fabrics.

Backing out of an upgrade in progress returns all nodes in the ring to their pre-upgrade state.

To temporarily stop the upgrade refer to

Procedure 12-13: “Suspend OC-48 BLSR to

OC-192 BLSR upgrade” (p. 12-294) .

Important! Transmission hits will occur during this procedure whenever an OLIU circuit pack with a different line rate is installed or removed from a Main slot. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

.................................................................................................................................................................................................................................

12-262 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-12: Back out OC-48 BLSR to OC-192

BLSR upgrade

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

The following equipment is required to perform this procedure:

•

Wrist strap

•

Original OC-48 OLIU circuit packs for each node to be backed out

•

As the upgrade is backed out around the BLSR, ensure that technicians are available at each end of an optical span as the upgrade is backed out.

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this back out procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-263

Ring and circuit pack upgrade procedures

Step

Procedure 12-12: Back out OC-48 BLSR to OC-192

BLSR upgrade

1

Important! This procedure starts at the last node upgraded.

Complete the following steps to back out an OC-48 BLSR to OC-192 BLSR upgrade.

.................................................................................................................................................................................................

From office records and work instructions, determine the current network configuration and status of the upgrade.

2

.................................................................................................................................................................................................

If backing out an OC-48 BLSR to OC-192 BLSR upgrade with...

LNW26B, LNW27 (pre Series 1:6),

LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, and/or

LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs originally at all nodes,

LNW27 (Series 1:6 and later),

LNW29 (Series 1:6 and later),

LNW32, LNW76 (Series 1:6 and later), and/or LNW221-259 (Series

1:6 and later) OC-48 OLIU circuit packs originally at one or more nodes,

Then proceed to and perform...

Procedure 12-12.1: “Back out OC-48 BLSR to

OC-192 BLSR upgrade (incompatible OC-48

OLIUs originally at all nodes)” (p. 12-265)

Procedure 12-12.2: “Back out OC-48 BLSR to

OC-192 BLSR Upgrade (compatible OC-48

OLIUs originally at one or more nodes)”

(p. 12-275)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-264 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-12.1: Back out OC-48 BLSR to OC-192 BLSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-12: “Back out OC-48 BLSR to OC-192 BLSR upgrade”

(p. 12-262) .

Step

CAUTION

Service disruption hazard

If a node has been taken out of the Ring Upgrade mode, the node cannot be returned to the original pre-upgrade state without affecting service.

All nodes in the ring must be in the provisioned Ring Upgrade mode.

1

Important! This procedure starts at the last node upgraded.

Incompatible OC-48 OLIU circuit packs include the LNW26B, LNW27 (pre Series

1:6), LNW28, LNW29 (pre Series 1:6), LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, and LNW221-259 (pre Series 1:6) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-48 to OC-192 BLSR upgrade

(incompatible OC-48 OLIU circuit packs originally at all nodes).

.................................................................................................................................................................................................

Identify the last node that was upgraded.

If the last node upgraded is...

the starting node, and the ring upgrade is complete (all nodes are in the Ring

Upgrade mode), not the starting node,

Then log in to the...

starting node (refer to the

“BLSR example”

(p. 12-274)

at the end of the procedure) and continue with

Step 2 .

last node upgraded (refer to the

“BLSR example” (p. 12-274)

at the end of the procedure) and proceed to

Step 10 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-265

Ring and circuit pack upgrade procedures Procedure 12-12.1: Back out OC-48 BLSR to OC-192

BLSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

2

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 8 .

Continue with

Step 3 .

3

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than 60 ms) will occur. If desired, perform this step to determine the transmission and timing state of the OC-192 OLIU circuit pack in

Main slot

M1

.

From the System View select

Reports

→

Status Lists

→

Pack

. Click Shelf and

Select

. Observe the value of the Switch State parameter for the main-1 circuit pack. If the Switch State parameter is ACTIVE-TIMING, all Function units are selecting timing from the main-1 circuit pack, and some Function units are receiving traffic from the

main-1 circuit pack. If the Switch State parameter is ACTIVE, some Function units are receiving traffic from the main-1 circuit pack. Click

Close

.

.................................................................................................................................................................................................

4

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

.................................................................................................................................................................................................................................

12-266 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-12.1: Back out OC-48 BLSR to OC-192

BLSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

5

6

7

.................................................................................................................................................................................................

If required, repeat

Step 3

to determine the transmission and timing state of the OC-192

OLIU circuit pack in Main slot

M1

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, an optional manual switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 7 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Click on 2F BLSR main-1-1 and

Select

. Select the West Direction and Manual to

Protection, Ring Switch Type, and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and

Close

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the Alarm List shows the

Protection Switch, OC48 Port, Manual Switch, MSR, 2F condition (not alarmed).

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for transmission.

8

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-192 OLIU circuit pack is backed out at each end of the optical span.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-267

Ring and circuit pack upgrade procedures Procedure 12-12.1: Back out OC-48 BLSR to OC-192

BLSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

Important! At the starting node, the OC-192 OLIU circuit pack in Main slot

M1

must be first replaced with the temporary replacement OC-48 OLIU circuit pack.

The temporary replacement OC-48 OLIU circuit pack maintains traffic while backing out of the upgrade. As a final step in backing out the ring upgrade, this temporary replacement OC-48 OLIU circuit pack is replaced with the original

OC-48 OLIU circuit pack.

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M1

. Then replace the OC-192 OLIU circuit pack in Main slot

M1

with the temporary replacement OC-48 OLIU circuit pack.

Result:

A transmission hit will occur after the temporary replacement OC-48

OLIU circuit pack is inserted in the slot. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two

Main slots.

The temporary replacement OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned. Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M1

. If active through traffic exists on the circuit pack in Main slot

M1

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected circuit pack type condition and an inc.

OC48 LOS alarm for Main slot

M1

. The system also reports a

Line Automatic

Switch condition for Main slot

M1

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

This completes the first phase of the back out at the starting node. The back out at the starting node will be completed after backing out of all the other nodes in the ring.

9

10

.................................................................................................................................................................................................

Log in to the adjacent node connected to Main slot

M1

(refer to the

“BLSR example”

(p. 12-274)

at the end of the procedure).

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Back out the upgrade at the node using the original incompatible OC-48 OLIU circuit packs.

.................................................................................................................................................................................................................................

12-268 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-12.1: Back out OC-48 BLSR to OC-192

BLSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

Reference:

Procedure 12-12.3: “Back out high-speed BLSR upgrade at node originally equipped with incompatible OC-48 OLIUs” (p. 12-284)

11

.................................................................................................................................................................................................

Except for the starting node, has the upgrade been backed out of all nodes in the

BLSR.

If...

No,

Yes,

Then...

Repeat

Step 9

and

Step 10

as required at the next node (refer to the

“BLSR example” (p. 12-274)

at the end of the procedure).

Continue with

Step 12 .

12

13

14

.................................................................................................................................................................................................

Log in to the starting node (refer to the

“BLSR example” (p. 12-274)

at the end of the procedure).

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M1

clears. The system reports an unexpected circuit pack type condition for Main slot

M2

.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-269

Ring and circuit pack upgrade procedures Procedure 12-12.1: Back out OC-48 BLSR to OC-192

BLSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 18 .

Continue with

Step 15 .

15

16

17

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-192 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 15

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

12-270 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-12.1: Back out OC-48 BLSR to OC-192

BLSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

.................................................................................................................................................................................................

18

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M2

. Then replace the OC-192 OLIU circuit pack in Main slot

M2

with the original OC-48 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-192 OLIU circuit pack is removed. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The system reports an unexpected CP type alarm and a

Line Automatic Switch condition for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

19

20

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-48 OLIU circuit pack in Main slot

M2

and the required OC-48 circuit pack/port at the opposite end of the original OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The original OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The system performs an automatic line protection switch, and all traffic is now active on Main slot

M2

. Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in Main slot

M1

to the circuit pack in Main slot

M2

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-271

Ring and circuit pack upgrade procedures Procedure 12-12.1: Back out OC-48 BLSR to OC-192

BLSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

The unexpected CP type alarm and

Line Automatic Switch condition for Main slot

M2

clear. The system reports an unexpected CP type alarm and a

Line

Automatic Switch condition for Main slot

M1

.

.................................................................................................................................................................................................

21

Open a faceplate latch on the temporary replacement OC-48 OLIU circuit pack in

Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

. Then replace the temporary replacement OC-48 OLIU circuit pack in Main slot

M1

with the original

OC-48 OLIU circuit pack.

Result:

The original OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M1

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M1

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

22

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-48 OLIU circuit pack in Main slot

M1

and the required OC-48 circuit pack/port at the opposite end of the original OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The

Line Automatic Switch conditions and inc. OC48 LOS alarms clear. Transmission is now supported on the original OC-48 span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

23

.................................................................................................................................................................................................

Important! All BLSR protection switches in the ring must be cleared before any node is taken out of the Ring Upgrade mode.

To clear a BLSR protection switch at each node in the BLSR as required, select

Fault

→

Protection Switch

. Click on 2F BLSR main-1-1 and

Select

. Select the required

Direction and Clear Switch Type, and click

Apply

.

.................................................................................................................................................................................................................................

12-272 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-12.1: Back out OC-48 BLSR to OC-192

BLSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and

Close

.

24

.................................................................................................................................................................................................

Important! At each node in the BLSR, the system reports the ring upgrade mode standing condition (not alarmed) in the NE Alarm List until the node is manually provisioned back to the Normal mode.

At each node in the BLSR, click the

Alarm List

button in the top right corner of the

System View or select

Fault

→

NE Alarm List

to view the NE Alarm List and verify that no alarms or standing conditions are present (except ring upgrade mode and

ABN condition

).

Refer to the appropriate trouble clearing procedures to clear all existing alarms and standing conditions (except ring upgrade mode and

ABN condition

) before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

25

.................................................................................................................................................................................................

Important! This completes the back out procedure, except for taking the nodes out of the Ring Upgrade mode and enabling Automatic Ring Discovery. The decision to take all nodes out of the Ring Upgrade mode depends on the reason the back out was necessary, and what is required before again starting or completing the ring upgrade. All nodes must remain in the Ring Upgrade node until the ring upgrade is completed.

At each node in the BLSR as required, select

Configuration

→

Normal Mode

to take the node out of the Ring Upgrade mode.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode will be removed from the WaveStar

®

CIT alarm list.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-273

Ring and circuit pack upgrade procedures Procedure 12-12.1: Back out OC-48 BLSR to OC-192

BLSR upgrade (incompatible OC-48 OLIUs originally at all nodes)

.................................................................................................................................................................................................

26

If Automatic Ring

Discovery was...

Disabled,

Then...

not Disabled,

Perform the following to enable Automatic Ring Discovery.

1. Select

Configuration

→

Equipment.

.

2. Select the

Ptn Grp

tab and the 2F BLSR main-1-1 protection group. Then click

Select

.

3. Provision the Automatic Ring Discovery parameter to

Enabled and click

Apply

. Then click

Close

.

Repeat this step to enable Automatic Ring Discovery at each node in the BLSR.

STOP!

End of Procedure.

E

N D O F

S

T E P S

BLSR example

N

(Starting Node)

West East

MAIN-1 MAIN-2

East

N+3

West

West

N+1

East

MAIN-2 MAIN-1

East

N+2

West nc-dmx-256

.................................................................................................................................................................................................................................

12-274 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-12.2: Back out OC-48 BLSR to OC-192 BLSR

Upgrade (compatible OC-48 OLIUs originally at one or more nodes)

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-12: “Back out OC-48 BLSR to OC-192 BLSR upgrade”

(p. 12-262) .

Step

CAUTION

Service disruption hazard

If a node has been taken out of the Ring Upgrade mode, the node cannot be returned to the original pre-upgrade state without affecting service.

All nodes in the ring must be in the provisioned Ring Upgrade mode.

1

Important! This procedure starts at the last node upgraded.

Compatible OC-48 OLIU circuit packs include LNW27 (Series 1:6 and later),

LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-48 BLSR to OC-192 BLSR upgrade

(compatible OC-48 OLIU circuit packs originally at one or more nodes).

.................................................................................................................................................................................................

Identify the last node that was upgraded.

If the last node upgraded is...

the starting node, and the ring upgrade is complete (all nodes are in the Ring Upgrade mode), not the starting node,

Then log in to the...

starting node (refer to the

“BLSR example”

(p. 12-283)

at the end of the procedure) and continue with

Step 2 .

last node upgraded (refer to the

“BLSR example” (p. 12-283)

at the end of the procedure) and proceed to

Step 10 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-275

Ring and circuit pack upgrade procedures Procedure 12-12.2: Back out OC-48 BLSR to OC-192

BLSR Upgrade (compatible OC-48 OLIUs originally at one or more nodes)

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

2

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 8 .

Continue with

Step 3 .

3

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than 60 ms) will occur. If desired, perform this step to determine the transmission and timing state of the OC-192 OLIU circuit pack in

Main slot

M1

.

Select

Reports

→

Status Lists

→

Pack

. Click Shelf and

Select

. Observe the value of the Switch State parameter for the main-1 circuit pack. If the Switch State parameter is

ACTIVE-TIMING, all Function units are selecting timing from the main-1 circuit pack, and some Function units are receiving traffic from the main-1 circuit pack. If the

Switch State parameter is ACTIVE, some Function units are receiving traffic from the

main-1 circuit pack. Click

Close

.

.................................................................................................................................................................................................

4

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

.................................................................................................................................................................................................................................

12-276 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-12.2: Back out OC-48 BLSR to OC-192

BLSR Upgrade (compatible OC-48 OLIUs originally at one or more nodes)

If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

5

6

7

.................................................................................................................................................................................................

If required, repeat

Step 3

to determine the transmission and timing state of the OC-192

OLIU circuit pack in Main slot

M1

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, an optional manual switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 7 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Click on 2F BLSR main-1-1 and

Select

. Select the West Direction and Manual to

Protection, Ring Switch Type, and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and

Close

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the Alarm List shows the

Protection Switch, OC48 Port, Manual Switch, MSR, 2F condition (not alarmed).

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for transmission.

8

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-192 OLIU circuit pack is backed out at each end of the optical span.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-277

Ring and circuit pack upgrade procedures Procedure 12-12.2: Back out OC-48 BLSR to OC-192

BLSR Upgrade (compatible OC-48 OLIUs originally at one or more nodes)

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M1

. Then replace the OC-192 OLIU circuit pack in Main slot

M1

with the original OC-48 OLIU circuit pack.

Result:

A transmission hit will occur after the original OC-48 OLIU circuit pack is inserted. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The original OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned. Transmission hits (less than 60 ms) may occur if active traffic exists on the circuit pack in Main slot

M1

. If active through traffic exists on the circuit pack in Main slot

M1

, transmission hits (less than 60 ms) may occur at the nodes where the traffic is added/dropped.

The system reports an unexpected circuit pack type condition and an inc.

OC48 LOS

Switch alarm for Main slot condition for Main slot

M1

. The system also reports a

M1

Line Automatic

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

This completes the first phase of the back out at the starting node. The back out at the starting node will be completed after backing out of all the other nodes in the ring.

9

.................................................................................................................................................................................................

Log in to the adjacent node connected to Main slot

M1

(refer to the

“BLSR example”

(p. 12-283)

at the end of the procedure).

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

10

.................................................................................................................................................................................................

Determine how the node was originally equipped and back out the upgrade.

If the node was originally equipped with...

LNW26B, LNW27 (pre Series 1:6),

LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, and/or

LNW221-259 (pre Series 1:6)

OC-48 OLIU circuit packs in the

Main slots,

Then back out the BLSR upgrade using...

Procedure 12-12.3: “Back out high-speed BLSR upgrade at node originally equipped with incompatible OC-48 OLIUs” (p. 12-284) . Then

continue with

Step 11 .

.................................................................................................................................................................................................................................

12-278 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-12.2: Back out OC-48 BLSR to OC-192

BLSR Upgrade (compatible OC-48 OLIUs originally at one or more nodes)

Then back out the BLSR upgrade using...

If the node was originally equipped with...

LNW27 (Series 1:6 and later),

LNW29 (Series 1:6 and later),

LNW32, LNW76 (Series 1:6 and later), and/or LNW221-259 (Series

1:6 and later) OC-48 OLIU circuit packs in the Main slots,

Procedure 12-12.4: “Back out high-speed BLSR upgrade at node originally equipped with compatible OC-48 OLIUs” (p. 12-288) . Then

continue with

Step 11 .

11

.................................................................................................................................................................................................

Except for the starting node, has the upgrade been backed out of all nodes in the

BLSR.

If...

No

Yes

Then...

Repeat

Step 9

and

Step 10

as required at the next node (refer to the

“BLSR example” (p. 12-283)

at the end of the procedure).

Continue with

Step 12 .

12

13

14

.................................................................................................................................................................................................

Log in to the starting node (refer to the

“BLSR example” (p. 12-283)

at the end of the procedure).

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-1

(default) as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an unexpected circuit pack type condition for Main slot

M2

.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-279

Ring and circuit pack upgrade procedures Procedure 12-12.2: Back out OC-48 BLSR to OC-192

BLSR Upgrade (compatible OC-48 OLIUs originally at one or more nodes) if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 18 .

Continue with

Step 15 .

.................................................................................................................................................................................................

15

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-192 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

16

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

17

If required, repeat

Step 15

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

12-280 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-12.2: Back out OC-48 BLSR to OC-192

BLSR Upgrade (compatible OC-48 OLIUs originally at one or more nodes)

.................................................................................................................................................................................................

18

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M2

. Then replace the OC-192 OLIU circuit pack in Main slot

M2

with the original OC-48 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-192 OLIU circuit pack is removed. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The original OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected circuit pack type condition for Main slot

M2

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

19

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-48 OLIU circuit pack in Main slot

M2

and the required OC-48 OLIU circuit pack/port at the opposite end of the original OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC48 LOS alarms clear. Transmission is now supported on the original OC-48 optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

20

Important! All BLSR protection switches in the ring must be cleared before any node is taken out of the Ring Upgrade mode.

To clear a BLSR protection switch at each node in the BLSR as required, select

Fault

→

Protection Switch

. Click on 2F BLSR main-1-1 and

Select

. Select the required

Direction and Clear Switch Type, and click

Apply

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-281

Ring and circuit pack upgrade procedures Procedure 12-12.2: Back out OC-48 BLSR to OC-192

BLSR Upgrade (compatible OC-48 OLIUs originally at one or more nodes)

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and

Close

.

21

.................................................................................................................................................................................................

Important! At each node in the BLSR, the system reports the ring upgrade mode standing condition (not alarmed) in the NE Alarm List until the node is manually provisioned back to the Normal mode.

At each node in the BLSR, click the

Alarm List

button in the top right corner of the

System View or select

Fault

→

NE Alarm List

to view the NE Alarm List and verify that no alarms or standing conditions are present (except ring upgrade mode and

ABN condition

).

Refer to the appropriate trouble clearing procedures to clear all existing alarms and standing conditions (except ring upgrade mode and

ABN condition

) before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

22

.................................................................................................................................................................................................

Important! This completes the back out procedure, except for taking the nodes out of the Ring Upgrade mode and enabling Automatic Ring Discovery. The decision to take all nodes out of the Ring Upgrade mode depends on the reason the back out was necessary, and what is required before again starting or completing the ring upgrade. All nodes must remain in the Ring Upgrade node until the ring upgrade is completed.

At each node in the BLSR as required, select

Configuration

→

Normal Mode

to take the node out of the Ring Upgrade mode.

Result:

A dialog box appears asking you to confirm changing the NE Mode to

Normal mode. Click

Yes

.

The

ABN

LED is turned off on the SYSCTL circuit pack faceplate and the Ring

Upgrade mode will be removed from the WaveStar

®

CIT alarm list.

.................................................................................................................................................................................................................................

12-282 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-12.2: Back out OC-48 BLSR to OC-192

BLSR Upgrade (compatible OC-48 OLIUs originally at one or more nodes)

.................................................................................................................................................................................................

23

If Automatic Ring

Discovery was...

Disabled,

Then...

not Disabled,

Perform the following to enable Automatic Ring Discovery.

1. Select

Configuration

→

Equipment.

.

2. Select the

Ptn Grp

tab and the 2F BLSR main-1-1 protection group. Then click

Select

.

3. Provision the Automatic Ring Discovery parameter to

Enabled and click

Apply

. Then click

Close

.

Repeat this step to enable Automatic Ring Discovery at each node in the BLSR.

STOP!

End of Procedure.

E

N D O F

S

T E P S

BLSR example

N

(Starting Node)

West East

MAIN-1 MAIN-2

East

N+3

West

West

N+1

East

MAIN-2 MAIN-1

East

N+2

West nc-dmx-256

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-283

Ring and circuit pack upgrade procedures

Procedure 12-12.3: Back out high-speed BLSR upgrade at node originally equipped with incompatible OC-48 OLIUs

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-12: “Back out OC-48 BLSR to OC-192 BLSR upgrade”

(p. 12-262) .

Step

1

Important! Incompatible OC-48 OLIU circuit packs include the LNW26B, LNW27

(pre Series 1:6), LNW28, LNW29 (pre Series 1:6), LNW76 (pre Series 1:6),

LNW77, LNW121B-159B, and LNW221-259 (pre Series 1:6) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-48 BLSR to OC-192 BLSR upgrade at a node originally equipped with incompatible OC-48 OLIU circuit packs in the Main slots.

.................................................................................................................................................................................................

Determine the current status of the upgrade at the node.

If...

both Main slots have been upgraded with

OC-192 OLIU circuit packs, only Main slot

M1

has been upgraded with an OC-192 OLIU circuit pack,

Then...

Continue with

Step 2 .

Proceed to

Step 8 .

2

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

.................................................................................................................................................................................................................................

12-284 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-12.3: Back out high-speed BLSR upgrade at node originally equipped with incompatible OC-48

OLIUs

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

Continue with

Step 3 .

3

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-192 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-285

Ring and circuit pack upgrade procedures Procedure 12-12.3: Back out high-speed BLSR upgrade at node originally equipped with incompatible OC-48

OLIUs

.................................................................................................................................................................................................

6

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M2

. Then replace the OC-192 OLIU circuit pack in Main slot

M2

with the original OC-48 OLIU circuit pack.

Result:

Switch

The system reports an unexpected CP type condition for Main slot

M2

.

alarm and a

Line Automatic

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

7

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-48 OLIU circuit pack in Main slot

M2

and the required OC-48 circuit pack/port at the opposite end of the original OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

8

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The original OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The system performs an automatic line protection switch, and all traffic is now active on Main slot

M2

. Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in Main slot

M1

to the circuit pack in Main slot

M2

.

The unexpected CP type alarm and

Line Automatic Switch condition for Main slot

M2

clear, and the system reports an unexpected CP type alarm and

Line

Automatic Switch condition for Main slot

M1

.

.................................................................................................................................................................................................................................

12-286 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

9

Procedure 12-12.3: Back out high-speed BLSR upgrade at node originally equipped with incompatible OC-48

OLIUs

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-192 OLIU circuit pack is backed out at each end of the optical span.

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M1

. Then replace the OC-192 OLIU circuit pack in Main slot

M1

with the original OC-48 OLIU circuit pack.

Result:

The original OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M1

clears. The system reports an inc. OC48 LOS alarm and a

Line Automatic Switch condition for Main slot

M1

.

Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

STOP!

To complete backing out the BLSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-287

Ring and circuit pack upgrade procedures

Procedure 12-12.4: Back out high-speed BLSR upgrade at node originally equipped with compatible OC-48 OLIUs

.................................................................................................................................................................................................................................

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 12-12: “Back out OC-48 BLSR to OC-192 BLSR upgrade”

(p. 12-262) .

Step

1

Important! Compatible OC-48 OLIU circuit packs include LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to back out an OC-48 BLSR to OC-192 BLSR upgrade at a node originally equipped with compatible OC-48 OLIU circuit packs in the Main slots.

.................................................................................................................................................................................................

Determine the current status of the upgrade at the node.

If...

both Main slots have been upgraded with

OC-192 OLIU circuit packs, only Main slot

M1

has been upgraded with an OC-192 OLIU circuit pack,

Then...

Continue with

Step 2 .

Proceed to

Step 8 .

2

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

.................................................................................................................................................................................................................................

12-288 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-12.4: Back out high-speed BLSR upgrade at node originally equipped with compatible OC-48 OLIUs

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

Continue with

Step 3 .

3

4

5

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-192 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-289

Ring and circuit pack upgrade procedures Procedure 12-12.4: Back out high-speed BLSR upgrade at node originally equipped with compatible OC-48 OLIUs

6

7

8

.................................................................................................................................................................................................

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M2

. Then replace the OC-192 OLIU circuit pack in Main slot

M2

with the original OC-48 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-48 OLIU is inserted. The transmission hit is the result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The original OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The system reports an inc. OC48 LOS alarm, and an unexpected circuit pack type and

Line Automatic Switch condition for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span to be backed out, perform the following to connect the original OC-48 circuit pack in Main slot

M2

and the required OC-48 circuit pack/port at the opposite end of the original OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC48 LOS alarm and

Line Automatic Switch condition for

Main slot

M2

clears. Transmission is now supported on the original OC-48 optical span.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

At the System View select

Configuration

→

Update System

→

Update All

. Select

main-2

as the Ring Upgrade Choice and click

OK

.

.................................................................................................................................................................................................................................

12-290 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-12.4: Back out high-speed BLSR upgrade at node originally equipped with compatible OC-48 OLIUs

9

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M2

clears, and the system reports an unexpected circuit pack type condition for Main slot

M1

.

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M1

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 15 .

Continue with

Step 10 .

.................................................................................................................................................................................................

10

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for transmission and timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than 60 ms) will occur. If desired, perform this step to determine the transmission and timing state of the OC-192 OLIU circuit pack in

Main slot

M1

.

Select

Reports

→

Status Lists

→

Pack

. Click Shelf and

Select

. Observe the value of the Switch State parameter for the main-1 circuit pack. If the Switch State parameter is

ACTIVE-TIMING, all Function units are selecting timing from the main-1 circuit pack, and some Function units are receiving traffic from the main-1 circuit pack. If the

Switch State parameter is ACTIVE, some Function units are receiving traffic from the

main-1 circuit pack. Click

Close

.

.................................................................................................................................................................................................

11

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, an optional manual timing switch can be

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-291

Ring and circuit pack upgrade procedures Procedure 12-12.4: Back out high-speed BLSR upgrade at node originally equipped with compatible OC-48 OLIUs

12

13

14

performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-48 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, do not perform this step.

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 10

to determine the transmission and timing state of the

OC-192 OLIU circuit pack in Main slot

M1

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M1

is an active circuit pack for transmission, an optional manual switch can be performed before replacing the circuit pack in Main slot

M1

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M1

is not the active circuit pack for transmission, proceed to

Step 14 .

To perform an optional manual transmission switch, select

Fault

→

Protection Switch

.

Click on 2F BLSR main-1-1 and

Select

. Select the West Direction and Manual to

Protection, Ring Switch Type, and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and

Close

.

The

ABN

LED is lit on the SYSCTL circuit pack faceplate and the Alarm List shows the

Protection Switch, OC48 Port, Manual Switch, MSR, 2F condition (not alarmed).

.................................................................................................................................................................................................

If required, repeat

Step 10

to verify that the circuit pack in Main slot

M2

is now the active circuit pack for transmission.

.................................................................................................................................................................................................................................

12-292 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-12.4: Back out high-speed BLSR upgrade at node originally equipped with compatible OC-48 OLIUs

15

.................................................................................................................................................................................................

CAUTION

Equipment damage

If an OC-192 OLIU circuit pack is connected to an OC-48 OLIU circuit pack equipment damage may occur.

Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-192 OLIU circuit pack is backed out at each end of the optical span.

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M1

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M1

. Then replace the OC-192 OLIU circuit pack in Main slot

M1

with the original OC-48 OLIU circuit pack.

Result:

A transmission hit will occur after the OC-192 OLIU is removed. The transmission hit is the result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

The original OC-48 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The unexpected circuit pack type condition for Main slot

M1

clears. The system reports an inc. OC48 LOS alarm and a

Line Automatic Switch condition for Main slot

M1

. Alarms may also be reported at other nodes in the ring.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

STOP!

To complete backing out the BLSR upgrade, return to the procedure that directed you to perform this procedure.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-293

Ring and circuit pack upgrade procedures

Procedure 12-13: Suspend OC-48 BLSR to OC-192 BLSR upgrade

.................................................................................................................................................................................................................................

Overview

CAUTION

Service disruption hazard

If a node has been taken out of the Ring Upgrade mode, the node cannot be returned to the original pre-upgrade state without affecting service.

All nodes in the ring must be in the provisioned Ring Upgrade mode.

Use this procedure to temporarily suspend an OC-48 BLSR to OC-192 BLSR upgrade.

Suspending an upgrade in progress temporarily stops the upgrade.

To return all nodes in the ring to their pre-upgrade state, refer to

Procedure 12-12:

“Back out OC-48 BLSR to OC-192 BLSR upgrade” (p. 12-262) .

When the ring upgrade is temporarily suspended before completion, some spans are operating at the OC-48 line rate and some at the OC-192 line rate. This requires two nodes that are equipped with an OC-48 OLIU circuit pack in one Main slot and an

OC-192 OLIU circuit pack in the other Main slot. These nodes are the starting node and the last node upgraded.

To continue to operate temporarily with different circuit packs in the Main slots, the starting node and the nodes that have been upgraded must remain in the Ring Upgrade mode.

Important! Transmission hits will occur during this procedure whenever an OLIU circuit pack with a different line rate is installed or removed from a Main slot. The transmission hit is a result of an internal system timing adjustment to accommodate different line rates in the two Main slots.

Privilege level

You must log in as a Privileged user to complete this procedure.

.................................................................................................................................................................................................................................

12-294 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-13: Suspend OC-48 BLSR to OC-192

BLSR upgrade

Required equipment

The following equipment is required to perform this procedure:

•

Wrist strap

•

One original OC-48 OLIU circuit pack if the upgrade is suspended at an upgraded node originally equipped with LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and/or LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs

•

One LNW27 (Series 1:6 and later) or LNWUPG OC-48 OLIU circuit pack

(temporarily required if the upgrade is suspended at a partially upgraded node originally equipped with LNW26B, LNW27 (pre Series 1:6), LNW28, LNW29 (pre

Series 1:6), LNW76 (pre Series 1:6), LNW77, LNW121B-159B, and/or

LNW221-259 (pre Series 1:6) OC-48 OLIU circuit packs)

The LNWUPG OC-48 OLIU circuit pack is a special LNW27 OC-48 OLIU circuit pack that is intended for use only as the temporary transition circuit pack. There are no differences between the LNW27 (Series 1:6 and later) and LNWUPG circuit packs with respect to in-service backouts/suspends.

The LNW29 (Series 1:6 and later), LNW32, LNW76 (Series 1:6 and later), and/or

LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs may also be used as the temporary replacement circuit packs. However, the temporary replacement circuit packs must have compatible optics. For example, do not replace a circuit pack that has long range optics with a circuit pack that has intermediate reach optics. Refer to the Metropolis

®

DMX Access Multiplexer Applications and

Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48

OLIU circuit packs.

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-295

Ring and circuit pack upgrade procedures Procedure 12-13: Suspend OC-48 BLSR to OC-192

BLSR upgrade

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this suspend procedure.

Step

1

Important! This procedure starts at the last node upgraded.

When optical fibers are disconnected during this procedure, inc. LOS

, section

DCC channel failed

, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.

Complete the following steps to temporarily suspend an OC-48 BLSR to OC-192

BLSR upgrade.

.................................................................................................................................................................................................

Identify the last node that was upgraded.

If...

both Main slots have been upgraded, one Main slot has been upgraded and the node was originally equipped with

LNW26B, LNW27 (pre Series 1:6),

LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, or LNW221-259 (pre

Series 1:6) OC-48 OLIU circuit packs one Main slot has been upgraded and the node was originally equipped with

LNW27 (Series 1:6 and later), LNW29

(Series 1:6 and later), LNW32, LNW76

(Series 1:6 and later), or LNW221-259

(Series 1:6 and later) OC-48 OLIU circuit packs

Then...

Log in to the last node upgraded (refer to the

“BLSR example” (p. 12-302)

at the end of the procedure) and continue with

Step 2 .

Log in to the last node upgraded (refer to the

“BLSR example” (p. 12-302)

the procedure) and proceed to at the end of

Step 8 .

Log in to the last node upgraded (refer to the

“BLSR example” (p. 12-302)

at the end of the procedure) and proceed to

Step 11 .

.................................................................................................................................................................................................................................

12-296 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-13: Suspend OC-48 BLSR to OC-192

BLSR upgrade

2

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Important! Both Main slots have been upgraded and the system is reporting an inc. OC192 LOS alarm and a

Line Automatic Switch condition for Main slot

M2

.

Local operating procedures for removing a circuit pack may vary. One method is to disconnect the optical fibers and remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the OC-192 OLIU circuit pack in Main slot

M2

.

If the local operating procedures specify

{ disconnect the optical fibers and remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then disconnect the optical fibers and remove the circuit pack,

Then...

Proceed to

Step 6 .

Continue with

Step 3 .

3

4

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing and the circuit pack is removed, the system performs an automatic protection switch and subsequent transmission hits (less than

60 ms) will occur. If desired, perform this step to determine the timing state of the

OC-192 OLIU circuit pack in Main slot

M2

.

Select

View

→

Timing/Sync

. Observe the value of the Active Circuit Pack parameter to determine the active circuit pack for timing. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the OC-192 OLIU circuit pack in Main slot

M2

is the active circuit pack for timing, an optional manual timing switch can be performed before replacing the circuit pack in Main slot

M2

. Transmission hits (less than 60 ms) will occur for each separate protection switch.

If the OC-192 OLIU circuit pack in Main slot

M1

is the active circuit pack for timing, do not perform this step.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-297

Ring and circuit pack upgrade procedures

5

6

Procedure 12-13: Suspend OC-48 BLSR to OC-192

BLSR upgrade

To perform an optional manual timing switch, select

Fault

→

Timing/Sync Protection

Switch

→

Main Circuit Pack Timing Switch

. Select the Manual Switch Command and click

OK

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

If required, repeat

Step 3

to verify that the circuit pack in Main slot

M1

is now the active circuit pack for timing.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-192 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-192 OLIU circuit pack in Main slot

M2

.

If the Main slots were originally equipped with...

LNW26B, LNW27 (pre Series 1:6),

LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77,

LNW121B-159B, or LNW221-259 (pre

Series 1:6) OC-48 OLIUs,

LNW27 (Series 1:6 and later), LNW29

(Series 1:6 and later), LNW32, LNW76

(Series 1:6 and later), or LNW221-259

(Series 1:6 and later) OC-48 OLIUs,

Then replace the OC-192 OLIU circuit pack in Main slot M2 with...

the temporary replacement OC-48 OLIU circuit pack.

the original OC-48 OLIU circuit pack

Result:

The OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The inc. OC192 LOS alarm for Main slot

M2

clears, and the system reports an inc. OC48 LOS alarm for Main slot

M2

. The system also reports unexpected circuit pack type and

Line Automatic Switch conditions for Main slot

M2

.

.................................................................................................................................................................................................................................

12-298 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-13: Suspend OC-48 BLSR to OC-192

BLSR upgrade

7

8

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span, perform the following to connect the OC-48 OLIU circuit pack in Main slot

M2

and the required OC-48 circuit pack/port at the opposite end of the OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC48 LOS alarm for Main slot

M2

clears, and the system still reports an unexpected circuit pack type condition for Main slot

M2

.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

STOP!

End of Procedure. The upgrade procedure is now temporarily suspended and traffic is supported to the adjacent nodes.

To resume the upgrade, replace the OC-48 OLIU circuit pack in Main slot

M2

with the OC-192 OLIU circuit pack. Refer to

Procedure 12-11: “Upgrade OC-48 BLSR to OC-192 BLSR” (p. 12-223) .

To back out the upgrade, refer to

Procedure 12-12: “Back out OC-48 BLSR to

OC-192 BLSR upgrade” (p. 12-262) .

.................................................................................................................................................................................................

Important! Main slot

M1

has been upgraded and the node was originally equipped with LNW26B, LNW27 (pre Series 1:6), LNW28, LNW29 (pre Series 1:6),

LNW76 (pre Series 1:6), LNW77, LNW121B-159B, or LNW221-259 (pre Series

1:6) OC-48 OLIU circuit packs.

If an unexpected CP type alarm is reported for Main slot

M1

, select

Configuration

→

Update System

→

Update All

, then select

main-1

(default) as the Ring Upgrade

Choice and click

OK

. Otherwise, proceed to the next step.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The OC-192 OLIU circuit pack in Main slot

M1

is tested and autoprovisioned.

The system performs an automatic line protection switch, and all traffic is now active on Main slot

M1

. Transmission hits (less than 60 ms) occur as active traffic switches from the circuit pack in the Main slot

M2

to the circuit pack in Main slot

M1

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-299

Ring and circuit pack upgrade procedures

9

10

Procedure 12-13: Suspend OC-48 BLSR to OC-192

BLSR upgrade

The unexpected CP type alarm and

Line Automatic Switch condition for Main slot

M1

clear, and the system reports an unexpected CP type alarm and

Line

Automatic Switch condition for Main slot

M2

.

.................................................................................................................................................................................................

Open a faceplate latch on the OC-48 OLIU circuit pack in Main slot

M2

. If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Disconnect the optical fibers from the OC-48 OLIU circuit pack in Main slot

M2

. Then replace the OC-48 OLIU circuit pack in Main slot

M2

with the temporary replacement OC-48 OLIU circuit pack.

Result:

The temporary replacement OC-48 OLIU circuit pack in Main slot

M2

is tested and autoprovisioned.

The unexpected CP type alarm for Main slot

M2

clears. The system reports an unexpected circuit pack type condition and an inc. OC48 LOS alarm for Main slot

M2

.

Reference:

Procedure 4-2: “Install OLIU circuit packs in Main slots” (p. 4-7)

.................................................................................................................................................................................................

At both ends of the optical span, perform the following to connect the temporary replacement OC-48 OLIU circuit pack in Main slot

M2

and the required OC-48 circuit pack/port at the opposite end of the OC-48 optical span:

1. Clean and connect the transmit optical fibers.

2. Measure the optical receive power of the receive fibers using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Metropolis

®

DMX Access

Multiplexer Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OC-48 circuit packs.)

3. Clean and connect the receive fibers.

Result:

The inc. OC48 LOS alarm for Main slot

M2

clears, and the system still reports an unexpected circuit pack type condition for Main slot

M2

.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

STOP!

End of Procedure. The upgrade procedure is now temporarily suspended and traffic is supported to the adjacent nodes.

To resume the upgrade, replace the temporary replacement OC-48 OLIU circuit pack in Main slot

M2

with the OC-192 OLIU circuit pack. Refer to

Procedure

12-11: “Upgrade OC-48 BLSR to OC-192 BLSR” (p. 12-223) .

To back out the upgrade, refer to

Procedure 12-12: “Back out OC-48 BLSR to

OC-192 BLSR upgrade” (p. 12-262) .

.................................................................................................................................................................................................................................

12-300 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

11

Procedure 12-13: Suspend OC-48 BLSR to OC-192

BLSR upgrade

.................................................................................................................................................................................................

Important! Main slot

M1

has been upgraded and the node was originally equipped with LNW27 (Series 1:6 and later), LNW29 (Series 1:6 and later), LNW32,

LNW76 (Series 1:6 and later), or LNW221-259 (Series 1:6 and later) OC-48 OLIU circuit packs.

If an unexpected circuit pack type condition is reported for Main slot

M1

, select

Configuration

→

Update System

→

Update All

, then select

main-1

(default) as the

Ring Upgrade Choice and click

OK

. Otherwise, the node is already in the proper suspend configuration and no further action is required.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The unexpected circuit pack type condition for Main slot

M1

clears, and the system reports an unexpected circuit pack type condition for Main slot

M2

.

STOP!

End of Procedure. The upgrade procedure is now temporarily suspended and traffic is supported to the adjacent nodes.

To resume the upgrade, replace the OC-48 OLIU circuit pack in Main slot

M2

with the OC-192 OLIU circuit pack. Refer to

Procedure 12-11: “Upgrade OC-48 BLSR to OC-192 BLSR” (p. 12-223) .

To back out the upgrade, refer to

Procedure 12-12: “Back out OC-48 BLSR to

OC-192 BLSR upgrade” (p. 12-262) .

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-301

Ring and circuit pack upgrade procedures

BLSR example

N

(Starting Node)

West East

MAIN-1 MAIN-2

East

N+3

West

MAIN-2

East

N+2

MAIN-1

West

West

N+1

East

Procedure 12-13: Suspend OC-48 BLSR to OC-192

BLSR upgrade nc-dmx-256

.................................................................................................................................................................................................................................

12-302 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

.................................................................................................................................................................................................................................

Overview

Use this procedure to perform an in-service upgrade of an existing DDM-2000 OC-3

or OC-12 UPSR ( Figure 12-1, “Initial configuration for upgrade” (p. 12-305) ) to a

Metropolis

®

DMX OC-48/192 UPSR. This procedure establishes a final configuration

( Figure 12-7, “Final configuration in upgrade sequence” (p. 12-317) ) with the

Metropolis

®

DMX OC-48/192 UPSR serving as a backbone ring for the subtending

OC-3/OC-12 ring.

Privilege level

You must log in as a Privileged user to complete this procedure.

Required equipment

The following equipment is required:

•

Wrist strap

•

Optical power meter, to measure the level of received power

•

Appropriate optical LBOs

•

Technical assistance at the two (East and West) adjacent nodes.

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Notify the maintenance center of these planned upgrade activities and that alarms will be generated.

3. At each DDM-2000 OC-3 or OC-12 UPSR node, verify that no alarms, lockouts, loopbacks, or switches are present. Refer to the DDM-2000 User Service Manual

(USM) if you need additional instruction. Any existing alarms must be cleared before starting this procedure.

4. This procedure is used to update a DDM-2000 OC-3/12 UPSR to a Metropolis

®

DMX OC-48/192 UPSR. It is assumed that the fiber being used in the current

OC-3/12 ring will be used to build the new Metropolis

®

DMX UPSR.

5. With minor changes, this procedure may also be used to move VT1.5 service onto an existing OC-48/192 ring. The fiber connecting the OC-48/192 nodes at each site would already be connected and the OC-48/192 ring would already be carrying service.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-303

Ring and circuit pack upgrade procedures Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

6. This procedure uses an existing 3 node DDM-2000 OC-3/12 ring as an example for the OC-3/12 to OC-48/192 ring upgrade (See

Figure 12-1, “Initial configuration for upgrade” (p. 12-305) ). Other OC-3/12 network upgrades are possible and can be

done using this procedure with minor modifications. Local procedures will have to be written, using the concepts of this procedure, to upgrade the particular configuration that you have.

7. This procedure assumes that a Metropolis

®

DMX has been installed and equipped

( Procedure 5-1: “Equip new Metropolis

®

DMX Access Multiplexer with OLIUs in

Main slots” (p. 5-3) ) at each existing OC-3/12 shelf location. The Metropolis

®

DMX shelf must be equipped with Main OLIUs and OC-3/12 OLIUs (in the

Function Group or Growth slots being used to connect to the DDM-2000).

8. The application parameter of the OC-3/12 interfaces on the Metropolis

®

DMX must be set to

0x1

(Release 2 and earlier) or

UPSR

in Release 3 or later.

Note that in Release 3 or later, the

0X1

application parameter is no longer valid, and you have to use the

UPSR

application parameter for this configuration. A new parameter has been added to the cross-connection command to accomplish the function of 0X1 application. The new cross-connection parameter is channel application (

chappl)

, with a value of

UNSWITCHED

.

9. TARP Release 15 or later ring software must be installed on the DDM-2000 shelves.

10. You may also contact Lucent Technologies to perform this in-service upgrade.

Experienced Lucent Technologies installers will help you plan and execute the network upgrade. For more information, contact your Lucent Technologies Account

Representative.

.................................................................................................................................................................................................................................

12-304 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Step

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

1

Complete the following steps to convert an in-service OC-3/12 UPSR to a Metropolis

®

DMX OC-48/192 UPSR.

.................................................................................................................................................................................................

Reference

Figure 12-1, “Initial configuration for upgrade” (p. 12-305)

as the starting point for this procedure.

Figure 12-1 Initial configuration for upgrade

Node 2

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 1

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 3

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 2

OC-3/12

MAIN 2

OLIU

IN

OUT

A B

MAIN 1

OLIU

OUT

IN

C

Node 1

OC-3/12

MAIN 1

OLIU

IN

OUT

A B

MAIN 2

OLIU

OUT

IN

C

Node 3

OC-3/12

MAIN 1

OLIU

IN

OUT

A B

MAIN 2

OLIU

OUT

IN

C nc-dmx-034

2

.................................................................................................................................................................................................

At each Metropolis

®

DMX node, connect the PC and establish a WaveStar

®

CIT session.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-305

Ring and circuit pack upgrade procedures

3

4

5

6

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

At each Metropolis

®

DMX node, use the

Configuration

→

DCC Terminations

command to verify/set Network Side/User Side parameters at each end of the optical span being established.

Refer to the DDM-2000 user manual to verify/set NS/US parameters for this configuration.

Note that if the default settings were not changed in the DDM-2000 ring configuration and the default settings are retained in the Function or Growth slots of the Metropolis

®

DMX node, no changes should be required.

Important! The requirement is that one end of the optical fiber connection must be set to Network-Side and the other end must be set to User-Side.

.................................................................................................................................................................................................

Refer to office records and verify that no duplicate TID settings exist among the existing network nodes and the new network nodes.

Important! If duplicate TIDs exist, they must be resolved before continuing. As appropriate, refer to

Procedure 7-11: “Set/change system TID” (p. 7-38)

to change a Metropolis

®

DMX TID. Or, to the User Service Manual of the OC-3/OC-12 subtending shelf.

If you need additional instructions to help you complete this step on the

DDM-2000 NEs, refer to the DDM-2000 documentation.

.................................................................................................................................................................................................

At the Metropolis

®

DMX Nodes (1, 2, and 3 in this example) use the

Configuration

→

Provision

command to verify/set the

Application

parameter to 0x1 (Release 2 and earlier) or

UPSR

(Release 3 and later) for the OC-3 or OC-12 interfaces that are being used for this single-homed configuration.

Reference:

(p. 4-22)

Procedure 4-4: “Provision OLIU circuit packs/ports for service”

.................................................................................................................................................................................................

At each of the Metropolis

®

DMX host nodes (nodes 1, 2, and 3 in this example), determine and provision the add/drop cross-connections to support each single-homed

OC-3 or OC-12 node. From the System View menu, select

Configuration

→

Cross-Connections

to start the Cross-Connection Wizard. Refer to

Procedure 10-8:

“Make single-homed cross-connections” (p. 10-32) .

.................................................................................................................................................................................................................................

12-306 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

7

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

Important! Refer to the OLIU circuit pack descriptions in the descriptive chapters of this document to find the cross-connection capacities for Virtual Tributaries

(VTs) for the OLIU circuit packs in the Metropolis

®

DMX.

Any channels that are presently in service or cross-connected in the existing

DDM-2000 ring must be cross-connected to the single-homed Function or Growth group OLIUs in the Metropolis

®

DMX nodes.

In the case of a VT1.5 signal, the same STS-1 may be cross-connected to the

OC-3/12 shelves at several Metropolis

®

DMX nodes until the STS-1 signal reaches its capacity of 28 VT1.5 signals.

In Release 3 or later, note that the single-homed cross-connections to the

DDM-2000 shelves must be cross-connected in the Metropolis

®

DMX from the main OLIUs to the Function or Growth OLIUs using the cross-connection parameter of

chappl

=

UNSWITCHED

.

The connection between the DDM-2000 and Metropolis

®

DMX is a single-homed connection. In single-homed connections, the Function Group slot A1, B1, C1, D1, or Growth slot G1 OLIU in the Metropolis

®

DMX host shelf connects to the M1

OLIU at the first DDM-2000 shelf from the Metropolis

®

DMX host shelf. M2

OLIU at the first DDM-2000 shelf connects to Function Group slot A2, B2, C2,

D2, or Growth slot G2 OLIU in the Metropolis

®

DMX host shelf. This procedure establishes the ring configuration starting from the Metropolis

®

DMX host node to the far-end DDM-2000 shelf and back to the host node.

.................................................................................................................................................................................................

At each Metropolis

®

DMX shelf, determine the channels to be pass-through cross-connected in the Metropolis

®

DMX. Use

Configuration

→

Cross-Connections

at each required Metropolis

®

DMX shelf to make all required pass-through cross-connections for the previously selected channels.

Important! At each Metropolis

®

DMX node in the ring, pass-through cross-connections must be made for each channel that is carrying traffic and that has not been cross-connected to a circuit pack in a Function or Growth slot in that

Metropolis

®

DMX node. Critical or Major alarms will be generated if pass-through cross-connections are not made on each required Metropolis

®

DMX shelf in the ring.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-307

Ring and circuit pack upgrade procedures

8

9

10

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

Note that in the examples in this procedure there are no pass-through Metropolis

®

DMX nodes. All the Metropolis

®

DMX nodes serve as host nodes to support the single homed configuration. As an example, if another Metropolis

®

DMX node was placed between Metropolis

®

DMX Node 1 and Node 2, then you would provision the necessary pass-through cross-connections at that node.

.................................................................................................................................................................................................

At all Metropolis

®

DMX shelves in the network, select

Configuration

→

Timing/Sync

and click on the tab labeled System Timing and for the box that is labeled

Synchronization Autoreconfiguration select option disabled.

Important! Sync auto-reconfiguration is disabled during this upgrade to avoid timing hits and unnecessary alarms. After the upgrade is completed, it is recommended that sync auto-reconfiguration be enabled at all nodes in the network.

.................................................................................................................................................................................................

As appropriate, at each Metropolis

®

DMX node, select

Configuration

→

DCC

Terminations

and for the field DCC Channel Parameter Termination State select option enabled.

Important! An inconsistent DCC values alarm occurs when the Metropolis

®

DMX

OLIUs are looped back and fecom is enabled. The alarm clears as the OLIU loopbacks are removed and the Metropolis

®

DMX and DDM-2000 shelves are interconnected.

.................................................................................................................................................................................................

Starting at any location, disconnect the fiber pair between one DDM-2000 shelf and a neighboring DDM-2000 shelf.

.................................................................................................................................................................................................................................

12-308 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

For example, in

Figure 12-2, “First figure in upgrade sequence” (p. 12-309) , disconnect

the fiber pairs between DDM-2000 Node 1 and DDM-2000 Node 2. If required, use these fibers to connect Metropolis

®

DMX Node 1 and Metropolis

®

DMX Node 2.

Figure 12-2 First figure in upgrade sequence

Node 2

®

Metropolis DMX

Fibers added

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 1

®

Metropolis DMX

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Fibers removed

Node 2

OC-3/12

MAIN 2

OLIU

IN

OUT

A B

MAIN 1

OLIU

OUT

IN

C

Node 1

OC-3/12

MAIN 1

OLIU

IN

MAIN 2

OLIU

OUT

OUT

A B

IN

C

New Connection

Node 3

®

Metropolis DMX

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 3

OC-3/12

MAIN 1

OLIU

IN

MAIN 2

OLIU

OUT

OUT

A B

IN

C nc-dmx-035

Important! A protection switch may occur when fibers are removed and cause a transmission hit. This procedure begins at one location and progresses around the ring until all optical fiber connections are made.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-309

Ring and circuit pack upgrade procedures

11

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

At Metropolis

®

DMX Node 1, connect the optical fibers from DDM-2000 Node 1

MAIN1 slot to Metropolis

®

DMX Function Group Slot A1, B1, C1, D1, or Growth slot G1. See

Figure 12-3, “Second figure in upgrade sequence” (p. 12-311) .

.................................................................................................................................................................................................................................

12-310 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

12

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

At Metropolis

®

DMX Node 2, connect the optical fibers from DDM-2000 Node 2

MAIN2 slot to Metropolis

®

DMX Function Group Slot A2, B2, C2, D2, or Growth slot G2. See

Figure 12-3, “Second figure in upgrade sequence” (p. 12-311) .

Figure 12-3 Second figure in upgrade sequence

Node 2

®

Metropolis DMX

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 1

®

Metropolis DMX

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 2

OC-3/12

MAIN 2

OLIU

IN

OUT

A B

MAIN 1

OLIU

OUT

IN

C

Node 3

®

Metropolis DMX

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 1

OC-3/12

MAIN 1

OLIU

IN

MAIN 2

OLIU

OUT

OUT

A B

IN

C

Node 3

OC-3/12

MAIN 1

OLIU

IN

MAIN 2

OLIU

OUT

OUT

A B

IN

C

New Connection nc-dmx-036

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

13

Click on the Alarm List button and verify that no alarms are being reported for channels that are connected between MAIN-1 of the DDM-2000 shelf at Node 1

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-311

Ring and circuit pack upgrade procedures

14

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

(through the Metropolis

®

DMXs at Nodes 1 and 2) and MAIN-2 of the DDM-2000 at

Node 2. If there are any alarms, recheck the cross-connections at the Metropolis

®

DMXs.

.................................................................................................................................................................................................

See

Figure 12-4, “Third figure in upgrade sequence” (p. 12-312) . Disconnect the fiber

pair between DDM-2000 Nodes 2 and 3. If required, use these fibers to connect

Metropolis

®

DMX Node 2 and Node 3.

Figure 12-4 Third figure in upgrade sequence

Node 2

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Fibers added

Node 1 Node 3

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 2

OC-3/12

MAIN 2

OLIU

IN

OUT

A B

MAIN 1

OLIU

OUT

IN

C

Fibers removed

Node 1

OC-3/12

MAIN 1

OLIU

IN

MAIN 2

OLIU

OUT

OUT

A B

IN

C

New Connection

Node 3

OC-3/12

MAIN 1

OLIU

IN

MAIN 2

OLIU

OUT

OUT

A B

IN

C nc-dmx-037

.................................................................................................................................................................................................................................

12-312 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

15

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

See

Figure 12-5, “Fourth figure in upgrade sequence” (p. 12-314) . At Metropolis

®

DMX Node 2, connect the optical fibers from DDM-2000 Node 2 MAIN1 slot to

Metropolis

®

DMX Function Group slot A1, B1, C1, D1, or Growth slot G1.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-313

Ring and circuit pack upgrade procedures

16

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

At Metropolis

®

DMX Node 3, connect the optical fibers from DDM-2000 Node 3

MAIN2 slot to Metropolis

®

DMX Function Group slot A2, B2, C2, D2, or Growth slot

G2. See

Figure 12-5, “Fourth figure in upgrade sequence” (p. 12-314) .

Figure 12-5 Fourth figure in upgrade sequence

Node 2

®

Metropolis DMX

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 1

®

Metropolis DMX

Fibers added

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 2

OC-3/12

MAIN 2

OLIU

IN

OUT

A B

MAIN 1

OLIU

OUT

IN

C

Node 3

®

Metropolis DMX

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Fibers added

Node 1

OC-3/12

MAIN 1

OLIU

IN

OUT

A B

MAIN 2

OLIU

OUT

IN

C

Node 3

OC-3/12

MAIN 1

OLIU

IN

OUT

A B

MAIN 2

OLIU

OUT

IN

C

New Connection nc-dmx-038

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

17

Click on the Alarm List button and verify that no alarms are being reported for channels that are connected between MAIN-1 of the DDM-2000 shelf at Node 2

.................................................................................................................................................................................................................................

12-314 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

18

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

(through the Metropolis

®

DMXs at Nodes 2 and 3) and MAIN-2 of the DDM-2000 at

Node 3. If there are any such alarms, recheck the cross-connections at the Metropolis

®

DMXs.

.................................................................................................................................................................................................

See

Figure 12-6, “Fifth figure in upgrade sequence” (p. 12-315) . Disconnect the fiber

pair between DDM-2000 Nodes 2 and 3. If required, use these fibers to connect

Metropolis

®

DMX Nodes 1 and 3.

Figure 12-6 Fifth figure in upgrade sequence

Node 2

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Fibers added

Node 1

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Fibers added

Node 3

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 2

OC-3/12

MAIN 2

OLIU

IN

OUT

A B

MAIN 1

OLIU

OUT

IN

C

Node 1

OC-3/12

MAIN 1

OLIU

IN

MAIN 2

OLIU

OUT

OUT

A B

IN

C

Fibers Removed

Node 3

OC-3/12

MAIN 1

OLIU

IN

MAIN 2

OLIU

OUT

OUT

A B

IN

C

New Connection nc-dmx-039

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-315

Ring and circuit pack upgrade procedures

19

20

21

22

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

See

Figure 12-7, “Final configuration in upgrade sequence” (p. 12-317) . At

Metropolis

®

DMX Node 3, connect the optical fibers from DDM-2000 Node 3 MAIN1 slot to Metropolis

®

DMX Function Group slot A1, B1, C1, D1, or Growth slot G1.

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

At Metropolis

®

DMX Node 1, perform the optical fiber connections from DDM

MAIN2 slot to Metropolis

®

DMX Function Group Slot A, B, C, D, or G 2. See

Figure

12-7, “Final configuration in upgrade sequence” (p. 12-317) .

Reference:

Procedure 14-4: “Perform connection and verification of optical facility” (p. 14-44)

.................................................................................................................................................................................................

Click on the Alarm List button and verify that no alarms are being reported for channels that are connected between MAIN-1 of the DDM shelf at Node 3 (through the Metropolis

®

DMXs at Nodes 3, 2, and 1) and MAIN-2 of the DDM at Node 1. If there are any such alarms, recheck the cross-connections at the Metropolis

®

DMXs.

.................................................................................................................................................................................................

Refer to the work instructions and determine the timing/synchronization plan for each node. Select

Configuration

→

Timing/Sync

from the System View menu at each node. Click on the tab that is labeled System Timing and select the appropriate options for that particular node.

Important! The simplest timing configuration would be to set one Metropolis

®

DMX node to receive external timing from the BITS clock, and all other nodes in the network to receive line timing. Many other timing configurations are possible.

.................................................................................................................................................................................................................................

12-316 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

23

Procedure 12-14: Upgrade OC-3 or OC-12 UPSR to a

Metropolis

®

DMX OC-48/192 UPSR

.................................................................................................................................................................................................

At any one of the Metropolis

Map

®

DMX nodes select

Administration

→

OSI Routing

in order to verify that the UPSR is functional.

Figure 12-7 Final configuration in upgrade sequence

Node 2

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 1

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Node 3

IN

MAIN 2

OLIU

OUT

MAIN 1

OLIU

OUT

IN

A1 A2 B1 B2 C1 C2 D1 D2 G1 G2

Fibers added

Node 2

OC-3/12

MAIN 2

OLIU

IN

OUT

A B

MAIN 1

OLIU

OUT

IN

C

Node 1

OC-3/12

MAIN 1

OLIU

IN

MAIN 2

OLIU

OUT

OUT

A B

IN

C

Fibers added

Node 3

OC-3/12

MAIN 1

OLIU

IN

MAIN 2

OLIU

OUT

OUT

A B

IN

C

New Connection nc-dmx-040

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-317

Ring and circuit pack upgrade procedures

Procedure 12-15: Upgrade low-speed electrical circuit packs

.................................................................................................................................................................................................................................

Overview

Use this procedure to upgrade the following in-service low-speed electrical circuit packs in a function unit.

•

LNW6 28DS1 to high-density LNW8 56DS1/E1

•

LNW7 28DS1PM to high-density LNW8 56DS1/E1

•

LNW16 12DS3/EC1 to high-density LNW19/LNW19B 48DS3/EC1

Important! The high-density circuit packs are only compatible with the

Metropolis

®

DMX High Capacity Shelf. The standard Metropolis

®

DMX Shelf does not support the high-density circuit packs. If a high-density circuit pack is installed in the standard Metropolis

®

DMX Shelf, the system will not recognize the circuit pack as an allowable type.

To determine the shelf type, select

View

→

Equipment

, highlight Shelf, and click

Select

to obtain the shelf details. The Shelf Type is DMX-HC-30A for the

Metropolis

®

DMX High Capacity Shelf.

Important! The system does not support mixing standard density and high-density circuit packs in the same Function unit. Both slots of a Function unit must be equipped with the same circuit pack type.

Important! An upgrade from an LNW6/7 to an LNW8 is denied if either of the following situations occur:

•

Available VT resources are not sufficient to support the cross-connections to the

LNW8.

•

The upgrade would result in a source and destination conflict of VT bandwidth.

Refer to the Metropolis

®

DMX Access Multiplexer Applications and Planning

Guide, 365-372-300 for more information about the assignment of VT bandwidth.

Important! If an LNW19 48DS3/EC1 circuit pack and an LNW19B 48DS3/EC1 circuit pack are installed in the same Function unit, then both circuit packs function as an LNW19 48DS3/EC1 circuit pack. Therefore, the LNW19B 48DS3/EC1 circuit pack would not support DS3 terminal loopbacks.

Privilege level

You must log in as either a Privileged or General user to complete this procedure.

.................................................................................................................................................................................................................................

12-318 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-15: Upgrade low-speed electrical circuit packs

Required equipment

The following equipment is required to perform this procedure:

•

Wrist strap

•

Two replacement high-density circuit packs for each Function unit to be upgraded.

Release 3.1 or later software is required to support the high-density LNW8 56DS1/E1 and LNW19 48DS3/EC1 circuit packs.

Release 5.0 or later software is required to support the high-density LNW19B

48DS3/EC1 circuit packs.

CAUTION

Equipment damage

Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.

Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs in to or out of the shelf slot.

CAUTION

Service disruption hazard

Removing or installing circuit packs during a System Reset can cause system errors.

Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.

Before you begin

Prior to performing this procedure:

1. Refer to

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Obtain the work instructions for this procedure, and verify that the affected circuit pack/protection group AIDs are specified.

3. Verify that the circuit packs to be upgraded are protected. Both Function unit slots

(

A

,

B

,

C

,

D

)

1

and (

A

,

B

,

C

,

D

)

2

must be equipped before performing this procedure. If necessary, install the companion circuit pack. Refer to

Procedure 4-6: “Install

DS3/EC1 circuit packs” (p. 4-32)

or

Procedure 4-8: “Install DS1/E1 circuit packs”

(p. 4-39) .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-319

Ring and circuit pack upgrade procedures Procedure 12-15: Upgrade low-speed electrical circuit packs

4. Verify that the DS1 and/or DS3 cables necessary to support the high-density circuit packs have already been installed. Refer to the Metropolis

®

DMX Access

Multiplexer Installation Manual, 365-372-304 for cabling information.

5. Review the applicable Metropolis

®

DMX Access Multiplexer Software Release

Description for any detailed procedures or cautions that may apply to this upgrade procedure.

Step

1

2

3

Complete the following steps to upgrade the in-service low-speed electrical circuit packs in a function unit.

.................................................................................................................................................................................................

Click the

Alarm List

button in the top right corner of the System View or select

Fault

→

NE Alarm List

to view the NE Alarm List and verify that no alarms are present.

Refer to the appropriate trouble clearing procedures to clear all existing alarms before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

To verify that no loopbacks, protection switch lockouts, or protection switches are present, select

View

→

Rolling Events

. Under the line reading

RTRV-COND-ALL determine if any loopbacks, protection switch lockouts, or protection switches are displayed.

Remove all existing loopbacks, protection switch lockouts, or protection switches before continuing with this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and verify that no test access sessions exist.

Select

Fault

→

Analysis

→

Test Access

to access the Test Access Wizard and delete all existing test access sessions.

Reference:

•

Procedure 14-27: “View test access session(s)” (p. 14-130)

•

Procedure 14-26: “Delete test access session” (p. 14-129)

.................................................................................................................................................................................................................................

12-320 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-15: Upgrade low-speed electrical circuit packs

.................................................................................................................................................................................................

4

If upgrading...

DS1 circuit packs,

DS3/EC1 circuit packs,

Then...

Continue with

Proceed to

Step 5

Step 6 .

.

5

6

.................................................................................................................................................................................................

Important! When the standard density DS1 circuit pack in slot (

A

,

B

,

C

,

D

)

2

is removed, transmission hits occur causing the system to report the inc. (from

DSX) DS1 sig. failed condition. Depending on the provisioned value of the DS1 port Signal Degrade threshold, it may take up to 20 minutes for the inc. (from

DSX) DS1 sig. failed condition to automatically clear. It is recommended that the DS1 port Signal Degrade threshold be provisioned 10E-3 to minimize the time it takes the system to clear the condition. The original DS1 port Signal Degrade threshold can be reprovisioned when the upgrade is complete.

From System View select

Reports

→

Equipment Lists

→

Port

. Click on the DS1 circuit pack in slot (

A

,

B

,

C

,

D

)

2

and

Select

. Record the Signal Degrade threshold of each DS1 port. If required, provision the Signal Degrade threshold of the DS1 ports to

10E-3.

Reference:

(p. 4-42)

Procedure 4-9: “Provision DS1/E1 circuit packs/ports for service”

.................................................................................................................................................................................................

Important! Local operating procedures for removing a circuit pack may vary. One method is to simply remove the circuit pack. Another method is to verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then remove the circuit pack.

Determine the local operating procedures for removing a circuit pack before removing the circuit pack in slot (

A

,

B

,

C

,

D

)

1

.

If the local operating procedures specify

{ remove the circuit pack, verify the circuit pack active/standby status, perform manual switches if the circuit pack is active, and then remove the circuit pack,

Then...

Proceed to

Step 9 .

Continue with

Step 7 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-321

Ring and circuit pack upgrade procedures Procedure 12-15: Upgrade low-speed electrical circuit packs

7

8

9

10

.................................................................................................................................................................................................

Important! The circuit pack in slot (

A

,

B

,

C

,

D

)

1

must be replaced first. Perform this step to determine if the circuit pack in slot (

A

,

B

,

C

,

D

)

1

is active for transmission.

From the System View select

Reports

→

Status Lists

→

Pack

. Click on Shelf and

Select

. Observe the value of the Switch State parameter for the required fn-{a,b,c,d}-1 circuit pack (according to the work instructions). If the Switch State parameter is

active, the circuit pack in slot (

A

,

B

,

C

,

D

)

1

is the active circuit pack for transmission.

Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the circuit pack in slot (

A

,

B

,

C

,

D

)

1

is the active circuit pack for transmission, then a manual switch must be performed before replacing the circuit pack.

If the circuit pack in slot (

A

,

B

,

C

,

D

)

2

is the active circuit pack for transmission, do not perform this step.

To perform a manual transmission switch, select

Fault

→

Protection Switch

. Click on the required 1+1 Equip protection group (according to the work instructions) and

Select

. Select the Manual (Normal) Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

. Then click

Close

.

.................................................................................................................................................................................................

Replace the circuit pack in slot (

A

,

B

,

C

,

D

)

1

with the replacement high-density circuit pack.

Result:

If a circuit pack firmware update is required, the system reports the

Waiting for Download and

Install Program IP slot conditions when the replacement high-density circuit pack is inserted in the slot. After the circuit pack firmware update is complete, the system reports an unexpected CP type alarm for slot (

A

,

B

,

C

,

D

)

1

.

If a circuit pack firmware update is not required, the system reports an unexpected

CP type alarm for slot (

A

,

B

,

C

,

D

)

1

when the replacement high-density circuit pack is inserted.

.................................................................................................................................................................................................

Important! The

UPD/INIT

button does not work during this upgrade.

From the System View select

Configuration

→

Update System

→

Update All

.

.................................................................................................................................................................................................................................

12-322 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-15: Upgrade low-speed electrical circuit packs

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

The replacement high-density circuit pack in slot (

A

,

B

,

C

,

D

)

1

is autoprovisioned, and the system performs an automatic circuit pack protection switch. Active traffic is automatically switched from the circuit pack in slot (

A

,

B

,

C

,

D

)

2

, to the circuit pack in slot (

A

,

B

,

C

,

D

)

1

.

If upgrading DS1 circuit packs, transmission hits (up to 130 ms) occur as the automatic switches are performed.

All traffic is now active on the circuit pack in slot (

A

,

B

,

C

,

D

)

1

.

The unexpected CP type alarm for slot (

A

,

B

,

C

,

D

)

1

, clears, and the system reports an

CP not allowed - eqpt alarm for slot (

A

,

B

,

C

,

D

)

2

.

.................................................................................................................................................................................................

11

Important! When a standard density LNW6 28DS1 or LNW7 28DS1PM circuit pack is removed from slot (

A

,

B

,

C

,

D

)

2

, transmission hits occur causing the system to report and automatically clear the inc. (from DSX) DS1 sig. failed condition.

Replace the other circuit pack in the companion slot (

A

,

B

,

C

,

D

)

2

with the replacement high-density circuit pack.

Result:

The replacement high-density circuit pack in slot (

A

,

B

,

C

,

D

)

2

is autoprovisioned and all alarms clear.

12

.................................................................................................................................................................................................

From the System View select

View

→

Refresh System View

to update the graphical circuit pack and port information currently displayed for the network element.

Result:

A warning message appears asking you to confirm executing this command. Click

Yes

.

The graphical circuit pack and port information displayed in the System View is updated to show the replacement high-density circuit packs and additional ports.

.................................................................................................................................................................................................

13

If upgrading...

DS1 circuit packs,

DS3/EC1 circuit packs,

Then...

Continue with

Proceed to

Step 14

Step 15 .

.

14

.................................................................................................................................................................................................

If required, provision the Signal Degrade threshold of the DS1 ports to the original values recorded in

Step 5 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-323

Ring and circuit pack upgrade procedures Procedure 12-15: Upgrade low-speed electrical circuit packs

15

16

Reference:

(p. 4-42)

Procedure 4-9: “Provision DS1/E1 circuit packs/ports for service”

.................................................................................................................................................................................................

This completes the low-speed electrical circuit pack upgrade in a Function unit. If the low-speed electrical circuit packs in other Function units are to be upgraded at this node, repeat

Step 4

through

Step 14 ; otherwise, continue with the next step.

.................................................................................................................................................................................................

Important! It is recommended that the network element database be backed up to a remote OS (for example, the Navis

®

Optical Element Management System) after an upgrade. This creates a current backup copy that includes the replacement circuit packs. The remote OS could use this backup copy to restore the network element database in the event of a catastrophic failure. Attempts to restore the network element database using a backup copy created prior to the upgrade may result in circuit pack failures.

Back up the network element database using the

Configuration

→

Software

→

Remote Backup

command.

Reference:

•

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123)

•

Procedure 2-9: “Backup and restore NE database via FTTD” (p. 2-135)

•

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-324 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-16: Upgrade or replace SYSCTL (LNW2) circuit pack

.................................................................................................................................................................................................................................

Overview

Use this procedure to upgrade/replace a SYSCTL (LNW2) circuit pack in an in-service shelf.

If you wish to upgrade an LNW1 to an LNW2, you must use either

Procedure 2-3:

“Upgrade software generic via FTAM” (p. 2-40)

or

Procedure 2-4: “Upgrade software generic via FTP” (p. 2-72) .

Important! Performing this procedure under the following scenarios may cause transmission losses and/or require a restore from a remote backup file.

•

While the SYSCTL is removed, DO NOT remove or replace either Main circuit pack (M1, M2).

•

If an equipped Main (M1 or M2) is removed from the NE, DO NOT replace the SYSCTL.

•

DO NOT remove the SYSCTL, put it into another NE, then return it to the original NE (unless another SYSCTL has been installed in the original NE during the interim).

Required equipment

The following equipment is required:

•

At least one of the following cables:

– RS-232 cable with an RJ-45 connector on one end and a PC serial connector on the other (typically DB9) for the

RS232

port

– CAT5 Ethernet cable with either a 10/100 hub or a cross-over cable for the front

LAN

or

J16 IAO LAN

ports

•

Personal computer (PC) with WaveStar

®

CIT software installed

•

Wrist strap

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-325

Ring and circuit pack upgrade procedures Procedure 12-16: Upgrade or replace SYSCTL (LNW2) circuit pack

CAUTION

Service disruption hazard

Failure to equip the expected circuit packs in the shelf and clear any circuit pack-related alarms before replacing the SYSCTL circuit pack can result in a loss of transmission. If this occurs, you can recover transmission by equipping the expected circuit packs and restoring the database.

Equip an expected circuit pack in every slot for which there is an expected circuit pack type.

If the network element is reporting any

CP removed

,

CP not allowed

, or

Unexpected

CP type

alarms, do NOT replace the SYSCTL circuit pack.

Before you begin

Prior to performing this procedure:

1. Refer to

“Electrostatic discharge” (p. 1-14)

information in

Chapter 1, “Safety” .

2. Ensure that an LNW2 SYSCTL circuit pack is available for replacement.

3. Restoring the network element database may be service-affecting. If provisioning changes were made after the last backup files were created, examine the security log and use the appropriate WaveStar

®

CIT commands to manually apply the recent provisioning changes to the just-restored database.

Procedure 2-8: “Backup and restore NE database via FTP” (p. 2-123)

or

Procedure 2-9:

“Backup and restore NE database via FTTD” (p. 2-135)

or

Procedure 2-10: “Backup and restore NE database via FTAM” (p. 2-150)

Important! If you wish to upgrade an LNW1 to an LNW2, you must use either

Procedure 2-3: “Upgrade software generic via FTAM” (p. 2-40)

or

Procedure 2-4:

“Upgrade software generic via FTP” (p. 2-72) .

.................................................................................................................................................................................................................................

12-326 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Step

Procedure 12-16: Upgrade or replace SYSCTL (LNW2) circuit pack

1

Complete the following steps to replace an LNW2 SYSCTL with an LNW2 SYSCTL.

.................................................................................................................................................................................................

Do you wish to use the upgrade/replace your LNW2 SYSCTL by replacing NVMs or by using Maintenance Mode Wizard (FTP or FTAM)?

If...

NVM replacement

(recommended method)

FTAM

FTP

Then...

You must have physical access to your shelf and controller. Your LNW2 may be functioning or failed.

Proceed to

Procedure 12-16.1: “Upgrade or replace SYSCTL (LNW2) by replacing NVMs”

(p. 12-330) .

Continue with

Step 2 .

Your LNW2 must be functioning; not failed.

Continue with

Step 2 .

Your LNW2 must be functioning; not failed.

2

3

.................................................................................................................................................................................................

Connect the cross-over LAN cable from the PC’s Network Interface Card (NIC) to the rear

J16 IAO LAN

port on the Metropolis

®

DMX shelf backplane or the front

LAN

port on the SYSCTL circuit pack faceplate and establish a WaveStar

®

CIT session. (When

TCP/IP is enabled on the rear LAN port, OSI is disabled.)

Start the WaveStar

®

CIT software on the PC by double-clicking on the WaveStar

®

CIT icon on your desktop and login (if necessary). Refer to

Procedure 14-2: “Connect

Personal Computer (PC) and establish WaveStar

®

CIT session” (p. 14-24) .

Result:

The Network View appears.

.................................................................................................................................................................................................

From the

View:

pull-down menu, select

CIT OSI Neighbors

.

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-327

Ring and circuit pack upgrade procedures Procedure 12-16: Upgrade or replace SYSCTL (LNW2) circuit pack

Result:

The CIT OSI neighbor(s) are automatically detected.

If you were previously logged in to the NE and/or you do not see your NE, from the Network View, select

View

→

Refresh OSI View

.

Figure 12-8 CIT OSI neighbor

4

5

.................................................................................................................................................................................................

In the Network View,

Figure 12-8, “CIT OSI neighbor” (p. 12-328) , right-click on the

NE icon that was detected (default TID is LT-DMX, your TID may be different), and select

Graphical Using

→

OSI

from the resulting menu.

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX and click

OK

.

.................................................................................................................................................................................................................................

12-328 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16: Upgrade or replace SYSCTL (LNW2) circuit pack

6

7

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

In the NE login window, login to the shelf using your user ID and password.

Click

OK

.

.................................................................................................................................................................................................

Would you prefer to use FTAM or FTP to continue with the SYSCTL replacement?

If...

FTAM

FTP

Then...

You must have OSI connectivity (via your OSI

LAN or DCC) to your shelf.

Proceed to

Procedure 12-16.2: “Upgrade or replace SYSCTL (LNW2) circuit pack using

FTAM” (p. 12-332) .

You must have direct TCP/IP connectivity to your

NE and the NE must have a defined IP address.

Proceed to

Procedure 12-16.3: “Upgrade or replace SYSCTL (LNW2) circuit pack using

FTP” (p. 12-352) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-329

Ring and circuit pack upgrade procedures

Procedure 12-16.1: Upgrade or replace SYSCTL (LNW2) by replacing NVMs

.................................................................................................................................................................................................................................

Overview

Use this procedure to replace an LNW2 by replacing NVMs.

Important! You must have physical access to your shelf and controller.

Required equipment

Refer to

“Required equipment” (p. 12-325)

in

Procedure 12-16: “Upgrade or replace

SYSCTL (LNW2) circuit pack” (p. 12-325)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 12-16: “Upgrade or replace

SYSCTL (LNW2) circuit pack” (p. 12-325) .

Step

1

2

3

4

Complete the following steps to replace an LNW2 by replacing NVMs.

.................................................................................................................................................................................................

Initiate a ten-second countdown (9, 8, 7, 6, 5, 4, 3, 2, 1, 0) in the

IND

display on the

LNW2 SYSCTL by simultaneously depressing the

ACO TEST

and

SEL

buttons on the front of the LNW2 SYSCTL.

Important! Removing the LNW2 without initiating the ten-second countdown may result in unexpected and undesirable protection switches, incorrect circuit fault indications, or incoming signal failure alarms. All SYSCTL functions are suspended during the countdown.

.................................................................................................................................................................................................

Remove the LNW2 SYSCTL circuit pack during the 10-second countdown. This

LNW2 will be referred to as the “old” SYSCTL throughout this procedure.

Important! While the SYSCTL circuit pack is removed, do NOT remove or replace any transmission circuit packs.

.................................................................................................................................................................................................

Physically remove the NVMs from your old LNW2 and set them aside.

.................................................................................................................................................................................................

Remove the NVMs from your new (replacement) LNW2 and set them aside.

.................................................................................................................................................................................................................................

12-330 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.1: Upgrade or replace SYSCTL (LNW2) by replacing NVMs

5

6

7

.................................................................................................................................................................................................

Insert the NVMs that you removed from the old SYSCTL in

Step 3

in the empty NVM sockets in your new (replacement) LNW2.

.................................................................................................................................................................................................

Important! For software installation, two NVMs must be present in the LNW2

SYSCTL. You should have installed the NVMs from your old SYSCTL in your new SYSCTL.

Seat the new LNW2 SYSCTL circuit pack equipped with the NVMs from the old

SYSCTL and allow a few minutes for the pack to complete initialization.

Result:

The LNW2 SYSCTL exhibits the following visible cycles during initialization:

1. The

FAULT

LED lights and remains lighted for approximately 15 seconds. After approximately 15 seconds, a flashing

b

appears in the

IND

display on the

SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 60 seconds and then

IND

display is blank.

2. The

FAULT

LED remains lighted for approximately another 20 seconds and then extinguishes.

3. The

ACTIVE

LED lights and remains lighted.

4. A flashing

b

appears again in the

IND

display on the SYSCTL, indicating that a boot is in progress. After approximately 30 seconds, the

CR

LED flashes 10 times and then extinguishes, and the

b

continues flashing for approximately another 30 seconds, and then

IND

display is blank.

5. The

ACTIVE

LED remains lighted and the other LEDs return to their previous states; prior to the replacement.

6. Continue with

Step 7 .

.................................................................................................................................................................................................

Proceed to

Procedure 12-16.4: “Verify proper software generic” (p. 12-375) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-331

Ring and circuit pack upgrade procedures

Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

.................................................................................................................................................................................................................................

Overview

Use this procedure to replace an LNW2 using the File Transfer and Access

Management (FTAM) protocol.

Important! You must have OSI connectivity (via your OSI LAN or DCC) to the network element to use FTAM.

Required equipment

Refer to

“Required equipment” (p. 12-325)

in

Procedure 12-16: “Upgrade or replace

SYSCTL (LNW2) circuit pack” (p. 12-325)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 12-16: “Upgrade or replace

SYSCTL (LNW2) circuit pack” (p. 12-325) .

Step

Complete the following steps to replace your SYSCTL using FTAM.

1

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Remote Backup

.

.................................................................................................................................................................................................

In the pull-down

Backup To/Via:

menu, select

FTAM

.

2

3

.................................................................................................................................................................................................

In the

Source/Destination Directory Path

field, enter

backups/<filename>

.

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

.................................................................................................................................................................................................................................

12-332 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

4

5

If you wish to store your data in a subdirectory, you may enter

backups/<subdirectory>/<filename>

if the subdirectory exists before the command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.

.................................................................................................................................................................................................

Click

OK

.

You will be asked to verify that you wish to backup to the directory that you entered above. Click

Yes

if you typed the path correctly.

Result:

The Progress Indicator screen appears, indicating that the backup is in progress. When the backup completes, a

Remote Backup successful screen appears. Click

OK

. The backup file is now stored. If the default path and a subdirectory were used, the file may be found at:

C:/Program Files/Lucent Technologies/WaveStar

IT/backups/<subdirectory>/<filename>

.................................................................................................................................................................................................

Close your WaveStar

®

CIT session with the NE. From the System View, select

File

→

NE Disconnect

and click

Yes

in the confirmation window.

Result:

The System View closes.

6

7

8

.................................................................................................................................................................................................

Disconnect the LAN and/or serial cables from the

LAN

and/or

RS232

port(s) on the front of the LNW2 SYSCTL.

.................................................................................................................................................................................................

Initiate a ten-second countdown (9, 8, 7, 6, 5, 4, 3, 2, 1, 0) in the

IND

display on the

LNW2 SYSCTL by simultaneously depressing the

ACO TEST

and

SEL

buttons on the front of the LNW2 SYSCTL.

Important! Removing the LNW2 without initiating the ten-second countdown may result in unexpected and undesirable protection switches, incorrect circuit fault indications, or incoming signal failure alarms. All SYSCTL functions are suspended during the countdown.

.................................................................................................................................................................................................

Remove the SYSCTL circuit pack during the 10-second countdown.

Important! While the SYSCTL circuit pack is removed, do NOT remove or replace any transmission circuit packs.

.................................................................................................................................................................................................

9

Important! For installation, two NVMs must be present in the LNW2 SYSCTL. If either NVM is missing, an

NVM removed alarm will be issued. If both NVM

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-333

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

10

holders are empty, after the circuit pack is installed the

IND

displays an alternating

E

and

0

and

1

. Refer to

Step 10

for the complete listing of codes.

Seat the new LNW2 SYSCTL circuit pack and allow a few minutes for the pack to complete initialization.

Result:

The LNW2 SYSCTL exhibits the following visible cycles during initialization:

1. The

FAULT

LED lights and remains lighted for approximately 90 seconds. After approximately 15 seconds, a flashing

b

appears in the

IND

display on the

SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 75 seconds and then

IND

display is blank.

2. The

FAULT

LED remains lighted for approximately another 20 seconds and then extinguishes.

3. The

ACTIVE

LED lights and remains lighted and the

CR

LED flashes 10 times.

While the

CR

LED is flashing, the

MJ

,

ABN

, and

NE

LEDs light and remain lighted.

Because the LNW2 SYSCTL is in 6.0 Maintenance Mode, an alternating

M

and

P

and

6

and “

.

” (“.” is a red, four-segment square [2 x 2] representing a period) and

0

appear in the

IND

display.

4. Continue with

Step 10 .

.................................................................................................................................................................................................

Observe the

IND

display on the LNW2 SYSCTL; the display indicates the state of the

SYSCTL.

If...

alternating

M

and

P

and

6

and “

.

”

(“.” is a red, four-segment square

[2 x 2] representing a period) and

0

alternating

E

and

0

and

0

Then...

6.0 Maintenance Mode. Continue with

Step 11 .

alternating

E

and

0

and

1

alternating

E

and

0

and

2

LNW2 SYSCTL must be replaced.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

No NVMs are detected on the LNW2 SYSCTL.

Install two Lucent-supplied NVMs in the LNW2 or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

NVMs are present but not readable. Check to make sure they are properly seated and repeat this procedure.

.................................................................................................................................................................................................................................

12-334 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

If...

alternating alternating

Letter

F

alternating

Letter

U

E

E

N

and and and

0

1

O

and and and

3

0 x

flashing

b

A red, four-segment square (2 x 2) appears in the

IND

display on the

LNW2 SYSCTL.

Then...

Not Supported.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

LNW2 SYSCTL will not boot.

No compatible generic on the NVMs in the

LNW2 SYSCTL.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure or contact your next level of support.

LNW2 SYSCTL faceplate latches are not fully seated.

Unseat the LNW2 SYSCTL and repeat this procedure, properly seating the faceplate latch.

“x” indicates that the NVM socket (1 or 2) is empty or the NVM installed is failed. Replace the indicated NVM or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

LNW2 SYSCTL will not boot due to unexpected or unreadable shelf type.

Repair the problem generally caused by bent pins and repeat this procedure.

Boot in progress.

Acknowledges the

UPD/INIT

button was momentarily pushed.

Pushing the

UPD/INIT

button while in

Maintenance Mode has no effect.

11

12

.................................................................................................................................................................................................

Connect the cross-over LAN cable from the PC’s Network Interface Card (NIC) to the rear

J16 IAO LAN

port on the Metropolis

®

DMX shelf backplane or the front

LAN

port on the LNW2 SYSCTL circuit pack faceplate. (When TCP/IP is enabled on the rear

LAN port, OSI is disabled.)

.................................................................................................................................................................................................

From the Network View of the WaveStar

®

CIT session you established in

Procedure

12-16: “Upgrade or replace SYSCTL (LNW2) circuit pack” (p. 12-325) , select the

View:

pull-down menu and select

CIT OSI Neighbors

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-335

Ring and circuit pack upgrade procedures

13

Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................

From the Network View, select

View

→

Refresh OSI View

.

Result:

The CIT OSI neighbor(s) are automatically detected.

Your TID will be LT-DMX; when in Maintenance Mode, the TID is always default.

Figure 12-9 CIT OSI neighbor

14

.................................................................................................................................................................................................

In the Network View,

Figure 12-9, “CIT OSI neighbor” (p. 12-336) ,, right-click on the

LT-DMX NE icon that was detected, and select

Graphical Using

→

OSI

from the resulting menu.

.................................................................................................................................................................................................................................

12-336 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

15

16

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX and click

OK

.

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

Important! Because the shelf is in Maintenance Mode, your logins and passwords are default.

Enter the following in the NE Login Dialog window (login information is case sensitive) to log in to the NE:

User ID:

LUC01

Password:

DMX2.5G10G

Click

OK

.

Important! After you select your backup database, complete the Maintenance

Mode Wizard, and the NE restarts, your original User IDs and Passwords will be restored.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-337

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

Result:

Screen 1 of 4 in the Maintenance Mode Wizard appears.

This screen picks up the time format preference from the WaveStar

®

CIT.

You can provision the time format display for your WaveStar

®

CIT from the

Network View by selecting

View

→

Preferences

and clicking on the Display tab.

.................................................................................................................................................................................................................................

12-338 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

17

This screen allows you to choose your preference for time format, either a 12-hour clock or a 24-hour clock.

•

If your time format preference is a 12-hour clock, from the

Time

panel, select

Hour:

(0-12),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus.

You must also specify am or pm by selecting one of the radio buttons.

•

If your time format preference is a 24-hour clock, From the

Time

panel, select the

Hour:

(0-23),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus.

.................................................................................................................................................................................................

Important! The actual time and date are preset from your PC.

On Screen 1 of 4 in the Maintenance Mode Wizard, read the information, verify the date and time, make any required changes, and click

Next

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-339

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

Result:

Screen 2 of 4 in the Maintenance Mode Wizard appears.

18

.................................................................................................................................................................................................

On Screen 2 of 4 in the Maintenance Mode Wizard, click

Download

.

.................................................................................................................................................................................................................................

12-340 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

Result:

Screen 1 of 3 in the Download Generic Wizard appears.

19

.................................................................................................................................................................................................

On Screen 1 of 3 in the Download Generic Wizard, read the information, select

FTAM

and click

Next

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-341

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

Result:

Screen 2 of 3 in the Download Generic Wizard appears.

20

.................................................................................................................................................................................................

Important! LAN-1 is the

LAN

port on the faceplate of the LNW2 SYSCTL circuit pack. LAN-2 is the

J16 IAO LAN

port on the rear of the Metropolis

®

DMX shelf.

On Screen 2 of 3 in the Download Generic Wizard, read the information, verify that the LAN port you are connected to has OSI Function Enable selected and click

Next

.

.................................................................................................................................................................................................................................

12-342 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

Result:

Screen 3 of 3 in the Download Generic Wizard appears.

21

.................................................................................................................................................................................................

On Screen 3 of 3 in the Download Generic Wizard in the

Path

panel, enter the current location of the generic to be downloaded in the Path field or use the

Browse

button to select the generic to be downloaded. Click

Download

.

The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:/Program

Files/Lucent Technologies/WaveStar CIT/generics/DMX/6.0.1/p/

. The syntax

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-343

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

22

of the relative path must start with the path name; for example:

/generics/DMX/6.0.1/p/

. (If necessary, replace 6.0.1 with your current release, for example 6.0.2.)

Result:

A warning message appears listing the options you provisioned in the previous screens.

.................................................................................................................................................................................................

Verify the information and either click

Yes

to start the download process or click

No

to return to the download screen and change your selections.

Result:

If you choose yes, the following initial software download progress indicator runs for approximately 15 minutes.

23

.................................................................................................................................................................................................

Once the software generic download is complete, the following confirmation message appears. Click

Yes

to use the generic that is now in the Dormant area.

.................................................................................................................................................................................................................................

12-344 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

Result:

Screen 3 of 4 in the Maintenance Mode Wizard appears.

24

.................................................................................................................................................................................................

On Screen 3 of 4 in the Maintenance Mode Wizard, click

Download

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-345

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

Result:

Screen 1 of 3 in the Download Database Wizard appears.

25

.................................................................................................................................................................................................

On Screen 1 of 3 in the Download Database Wizard, read the information, select

FTAM

and click

Next

.

.................................................................................................................................................................................................................................

12-346 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

Result:

Screen 2 of 3 in the Download Database Wizard appears.

26

.................................................................................................................................................................................................

On Screen 2 of 3 in the Download Database Wizard, read the information, verify that the LAN port you are connected to has OSI Function Enable selected and click

Next

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-347

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

Result:

Screen 3 of 3 in the Download Database Wizard appears.

27

.................................................................................................................................................................................................

On Screen 3 of 3 in the Download Database Wizard in the

Path

panel, enter the location where the database information is stored. Enter the path and filename exactly as it was entered in

Step 3 . For example:

backups/<subdirectory>/<filename>

.

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and select the required file.

Click

Download

.

.................................................................................................................................................................................................................................

12-348 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

28

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

Result:

A warning message appears listing the options you provisioned in the previous screens.

.................................................................................................................................................................................................

Verify the information and click

Yes

.

Result:

If you choose Yes, the database download progress indicator runs for approximately two minutes.

29

.................................................................................................................................................................................................

Once the database download is complete, the following confirmation message appears.

Click

Yes

to use the database that is now in the Backup area.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-349

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

Result:

Screen 4 of 4 in the Maintenance Mode Wizard appears. In this screen,

6.0.1 is an example; your selected generic/database could be different, for example

6.0.2.

30

.................................................................................................................................................................................................

On Screen 4 of 4 in the Maintenance Mode Wizard, read the information, verify that you have selected the correct generic and database and click

Finish

to restart the system and apply the generic and database.

.................................................................................................................................................................................................................................

12-350 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.2: Upgrade or replace SYSCTL (LNW2) circuit pack using FTAM

31

Result:

The Maintenance Mode Wizard closes and your connection to the shelf is terminated.

The LNW2 SYSCTL exhibits the following visible cycles while the generic and database are installed and validated and the SYSCTL reboots:

1. For approximately 10 minutes, the alternating

M

and

P

and

6

and “

.

” (“.” is a red, four-segment square [2 x 2] representing a period) and

0

continue to appear in the

IND

display on the SYSCTL.

2. After approximately 10 minutes, all LEDs extinguish and the

IND

display on the

SYSCTL is blank for approximately 5 seconds.

3. A flashing

b

appears in the

IND

display on the SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 60 seconds and then

IND

display is blank for approximately 20 seconds.

4. The

ACTIVE

LED lights and remains lighted.

5. A flashing

b

appears again in the

IND

display on the SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 60 seconds while the database is being converted and then

IND

display is blank.

6. When nothing appears in the

IND

display and the

ACTIVE

LED is lighted and the other LEDs return to their previous state (prior to the SYSCTL replacement), the NE software and database installation is complete.

However, smart circuit packs may be upgrading their firmware. If flashing green

ACTIVE

LEDs are present on a circuit pack, firmware is currently being downloaded to that pack. Wait until all smart circuit packs finish upgrading their firmware before proceeding.

7. Continue with

Step 31 .

.................................................................................................................................................................................................

Proceed to

Procedure 12-16.4: “Verify proper software generic” (p. 12-375) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-351

Ring and circuit pack upgrade procedures

Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

.................................................................................................................................................................................................................................

Overview

Use this procedure to replace an LNW2 using File Transfer Protocol (FTP).

Important! You must have direct TCP/IP connectivity to your NE and the NE must have a defined IP address.

Required equipment

Refer to

“Required equipment” (p. 12-325)

in

Procedure 12-16: “Upgrade or replace

SYSCTL (LNW2) circuit pack” (p. 12-325)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 12-16: “Upgrade or replace

SYSCTL (LNW2) circuit pack” (p. 12-325) .

Step

1

2

3

Complete the following steps to replace your SYSCTL using FTP.

.................................................................................................................................................................................................

From the System View menu, select

Configuration

→

Software

→

Remote Backup

.

.................................................................................................................................................................................................

In the pull-down

Backup To/Via:

menu, select

FTP

.

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and proceed to

Step 5 . OR

Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

ipconfig

CIT is the FTP server, you can determine its IP address by entering from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the backup to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar

®

CIT as your FTP server, the default user name/password for the WaveStar

®

CIT is

LUC01

/

LUC+01

, however your user ID/password may be different.)

.................................................................................................................................................................................................................................

12-352 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

4

5

6

.................................................................................................................................................................................................

If you entered connection information in

Step 3

and wish to keep the information for future backups:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Entries to the

Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

.................................................................................................................................................................................................

In the

Source/Destination Directory Path

field, enter

backups/<filename>

if you wish to save the backup file to the default location. (If the WaveStar

®

CIT is the FTP server, a maximum of 80 characters is suggested for this field.)

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and over-write the default entry. The

Browse

button is not available (greyed out) if the FTP server is not the local WaveStar

®

CIT.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

If you wish to store your data in a subdirectory within the default path, you may enter

backups/<subdirectory>/<filename>

if the subdirectory exists before the command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.

.................................................................................................................................................................................................

Click

OK

.

You will be asked to verify that you wish to backup to the directory that you entered above. Click

Yes

if you typed the path correctly.

Result:

The Progress Indicator screen appears to indicate that the backup is in progress. When the backup completes, a WaveStar

®

CIT information screen appears that indicates

Remote Backup successful

. Click the

OK

button.

The backup file is now stored. If the default path and a subdirectory were used, the file may be found at:

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-353

Ring and circuit pack upgrade procedures

7

8

9

10

11

Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

C:/Program Files/Lucent Technologies/WaveStar

CIT/backups/<subdirectory>/<filename>

.................................................................................................................................................................................................

Close your WaveStar

NE Disconnect

®

CIT session with the NE. From the System View, select

File

→ and click

Yes

in the confirmation window.

Result:

The System View closes.

.................................................................................................................................................................................................

Disconnect the LAN and/or serial cables from the

LAN

and/or

RS232

port(s) on the front of the LNW2 SYSCTL.

.................................................................................................................................................................................................

Initiate a ten-second countdown (9, 8, 7, 6, 5, 4, 3, 2, 1, 0) in the

IND

display on the

LNW2 SYSCTL by simultaneously depressing the

ACO TEST

and

SEL

buttons on the front of the LNW2 SYSCTL.

Important! Removing the LNW2 without initiating the ten-second countdown may result in unexpected and undesirable protection switches, incorrect circuit fault indications, or incoming signal failure alarms. All SYSCTL functions are suspended during the countdown.

.................................................................................................................................................................................................

Remove the SYSCTL circuit pack during the 10-second countdown.

Important! While the SYSCTL circuit pack is removed, do NOT remove or replace any transmission circuit packs.

.................................................................................................................................................................................................

Important! For installation, two NVMs must be present in the LNW2 SYSCTL. If either NVM is missing, an

NVM removed alarm will be issued. If both NVM holders are empty, after the circuit pack is installed the

IND

displays an alternating

E

and

0

and

1

. Refer to

Step 12

for the complete listing of codes.

Seat the new LNW2 SYSCTL circuit pack and allow a few minutes for the pack to complete initialization.

Result:

The LNW2 SYSCTL exhibits the following visible cycles during initialization:

1. The

FAULT

LED lights and remains lighted for approximately 90 seconds. After approximately 15 seconds, a flashing

b

appears in the

IND

display on the

SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 75 seconds and then

IND

display is blank.

2. The

FAULT

LED remains lighted for approximately another 20 seconds and then extinguishes.

.................................................................................................................................................................................................................................

12-354 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

12

3. The

ACTIVE

LED lights and remains lighted and the

CR

LED flashes 10 times.

While the

CR

LED is flashing, the

MJ

,

ABN

, and

NE

LEDs light and remain lighted.

Because the LNW2 SYSCTL is in 6.0 Maintenance Mode, an alternating

M

and

P

and

6

and “

.

” (“.” is a red, four-segment square [2 x 2] representing a period) and

0

appear in the

IND

display.

4. Continue with

Step 12 .

.................................................................................................................................................................................................

Observe the

IND

display on the LNW2 SYSCTL; the display indicates the state of the

SYSCTL.

If...

alternating

M

and

P

and

6

and “

.

”

(“.” is a red, four-segment square

[2 x 2] representing a period) and

0

alternating

E

and

0

and

0

Then...

6.0 Maintenance Mode. Continue with

Step 13 .

alternating alternating alternating alternating

E

E

E

E

and and and and

0

0

0

1

and and and and

1

2

3

0

LNW2 SYSCTL must be replaced.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

No NVMs are detected on the LNW2 SYSCTL.

Install two Lucent-supplied NVMs in the LNW2 or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

NVMs are present but not readable. Check to make sure they are properly seated and repeat this procedure.

Not Supported.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

LNW2 SYSCTL will not boot.

No compatible generic on the NVMs in the

LNW2 SYSCTL.

Find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure or contact your next level of support.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-355

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

If...

Letter

F

alternating

Letter

U

N

and

O

and

x

flashing

b

A red, four-segment square (2 x 2) appears in the

IND

display on the

LNW2 SYSCTL.

Then...

LNW2 SYSCTL faceplate latches are not fully seated.

Unseat the LNW2 SYSCTL and repeat this procedure, properly seating the faceplate latch.

“x” indicates that the NVM socket (1 or 2) is empty or the NVM installed is failed. Replace the indicated NVM or find another LNW2 SYSCTL equipped with two factory-installed NVMs and repeat this procedure.

LNW2 SYSCTL will not boot due to unexpected or unreadable shelf type.

Repair the problem generally caused by bent pins and repeat this procedure.

Boot in progress.

Acknowledges the

UPD/INIT

button was momentarily pushed.

Pushing the

UPD/INIT

button while in

Maintenance Mode has no effect.

13

14

.................................................................................................................................................................................................

Connect the cross-over LAN cable from the PC’s Network Interface Card (NIC) to the rear

J16 IAO LAN

port on the Metropolis

®

DMX shelf backplane or the front

LAN

port on the LNW2 SYSCTL circuit pack faceplate. (When TCP/IP is enabled on the rear

LAN port, OSI is disabled.)

.................................................................................................................................................................................................

From the Network View of the WaveStar

®

CIT session you established in

Procedure

12-16: “Upgrade or replace SYSCTL (LNW2) circuit pack” (p. 12-325) , select the

View:

pull-down menu and select

CIT OSI Neighbors

.

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................................................

12-356 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

Result:

The CIT OSI Neighbor(s) are automatically detected.

If you were previously logged in to the NE and/or you do not see your NE, from the Network View, select

View

→

Refresh OSI View

.

Figure 12-10 CIT OSI neighbor

15

16

.................................................................................................................................................................................................

In the Network View, Figure 12-10, “CIT OSI neighbor” (p. 12-357) , right-click on the

LT-DMX NE icon that was detected, and select

Graphical Using

→

OSI

from the resulting menu.

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX and click

OK

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-357

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

17

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

Important! Because the shelf is in Maintenance Mode, your logins and passwords are default.

Enter the following in the NE Login Dialog window (login information is case sensitive) to log in to the NE:

User ID:

LUC01

Password:

DMX2.5G10G

Click

OK

.

Important! After you select your backup database, complete the Maintenance

Mode Wizard, and the NE restarts, your original User IDs and Passwords will be restored.

.................................................................................................................................................................................................................................

12-358 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

Result:

Screen 1 of 4 in the Maintenance Mode Wizard appears.

This screen picks up the time format preference from the WaveStar

®

CIT.

You can provision the time format display for your WaveStar

®

CIT from the

Network View by selecting

View

→

Preferences

and clicking on the Display tab.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-359

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

18

This screen allows you to choose your preference for time format, either a 12-hour clock or a 24-hour clock.

•

If your time format preference is a 12-hour clock, from the

Time

panel, select

Hour:

(0-12),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus.

You must also specify am or pm by selecting one of the radio buttons.

•

If your time format preference is a 24-hour clock, From the

Time

panel, select the

Hour:

(0-23),

Minute:

(0-59), and

Second:

(0-59) from the pull-down menus.

.................................................................................................................................................................................................

Important! The actual time and date are preset from your PC.

On Screen 1 of 4 in the Maintenance Mode Wizard, read the information, verify the date and time, make any required changes, and click

Next

.

.................................................................................................................................................................................................................................

12-360 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

Result:

Screen 2 of 4 in the Maintenance Mode Wizard appears.

19

.................................................................................................................................................................................................

On Screen 2 of 4 in the Maintenance Mode Wizard, click

Download

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-361

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

Result:

Screen 1 of 3 in the Download Generic Wizard appears.

20

.................................................................................................................................................................................................

On Screen 1 of 3 in the Download Generic Wizard, read the information, select

FTP

and click

Next

.

.................................................................................................................................................................................................................................

12-362 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

Result:

Screen 2 of 3 in the Download Generic Wizard appears.

21

.................................................................................................................................................................................................

Important! LAN-1 is the

LAN

port on the faceplate of the LNW2 SYSCTL circuit pack. LAN-2 is the

J16 IAO LAN

port on the rear of the Metropolis

®

DMX shelf.

On Screen 2 of 3 in the Download Generic Wizard, follow the instructions to enable

TCP/IP Control on the LAN port to which you are connected. Click

Modify

to enter the IP Address, IP Subnet Mask, and/or IP Default Router Address. Click

Next

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-363

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

Result:

Screen 3 of 3 in the Download Generic Wizard appears.

.................................................................................................................................................................................................................................

12-364 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

22

23

24

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and proceed to

Step 24 . OR

Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

CIT is the FTP server, you can determine its IP address by entering

ipconfig

from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the backup to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar

®

CIT as your FTP server, the default user name/password for the WaveStar

®

CIT is

LUC01

/

LUC+01

, however your user ID/password may be different.)

.................................................................................................................................................................................................

If you entered connection information in

Step 22

and wish to keep the information for future FTP activities:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Important! Entries to the

Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

.................................................................................................................................................................................................

On Screen 3 of 3 in the Download Generic Wizard in the

Path

panel, enter the current location of the generic to be downloaded in the Path field or use the

Browse

button to select the generic to be downloaded. (If the FTP server is not the local host, the

Browse

button is greyed out.) Click

Download

.

The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:/Program

Files/Lucent Technologies/WaveStar CIT/generics/DMX/6.0.1/p/

. The syntax of the relative path must start with the path name; for example:

/generics/DMX/6.0.1/p/

. (If necessary, replace 6.0.1 with your current release, for example 6.0.2.)

If the FTP server is not the WaveStar

®

CIT, then enter the path starting at the FTP home directory on the server.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-365

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

25

Result:

A warning message appears listing the options you provisioned in the previous screens.

.................................................................................................................................................................................................

Verify the information and either click

Yes

to start the download process or click

No

to return to the download screen and change your selections.

Result:

If you choose yes, the following initial software download progress indicator runs for approximately 15 minutes.

26

.................................................................................................................................................................................................

Do you wish to observe the FTP download progress?

If...

Yes

No

Then...

Proceed to

Procedure 14-17: “Observe FTP progress”

(p. 14-101)

and then continue with

Step 27 .

Continue with

Step 27 .

27

.................................................................................................................................................................................................

Once the software generic download is complete, the following confirmation message appears. Click

Yes

to use the generic that is now in the Dormant area.

.................................................................................................................................................................................................................................

12-366 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

Result:

Screen 3 of 4 in the Maintenance Mode Wizard appears.

28

.................................................................................................................................................................................................

On Screen 3 of 4 in the Maintenance Mode Wizard, click

Download

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-367

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

Result:

Screen 1 of 3 in the Download Database Wizard appears.

29

.................................................................................................................................................................................................

On Screen 1 of 3 in the Download Database Wizard, read the information, select

FTP

and click

Next

.

.................................................................................................................................................................................................................................

12-368 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

Result:

Screen 2 of 3 in the Download Database Wizard appears.

.................................................................................................................................................................................................

30

Important! LAN-1 is the

LAN

port on the faceplate of the LNW2 SYSCTL circuit pack. LAN-2 is the

J16 IAO LAN

port on the rear of the Metropolis

®

DMX shelf.

On Screen 2 of 3 in the Download Generic Wizard, the information entered in

Step 21

should still be present and valid. If the information is not present, follow the instructions to enable TCP/IP Control on the LAN port to which you are connected.

Click

Modify

to enter the IP Address, IP Subnet Mask, and/or IP Default Router

Address.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-369

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

Click

Next

.

Result:

Screen 3 of 3 in the Download Database Wizard appears.

.................................................................................................................................................................................................................................

12-370 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

31

32

33

.................................................................................................................................................................................................

Select the connection from the

Profile

pull-down menu and proceed to

Step 33 . OR

Enter information for a new profile as follows:

1. In the

Server

panel, select

IP

and enter the address of the FTP server. (If the

WaveStar

®

CIT is the FTP server, you can determine its IP address by entering

ipconfig

from the

MS DOS

prompt on your PC.)

2. If necessary, enter the port (default is blank). Defining the port is not required for the backup to execute successfully. However, a value of 21 is valid if entered.

3. In the

User

panel, enter the user name and password for the FTP server. (If you are using the WaveStar

®

CIT as your FTP server, the default user name/password for the WaveStar

®

CIT is

LUC01

/

LUC+01

, however your user ID/password may be different.)

.................................................................................................................................................................................................

If you entered connection information in

Step 31

and wish to keep the information for future FTP activities:

1. Type a new name in the

Profile

menu.

2. Click

Add

to add the profile to the list.

3. Click

Save

to save the list.

Important! Entries to the

Profile

pull-down menu may be changed using the

Modify

,

Apply

, and

Save

buttons or removed using the

Delete

button.

.................................................................................................................................................................................................

On Screen 3 of 3 in the Download Database Wizard in the

Path

panel, enter the location where the database information is stored. Enter the path and filename exactly as it was entered in

Step 5 . For example:

backups/<subdirectory>/<filename>

.

You may also click the

Browse

button next to the Path: field to browse to any directory on your PC and select the required file.

Click

Download

.

Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path names; for example:

C:\temp\today\backup. The syntax of the relative path must start with the path name; for example: \temp\backup.

The WaveStar

®

CIT directory automatically enters the relative path for the

WaveStar

®

CIT. The default relative path is

C:/Program Files/Lucent Technologies/WaveStar CIT/

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-371

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

34

Result:

A warning message appears listing the options you provisioned in the previous screens.

.................................................................................................................................................................................................

Verify the information and click

Yes

.

Result:

If you choose Yes, the database download progress indicator runs for approximately two minutes.

35

.................................................................................................................................................................................................

Do you wish to observe the FTP download progress?

If...

Yes

No

Then...

Proceed to

Procedure 14-17: “Observe FTP progress”

(p. 14-101)

and then continue with

Step 36 .

Continue with

Step 36 .

36

.................................................................................................................................................................................................

Once the database download is complete, the following confirmation message appears.

Click

Yes

to use the database that is now in the Backup area.

.................................................................................................................................................................................................................................

12-372 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

Result:

Screen 4 of 4 in the Maintenance Mode Wizard appears. In this screen,

6.0.1 is an example; your selected generic could be different, for example 6.0.2.

37

.................................................................................................................................................................................................

On Screen 4 of 4 in the Maintenance Mode Wizard, read the information, verify that you have selected the correct generic and database and click

Finish

to restart the system and apply the generic and database.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-373

Ring and circuit pack upgrade procedures Procedure 12-16.3: Upgrade or replace SYSCTL (LNW2) circuit pack using FTP

38

39

Result:

The Maintenance Mode Wizard closes and your connection to the shelf is terminated.

The LNW2 SYSCTL exhibits the following visible cycles while the generic and database are installed and validated and the SYSCTL reboots:

1. For approximately 10 minutes, the alternating

M

and

P

and

6

and “

.

” (“.” is a red, four-segment square [2 x 2] representing a period) and

0

continue to appear in the

IND

display on the SYSCTL.

2. After approximately 10 minutes, all LEDs extinguish and the

IND

display on the

SYSCTL is blank for approximately 5 seconds.

3. A flashing

b

appears in the

IND

display on the SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 60 seconds and then

IND

display is blank for approximately 20 seconds.

4. The

ACTIVE

LED lights and remains lighted.

5. A flashing

b

appears again in the

IND

display on the SYSCTL, indicating that a boot is in progress. The

b

continues flashing for approximately 60 seconds while the database is being converted and then

IND

display is blank.

6. When nothing appears in the

IND

display and the

ACTIVE

LED is lighted and the other LEDs return to their previous state (prior to the SYSCTL replacement), the NE software and database installation is complete.

However, smart circuit packs may be upgrading their firmware. If flashing green

ACTIVE

LEDs are present on a circuit pack, firmware is currently being downloaded to that pack. Wait until all smart circuit packs finish upgrading their firmware before proceeding.

7. Continue with

Step 38 .

.................................................................................................................................................................................................

To verify that the upgrade was successful, depress and hold the

ACO TEST

push-button on the LNW2 SYSCTL for about 4 seconds.

Result:

All LEDs on the shelf light. A red, 35-segment (5 x 7) rectangle appears in the

IND

display on the SYSCTL. Since the

IND

display is a 35-segment display, this test indicates all segments are working.

.................................................................................................................................................................................................

Proceed to

Procedure 12-16.4: “Verify proper software generic” (p. 12-375) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-374 365-372-301 R6.0

Issue 15, January 2006

Ring and circuit pack upgrade procedures

Procedure 12-16.4: Verify proper software generic

.................................................................................................................................................................................................................................

Overview

Use this procedure to verify that the proper software generic is active on your

SYSCTL and you can log in to the NE.

Required equipment

Refer to

“Required equipment” (p. 12-325)

in

Procedure 12-16: “Upgrade or replace

SYSCTL (LNW2) circuit pack” (p. 12-325)

for a list of equipment required to perform this procedure.

Before you begin

Prior to performing this procedure, complete

Procedure 12-16: “Upgrade or replace

SYSCTL (LNW2) circuit pack” (p. 12-325) .

Step

1

2

3

4

.................................................................................................................................................................................................

Release the

ACO TEST

push-button on the LNW2 SYSCTL when the red rectangle disappears in the

IND

display.

Result:

The current software generic appears in the

IND

display on the LNW2

SYSCTL and the shelf LEDs return to their previous status.

.................................................................................................................................................................................................

From the Network View of the WaveStar

®

CIT session you established in

Procedure

2-4: “Upgrade software generic via FTP” (p. 2-72) , select

View:

pull-down menu, select

CIT OSI Neighbors

.

Important! This

View:

is not the menu bar item View

→

...; it is located above the

NE Name pull-down menu.

.................................................................................................................................................................................................

From the Network View, select

View

→

Refresh OSI View

.

Result:

The CIT OSI neighbor(s) are automatically detected.

Your TID will be your original TID, the same TID provisioned on your NE prior to the SYSCTL replacement.

.................................................................................................................................................................................................

In the Network View, right-click on the NE icon that was detected, and select

Graphical Using

→

OSI

from the resulting menu.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

12-375

Ring and circuit pack upgrade procedures Procedure 12-16.4: Verify proper software generic

5

6

7

Result:

The System Type Selection window appears.

.................................................................................................................................................................................................

In the System Type Selection window, select Metropolis(R) DMX and click

OK

.

Result:

The NE Login Dialog window appears.

.................................................................................................................................................................................................

In the NE login window, login to the shelf using your original user ID and password; the same user ID and password provisioned prior to the SYSCTL replacement.

Click

OK

.

Result:

The title bar of the System View and the legal notice text should both reflect the current NE software generic, for example: R6.0.1.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Is the Generic Software Version correct?

If...

Yes

No

Then...

STOP! End of Procedure.

Contact your next level of support.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

12-376 365-372-301 R6.0

Issue 15, January 2006

13

13

Overview

.................................................................................................................................................................................................................................

Purpose

This chapter includes maintenance procedures, for example, replacing a fan filter and replacing a shelf.

Contents

Before you begin

Procedure 13-1: Replace fan filter

Procedure 13-2: Replace Metropolis

®

DMX standard shelf

Procedure 13-3: Replace Metropolis

®

DMX High Capacity shelf

Procedure 13-4: Enter/exit pluggable transmission module maintenance state

13-2

13-3

13-5

13-15

13-25

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

13-1

Routine maintenance procedures

Before you begin

.................................................................................................................................................................................................................................

Before you begin

Prior to performing all procedures in this chapter,

1. If not previously completed, install generic and WaveStar

®

CIT software on the PC.

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

2. Connect PC and establish a WaveStar

®

CIT session.

Refer to

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24) .

.................................................................................................................................................................................................................................

13-2 365-372-301 R6.0

Issue 15, January 2006

Routine maintenance procedures

Procedure 13-1: Replace fan filter

.................................................................................................................................................................................................................................

Overview

Use this procedure to replace a fan filter.

Important! In central office applications, the fan shelf must equipped with a fan filter. To keep the fan shelf operating properly, it is recommended that users routinely change the fan filter every 6 to 9 months.

In outside plant (OSP) applications, remove the fan filter. Operating Metropolis

®

DMX in an OSP without the fan filter improves air flow and therefore enhances cooling performance and extends the life of the equipment.

Required equipment

The following equipment is required:

•

Wrist strap

•

A replacement filter

– For Metropolis

®

DMX Comcode: 408 456 770

– For Metropolis

®

DMX High Capacity shelf Comcode: 408 682 615

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 13-2)

in this chapter

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety”

3. Ensure that the replacement fan filter is the same type as the original fan filter.

4. Note that the Standard Shelf is Discontinued Availability effective 6/30/04.

Step

1

Complete the following steps to replace the fan filter.

.................................................................................................................................................................................................

Remove the fan filter by pulling it towards you.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

13-3

Routine maintenance procedures Procedure 13-1: Replace fan filter

In the Metropolis

®

DMXstandard shelf, the fan shelf is installed above the shelf.

However, fan filter is located below the shelf, under the Metropolis

®

DMX fiber tray

(see

Figure 13-1, “Metropolis

®

DMX standard shelf fan filter” (p. 13-4) ).

Figure 13-1 Metropolis

®

DMX standard shelf fan filter

A1 A2 B1 B2 G1 M1 CTL G2 M2 C1 C2 D1 D2

Fan Filter nc-dmx-214

In the Metropolis

®

DMX High Capacity shelf, the fan shelf is installed below shelf.

The fan filter is located directly below the fan shelf (see

Figure 13-2, “Metropolis

®

DMX High Capacity shelf fan filter” (p. 13-4) ).

Figure 13-2

Metropolis

®

DMX High Capacity shelf fan filter

G1 A1 A2 B1 B2

Lucent Technologies

Metropolis DMX

M1 CTL G2 M2 C1 C2 D1

POWER

FAULT

D2

Fan Filter nc-dmx-215

2

.................................................................................................................................................................................................

Install new filter into the fan filter slot.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

13-4 365-372-301 R6.0

Issue 15, January 2006

Routine maintenance procedures

Procedure 13-2: Replace Metropolis

®

DMX standard shelf

.................................................................................................................................................................................................................................

Overview

Use this procedure to replace the Metropolis

®

DMX Access Multiplexerstandard shelf

(C848540464). The standard shelf has a separate fan shelf. The High Capacity shelf has an integrated fan shelf.

Note that the Standard Shelf is Discontinued Availability effective 6/30/04.

Important! It is assumed that the Metropolis

®

DMX is out of service. Power to the shelf will be removed in this procedure.

Required equipment

Important! A standard Metropolis

®

DMX shelf can be replaced with either a

Standard or High Capacity Metropolis

®

DMX shelf.

The following equipment may be required:

•

Replacement Metropolis

®

DMX shelf (Refer to Engineering Drawing ED8C871-10 for a complete list of required cables.)

•

If a High Capacity shelf is replacing a Standard shelf the following circuit packs and cables may be required in addition to the shelf

– If high-density 56DS1/E1 circuit packs (LNW8) are being installed, additional

DS1 cabling is required (same as the 28DS1/28DS1PM [LNW6/7]).

– If high-density 48DS3/EC1 circuit packs (LNW19) are being installed, doubledensity DS3 cabling is required. The high density circuit packs cannot use the same cables as the 12DS3/EC1 (LNW16) circuit packs.

•

Personal Computer (PC) with WaveStar

®

CIT software installed

•

Wrist strap

•

Optical fiber connector dust covers

•

Optical circuit pack connector dust covers

•

ESD protective bags for temporary storage of circuit packs

•

Metropolis

®

DMX Access Multiplexer Installation Manual, 365-372-304

If sync cables with molded DB-9 connectors are installed, then two sync cables as follows:

Cable Assembly #

848839619

848839627

848839635

Cable Length (feet)

50

100

150

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

13-5

Routine maintenance procedures Procedure 13-2: Replace Metropolis

®

DMX standard shelf

Cable Assembly #

848839643

848839650

Cable Length (feet)

250

450

Miscellaneous discrete cables as follows:

Cable Assembly #

848839569

848839577

848839585

848839593

848839601

Cable Length (feet)

50

100

150

250

350

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 13-2)

in this chapter

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Verify that the Metropolis

®

DMX shelf is out of service.

Step

1

2

Complete the following steps to replace a Metropolis

®

DMX shelf.

.................................................................................................................................................................................................

Remove power to the Metropolis

®

DMX shelf by operating the circuit breakers to the

OFF position at the Battery Distribution Fuse Bay (BDFB) in the central office or removing the fuses at the BDFB.

Important! Remove power for both A and B feeders to the shelf.

Result:

Both

PWR (A)

and

PWR (B)

LEDs on the front of the shelf extinguish.

Reference:

Refer to the user documentation for your BDFB for more information.

.................................................................................................................................................................................................

Disconnect the A and B power connectors from the left and right sides of the

Metropolis

®

DMX shelf.

.................................................................................................................................................................................................................................

13-6 365-372-301 R6.0

Issue 15, January 2006

Routine maintenance procedures Procedure 13-2: Replace Metropolis

®

DMX standard shelf

3

4

5

6

7

.................................................................................................................................................................................................

Using a voltmeter, measure the voltage on the power cable connectors (looking towards the BDFB) between BAT A and BAT A RTN (red cable).

Result:

Voltmeter indicates no voltage.

.................................................................................................................................................................................................

Using a voltmeter, measure the voltage on the power cable connectors (looking towards the shelf’s backplane) between BAT B and BAT B RTN (blue cable).

Result:

Voltmeter indicates no voltage.

.................................................................................................................................................................................................

On the backplane, label all cables connecting to the Metropolis

®

DMX shelf. These include:

•

Fan Shelf Power/Alarm Cable (J15)

•

DS1/DS3/EC1/FastE Transmission Cables as equipped (J1, J2, J3, J4, J5, J6, J7, J8)

•

IAO LAN (J16)

•

Modem cable (J17)

•

TL1 Interface Cable (J10)

•

Sync Cables (J9 and J14)

•

Office Alarm Cable (J12)

•

Alarm Mult (J13)

•

Miscellaneous (Environmental) Discrete (J11)

.................................................................................................................................................................................................

Remove all cables from the Metropolis

®

DMX shelf backplane. It may be necessary to untie the cables from the cable tie bar.

Important! It is not necessary to disconnect the power cables on the backplane connectors (P15 and P14); they are internal to the shelf that is being removed.

.................................................................................................................................................................................................

On the front of the Metropolis

®

DMX shelf, label all cables connecting to circuit packs. These include:

•

Optical Fibers connected to the Main OLIUs (Transmit/Receive)

•

Optical Fibers connected to OC3/OC12/OC48 Low Speed OLIUs in Function Slots

A, B, C, D and Growth Slots (Transmit/Receive)

•

Optical Fibers connected to Gigabit Ethernet Circuit Packs in Function Slots A, B,

C, D and Growth Slots (Transmit/Receive)

•

LAN cable

•

CIT cable

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

13-7

Routine maintenance procedures Procedure 13-2: Replace Metropolis

®

DMX standard shelf

8

9

10

11

12

13

14

15

16

.................................................................................................................................................................................................

Remove all cables from circuit packs in the Metropolis

®

DMX shelf.

.................................................................................................................................................................................................

Place protective dust covers on fiber connections (fibers and circuit packs).

.................................................................................................................................................................................................

Note the position of each circuit pack (Function slot number or Growth slot) for reference when installing the new shelf.

.................................................................................................................................................................................................

Carefully remove the fibers from the Metropolis

®

DMX shelf fiber tray.

.................................................................................................................................................................................................

Disengage and remove each circuit pack and place each in an ESD protective bag.

.................................................................................................................................................................................................

Unscrew the mounting screws that attach the Metropolis

®

DMX shelf to the bay frame and remove the shelf. If your replacement shelf is a Metropolis

®

DMX High Capacity shelf, you must also remove the fan shelf above the standard shelf.

Important! Do not disturb cables associated with other Metropolis

®

DMX Access

Multiplexer shelves in the bay or equipment in adjacent bays.

.................................................................................................................................................................................................

Inspect the replacement Metropolis

®

DMX shelf for visible damage including bent or touching backplane pins.

.................................................................................................................................................................................................

Determine the mounting configuration for the Metropolis

®

DMX shelf:

• type of bay frame (23-inch or 19-inch wide)

• mounting position (front or rear)

• position in bay (bottom to top).

Important! The Metropolis

®

DMX shelf is shipped with the mounting brackets positioned for mounting to the rear of a 23-inch wide network bay frame.

The Metropolis

®

DMX shelf mounting brackets may have to be repositioned and remounted, depending on the frame type and mounting position (front or rear).

.................................................................................................................................................................................................

If necessary, reposition the shelf mounting brackets accordingly.

For 23-inch frame, front or rear mounting, refer to

Figure 13-3, “Metropolis

®

DMX mounting bracket positions - 23-inch frame” (p. 13-9) .

.................................................................................................................................................................................................................................

13-8 365-372-301 R6.0

Issue 15, January 2006

Routine maintenance procedures Procedure 13-2: Replace Metropolis

®

DMX standard shelf

For 19-inch frame, front or rear mounting, refer to

Figure 13-4, “Metropolis

®

mounting bracket positions - 19-inch frame” (p. 13-9) .

DMX

Figure 13-3 Metropolis

®

DMX mounting bracket positions - 23-inch frame

23-inch Frame - Rear Mounted (as shipped)

REAR FRONT

23-inch Frame - Front Mounted

Tighten Screws to 10 IN.-LB.

Tighten Screws to 10 IN.-LB.

nc-dmx-265

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

13-9

Routine maintenance procedures Procedure 13-2: Replace Metropolis

®

DMX standard shelf

Figure 13-4 Metropolis

®

DMX mounting bracket positions - 19-inch frame

19-inch Frame - Rear Mounted

REAR

FRONT

Tighten Screws to 10 IN.-LB.

19-inch Frame - Front Mounted

Tighten Screws to 10 IN.-LB.

nc-dmx-259

17

.................................................................................................................................................................................................

Determine the position that the Metropolis

®

DMX shelf will be mounted.

Figure 13-5, “Typical Metropolis

®

DMX standard shelf bay mounting arrangements”

(p. 13-11)

shows the recommended mounting positions for a standard shelves.

.................................................................................................................................................................................................................................

13-10 365-372-301 R6.0

Issue 15, January 2006

Routine maintenance procedures Procedure 13-2: Replace Metropolis

®

DMX standard shelf

The Metropolis

®

DMX High Capacity shelf has an integrated fan shelf.

Figure 13-9,

“Typical Metropolis

®

DMX High Capacity shelf bay mounting arrangements”

(p. 13-21)

shows the recommended mounting positions for a high capacity shelves.

Figure 13-5 Typical Metropolis

®

DMX standard shelf bay mounting arrangements

FAN SHELF

DMX SHELF

FAN SHELF

DMX SHELF

FAN SHELF

DMX SHELF

FAN SHELF

DMX SHELF

3.47"

0.50"

15.97" nc-dmx-257

18

.................................................................................................................................................................................................

Position the Metropolis

®

DMX replacement shelf in the frame and secure the shelf to the frame using the thread-forming screws included with the shelf (3 screws per side).

Tighten the screws to 21 in.-lb. (minimum)/30 in.-lb. (maximum)

Figure 13-6, “Metropolis

®

DMX shelf mounted to the rear of a 23-inch frame”

(p. 13-12)

shows the Metropolis

®

DMX shelf being mounted to the rear of a 23-inch frame in a fully equipped Metropolis

®

DMX bay. The fan shelf may or may not be replaced while replacing the shelf.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

13-11

Routine maintenance procedures Procedure 13-2: Replace Metropolis

®

DMX standard shelf

Important! Be sure to mount the shelf using the thread-forming screws provided with the shelf to ensure a solid ground connection from the bay to the shelf.

Figure 13-6 Metropolis

®

DMX shelf mounted to the rear of a 23-inch frame

Fan Shelf

Fan Shelf

DMX Shelf

Fan Shelf

DMX Shelf

Fan Shelf

84.00"

25.875"

0.50 Inch Space for Ventilation

®

DMX = Metropolis DMX Access Multiplexer nc-dmx-263

19

.................................................................................................................................................................................................

Verify with an ohmmeter that the Metropolis

®

DMX shelf is grounded to the bay frame. Measure between the Metropolis

®

DMX shelf mounting bracket and the office ground lug on the bay frame.

.................................................................................................................................................................................................................................

13-12 365-372-301 R6.0

Issue 15, January 2006

Routine maintenance procedures Procedure 13-2: Replace Metropolis

®

DMX standard shelf

20

21

22

23

24

25

26

27

Result:

The ohmmeter reads less than 1 ohm.

.................................................................................................................................................................................................

Ensure that both 20-ampere circuit breakers on the Metropolis

®

DMX shelf to the OFF position.

Important! A small flat-bladed screwdriver or other similar type tool is required to operate the circuit breakers to the OFF position.

.................................................................................................................................................................................................

Reconnect the A and B power connectors to the left and right sides of the Metropolis

®

DMX shelf.

.................................................................................................................................................................................................

At the rear of the shelf, reconnect all cables based on the labels placed on them when they were removed. If your replacement shelf is a Metropolis

®

DMX High Capacity shelf with high density circuit packs, you must also install additional DS1 cables and/or replace existing DS3 cables with double- density DS3 cabling.

.................................................................................................................................................................................................

Restore power to the Metropolis

®

DMX shelf by operating the circuit breakers to the

ON position at the Battery Distribution Feeder Bay (BDFB) or replacing the fuses at the BDFB.

Important! Restore power for both the A and B feeders.

.................................................................................................................................................................................................

Operate both 20-ampere circuit breakers on the Metropolis

®

DMX shelf to the ON position. These breakers are located on the front of the shelf.

Result:

The fans start running and both

PWR (A)

and

PWR (B)

LEDs on the front of the shelf light.

.................................................................................................................................................................................................

Fully engage the LNW1 SYSCTL circuit pack in the shelf.

.................................................................................................................................................................................................

Fully engage the M1 and M2 circuit packs in the shelf.

.................................................................................................................................................................................................

Starting at the left side of the shelf, fully engage each circuit pack in the shelf.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

13-13

Routine maintenance procedures Procedure 13-2: Replace Metropolis

®

DMX standard shelf

28

Result:

ACTIVE

After approximately three minutes, all circuit packs have a lighted, green

LED.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Signal performance may be degraded if the connectors/adapters, fiber, and LBOs are not cleaned.

Ensure all optical fiber connectors/adapters, fiber, and LBOs are properly cleaned.

29

30

31

32

Clean and reconnect all optical fibers to the front of the optical circuit packs based on the fiber labels attached earlier and the circuit pack positions noted.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Place loose fibers in the shelf fiber tray.

.................................................................................................................................................................................................

Reconnect the LAN and CIT cables (if equipped) to the front of the LNW1 SYSCTL circuit pack.

.................................................................................................................................................................................................

Connect the WaveStar

®

CIT and log into the shelf.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

From the System View window, click on

Alarm List

button and verify that there are no alarms, lockouts, loopbacks, or switches present.

If required, refer to the appropriate trouble clearing procedures to clear any existing alarms.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

13-14 365-372-301 R6.0

Issue 15, January 2006

Routine maintenance procedures

Procedure 13-3: Replace Metropolis

®

DMX High Capacity shelf

.................................................................................................................................................................................................................................

Overview

Use this procedure to replace the Metropolis

®

DMX Access Multiplexer High Capacity shelf (C848793287). The High Capacity shelf has an integrated fan shelf. The standard shelf has a separate fan shelf.

Important! It is assumed that the Metropolis

®

DMX High Capacity shelf is out of service. Power to the shelf will be removed in this procedure.

Required equipment

Important! A Metropolis

®

DMX High Capacity shelf can only be replaced with a

Metropolis

®

DMX High Capacity shelf.

The following equipment is required:

•

Replacement Metropolis

®

DMX High Capacity shelf. (Refer to Engineering

Drawing ED8C871-10 for a complete list of required cables.)

•

Personal Computer (PC) with WaveStar

®

CIT software installed

•

Wrist strap

•

Optical fiber connector dust covers

•

Optical circuit pack connector dust covers

•

ESD protective bags for temporary storage of circuit packs

•

Metropolis

®

DMX Access Multiplexer Installation Manual, 365-372-304

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 13-2)

in this chapter

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Verify that the Metropolis

®

DMX High Capacity shelf is out of service.

Step

1

Complete the following steps to replace a Metropolis

®

DMX High Capacity shelf.

.................................................................................................................................................................................................

Remove power from the Metropolis

®

DMX High Capacity shelf by operating the circuit breakers to the OFF position at the Battery Distribution Fuse Bay (BDFB) in the central office or removing the fuses at the BDFB.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

13-15

Routine maintenance procedures Procedure 13-3: Replace Metropolis

®

DMX High Capacity shelf

2

3

4

5

6

Important! Remove power for both A and B feeders to the shelf.

Result:

Both

PWR (A)

and

PWR (B)

LEDs on the front of the shelf extinguish.

Reference:

Refer to the user documentation for your BDFB for more information.

.................................................................................................................................................................................................

Disconnect the A and B power connectors from the left and right sides of the

Metropolis

®

DMX High Capacity shelf.

.................................................................................................................................................................................................

Using a voltmeter, measure the voltage on the power cable connectors (looking towards the BDFB) between BAT A and BAT A RTN (red cable).

Result:

Voltmeter indicates no voltage.

.................................................................................................................................................................................................

Using a voltmeter, measure the voltage on the power cable connectors (looking towards the shelf’s backplane) between BAT B and BAT B RTN (blue cable).

Result:

Voltmeter indicates no voltage.

.................................................................................................................................................................................................

On the backplane, label all cables connecting to the Metropolis

®

DMX High Capacity shelf. These include:

•

DS1/DS3/EC1/FastE Transmission Cables as equipped (J1, J2, J3, J4, J5, J6, J7, J8,

J20, J21, J22, J23, J24, J25, J26, J27)

•

IAO LAN (J16)

•

Modem cable (J17)

•

TL1 Interface Cable (J10)

•

Sync Cables (J9 and J14)

•

Office Alarm Cable (J12)

•

Alarm Mult (J13)

•

Miscellaneous (Environmental) Discrete (J11)

.................................................................................................................................................................................................

Remove all cables from the Metropolis

®

DMX High Capacity shelf backplane. It may be necessary to untie the cables from the cable tie bar.

.................................................................................................................................................................................................................................

13-16 365-372-301 R6.0

Issue 15, January 2006

Routine maintenance procedures Procedure 13-3: Replace Metropolis

®

DMX High Capacity shelf

7

8

9

10

11

12

13

14

It is not necessary to disconnect the power cables on the backplane connectors (P15 and P14); they are internal to the shelf that is being removed.

.................................................................................................................................................................................................

On the front of the Metropolis

®

to circuit packs. These include:

DMX High Capacity shelf, label all cables connecting

•

Optical Fibers connected to the Main OLIUs (Transmit/Receive)

•

Optical Fibers connected to OC3/OC12/OC48 Low Speed OLIUs in Function Slots

A, B, C, D and Growth Slots (Transmit/Receive)

•

Optical Fibers connected to Gigabit Ethernet Circuit Packs in Function Slots A, B,

C, D and Growth Slots (Transmit/Receive)

•

LAN cable

•

CIT cable

.................................................................................................................................................................................................

Remove all cables from circuit packs in the Metropolis

®

DMX High Capacity shelf.

.................................................................................................................................................................................................

Place protective dust covers on fiber connections (fibers and circuit packs).

.................................................................................................................................................................................................

Note the position of each circuit pack (Function slot number or Growth slot) for reference when installing the new shelf.

.................................................................................................................................................................................................

Carefully remove the fibers from the Metropolis

®

DMX High Capacity shelf fiber tray.

.................................................................................................................................................................................................

Disengage and remove each circuit pack and place each in an ESD protective bag.

.................................................................................................................................................................................................

Unscrew the mounting screws that attach the Metropolis

®

DMX High Capacity shelf to the bay frame and remove the shelf.

Important! Do not disturb cables associated with other Metropolis

®

DMX High

Capacity shelves in the bay or equipment in adjacent bays.

.................................................................................................................................................................................................

Inspect the replacement Metropolis

®

DMX High Capacity shelf for visible damage including bent or touching backplane pins.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

13-17

Routine maintenance procedures Procedure 13-3: Replace Metropolis

®

DMX High Capacity shelf

15

16

.................................................................................................................................................................................................

Determine the mounting configuration for the Metropolis

®

DMX High Capacity shelf:

• type of bay frame (23-inch or 19-inch wide)

• mounting position (front or rear)

• position in bay (bottom to top).

Important! The Metropolis

®

DMX High Capacity shelf is shipped with the mounting brackets positioned for mounting to the rear of a 23-inch wide network bay frame. The Metropolis

®

DMX High Capacity shelf mounting brackets may have to be repositioned and remounted, depending on the frame type and mounting position (front or rear).

.................................................................................................................................................................................................

If necessary, reposition the shelf mounting brackets accordingly.

For 23-inch frame, front or rear mounting, refer to

Figure 13-7, “Metropolis

®

DMX

High Capacity mounting bracket positions - 23-inch frame” (p. 13-19) .

.................................................................................................................................................................................................................................

13-18 365-372-301 R6.0

Issue 15, January 2006

Routine maintenance procedures Procedure 13-3: Replace Metropolis

®

DMX High Capacity shelf

For 19-inch frame, front or rear mounting, refer to

Figure 13-8, “Metropolis

®

High Capacity mounting bracket positions - 19-inch frame” (p. 13-19) .

DMX

Figure 13-7 Metropolis

®

DMX High Capacity mounting bracket positions -

23-inch frame

23-inch Frame - Rear Mounted (as shipped)

REAR FRONT

23-inch Frame - Front Mounted

Tighten Screws to 10 IN.-LB.

Tighten Screws to 10 IN.-LB.

nc-dmx-265

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

13-19

Routine maintenance procedures Procedure 13-3: Replace Metropolis

®

DMX High Capacity shelf

Figure 13-8 Metropolis

®

DMX High Capacity mounting bracket positions -

19-inch frame

19-inch Frame - Rear Mounted

REAR FRONT

19-inch Frame - Front Mounted

Tighten Screws to 10 IN.-LB.

Tighten Screws to 10 IN.-LB.

nc-dmx-259

17

.................................................................................................................................................................................................

Determine the position that the Metropolis

®

DMX High Capacity shelf will be mounted.

.................................................................................................................................................................................................................................

13-20 365-372-301 R6.0

Issue 15, January 2006

Routine maintenance procedures Procedure 13-3: Replace Metropolis

®

DMX High Capacity shelf

Figure 13-9, “Typical Metropolis

®

DMX High Capacity shelf bay mounting arrangements” (p. 13-21)

shows the recommended mounting positions.

Figure 13-9 Typical Metropolis

® arrangements

DMX High Capacity shelf bay mounting

DMX

High Capacity

Shelf

DMX

High Capacity

Shelf

19”

DMX

High Capacity

Shelf

DMX

High Capacity

Shelf nc-dmx-300

18

.................................................................................................................................................................................................

Position the Metropolis

®

DMX High Capacity shelf in the frame and secure the shelf to the frame using the thread-forming screws included with the shelf (3 screws per side). Tighten the screws to 21 in.-lb. (minimum)/30 in.-lb. (maximum)

Figure 13-10, “Metropolis

®

DMX High Capacity shelf mounted to the rear of a

23-inch frame” (p. 13-22)

shows the Metropolis

®

DMX High Capacity shelf being mounted to the rear of a 23-inch frame in a fully equipped Metropolis

®

DMX bay.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

13-21

Routine maintenance procedures Procedure 13-3: Replace Metropolis

®

DMX High Capacity shelf

Important! Be sure to mount the shelf using the thread-forming screws provided with the shelf to ensure a solid ground connection from the bay to the shelf.

Figure 13-10 Metropolis

®

DMX High Capacity shelf mounted to the rear of a

23-inch frame

DMX High

Capacity

Shelf

16.00"

Fan Unit

84.00"

DMX High

Capacity

Shelf

Fan Unit

DMX High

Capacity

Shelf

Fan Unit

0.50 Inch Space for Ventilation

®

DMX = Metropolis DMX Access Multiplexer

25.875" nc-dmx-262

19

.................................................................................................................................................................................................

Verify with an ohmmeter that the Metropolis

®

DMX High Capacity shelf is grounded to the bay frame. Measure between the Metropolis

®

DMX High Capacity shelf mounting bracket and the office ground lug on the bay frame.

Result:

The ohmmeter reads less than 1 ohm.

.................................................................................................................................................................................................

20

Ensure that both circuit breakers on the Metropolis

®

DMX High Capacity shelf to the

OFF position.

.................................................................................................................................................................................................................................

13-22 365-372-301 R6.0

Issue 15, January 2006

Routine maintenance procedures Procedure 13-3: Replace Metropolis

®

DMX High Capacity shelf

21

22

23

24

25

26

27

28

Important! A pen or similar object is required to operate the circuit breakers to the

OFF position.

.................................................................................................................................................................................................

Reconnect the A and B power connectors to the left and right sides of the Metropolis

®

DMX High Capacity shelf.

.................................................................................................................................................................................................

At the rear of the shelf, reconnect all cables based on the labels placed on them when they were removed.

.................................................................................................................................................................................................

Restore power to the Metropolis

®

DMX High Capacity shelf by operating the circuit breakers to the ON position at the Battery Distribution Feeder Bay (BDFB) or replacing the fuses at the BDFB.

Important! Restore power for both the A and B feeder.

.................................................................................................................................................................................................

Operate both circuit breakers on the Metropolis

®

DMX High Capacity shelf to the ON position. These breakers are located on the front of the shelf.

Result:

The fans start running and both

PWR (A)

and

PWR (B)

LEDs on the front of the shelf light.

.................................................................................................................................................................................................

Fully engage the LNW1 SYSCTL circuit pack in the shelf.

.................................................................................................................................................................................................

Fully engage the M1 and M2 circuit packs in the shelf.

.................................................................................................................................................................................................

Starting at the left side of the shelf, fully engage each circuit pack in the shelf.

Result:

ACTIVE

After approximately three minutes, all circuit packs have a lighted, green

LED.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Signal performance may be degraded if the connectors/adapters, fiber, and LBOs are not cleaned.

Ensure all optical fiber connectors/adapters, fiber, and LBOs are properly cleaned.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

13-23

Routine maintenance procedures Procedure 13-3: Replace Metropolis

®

DMX High Capacity shelf

29

30

31

32

Clean and reconnect all optical fibers to the front of the optical circuit packs based on the fiber labels attached earlier and the circuit pack positions noted.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Place loose fibers in the shelf fiber tray.

.................................................................................................................................................................................................

Reconnect the LAN and CIT cables (if equipped) to the front of the LNW1 SYSCTL circuit pack.

.................................................................................................................................................................................................

Connect the WaveStar

®

CIT and log into the shelf.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

From the System View window, click on

Alarm List

button and verify that there are no alarms, lockouts, loopbacks, or switches present.

If required, refer to the appropriate trouble clearing procedures to clear any existing alarms.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

13-24 365-372-301 R6.0

Issue 15, January 2006

Routine maintenance procedures

Procedure 13-4: Enter/exit pluggable transmission module maintenance state

.................................................................................................................................................................................................................................

Overview

Use this procedure to enter or exit the pluggable transmission module maintenance state.

Pluggable transmission module maintenance state

A pluggable transmission module enters the maintenance state when the pluggable transmission module Maintenance State parameter is provisioned Maint.

When the Maintenance State parameter is provisioned Maint, the system reports

Pluggable transmission module maintenance IP and

ABN condition

. Any subsequent removal of the pluggable transmission module is reported with an alarm severity level no higher than a standing condition regardless of the assigned ASAP alarm severity level.

A pluggable transmission module remains in the maintenance state until the pluggable transmission module Maintenance State parameter is provisioned Normal (default value). Any subsequent removal of the pluggable transmission module is reported using the applicable assigned ASAP alarm severity level.

Entering/exiting the Maintenance state does not affect the alarm severity level of any existing removal alarms.

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 13-2)

in this chapter

2. Obtain the work instructions for this procedure.

3. Verify that the work instructions specify the required pluggable transmission module addresses.

Step

1

Complete the following steps to enter or exit the pluggable transmission module maintenance state.

.................................................................................................................................................................................................

From the System View window, select

Configuration

→

Equipment

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

13-25

Routine maintenance procedures Procedure 13-4: Enter/exit pluggable transmission module maintenance state

2

3

Result:

The Configure Equipment window opens.

.................................................................................................................................................................................................

Find the circuit pack with the required pluggable transmission module, then expand the equipment list by clicking on the plus (+) sign next to the required circuit pack. Select the required PTM and click

Select

.

Result:

The pluggable transmission module parameters appear.

.................................................................................................................................................................................................

Important! When the Maintenance State parameter is provisioned Maint, the pluggable transmission module enters the maintenance state. When the Maintenance

State parameter is provisioned Normal, the pluggable transmission module exits the maintenance state.

Provision the Maintenance State parameter according to the work instructions, then click

Apply

. Click

Close

to exit.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

13-26 365-372-301 R6.0

Issue 15, January 2006

14

14

Overview

.................................................................................................................................................................................................................................

Purpose

The following procedures are detailed step-by-step instructions that support other procedures. Procedures for installing the WaveStar

®

CIT software onto a PC, connecting the WaveStar

®

CIT to the NE, and establishing a WaveStar

®

CIT session with the NE are also included.

Contents

Before you begin

Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

Procedure 14-2: Connect Personal Computer (PC) and establish

WaveStar

®

CIT session

Procedure 14-3: Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)

Procedure 14-4: Perform connection and verification of optical facility

Procedure 14-5: Install/remove LC lightguide buildouts (LBOs)

Procedure 14-6: Connect OLIU optical loopbacks

Procedure 14-7: Perform end-to-end optical line test on Main OLIUs

Procedure 14-8: Perform end-to-end optical line test on Function OLIUs

Procedure 14-9: Perform DS1/E1 transmission test

Procedure 14-10: Perform DS3 transmission test

Procedure 14-11: Perform EC-1 transmission test

Procedure 14-12: Test function unit equipment protection switching

Procedure 14-13: Perform LED test

14-3

14-4

14-24

14-34

14-44

14-54

14-56

14-61

14-64

14-67

14-74

14-80

14-86

14-88

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-1

Supporting procedures

Procedure 14-14: Retrieve software generic release and database information

Procedure 14-15: Check -48 V DC office battery

Procedure 14-16: Operate/release facility or terminal loopbacks

Procedure 14-17: Observe FTP progress

Procedure 14-18: Disable an FTP server on your PC

Procedure 14-19: Reset the system

Procedure 14-20: Reset smart circuit pack

Procedure 14-21: Change the network card selection

Procedure 14-22: Replace defective fan unit

Procedure 14-23: Establish test access session in the MON(E or EF) mode

Procedure 14-24: Establish test access session in the SPLT(E or EF) mode

Procedure 14-25: Change test access mode of test access session

Procedure 14-26: Delete test access session

Procedure 14-27: View test access session(s)

Procedure 14-28: View reports

Procedure 14-29: Clean optical pluggable transmission module

Procedure 14-30: Connect modems to establish communication from remote CIT location

Overview

14-90

14-93

14-97

14-101

14-103

14-105

14-108

14-110

14-111

14-114

14-121

14-127

14-129

14-130

14-131

14-135

14-138

.................................................................................................................................................................................................................................

14-2 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Before you begin

.................................................................................................................................................................................................................................

Before you begin

Prior to performing most procedures in this chapter,

1. If not previously completed, install generic and WaveStar

®

CIT software on the PC.

Refer to

Procedure 14-1: “Install generic and WaveStar

®

CIT software on the PC”

(p. 14-4) .

2. Connect PC and establish a WaveStar

®

CIT session.

Refer to

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24) .

Required equipment

Most procedures in this chapter require the following equipment:

•

Personal Computer (PC) with WaveStar

®

CIT software installed

•

Wrist strap

Important! Also refer to the procedure to be performed for other equipment requirements. If other equipment is required to perform a specific procedure, that equipment is listed in the procedure.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-3

Supporting procedures

Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

.................................................................................................................................................................................................................................

Overview

Use this procedure to install the Metropolis

®

DMX software generic and WaveStar

®

CIT software on a personal computer (PC).

Required equipment

The following equipment is required:

•

Personal Computer (PC) with at least one network interface card (NIC)

•

Copy of the WaveStar

®

CIT software program on CD-ROM

Copy of the system generic software program on CD-ROM

•

Current Metropolis

®

DMX Access Multiplexer Software Release Description for the software generic being installed.

Before you begin

Before beginning the software installation procedure, complete the following steps:

Preinstallation Steps

1. Become familiar with the characteristics and operating procedures of your PC and the operating system installed.

2. Operate laptop PCs on AC power during download procedures.

3. Follow proper procedures in handling the CD-ROM.

4. Read the Metropolis

®

DMX Access Multiplexer Software Release Description for the software generic being installed.

5. Ensure that all the NEs and releases that you wish to manage with this WaveStar

®

CIT are included in the list of supported network elements in the readme.txt file.

To access this readme.txt file, referring to the graphic in

Step 2 , click on

Documents

and then

List Contents

. The readme.txt file contains additional user information, including a list of supported network elements.

Step

1

Complete the following steps to install the WaveStar

®

CIT software and system software generic on your PC.

.................................................................................................................................................................................................

Insert the CD-ROM into the PC.

.................................................................................................................................................................................................................................

14-4 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

Result:

The CD autoruns and the following window opens:

2

If the CD-ROM does not autorun, verify that the CD is inserted properly in your

CD-ROM drive.

1. Double-click on My Computer on your desktop.

2. Double-click on your Compact Disc icon (often identified as drive D:)

3. Double-click on setup.exe

In the figure above Rxx.xx.xx represents the WaveStar

®

example R15.02.00.

CIT release number, for

.................................................................................................................................................................................................

Click

continue

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-5

Supporting procedures

Result:

The following window opens:

Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

3

.................................................................................................................................................................................................

Click

CIT Software

.

.................................................................................................................................................................................................................................

14-6 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Result:

The following window opens:

Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

4

5

.................................................................................................................................................................................................

Click

WaveStar CIT

to install the WaveStar

®

CIT software.

Result:

Either the WaveStar CIT InstallShield or the WaveStar CIT maintenance

installation screen appears.

.................................................................................................................................................................................................

Do you have a previous version of the WaveStar

®

CIT installed on your computer?

If...

Yes

Then...

Continue with

Step 6 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-7

Supporting procedures

If...

No

Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

Then...

Proceed to

Step 10 .

6

.................................................................................................................................................................................................

When the following window opens, select

Select to: Modify, Update, or Repair the current installation

. Click

Continue

.

7

.................................................................................................................................................................................................

Select either

•

Enable WaveStar CIT logins

to require that users enter a user ID and password to login to the WaveStar

®

CIT or

•

Disable WaveStar CIT logins

to allow users to run the WaveStar

®

CIT without entering a user ID and password.

.................................................................................................................................................................................................................................

14-8 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Click

Next

.

Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

8

.................................................................................................................................................................................................

Select either

•

Enable WaveStar CIT FTP Server

or

•

Disable WaveStar CIT FTP Server

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-9

Supporting procedures

Click

Next

.

Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

9

If the WaveStar

®

CIT FTP Server is disabled during installation, the FTP Server must be started manually from the Network View menu,

Administration

→

FTP

Administration

.

.................................................................................................................................................................................................

Do you see the Reboot Required screen illustrated below?

If...

Yes

No

Then...

The WaveStar

®

CIT installer has detected an older version of the WaveStar

®

CIT on your PC which must be removed prior to the new WaveStar

®

CIT installation.

Select

″

Yes, I want to restart my computer now

.

″

Click

OK

. After your computer reboots, restart the installation from

Step 1 .

Proceed to

Step 16 .

.................................................................................................................................................................................................................................

14-10 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

10

.................................................................................................................................................................................................

When the InstallShield

®

Wizard appears, click

Next

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-11

Supporting procedures Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

11

.................................................................................................................................................................................................

Follow the instructions on the different InstallShield

®

Wizard windows, including reading and agreeing to the following two License Agreements.

.................................................................................................................................................................................................................................

14-12 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Click

Yes

.

Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

Click

Yes

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-13

Supporting procedures Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

12

.................................................................................................................................................................................................

Select where you want the WaveStar

®

CIT software installed on your PC.

•

Select the default Destination Folder: C:\Program Files\Lucent Technologies\

OR

•

Click

Browse

and navigate to your desired directory.

Click

Next

.................................................................................................................................................................................................................................

14-14 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

13

.................................................................................................................................................................................................

Select either

•

Enable WaveStar CIT logins

to require that users enter a user ID and password to login to the WaveStar

®

CIT or

•

Disable WaveStar CIT Logins

to allow users to run the WaveStar

®

CIT without entering a user ID and password.

14

.................................................................................................................................................................................................

Select either

•

Enable WaveStar CIT FTP Server

or

•

Disable WaveStar CIT FTP Server

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-15

Supporting procedures

Click

Next

.

Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

.................................................................................................................................................................................................................................

14-16 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

15

Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

If the WaveStar

®

CIT FTP Server is disabled during installation, the FTP Server must be started manually from the Network View menu,

Administration

→

FTP

Administration

.

.................................................................................................................................................................................................

Select

WaveStar CIT

.

Click

Next

.

Important! This step only applies to new installations. Users should ignore this step when performing upgrade installations.

.................................................................................................................................................................................................

16

Select the components you wish to install:

•

Network View

(Required)

•

CutThrough View

(Recommended)

•

Command Builder

(Recommended)

•

BWM Graphical Package

•

SANE Graphical Package

•

METRO Graphical Package

(Required)

–

METRO On-Line Help Files

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-17

Supporting procedures Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

If you do not wish to install on-line help for any of the METRO products

(Metropolis

®

DMXtend, Metropolis

®

DMXpress, Metropolis

®

DMXplore, and

Metropolis

®

DMX), you may uncheck the

METRO On-Line Help Files

box.

•

UNITE Graphical Package

–

UNITE On-Line Help Files

If you do not wish to install on-line help for LambdaUnite MSS, you may uncheck the

UNITE On-Line Help Files

box.

Important! The initial component selections that appear are based on the previous installation.

In order to save valuable disk space and reduce installation time, you may deselect the graphical packages for all products that you do not plan to manage with this

WaveStar

®

CIT.

Space Required on “C”: indicates the space required to install you selected components. (“C” may be a different drive if you specified an installation location other than Drive C.) If you had a previous version of the WaveStar

®

CIT installed on your computer and you are not changing your selected components, the Space

Required on “C”: is zero. In this situation, the components are already resident on the computer, therefore no additional space required when performing an upgrade.

.................................................................................................................................................................................................................................

14-18 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

17

If any additional (new) package(s) are selected, the space required for those specific packages is displayed.

.................................................................................................................................................................................................

Click

Next

.

Result:

The following dialog box appears asking you to confirm your component selection.

18

Your list of selected components may be different from the figure above.

.................................................................................................................................................................................................

Click

Yes

.

Result:

You are prompted with the choice to install OSI (Open System Interconnect) communications protocol.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-19

Supporting procedures Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

19

.................................................................................................................................................................................................

If you wish to install OSI click

Yes

, otherwise, click

No

.

Result:

The following progress indicator screen appears while the InstallShield

®

Wizard installs the required files.

.................................................................................................................................................................................................................................

14-20 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

20

.................................................................................................................................................................................................

If you wish to copy the NE software to your PC, select

Yes

on the following screen.

21

.................................................................................................................................................................................................

Did you select Yes or No in

Step 20 ?

If...

Yes

No

Then...

Continue with

Step 22 .

Proceed to

Step 23 .

If you wish to install the NE software later, return to the

WaveStar CIT CD Browser

window, click on

NE Software

, click

NE Software (Copy the NE Software to the PC)

on the right.

A

Copying files, please wait

window appears.

When the window closes, the software files are successfully copied into the generics directory on your PC.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-21

Supporting procedures Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

22

.................................................................................................................................................................................................

A

Copying files, please wait

window appears. When the window closes, the software files are successfully copied into the generics directory on your PC. By default, this directory is

C:\Program Files\Lucent Technologies\WaveStar CIT\generics\DMX\6.0.1\p\

, however, the actual directory is determined by the path defined in

Step 12 .

Result:

After the NE software is successfully copied to the appropriate directory.

If you answered yes in

Step 5 , you will still have the following folder on your

Desktop. If you answered no in

Step 5 , you will not see this folder.

23

.................................................................................................................................................................................................

When the following window appears, the installation is complete.

.................................................................................................................................................................................................................................

14-22 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-1: Install generic and WaveStar

®

CIT software on the PC

24

.................................................................................................................................................................................................

Important! Before using your new WaveStar

®

computer.

CIT, you MUST reboot your

Select

Yes, I want to restart my computer now.

and click

Finish

.

Result:

The following icon appears on your desktop. Clicking on this short-cut icon launches the WaveStar

®

CIT.

25

If you did not install the NE software in

Step 20 , proceed to

Step 25 .

.................................................................................................................................................................................................

Important! The InstallShield

®

Wizard may create temporary folders/files in the PC system Temp folder. Temporary folders/files stored in the PC system Temp folder decrease available disk free space and may affect system performance.

If desired, close all open applications running on the PC and delete the appropriate temporary folders/files from the system Temp folder.

Windows 2000 and Windows XP operating systems provide a Disk Cleanup Wizard that can be used to remove temporary folders/files. To use the Disk Cleanup

Wizard select

Start

→

Programs

→

Accessories

→

System Tools

→

Disk

Cleanup

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-23

Supporting procedures

Procedure 14-2: Connect Personal Computer (PC) and establish

WaveStar

®

CIT session

.................................................................................................................................................................................................................................

Overview

Use this procedure to connect PC and establish a WaveStar

®

CIT session.

Important! You must be a member of either the Administrators Group or the

Power Users Group on your PC to establish a WaveStar

®

CIT session.

This procedure assumes that TCP/IP and OSI connectivity has been established to the required network elements in the network.

Required equipment

At least one of the following cables is required:

•

RS-232 cable with an RJ-45 connector on one end and a PC serial connector on the other (typically DB9) for the

RS232

port

•

CAT5 Ethernet cable with either a 10/100 hub or a cross-over cable for the

LAN

or

IAO LAN

ports. If you are connecting the PC directly to the NE, use the LAN

10Base-T cross-over cable. If you are connecting the PC directly to a hub, use the

LAN 10Base-T straight-through cable.

For detailed cabling information, refer to the Metropolis

®

Installation Manual, 365-372-304.

DMX Access Multiplexer

Before you begin

Prior to performing this procedure:

1. Refer to

Procedure 14-1: “Install generic and WaveStar

®

(p. 14-4) .

CIT software on the PC”

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. If WaveStar

®

CIT logins were enabled during installation, obtain a valid user ID and password for the WaveStar

®

CIT.

4. Obtain a valid user ID and password for the required network element.

5. Obtain the Target Identifier (TID)/NE name of the network element that you are establishing a WaveStar

®

CIT session with.

6. If establishing a WaveStar

®

CIT session with a network element using TCP/IP protocol, obtain the required IP address of the network element or gateway network element (if applicable).

7. If establishing a WaveStar

®

CIT session with a network element using OSI protocol, obtain the required NSAP address of the network element (if applicable).

Also refer to the CIT OSI Neighbors view and Address List from the WaveStar

®

CIT Network View.

.................................................................................................................................................................................................................................

14-24 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Step

Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar

®

CIT session

1

Complete the following steps to connect PC and establish a session.

.................................................................................................................................................................................................

Connect your PC (using the appropriate cable[s]) to at least one of the following ports:

•

RS232

serial port on the faceplate of the SYSCTL circuit pack to an available

COM port (COM1 or COM2) of the PC

•

LAN

port on the faceplate of the SYSCTL circuit pack to the NIC card of PC. If you are connecting the PC directly to the NE, use the LAN 10Base-T cross-over cable. If you connecting the PC to a hub, use the LAN 10Base-T straight-through cable.

•

J16 IAO LAN

port on the rear of the Metropolis

®

DMX shelf to the NIC card of PC.

If you are connecting the PC directly to the NE, use the LAN 10Base-T cross-over cable. If you are connecting the PC to a hub, use the LAN 10Base-T straight-through cable.

Important! You can be connected simultaneously to both the

RS232

and the front

LAN

or the rear

J16 IAO LAN

.

If you are uncertain that the LAN ports have already been provisioned, connecting via the serial port is recommended.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-25

Supporting procedures

2

Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar

®

CIT session

.................................................................................................................................................................................................

Start the WaveStar

®

CIT software on the PC by double-clicking on the WaveStar icon on your desktop (created by the installation procedure).

®

CIT

Figure 14-1 WaveStar

®

CIT welcome screen

3

.................................................................................................................................................................................................

Important! If you selected

Disable WaveStar CIT logins

during the WaveStar

®

CIT installation, you do not have to login to the WaveStar

®

CIT. You will see the

WaveStar

®

CIT legal notice ( Figure 14-3, “Legal notice” (p. 14-28) ).

.................................................................................................................................................................................................................................

14-26 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar

®

CIT session

Enter a valid User ID and password in the WaveStar

®

CIT Login screen and click

OK

.

Figure 14-2 WaveStar

®

CIT login screen

Important! LUC01/LUC+01 and LUC02/LUC+02 are the default User

ID/passwords for the WaveStar

®

CIT. It is highly recommended that you change these User IDs and passwords during your first session to preserve the security of your equipment. (To change your WaveStar

®

→

Change Password

from the WaveStar

®

CIT password, select

CIT Network View.)

Administration

User IDs must adhere to the following guidelines:

•

User IDs must be one to ten alphanumeric characters in length.

•

User IDs are case sensitive.

Passwords must adhere to the following guidelines:

•

Passwords must be six to ten characters in length.

•

Passwords must begin with a letter.

•

Passwords must contain at least two non-alphabetic characters (numbers or symbols). At least one of the non-alphabetic characters must be a symbol.

Symbols may not include space ( ), commercial at (@), comma (,), colon (:), equals sign (=), quotation mark (

″

), semicolon (;), ampersand (&), horizontal bar (underscore) (_), question mark (?).

•

Passwords are case sensitive.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-27

Supporting procedures Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar

®

CIT session

Result:

The Legal Notice appears. (Refer to the following figure.)

Figure 14-3 Legal notice

4

.................................................................................................................................................................................................

Read the Legal Notice and click

OK

.

.................................................................................................................................................................................................................................

14-28 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar

®

CIT session

Result:

The Network View screen appears. (Refer to the following figure. If your

PC is running a different version of WaveStar

®

CIT software, there may be some differences between the screen shown in the following figure and what is displayed on your PC.)

Figure 14-4 Example of network view

5

6

.................................................................................................................................................................................................

Enter the NE name/TID of the shelf that you wish to communicate with in the

NE

Name:

field. If you have previously established communications with the NE from this

WaveStar

®

CIT, click on the drop-down arrow and select the appropriate NE from the list.

.................................................................................................................................................................................................

In the

NE Type:

field, click on the drop-down arrow and select Metropolis(R) DMX

Access Multiplexer.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-29

Supporting procedures

7

8

Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar

®

CIT session

.................................................................................................................................................................................................

In the

Connection Type

: field, click on the drop-down arrow and select the appropriate connection type.

•

Serial should be selected if you are connected locally to the serial

RS232

port on the SYSCTL circuit pack. To establish a WaveStar

®

CIT session to a remote network element, you must have DCC connectivity. Also refer to the WaveStar

®

CIT CIT OSI Neighbors view and Address List. See the information in

“Before you begin” (p. 14-24) .

•

OSI should be selected if

– you are connected locally to LAN-1, the front

LAN

port on the SYSCTL circuit pack, OR LAN-2, the rear

J16 IAO LAN

port on the backplane, AND

– the LAN port is provisioned to use OSI protocol

To establish a WaveStar

®

CIT session to a remote network element, you must have

DCC connectivity. Also refer to the WaveStar

®

CIT CIT OSI Neighbors view and

Address List. See the information in

“Before you begin” (p. 14-24) .

•

TCP/IP should be selected if

– you are connected locally to LAN-1, the front

LAN

port on the SYSCTL circuit pack, OR LAN-2, the rear

J16 IAO LAN

port on the backplane, AND

– the LAN port is provisioned to use TCP/IP protocol, AND

– you know the IP address of the NE.

To establish a WaveStar

®

CIT session to a remote network element, you must have network connectivity and the IP address of the remote network element or gateway network element.

.................................................................................................................................................................................................

After completing the three fields, click on the

Graphical

button.

If you select the TCP/IP option, you must also enter the IP address of your NE and then click

OK

.

Important! All procedures in this manual assume that the Graphical button is used.

However, the

TL1

button can be selected to communicate directly with the network element using the TL1 Cut Through or Command Builder interface.

.................................................................................................................................................................................................................................

14-30 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

9

Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar

®

CIT session

.................................................................................................................................................................................................

An NE Login screen ( Figure 14-5, “NE login” (p. 14-31) ) appears:

Figure 14-5 NE login

10

Enter a valid User ID and password to log in to the NE:

By selecting the

Enable these as the default values

checkbox, you will be able to reconnect to this NE without entering the User ID and Password. However, if you attempt to connect to a different NE that does not have the same User ID and password, the connection will fail and you will be prompted to enter a valid User ID and password. The User ID and Password are stored for the duration of the CIT session and must be re-entered when the CIT is restarted.

Important! LUC01, LUC02, and LUC03 are the default privileged user IDs and

DMX2.5G10G is the default privileged password for Metropolis

®

DMX. It is highly recommended that you change all three user IDs and passwords during your first session to preserve the security of your equipment. (To change your network element password, refer to

Procedure 7-2: “Change your own password” (p. 7-10) .)

.................................................................................................................................................................................................

If the login is successful, the NE Legal Notice screen appears.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-31

Supporting procedures Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar

®

CIT session

If the login is not successful, try one of the following:

•

If you are connected locally to the

RS232

serial port, check cable connections.

Check COM port baud rate settings by selecting

Administration

→

Serial COM

Selection

from the WaveStar

®

CIT Network View. Try different COM port settings. The NE default baud rate setting for the

RS232

serial port (cit-1) is 9600.

The rate of the COM port must match the rate of the CIT port on the NE.

•

If you are connected locally to LAN-1 or LAN-2 and using the OSI protocol, check your network card (NIC) settings. Some NIC cards have an 802.1b option which must be enabled for OSI to work.

•

If you are connected locally to LAN-1 or LAN-2 and using the TCP/IP protocol, make sure you are entering the correct TCP/IP address.

Important! Your NE software Release number and User Privilege Level may be different. Your screen should be similar to

Figure 14-6, “NE level legal notice”

(p. 14-32) .

Figure 14-6 NE level legal notice

11

.................................................................................................................................................................................................

Read and observe the software Release (for example, 5.1.0), and the User Privilege

Level (for example,

Privileged

). Click

OK

to continue.

Important! The date and time of the last successful login and the number of unsuccessful login attempts are displayed.

Result:

The WaveStar

®

CIT System View window opens.

.................................................................................................................................................................................................

12

Familiarize yourself with the different aspects of the graphical presentation of the shelf, including the toolbars, and status indicators.

.................................................................................................................................................................................................................................

14-32 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar

®

CIT session

The WaveStar

®

CIT is designed to Microsoft Windows

®

standards.

The WaveStar

®

CIT System View has a menu bar at the top of the screen, and status indicators at the bottom of the screen. Each item on the menu bar has pull-down menus and submenus. (See

Figure 14-7, “Example of system view (graphical)”

(p. 14-33) .)

Figure 14-7 Example of system view (graphical)

TID NE Type

Software

Release

Login

Type of

Connection

Alarm List Button

Update Alarms

Button

Menu Bar

Most Recent

Command

List

Shelf:

Slots,

Circuit

Packs, and Ports

Last Alarm Update Information Fuse Indicators Fan Unit Indicator NE Date and Time

MA-DMX-292

13

.................................................................................................................................................................................................

It is recommended that you create a View List for future convenience. From the

WaveStar

®

CIT Network View window (NOT the System View window), select

Administration

→

Administer Views

. Click on the

Help

button and use the information on that screen to create a View List.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-33

Supporting procedures

Procedure 14-3: Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)

.................................................................................................................................................................................................................................

Overview

This procedure describes the Lucent recommended method for the cleaning and inspection of optical connectors using specific tools and materials that have been proven to be effective in the assembly and testing of optical transmission equipment.

Required equipment

The following table lists required and recommended equipment for proper cleaning:

Product

Optical Fiber

Scope

2.5mm Universal adapter cap

1.25mm Universal adapter cap

Model/

Description

Noyes OFS

300-200X

For use with the

Noyes OFS

300-200X

For use with the

Noyes OFS

300-200X

Noyes VFS-1

Comcode

408197028

408197044

408197069

ITE #

ITE-7129

ITE-7129D1

ITE-7129D2

Installation

Order #

33712900

33712901

33712902

Video Fiber

Scope*

CLETOP

Cleaning Cassette

Type A Reel

TBD

901375154

TBD

ITE-7137

TBD

33713700

CLETOP

Cleaning Cassette

Replacement Reel

Type A Reel 901375014 ITE-7137 D1 33713701

Luminex Stick port cleaners

Luminex Stick port cleaners

1.25 mm

2.5 mm

901375030

901375022

ITE-7134

ITE-7135

33713400

33713500

Luminex Cloth 5.5

″ x 5.5

″

408201226 R6033 23603300

* This equipment may not be necessary at all locations. It is to be used when the ports need to be verified for cleanliness. If care is exercised when cleaning fibers, the video scope may not be needed.

Note: The equipment and material listed above has been tested and is proven effective when used in conjunction with this procedure. Substitution of equipment or materials is at the discretion of the user and is not recommended.

.................................................................................................................................................................................................................................

14-34 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-3: Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)

Related information

A course on connector cleaning and the connector inspection process is now offered through Lucent Technologies Learning and Performance Center, Course Code:

LMC200H Understanding Fiber Optic Cleaning, Inspection and Testing. To learn more about this course, consult your local Lucent Account Representative.

The procedure that follows utilizes the Dry method for connector cleaning. This method utilizes a dry double clean wipe using the CLETOP cleaning cassette.

This procedure is recommended for connector ferrules 2.5 mm and 1.25 mm in diameter associated with LC connectors. The ferrule of a fiber optic connector consists of a ceramic or stainless steel cylinder with a hole located longitudinally down the center of its axis, allowing enough tolerance for a fiber to pass through.

All optical connectors should be cleaned prior to being connected. Keep the protective ferrule dust cap on the connector until initiating the cleaning process.

Important! It is critical that connector faces are clean and free from particular contamination to assure proper performance and reliability of lightwave systems.

With the modern high-speed, high-power, and wider-bandwidth optical transmission systems, clean connectors along the optical path are essential for successful operation.

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

2. Obtain the work instructions for this procedure.

Step

1

2

Refer to the following supporting elements to complete this procedure.

.................................................................................................................................................................................................

To clean the optical fibers, refer to

Procedure 14-3.1: “Clean optical fibers” (p. 14-37) .

.................................................................................................................................................................................................

To clean the fiber adapters and LBOs, refer to

Procedure 14-3.2: “Clean fiber adapters and circuit pack connectors” (p. 14-40) .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-35

Supporting procedures Procedure 14-3: Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)

3

.................................................................................................................................................................................................

To inspect the optics following cleaning, refer to

Procedure 14-3.3: “Optical fiber and connector inspection” (p. 14-41) .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-36 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-3.1: Clean optical fibers

.................................................................................................................................................................................................................................

Overview

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34) .

Use this procedure to clean optical fibers.

Step

1

2

The following cleaning procedure is acceptable for field service/installation activities.

.................................................................................................................................................................................................

Remove the dust cap from the connector ferrule, thus exposing the connector endface.

.................................................................................................................................................................................................

If a CLETOP cassette cleaner is not available, proceed to

Step 6 . Otherwise, hold the

CLETOP cassette cleaner in the palm of your hand with the cassette shutter door facing up.

Rotate the cassette lever all the way down with your thumb. Do not release the lever.

The lever advances the

″ dry

″

Luminex cleaning cloth inside the case and

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-37

Supporting procedures Procedure 14-3.1: Clean optical fibers simultaneously opens the shutter. The CLETOP cassette shutter door is now open and ready for cleaning the connector.

3

4

.................................................................................................................................................................................................

Insert and press the connector ferrule endface perpendicular against the cleaning cloth in the first of two slots of the cleaner.

Drag it down (in the direction indicated by the arrows on the cleaner). Make certain not to release the lever of the cassette.

.................................................................................................................................................................................................

Lift the connector from the first slot and rotate it 90 degrees and repeat the downward motion using the second slot. Be sure the ferrule is pressed snug against the cleaning cloth while dragging the ferrule to assure the proper cleaning action.

.................................................................................................................................................................................................................................

14-38 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-3.1: Clean optical fibers

5

6

7

.................................................................................................................................................................................................

Release the cassette lever allowing the shutter door to close to its initial position.

Proceed to

Step 7 .

.................................................................................................................................................................................................

Wrap a Luminex cleaning cloth around the ferrule and rotate the connector housing, cleaning the outside periphery of the ferrule.

Follow this by folding an unused portion of the cloth over the end of the ferrule endface and then with light pressure from the thumb, slightly drag the cloth from the center of the ferrule to the edge while rotating the connector 360 degrees. If the

Luminex cleaning cloth is not available, a cleanroom optic wipe can be used. The

Luminex cleaning cloth is washable and can be used multiple times; optic wipes are single use and disposable.

.................................................................................................................................................................................................

Inspect the connector for cleanliness. If necessary, repeat the cleaning process.

Reference:

Procedure 14-3.3: “Optical fiber and connector inspection” (p. 14-41)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-39

Supporting procedures

Procedure 14-3.2: Clean fiber adapters and circuit pack connectors

.................................................................................................................................................................................................................................

Overview

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34) .

Use this procedure to clean fiber adapters and circuit pack connectors.

Important! Do not attempt to clean ports equipped with yellow lightguide buildout

(LBO) attenuators. Attenuators contain a thin glass lens that is extremely fragile.

The LBO will be damaged if cleaned using this method.

Step

1

2

3

4

5

Complete the following steps to clean the optical buildout adapter or the circuit pack connector.

.................................................................................................................................................................................................

Insert the appropriate CLETOP stick cleaner (2.5 mm for SC, ST, and FC connectors,

1.25 mm for LC connectors) into the adapter rotating the stick 360 degrees while inserting. Push/rotate stick until the stick cleaner makes contact with the connector.

Apply slight pressure upon contact and rotate stick 360 degrees at least three (3) times.

.................................................................................................................................................................................................

Remove the stick cleaner rotating it upon removal.

.................................................................................................................................................................................................

Using a dry CLETOP stick cleaner of appropriate diameter, repeat the above cleaning procedure. This procedure will clean the side walls of the adapter and the endface of the circuit pack connector.

.................................................................................................................................................................................................

Gently insert the Video Fiber Scope probe into the port until the fiber ferrule comes into view.

Reference:

Procedure 14-3.3: “Optical fiber and connector inspection” (p. 14-41)

.................................................................................................................................................................................................

Verify that the fiber ferrule is clean. If required, repeat

Step 1

through

Step 3 .

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-40 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-3.3: Optical fiber and connector inspection

.................................................................................................................................................................................................................................

Overview

Important! This is not a stand-alone procedure. Perform this procedure only as directed by

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34) .

Use this procedure to inspect fiber adapters and circuit pack connectors following cleaning.

WARNING

Laser hazard

When using an optical power meter to verify the connector and fiber to be clean, take special precaution to make sure that no power is being emitted from the fiber before viewing.

Step

1

After cleaning the connector, inspect the ferrule endface to ensure that it is free from any particulate contamination using an optical fiber inspection scope of at least 200X magnification. When using an optical fiber scope (for example, the Noyes OFS

300-200X) exercise extreme caution to assure that the fiber being examined is de-energized.

.................................................................................................................................................................................................

Follow the instructions in the manual provided with the Optical Fiber Scope to view the ferrule endface of the fiber under inspection.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-41

Supporting procedures Procedure 14-3.3: Optical fiber and connector inspection

2

.................................................................................................................................................................................................

The visual area of the ferrule endface (ferrule and fiber) as observed by the inspection system/scope should be free of any contaminates.

No LOOSE contamination or particulate fibers in viewing area.

If not removable in 3 cleaning attempts, it is defined as fixed particulate, and is acceptable outside the restricted area.

Monitor

Viewing

Area

Core

No Loose or No Fixed

Contamination

Fiber nc-dmx-193

3

4

Repeat the Cleaning Procedure if the fiber endface does not meet the following requirements:

•

No fixed type of contamination (contaminates that remain at the same location after

3 wet-dry cleaning cycles), regardless of size, is allowed in the restricted area of the glass fiber endface.

Important: The restricted area is defined as ~66 microns (mm) diameter for both singlemode and multimode fibers.

•

No chips, cracks or scratches are allowed near the core of the glass fiber endface.

•

No large floating (loose) contaminates are allowed on the glass fiber and ceramic ferrule endface.

.................................................................................................................................................................................................

After the connector has been verified to be cleaned, it should be immediately inserted into the adapter buildout of the optical component. This will assure maximum cleanliness and effectiveness of the connector.

.................................................................................................................................................................................................

If the cleaned connector cannot be immediately connected to a corresponding adapter, the connector ferrule must be protected with a connector dust cap. Before placing the cap on the ferrule, make sure the cap is clean. This can be accomplished by inserting a

CLETOP stick cleaner (swab) of the same inside diameter as the cap (either 2.5 or

1.25 mm) and rotate the stick 360 degrees three (3) times. Following this procedure,

.................................................................................................................................................................................................................................

14-42 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-3.3: Optical fiber and connector inspection carefully place the cap over the ferrule. When the cleaned connector is ready for assembly, it should be re-inspected for cleanliness prior to connection.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-43

Supporting procedures

Procedure 14-4: Perform connection and verification of optical facility

.................................................................................................................................................................................................................................

Overview

Use this procedure to connect and verify an OC-n optical facility.

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to complete this procedure.

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 14-3) , the following

equipment is also required:

•

Lightguide Jumpers

•

Lightguide Buildouts (LBOs).

LC-type lightguide buildouts

The following lightguide buildouts are required for attenuating the OLIUs.

Product Code

ABLCS-05.0

ABLCS-10.0

ABLCS-15.0

ABLCS-20.0

Comcode

108279381

108279431

108279480

108279530

Loss (dB) Fiber Type

5

10

15

20

SM

SM

SM

SM

Color

Yellow

Yellow

Yellow

Yellow

Single-mode lightguide jumpers

The following single-mode lightguide angled boot jumpers are available for connecting the OLIUs to the optical span.

Product Code

MS1A40LC-A40LC-2

MS1A40LC-A40LC-4

MS1A40LC-A40LC-E/W

MS1A40LC-LC-2

Comcode

108918269

108918707

108918715

108918830

Length (ft.)

2

4

Customer

Specified

2

Connectors

LC-LC

LC-LC

LC-LC

LC-LC

.................................................................................................................................................................................................................................

14-44 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-4: Perform connection and verification of optical facility

Product Code

MS1A40LC-LC-4

MS1A40LC-LC-6

MS1A40LC-LC-8

MS1A40LC-LC-10

MS1A40LC-LC-15

MS1A40LC-LC-20

MS1A40LC-LC-25

MS1A40LC-LC-30

MS1A40LC-LC-35

MS1A40LC-LC-40

MS1A40LC-LC-50

MS1A40LC-LC-E/W

MS1A40LC-SC-2

MS1A40LC-SC-4

MS1A40LC-SC-6

MS1A40LC-SC-8

MS1A40LC-SC-10

MS1A40LC-SC-15

MS1A40LC-SC-20

MS1A40LC-SC-25

MS1A40LC-SC-30

MS1A40LC-SC-35

MS1A40LC-SC-40

MS1A40LC-SC-50

MS1A40LC-SC-E/W

Comcode

108918855

108918863

108918871

108918889

108918897

108918913

108918921

108918939

108918947

108918962

108918970

108918988

108919002

108919010

108919028

108919036

108919044

108919051

108919069

108919077

108919085

108919093

108919101

108919119

108919996

Length (ft.)

6

8

10

20

25

30

35

40

4

6

8

10

15

4

6

8

10

15

20

50

Customer

Specified

2

2

4

25

30

35

40

50

Customer

Specified

Connectors

LC-LC

LC-LC

LC-LC

LC-LC

LC-LC

LC-LC

LC-LC

LC-LC

LC-LC

LC-LC

LC-LC

LC-LC

LC-SC

LC-SC

LC-SC

LC-SC

LC-SC

LC-SC

LC-SC

LC-SC

LC-SC

LC-SC

LC-SC

LC-SC

LC-SC

MS1A40LC-FC-2

MS1A40LC-FC-4

MS1A40LC-FC-6

MS1A40LC-FC-8

MS1A40LC-FC-10

108918723

108918731

108918749

108918756

108918764

LC-FC

LC-FC

LC-FC

LC-FC

LC-FC

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-45

Supporting procedures

Product Code

MS1A40LC-FC-15

MS1A40LC-FC-20

MS1A40LC-FC-25

MS1A40LC-FC-30

MS1A40LC-FC-35

MS1A40LC-FC-40

MS1A40LC-FC-50

MS1A40LC-FC-E/W

MS1A40LC-EP-2

MS1A40LC-EP-4

MS1A40LC-EP-6

MS1A40LC-EP-8

MS1A40LC-EP-10

MS1A40LC-EP-15

MS1A40LC-EP-20

MS1A40LC-EP-25

MS1A40LC-EP-30

MS1A40LC-EP-35

MS1A40LC-EP-40

MS1A40LC-EP-50

MS1A40LC-EP-E/W

Comcode

108918772

108918780

108918798

108918806

108918814

108918822

108918848

108918905

108919713

108919721

108919739

108919747

108919754

108919770

108919788

108919796

108919804

108919812

108919820

108919838

108919846

Procedure 14-4: Perform connection and verification of optical facility

Length (ft.)

2

4

6

8

10

15

20

25

30

35

40

50

Customer

Specified

15

20

25

30

35

40

50

Customer

Specified

LC-ST

LC-ST

LC-ST

LC-ST

LC-ST

LC-ST

LC-ST

LC-ST

LC-ST

LC-ST

LC-ST

LC-ST

LC-ST

Connectors

LC-FC

LC-FC

LC-FC

LC-FC

LC-FC

LC-FC

LC-FC

LC-FC

Important! The single-mode angled boot lightguide jumpers used to connect the

OLIUs must be equipped with LC connectors.

.................................................................................................................................................................................................................................

14-46 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-4: Perform connection and verification of optical facility

Allowable optical receiver power ranges

The following information is required to determine the required LBO for the OC-N

OLIUs.

Optics

Long Reach (LR) Optics

Circuit Pack Allowable

Receiver Range

(dBm)

-8.0 to -29.0

LNW26B OC-48

LNW27 OC-48

LNW28 OC-48

LNW29 OC-48

LNW32 OC-48

LNW121B-159B OC-48

LNW221-259 OC-48

LNW421-459 OC-48

LNW36 OC-3

LNW37/LNW45 OC-3 with

OM155 1.3LR1 module

LNW46 OC-12

LNW49 OC-12 with OM622

1.3LR1 module

LNW50 OC-12

LNW54 OC-12

LNW60 OC-192

LNW57 OC-192

LNW555 OC-192

0.0 to -34.0

-10.0 to -34.0

-7.0 to -30.5

-8.0 to -28.0

-7.0 to -30.5

-8.0 to -29.0

-7.0 to -24.0

-1.0 to -14.0

-9.0 to -22.0

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-47

Supporting procedures

Optics

Intermediate Reach (IR)

Optics

Short Reach (SR) Optics

Procedure 14-4: Perform connection and verification of optical facility

Circuit Pack Allowable

Receiver Range

(dBm)

0.0 to -18.0

LNW31 OC-48

LNW77 OC-48

LNW37/LNW45 OC-3 with

OM155 1.3IR1 module

LNW48 OC-12

LNW49 OC-12 with OM622

1.3IR1 module

LNW56 OC-192

LNW523 OC-192

LNW527 OC-192

LNW554 OC-192

LNW76 OC-48

LNW58 OC-192

-8.0 to -28.0

-8.0 to -28.0

-8.0 to -28.0

-1.0 to -14.0

-3.0 to -18.0

-1.0 to -11.0

Important! Avoid excessive bending of the optical jumper used to loop the OLIU on itself.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Verify that the correct lightguide build-outs and jumpers are available.

4. Ensure all optical fiber connectors and couplings have been properly cleaned.

Signal performances may be degraded if the connections and couplings are not cleaned properly.

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

5. Ensure that technicians are available at both ends of the optical span(s).

6. Obtain the work instructions for this procedure.

.................................................................................................................................................................................................................................

14-48 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Step

Procedure 14-4: Perform connection and verification of optical facility

1

2

3

4

5

Complete the following steps to connect and verify an OC-n optical facility.

.................................................................................................................................................................................................

At the near-end Metropolis

®

WaveStar

®

CIT session.

DMX, connect personal computer and establish

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

Dress optical cables in the fiber tray at bottom front of the shelf.

.................................................................................................................................................................................................

Route the optical jumpers from the bottom of the shelf. See

“Single-mode lightguide jumpers” (p. 14-44) .

.................................................................................................................................................................................................

Establish communication with technician at other end of the optical span.

.................................................................................................................................................................................................

At both ends of the optical span, remove protective covers from receive and transmit optical jumper cables and clean LC connectors.

Important! The Metropolis

®

DMX OLIUs require single-mode lightguide cable.

Single-mode optical fibers connecting this shelf with the far-end shelf should not be connected to the OLIU until at least 45 seconds after an optical loopback is removed. It may take from 15 seconds to 3.5 minutes for the OLIU

FAULT

LED or port LED associated with the pluggable transmission module to stop flashing after the cables are connected, depending on the setting of the OC-n signal degrade threshold.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-49

Supporting procedures Procedure 14-4: Perform connection and verification of optical facility

6

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

At both ends of the optical span, ensure that only the dual LC adapter is installed on the OLIU (no LBOs) as indicated in the following figure:

OLIU

IN

OUT

OLIU

IN

OUT

DUAL LC CONNECTOR

NC-DMX-061

7

8

.................................................................................................................................................................................................

Important! Fiber connections for an optical span should be made in the following sequence to speed up the detection of looped-back or crossed-over cables/jumpers.

At Node 1 of the optical span, connect the optical fiber transmit cables to the OLIU

OUT

connectors.

.................................................................................................................................................................................................

Have you determined the value of the LBOs for this span?

If...

Yes

No

Then...

Proceed to

Step 10 .

Continue with

Step 9 .

9

10

.................................................................................................................................................................................................

At Node 2 of the optical span, measure the optical power of the optical fiber receive cable using an optical power meter.

For the allowable receiver power ranges, refer to the

“Allowable optical receiver power ranges ” (p. 14-47)

in this procedure. Select the appropriate LBO to build out to the middle of the range.

.................................................................................................................................................................................................

Install the LBO assembly at the OLIU

IN

connector of Node 2.

.................................................................................................................................................................................................................................

14-50 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-4: Perform connection and verification of optical facility

11

12

Reference:

(p. 14-54)

Procedure 14-5: “Install/remove LC lightguide buildouts (LBOs)”

.................................................................................................................................................................................................

At Node 2, connect the input optical fiber to the proper OLIU

IN

connector and LBO.

Result:

It may take from 15 seconds to 3.5 minutes for the OLIU

FAULT

LED or port LED associated with the pluggable transmission module to stop flashing after the cables are connected, depending on the setting of the OC-n signal degrade threshold.

.................................................................................................................................................................................................

Did the flashing OLIU

FAULT

LED or port LED associated with the pluggable transmission module go off at Node 2?

If...

No

Yes

Then...

Click the

Alarm List

button to obtain the NE

Alarm List. Refer to the Metropolis

®

DMX Access

Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302 to clear/isolate the trouble.

Continue with

Step 13 .

13

14

.................................................................................................................................................................................................

At Node 2 of the optical span, connect the optical fiber transmit cables to the OLIU

OUT

connector.

.................................................................................................................................................................................................

Have you determined the value of the LBOs for this span?

If...

Yes

No

Then...

Proceed to

Step 16 .

Continue with

Step 15 .

15

.................................................................................................................................................................................................

At Node 1 of the optical span, measure the optical power of the optical fiber receive cable using an optical power meter.

For the allowable receiver power ranges, refer to the

“Allowable optical receiver power ranges ” (p. 14-47)

in this procedure. Select the appropriate LBO to build-out to the middle of the range.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-51

Supporting procedures Procedure 14-4: Perform connection and verification of optical facility

16

17

18

.................................................................................................................................................................................................

Install the LBO assembly at the OLIU

IN

connector of Node 1.

Reference:

(p. 14-54)

Procedure 14-5: “Install/remove LC lightguide buildouts (LBOs)”

.................................................................................................................................................................................................

At Node 1, connect the input optical fiber to the proper OLIU

IN

connector and LBO.

Result:

It may take from 15 seconds to 3.5 minutes for the OLIU

FAULT

LED or port LED associated with the pluggable transmission module to stop flashing after the cables are connected, depending on the setting of the OC-n signal degrade threshold.

.................................................................................................................................................................................................

Did the flashing OLIU

FAULT

LED or port LED associated with the pluggable transmission module go off at Node 1?

If...

No

Yes

Then...

Click the

Alarm List

button to obtain the NE

Alarm List. Refer to the Metropolis

®

DMX Access

Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302 to clear/isolate the trouble.

Continue with

Step 19 .

19

20

.................................................................................................................................................................................................

Disconnect the fiber cable from the

OUT

connector on the OLIU at one end of the span. At the other end, verify that the associated OLIU

FAULT

LED or port LED associated with the pluggable transmission module is flashing, indicating a loss of signal. Reconnect the fiber and repeat the process for the other direction of transmission.

.................................................................................................................................................................................................

Use the

Administration

→

OSI Routing Map

and

Administration

→

OSI Neighbor

Maps

commands to retrieve a map of the network. Verify that nodes have been connected properly and that they can communicate with each other.

.................................................................................................................................................................................................................................

14-52 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-4: Perform connection and verification of optical facility

21

.................................................................................................................................................................................................

After all connections and tests have been made, verify optical fiber cables are placed correctly in fiber tray and properly routed in bay framework.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-53

Supporting procedures

Procedure 14-5: Install/remove LC lightguide buildouts (LBOs)

.................................................................................................................................................................................................................................

Overview

Use this procedure to install or remove an LC lightguide buildout (LBO).

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure.

Step

1

Complete the following steps to install or remove an LC lightguide buildout (LBO).

.................................................................................................................................................................................................

Remove the protector caps and plugs (if equipped) from the LC LBO and the dual adapter on the circuit pack, and store them in a clean container.

MA-DMX-403

.................................................................................................................................................................................................................................

14-54 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-5: Install/remove LC lightguide buildouts

(LBOs)

2

.................................................................................................................................................................................................

Is LC LBO being installed or removed?

IF the LC LBO is being...

Installed,

Removed,

Then...

Continue with

Step 3 .

Proceed to

Step 6 .

3

4

5

6

.................................................................................................................................................................................................

Important! All LC LBOs should be cleaned before making initial connections or reconnections. Only the components being assembled at this time should be cleaned.

Clean the LC LBO.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Align the LBO with the slot in the adapter, depress locking tab, and push the LBO into the dual adapter until a click is heard. The LBO is now locked into position.

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

Important! The locking tab must only be pushed along a line perpendicular to the

LBO body in the direction towards the LBO in order to avoid damage to the locking tab.

Depress the locking tab on the LBO and pull the LBO out of the dual adapter.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-55

Supporting procedures

Procedure 14-6: Connect OLIU optical loopbacks

.................................................................................................................................................................................................................................

Overview

Use this procedure to loop back an out-of-service optical line at the OLIU faceplate connectors. Optical lines can also be looped back at the LGX equipment to verify correct fiber installation and labeling.

Important! LBOs are installed on the OLIU faceplate

IN

connector only.

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 14-3) , one lightguide

jumper (MS1A40LC-A40LC-2, Comcode 108918269) for each optical line to be looped back (LC-type connections) is also required.

The following lightguide buildouts (LBOs) are required.

•

5-dB loss LBO (code ABLCS-05.0: comcode 108279381) or

•

10-dB loss LBO (code ABLCS-10.0: comcode 108279431) or

•

15-dB loss LBO (code ABLCS-15.0: comcode 108279480) or

•

20-dB loss LBO (code ABLCS-20.0: comcode 108279530)

Before you begin

Prior to performing this procedure:

1. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

2. Obtain the work instructions for this procedure.

.................................................................................................................................................................................................................................

14-56 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Step

Procedure 14-6: Connect OLIU optical loopbacks

1

Complete the following steps to loop back an out-of-service optical line at the OLIU faceplate connectors.

.................................................................................................................................................................................................

Obtain the correct LBO and lightguide jumper:

If the OLIU is...

Long Reach (LR) Optics LNW26B OC-48

LNW27 OC-48

LNW28 OC-48

LNW29 OC-48

LNW32 OC-48

LNW121B-159B OC-48

LNW221-259 OC-48

LNW421-459 OC-48

LNW36 OC-3

Then obtain a...

lightguide jumper

(MS1A40LC-A40LC-2,

Comcode 108918269) and a

15-dB

LBO (code

ABLCS-15.0, comcode

108279480 for LC connectors)

LNW37/LNW45 OC-3 with

OM155 1.3LR1 module

LNW46 OC-12

LNW49 OC-12 with

OM622 1.3LR1 module

LNW50 OC-12

LNW54 OC-12

LNW555 OC-192

LNW57 OC-192

LNW60 OC-192 lightguide jumper

(MS1A40LC-A40LC-2,

Comcode 108918269) and a

10-dB

LBO (code

ABLCS-10.0, comcode

108279431 for LC connectors) lightguide jumper

(MS1A40LC-A40LC-2,

Comcode 108918269) and a

15-dB

LBO (code

ABLCS-15.0, comcode

108279480 for LC connectors) lightguide jumper

(MS1A40LC-A40LC-2,

Comcode 108918269) and a

20-dB

LBO (code

ABLCS-20.0, comcode

108279530 for LC connectors)

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-57

Supporting procedures Procedure 14-6: Connect OLIU optical loopbacks

If the OLIU is...

Intermediate Reach (IR)

Optics

Short Reach (SR) Optics

LNW31 OC-48

LNW37/LNW45 OC-3 with

OM155 1.3IR1 module

LNW48 OC-12

LNW49 OC-12 with

OM622 1.3IR1 module

LNW56 OC-192

LNW77 OC-48

LNW523 OC-192

LNW527 OC-192

LNW554 OC-192

LNW76 OC-48

LNW58 OC-192

Then obtain a...

lightguide jumper

(MS1A40LC-A40LC-2,

Comcode 108918269) and a

5-dB

LBO (code

ABLCS-05.0, comcode

108279381 for LC connectors)

No LBO required

(attenuation not needed)

2

3

4

5

.................................................................................................................................................................................................

If required, remove the optical line connections from the OLIU faceplate. Make a record of these disconnections so they can be replaced.

.................................................................................................................................................................................................

Remove the LBO (if equipped) from the

IN

connector of the OLIU faceplate. Make a note of the value.

Reference:

(p. 14-54)

Procedure 14-5: “Install/remove LC lightguide buildouts (LBOs)”

.................................................................................................................................................................................................

Remove the protector caps from the ends of the lightguide jumper (loopback cable).

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

Signal performance may be degraded if the connectors/adapters and fiber are not cleaned.

Ensure all optical fiber connectors/adapters and fiber are properly cleaned.

Clean the fiber connectors/adapters and fiber.

.................................................................................................................................................................................................................................

14-58 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-6: Connect OLIU optical loopbacks

6

7

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

.................................................................................................................................................................................................

Important! Pluggable transmission modules are shipped with a dust plug installed into the optical ports to maintain cleanliness during storage and/or transportation. It is recommended that the dust plug be kept in place to maintain cleanliness until the optical fiber is connected. With proper care and handling, cleaning the pluggable transmission modules should not be necessary.

If required, clean the pluggable transmission module(s).

Reference:

(p. 14-135)

Procedure 14-29: “Clean optical pluggable transmission module”

.................................................................................................................................................................................................

If required, remove the protective dust plug from the pluggable transmission module.

Keep the dust plug clean until reinstalled later, if required.

8

.................................................................................................................................................................................................

Install the appropriate LBO on the

IN

connector, if required. The list of circuit packs and their corresponding LBOs may be found in

Step 1 .

Reference:

(p. 14-54)

Procedure 14-5: “Install/remove LC lightguide buildouts (LBOs)”

.................................................................................................................................................................................................

9

10

Important! The LBOs and lightguide jumpers connect to the LC-shielded, angled adapter on the OLIU faceplate.

Using the lightguide angled boot jumper (MS1A40LC-A40LC-2, Comcode

108918269), connect the

IN

connector and the corresponding

OUT

connector on the same OLIU.

Result:

After a short time, the OLIU

FAULT

LED or port LED associated with the pluggable transmission module stops flashing. (It may take from 15 seconds to 3.5

minutes for the LED to stop flashing after the cables are connected, depending on the setting of the OC-n signal degrade threshold.) The

ACTIVE

LED remains on.

If OSI over DCC is enabled for the port, the

MJ

and

NE

LEDs on the SYSCTL circuit pack do not extinguish and the following alarms are reported.

• inconsistent DCC values

• section DCC channel failed

.................................................................................................................................................................................................

If responses are not as indicated, check connections and the lightguide jumper. Clean connections and repeat

Step 9 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-59

Supporting procedures Procedure 14-6: Connect OLIU optical loopbacks

11

If responses are still not correct, click the

Alarm List

button to obtain the NE Alarm

List. Refer to the Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302 to clear/isolate the trouble.

Reference:

•

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

•

Procedure 14-29: “Clean optical pluggable transmission module” (p. 14-135)

.................................................................................................................................................................................................

If required, repeat

Step 1

through

Step 10

to loop back additional optical lines.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-60 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-7: Perform end-to-end optical line test on Main

OLIUs

.................................................................................................................................................................................................................................

Overview

Use this procedure to verify the integrity of a high-speed OC-n line.

Important! This test must be performed locally at each Metropolis

®

location associated with the optical span(s) being tested.

DMX shelf

Privilege level

You must log in as either a Privileged, General, or Maintenance user to complete this procedure.

Important! It is assumed that each Metropolis

®

DMX node has passed the local

(looped) transmission tests. If these tests have not been completed, refer to the appropriate procedure and perform the tests.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure.

Step

1

2

3

Complete the following steps to verify the integrity of a high-speed OC-n line.

.................................................................................................................................................................................................

From the System View menu, select

Performance

→

View PM Reports

→

OCn Line

.

Result:

The OCn Line PM Report window opens.

.................................................................................................................................................................................................

Expand the CP main-1 (OCn) circuit pack by clicking on the plus sign (+), select Port

1 (OCn), and then click

Select

.

Result:

The port performance monitoring parameters appear.

.................................................................................................................................................................................................

Provision the Time Period parameter

15 Min

, the Monitored Date parameter

Current

Date

, the Monitor Time parameter

Current

, and the Monitor Level parameter

1-UP

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-61

Supporting procedures Procedure 14-7: Perform end-to-end optical line test on

Main OLIUs

4

5

Then move all the Near End Available Parameters to Selected Parameters by clicking

Select All

. Click

Apply

to obtain the OCn Line PM Report.

Result:

no errors.

The OCn Line PM Report appears. The report should be empty, indicating

.................................................................................................................................................................................................

Wait 20 seconds and click

Refresh

on the OCn Line PM Report window. If a

15-minute boundary is crossed during the 20-second wait period, repeat this step.

Result:

If the report is still empty, the optical span is error-free. Click

Close

.

.................................................................................................................................................................................................

Did report indicate any errors?

If...

Yes,

No,

Then...

Continue with

Step 6 .

Proceed to

Step 7 .

6

7

8

.................................................................................................................................................................................................

Trouble may be in optical and/or fiber connections. Trouble may also be in OLIUs. If report indicated trouble when the report was obtained from the near end of the span, trouble may be in the receive direction. If the report indicated trouble when the report was obtained from the far end of the span, trouble may be in the transmit direction.

Check optical fiber and connections. Clean optical fiber connections.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

If no trouble was found in the optical fiber, click the

Alarm List

button to obtain the NE Alarm List. Refer to the Metropolis

®

DMX Access Multiplexer Alarm

Messages and Trouble Clearing Guide, 365-372-302 to clear/isolate the trouble.

.................................................................................................................................................................................................

If required, repeat this procedure from

Step 2

for the Main-2 OLIU; otherwise, click

Close

.

.................................................................................................................................................................................................

Have you retrieved error-free performance-monitoring reports from all shelf locations associated with the optical span(s) being tested?

If...

Yes,

Then...

STOP! End of Procedure.

.................................................................................................................................................................................................................................

14-62 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

If...

No,

Procedure 14-7: Perform end-to-end optical line test on

Main OLIUs

Then...

Repeat this procedure from

Step 1

at the other shelf locations.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-63

Supporting procedures

Procedure 14-8: Perform end-to-end optical line test on

Function OLIUs

.................................................................................................................................................................................................................................

Overview

Use this procedure to verify the integrity of a low-speed OC-n line.

Important! This test must be performed locally at each Metropolis

®

location associated with the optical span(s) being tested.

DMX shelf

Privilege level

You must log in as a Privileged, General, or Maintenance user to complete this procedure.

Important! It is assumed that each Metropolis

®

DMX has passed the local

(looped) transmission tests. If these tests have not been completed, refer to the appropriate procedure and perform the tests.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure.

Step

1

2

3

Complete the following steps to verify the integrity of a low-speed OC-n line.

.................................................................................................................................................................................................

From the System View menu, select

Performance

→

View PM Reports

→

OCn Line

.

Result:

The OCn Line PM Report window opens.

.................................................................................................................................................................................................

Expand the appropriate low-speed OLIU circuit pack by clicking on the plus sign (+), select the required Port n (OCn), and then click

Select

.

Result:

The port performance monitoring parameters appear.

.................................................................................................................................................................................................

Provision the Time Period parameter

15 Min

, the Monitored Date parameter

Current

Date

, the Monitor Time parameter

Current

, and the Monitor Level parameter

1-UP

.

.................................................................................................................................................................................................................................

14-64 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-8: Perform end-to-end optical line test on

Function OLIUs

4

5

Then move all the Near End Available Parameters to Selected Parameters by clicking

Select All

. Click

Apply

to obtain the OCn Line PM Report.

Result:

no errors.

The OCn Line PM Report appears. The report should be empty, indicating

.................................................................................................................................................................................................

Wait 20 seconds and click

Refresh

on the OCn Line PM Report window. If a

15-minute boundary is crossed during the 20-second wait period, repeat this step.

Result:

If the report is still empty, the optical span is error-free. Click

Close

.

.................................................................................................................................................................................................

Did report indicate any errors?

If...

Yes,

No,

Then...

Continue with

Step 6 .

Proceed to

Step 7 .

6

7

.................................................................................................................................................................................................

Trouble may be in optical and/or fiber connections. Trouble may also be in OLIUs or pluggable transmission modules. If report indicated trouble when the report was obtained from the near end of the span, trouble may be in the receive direction. If the report indicated trouble when the report was obtained from the far end of the span, trouble may be in the transmit direction. Check optical fiber and connections. Clean optical fiber connections.

Reference:

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34)

If no trouble was found in the optical fiber, click the

Alarm List

button to obtain the NE Alarm List. Refer to the Metropolis

®

DMX Access Multiplexer Alarm

Messages and Trouble Clearing Guide, 365-372-302 to clear/isolate the trouble.

.................................................................................................................................................................................................

If required, repeat this procedure from

Step 2

for the companion OLIU in the Function group; otherwise, click

Close

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-65

Supporting procedures Procedure 14-8: Perform end-to-end optical line test on

Function OLIUs

8

.................................................................................................................................................................................................

Have you retrieved error-free performance-monitoring reports from all shelf locations associated with optical line(s) being tested?

If...

Yes,

No,

Then...

STOP! End of Procedure.

Repeat this procedure from

Step 1

at other shelf locations.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-66 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-9: Perform DS1/E1 transmission test

.................................................................................................................................................................................................................................

Overview

Use this procedure to test a DS1 or E1 port at a stand-alone Metropolis

®

or in a Metropolis

®

DMX network.

DMX shelf

If this procedure is being used to perform end-to-end testing in a Metropolis

®

DMX network, it is assumed that the complete Metropolis

®

DMX network configuration

(BLSR, UPSR, 1+1, Bidirectional 1+1, or Optimized 1+1) has already been established/tested and that only a particular DS1 or E1 port is being tested at this time.

In end-to-end testing, one shelf is referred to as the near end and the other shelf as the far end. These designations are arbitrary; either shelf can be the near-end or the far-end shelf.

Important! The LNW18 TMUX circuit pack does not support the DS1 port transmission tests.

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 14-3) , a DS1 or E1

Test Set is also required.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure and note the assigned AIDs.

4. Using the

View

→

Equipment

command, verify that the DS1/E1 port parameters have been provisioned correctly (according to the work instructions) at the terminating Metropolis

®

DMX shelf(s) of the circuit being tested.

If required, make DS1/E1 port provisioning changes using the

Configuration

→

Equipment

command.

Refer to

Procedure 4-9: “Provision DS1/E1 circuit packs/ports for service” (p. 4-42)

for more information.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-67

Supporting procedures

Step

Procedure 14-9: Perform DS1/E1 transmission test

Complete the following steps to perform a DS1/E1 transmission test.

.................................................................................................................................................................................................

1

Important! Proper terminating and pass-through cross-connections must exist at each shelf (including stand-alone shelves) to establish continuity for the DS1/E1 circuit being tested.

Using the

View

→

Cross-Connections

command, verify that the proper VT1.5/STS-n

(DS1) cross-connections exist for the DS1 circuit to be tested. If an E1 circuit is to be tested, verify the proper STS-3 cross-connections exist.

If required, use the

Configuration

→

Cross-Connections

command to access the

Cross-Connection Wizard and create the proper VT1.5/STS-n cross-connections for the

DS1/E1 circuit to be tested.

Reference:

365-372-306

Metropolis

®

DMX Access Multiplexer TL1 Message Details,

.................................................................................................................................................................................................

2

If the transmission test is to be performed...

at a stand-alone shelf in the

Terminal direction (toward the fiber), at a stand-alone shelf in the

Facility direction (toward the

DSX), in a Metropolis

(end-to-end),

®

DMX network

Then...

At the required OLIUs, loop back the fiber.

Refer to

Procedure 14-6: “Connect OLIU optical loopbacks” (p. 14-56) .

At the DSX-1 panel or equivalent connection point, connect a patch cord from the

OUT

jack to the

IN

jack associated with the DS1/E1 circuit being tested.

At the far-end DSX-1 panel or equivalent connection point, connect a patch cord from the

OUT

jack to the

IN

jack associated with the

DS1/E1 circuit being tested, OR log in to the far-end Metropolis

®

DMX shelf and perform a

Terminal loopback on the DS1/E1 circuit being tested using the

Fault

→

Analysis

→

Loopback

command.

.................................................................................................................................................................................................................................

14-68 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-9: Perform DS1/E1 transmission test

Reference:

The following figures show the test arrangements.

Figure 14-8 Stand-Alone shelf with OLIU loopback

OLIU

Internal

Test Signal

Multiplex Direction

Fiber

Loopback

Monitor

Demultiplex Direction nc-dmx-180

Figure 14-9 Stand-Alone shelf with DSX loopback

DSX OLIU

IN

Monitor

Multiplex Direction

OUT

Internal

Test Signal nc-dmx-199

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-69

Supporting procedures Procedure 14-9: Perform DS1/E1 transmission test

Figure 14-10 End-to-End DS1/E1 circuit with far-end loopback

NEAR END

Internal

Test Signal

Multiplex Direction

Monitor

Demultiplex

Direction

Pass Through

Cross Connections

OLIU

OLIU OLIU FAR END DSX

OUT

IN

Terminal

Loopback

External

Loopback nc-dmx-198

3

.................................................................................................................................................................................................

If the transmission test is to be performed...

at a stand-alone shelf in the

Terminal direction (toward the fiber), at a stand-alone shelf in the

Facility direction (toward the

DSX), in a Metropolis

®

(end-to-end),

DMX network

Then...

Either perform a terminal transmission test on the

DS1/E1 port using the

Fault

→

Test

→

Transmission

command, or connect a test set to the port to be tested at the DSX-1 panel or equivalent connection point and apply a DS1/E1 test signal.

Perform a facility transmission test on the

DS1/E1 port using the

Fault

→

Test

→

Transmission

command.

At the Near End, either perform a terminal transmission test on the DS1/E1port using the

Fault

→

Test

→

Transmission

command, or connect a test set to the port to be tested at the

DSX-1 panel or equivalent connection point and apply a DS1/E1 test signal.

.................................................................................................................................................................................................................................

14-70 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-9: Perform DS1/E1 transmission test

4

.................................................................................................................................................................................................

Was the test successful (error free)?

If...

Yes,

No,

Then...

Continue with

Step 5 .

Proceed to

Step 21 .

5

.................................................................................................................................................................................................

Is the protection slot associated with the DS1/E1 circuit under test equipped with a companion circuit pack?

If...

Yes,

No,

Then...

Continue with

Step 6 .

Proceed to

Step 9 .

6

7

.................................................................................................................................................................................................

Use the

Fault

→

Protection

Switch command to perform a manual switch from the current active circuit pack to the standby circuit pack. This may cause a hit and register some errors during the switch.

.................................................................................................................................................................................................

Was the circuit pack protection switch successful (recovered error free)?

If...

Yes,

No,

Then...

Verify that the Standby circuit pack is now

Active, and repeat

Step 3

for the protection circuit pack. Then continue with

Step 8 .

Proceed to

Step 21 .

8

.................................................................................................................................................................................................

Was the test successful (error free)?

If...

Yes,

No,

Then...

Continue with

Step 9 .

Proceed to

Step 21 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-71

Supporting procedures Procedure 14-9: Perform DS1/E1 transmission test

9

.................................................................................................................................................................................................

Are you performing this test for a stand-alone Metropolis

®

end-to-end testing within a Metropolis

®

DMX network?

DMX shelf or for

If...

Stand-alone test,

End-to-end test,

Then...

Continue with

Step 10 .

Proceed to

Step 15 .

10

11

12

13

14

15

16

17

.................................................................................................................................................................................................

Remove any patch cords/fibers used to loop back the circuit under test and disconnect the test set from the DSX-1 panel or equivalent connection point, if required.

.................................................................................................................................................................................................

Delete any cross-connections entered to perform this procedure.

Reference:

Procedure 10-2: “Discontinue DS1 or E1 service” (p. 10-7)

.................................................................................................................................................................................................

In the System View screen, select

Configuration

→

Update System

→

Update All

to retire existing alarms caused by this procedure.

.................................................................................................................................................................................................

If required, repeat

Step 1

through

Step 12

for each DS1/E1 circuit to be tested.

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

At the near end, disconnect the test set from the DSX-1 panel or equivalent connection point, if required.

.................................................................................................................................................................................................

At the near end and far end, delete any cross-connections entered to perform this procedure.

Reference:

Procedure 10-2: “Discontinue DS1 or E1 service” (p. 10-7)

.................................................................................................................................................................................................

At the far end, release the terminal loopback using the

Fault

→

Analysis

→

Loopback

command, or remove the patch cords at the DSX-1 panel or equivalent connection point for the circuit under test.

.................................................................................................................................................................................................................................

14-72 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-9: Perform DS1/E1 transmission test

18

19

20

21

.................................................................................................................................................................................................

At the near end and far end, select

Configuration

→

Update System

→

Update All

to retire existing alarms caused by this procedure.

.................................................................................................................................................................................................

If required, return to

Step 1

and repeat this procedure for each DS1/E1 circuit to be tested.

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

Has the circuit pack that failed this test been replaced?

If...

Yes,

No,

Then...

Proceed to

Step 23 .

Continue with

Step 22 .

22

23

.................................................................................................................................................................................................

Replace the DS1/E1 circuit pack and repeat this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Trouble may be in the DSX cross-connect wiring, T1 interface wiring,

VT1.5/STS-1/STS-3 cross-connections in the network, or the shelf backplane. If you continue to experience problems, contact your next level of support.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-73

Supporting procedures

Procedure 14-10: Perform DS3 transmission test

.................................................................................................................................................................................................................................

Overview

Use this procedure to test a DS3 port at a stand-alone Metropolis

®

Metropolis

®

DMX network.

DMX shelf or in a

If this procedure is being used to perform end-to-end testing in a Metropolis

®

DMX network, it is assumed that the complete Metropolis

®

DMX network configuration

(BLSR, UPSR, 1+1, Bidirectional 1+1, or Optimized 1+1) has already been established/tested and that only a particular DS3 port is being tested at this time.

In end-to-end testing, one shelf is referred to as the near end and the other shelf as the far end. These designations are arbitrary; either shelf can be the near-end or the far-end shelf.

Important! The LNW18 TMUX and LNW19 48DS3EC1 circuit packs do not support internal DS3 port transmission tests. If the near end is equipped with an

LNW18 TMUX or LNW19 48DS3EC1 circuit pack, use a DS3 test set to apply a

DS3 test signal.

Privilege level

You must log in as either a Privileged or General user to complete this procedure.

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 14-3) , a DS3 Test Set

is also required.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure and note the assigned AIDs.

4. Using the

View

→

Equipment

command, verify that the DS3 port parameters have been provisioned correctly (according to the work instructions), at the terminating

Metropolis

®

DMX shelf(s) of the circuit being tested.

If required, make DS3 port provisioning changes using the

Configuration

→

Equipment

command.

Refer to

Procedure 4-7: “Provision DS3/EC1 circuit packs/ports for service”

(p. 4-37)

for more information.

.................................................................................................................................................................................................................................

14-74 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Step

Procedure 14-10: Perform DS3 transmission test

Complete the following steps to perform the DS3 transmission test.

.................................................................................................................................................................................................

1

Important! Proper terminating and pass-through cross-connections must exist at each shelf (including stand-alone shelves) to establish the continuity for the DS3 circuit being tested.

Using the

View

→

Cross-Connections

command, verify that the proper STS-1 cross-connections exist for the DS3 circuit to be tested. If required, use the

Configuration

→

Cross-Connections

command to access the Cross-Connection

Wizard and create the proper STS-1 cross-connections for the DS3 circuit to be tested

Reference:

365-372-306

Metropolis

®

DMX Access Multiplexer TL1 Message Details,

.................................................................................................................................................................................................

2

If the DS3 transmission test is to be performed...

at a stand-alone shelf in the

Terminal direction (toward the fiber), in a Metropolis

(end-to-end)

®

DMX network

Then...

At the required OLIUs, loop back the fiber.

Refer to

Procedure 14-6: “Connect OLIU optical loopbacks” (p. 14-56) .

At the far-end DSX-3 panel or equivalent connection point, connect a patch cord from the

OUT

jack to the

IN

jack associated with the DS3 circuit being tested, OR log in to the far-end

Metropolis

®

DMX shelf and perform a Terminal loopback on the DS3 circuit being tested using the

Fault

→

Analysis

→

Loopback

command.

Important! The LNW19 48DS3EC1 circuit pack does not support terminal loopbacks.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-75

Supporting procedures Procedure 14-10: Perform DS3 transmission test

Reference:

The following figures show the test arrangements.

Figure 14-11 Stand-Alone shelf with OLIU loopback

OLIU

Internal

Test Signal

Multiplex Direction

Fiber

Loopback

Monitor

Demultiplex Direction nc-dmx-180

Figure 14-12 End-to-End DS3 circuit with far-end loopback

NEAR END

Internal

Test Signal

Multiplex Direction

Monitor

Demultiplex

Direction

Pass Through

Cross Connections

OLIU

OLIU OLIU FAR END DSX

OUT

IN

Terminal

Loopback

External

Loopback nc-dmx-198

3

.................................................................................................................................................................................................

At the near end, perform a terminal transmission test on the DS3 port using the

Fault

→

Test

→

Transmission

command, or connect a DS3 test set to the port to be tested at the DSX-3 panel or equivalent connection point and apply a DS3 test signal.

Important! The LNW18 TMUX and LNW19 48DS3EC1 circuit packs do not support internal DS3 port transmission tests. If the near end is equipped with an

LNW18 TMUX or LNW19 48DS3EC1 circuit pack, use a DS3 test set to apply a

DS3 test signal.

.................................................................................................................................................................................................................................

14-76 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-10: Perform DS3 transmission test

4

.................................................................................................................................................................................................

Was the test successful (error free)?

If...

Yes,

No,

Then...

Continue with

Step 5 .

Proceed to

Step 21 .

5

.................................................................................................................................................................................................

Is the protection slot associated with the DS3 circuit under test equipped with a companion DS3 circuit pack?

If...

Yes,

No,

Then...

Continue with

Step 6 .

Proceed to

Step 9 .

6

7

.................................................................................................................................................................................................

Use the

Fault

→

Protection

Switch command to perform a manual switch from the current active circuit pack to the standby circuit pack. This may cause a hit and register some errors during the switch.

.................................................................................................................................................................................................

Was the circuit pack protection switch successful (recovered error free)?

If...

Yes,

No,

Then...

Verify that the Standby circuit pack is now

Active, and repeat

Step 3

for the protection circuit pack. Then proceed to

Step 8 .

Proceed to

Step 21 .

8

.................................................................................................................................................................................................

Was the test successful (error free)?

If...

Yes,

No,

Then...

Continue with

Step 9 .

Proceed to

Step 21 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-77

Supporting procedures Procedure 14-10: Perform DS3 transmission test

9

.................................................................................................................................................................................................

Are you performing this test for a stand-alone Metropolis

®

end-to-end testing within a Metropolis

®

DMX network?

DMX shelf or for

If...

Stand-alone test,

End-to-end test,

Then...

Continue with

Step 10 .

Proceed to

Step 15 .

10

11

12

13

14

15

16

17

.................................................................................................................................................................................................

Remove the fibers used to loop back the circuit under test and disconnect the DS3 test set from the DSX-3 panel or equivalent connection point, if required.

.................................................................................................................................................................................................

Delete any cross-connections entered to perform this procedure.

Reference:

Procedure 10-4: “Discontinue DS3 or EC-1 service” (p. 10-13)

.................................................................................................................................................................................................

In the System View screen, select

Configuration

→

Update System

→

Update All

to retire existing alarms caused by this procedure.

.................................................................................................................................................................................................

If required, repeat

Step 1

through

Step 12

for each DS3 circuit to be tested.

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

At the near end, disconnect the DS3 test set from the DSX-3 panel or equivalent connection point, if required.

.................................................................................................................................................................................................

At the near end and far end, delete any cross connections entered to perform this procedure.

Reference:

Procedure 10-4: “Discontinue DS3 or EC-1 service” (p. 10-13)

.................................................................................................................................................................................................

At the far end, release the terminal loopback using the

Fault

→

Analysis

→

Loopback

command, or remove the patch cords at the DSX-3 panel or equivalent connection point for the circuit under test.

.................................................................................................................................................................................................................................

14-78 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-10: Perform DS3 transmission test

18

19

20

21

.................................................................................................................................................................................................

At the near end and far end, select

Configuration

→

Update System

→

Update All

to retire existing alarms caused by this procedure.

.................................................................................................................................................................................................

If required, return to

Step 1

and repeat this procedure for each DS3 circuit to be tested.

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

Has the DS3 circuit pack that failed this test been replaced?

If...

Yes,

No,

Then...

Proceed to

Step 23 .

Continue with

Step 22 .

22

23

.................................................................................................................................................................................................

Replace the DS3 circuit pack and repeat this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Trouble may be in the DSX cross-connect wiring, T3 interface wiring, STS-1 cross-connections in the network, or the shelf backplane. If you continue to experience problems, contact your next level of support.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-79

Supporting procedures

Procedure 14-11: Perform EC-1 transmission test

.................................................................................................................................................................................................................................

Overview

Use this procedure to test an EC-1 port at a stand-alone Metropolis

®

a Metropolis

®

DMX network.

DMX shelf or in

If this procedure is being used to perform end-to-end testing in a Metropolis

®

DMX network, it is assumed that the complete Metropolis

®

DMX network configuration

(BLSR, UPSR, 1+1, Bidirectional 1+1, or Optimized 1+1) has already been established/tested and that only a particular EC-1 port is being tested at this time.

In end-to-end testing, one shelf is referred to as the near end and the other shelf as the far end. These designations are arbitrary; either shelf can be the near-end or the far-end shelf.

Privilege level

You must log in as either a Privileged or General user to complete this procedure.

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 14-3) , an EC-1

SONET Test Set is also required.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure and note the assigned AIDs.

4. Using the

View

→

Equipment

command, verify that the EC-1 port parameters have been provisioned correctly (according to the work instructions) at the terminating

Metropolis

®

DMX shelf(s) of the circuit being tested.

If required, make EC-1 port provisioning changes using the

Configuration

→

Equipment

command.

Refer to

Procedure 4-7: “Provision DS3/EC1 circuit packs/ports for service”

(p. 4-37)

for more information.

.................................................................................................................................................................................................................................

14-80 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Step

Procedure 14-11: Perform EC-1 transmission test

Complete the following steps to perform the EC-1 transmission test.

.................................................................................................................................................................................................

1

Important! Proper terminating and pass-through cross-connections must exist at each shelf (including stand-alone shelves) to establish the continuity for the EC-1 circuit being tested.

Using the

Configuration

→

Cross-Connections

command, make/verify the proper

STS-1 cross-connections for the EC-1 circuit to be tested, as required.

Reference:

365-372-306

Metropolis

®

DMX Access Multiplexer TL1 Message Details,

.................................................................................................................................................................................................

2

If the EC-1 transmission test is to be performed...

at a stand-alone shelf in the

Terminal direction (toward the fiber), in a Metropolis

(end-to-end)

®

DMX network

Then...

At the required OLIUs, loop back the fiber.

Refer to

Procedure 14-6: “Connect OLIU optical loopbacks” (p. 14-56) .

At the far-end STSX-1 panel or equivalent connection point, connect a patch cord from the

OUT

jack to the

IN

jack associated with the EC-1 circuit being tested, OR log in to the far-end

Metropolis

®

DMX shelf and perform a Terminal loopback on the EC-1 circuit being tested using the

Fault

→

Analysis

→

Loopback

command.

Reference:

The following figures show the test arrangements.

Figure 14-13 Stand-Alone shelf with OLIU loopback

NEAR END

EC-1

Test

Set

Metropolis

®

DMX

OLIU

Tx IN

Fiber

Loopback

Rx OUT nc-dmx-029

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-81

Supporting procedures Procedure 14-11: Perform EC-1 transmission test

Figure 14-14 End-to-End EC-1 circuit with far-end loopback

Pass Through

Cross Connects

EC-1

Test

Set

Tx

STSX-1

IN

NEAR END

OLIU OLIU

FAR END

Rx OUT

STSX-1

OUT

IN

External

Loopback

Incoming

Outgoing

Terminal

Loopback

MA-DMX-028

3

4

.................................................................................................................................................................................................

At the near end, connect a SONET test set to the EC-1 port to be tested at the STSX-1 panel or equivalent connection point and apply an EC-1 test signal.

.................................................................................................................................................................................................

Was the test successful (error free)?

If...

Yes,

No,

Then...

Continue with

Step 5 .

Proceed to

Step 21 .

.................................................................................................................................................................................................................................

14-82 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-11: Perform EC-1 transmission test

5

.................................................................................................................................................................................................

Is the protection slot associated with the EC-1 circuit under test equipped with a companion DS3/EC1 circuit pack?

If...

Yes,

No,

Then...

Continue with

Step 6 .

Proceed to

Step 9 .

6

7

.................................................................................................................................................................................................

Use the

Fault

→

Protection Switch

command to perform a manual switch from the current active circuit pack to the standby circuit pack. This may cause a hit and register some errors during the switch.

.................................................................................................................................................................................................

Was the circuit pack protection switch successful (recovered error free)?

If...

Yes,

No,

Then...

Verify that the Standby circuit pack is now

Active, and repeat

Step 3

for the protection circuit pack.

Proceed to

Step 8 .

Proceed to

Step 21 .

8

.................................................................................................................................................................................................

Was the test successful (error free)?

If...

Yes,

No,

Then...

Continue with

Step 9 .

Proceed to

Step 21 .

9

.................................................................................................................................................................................................

Are you performing this test for a stand-alone Metropolis

®

end-to-end testing within a Metropolis

®

DMX network?

DMX shelf or for

If...

Stand-alone test,

Then...

Continue with

Step 10 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-83

Supporting procedures Procedure 14-11: Perform EC-1 transmission test

If...

End-to-end test,

Then...

Proceed to

Step 15 .

10

11

12

13

14

15

16

17

18

.................................................................................................................................................................................................

Remove the fibers used to loop back the circuit under test and disconnect the SONET test set from the STSX-1 panel or equivalent connection point.

Important! Unterminated EC-1 circuits require a 75 ohm termination or loopback at the STSX-1 to prevent incoming alarm indications.

.................................................................................................................................................................................................

Delete the cross-connections entered to perform this procedure.

Reference:

Procedure 10-4: “Discontinue DS3 or EC-1 service” (p. 10-13)

.................................................................................................................................................................................................

In the System View screen, select

Configuration

→

Update System

→

Update All

to retire existing alarms caused by this procedure.

.................................................................................................................................................................................................

If required, repeat

Step 1

through

Step 12

for each EC-1 circuit to be tested.

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

At the near end, disconnect the SONET test set from the STSX-1 panel or equivalent connection point.

.................................................................................................................................................................................................

At the near end and far end, delete any cross connections entered to perform this procedure.

Reference:

Procedure 10-4: “Discontinue DS3 or EC-1 service” (p. 10-13)

.................................................................................................................................................................................................

At the far end, release the terminal loopback using the

Fault

→

Analysis

→

Loopback

command, or remove the patch cords at the STSX-1 panel or equivalent connection point the circuit under test.

.................................................................................................................................................................................................

At the near end and far end, select

Configuration

→

Update System

→

Update All

to retire existing alarms caused by this procedure.

.................................................................................................................................................................................................................................

14-84 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-11: Perform EC-1 transmission test

19

20

21

.................................................................................................................................................................................................

If required, return to

Step 1

and repeat this procedure for each EC-1 circuit to be tested.

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

Has the DS3/EC1 circuit pack that failed this test been replaced?

If...

Yes,

No,

Then...

Proceed to

Step 23 .

Continue with

Step 22 .

22

23

.................................................................................................................................................................................................

Replace the DS3/EC1 circuit pack and repeat this procedure.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

.................................................................................................................................................................................................

Trouble may be in the STSX-1 cross-connect wiring, EC-1 interface wiring, STS-1 cross-connections in the network, or the shelf backplane. If you continue to experience problems, contact your next level of support.

Reference:

Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble

Clearing Guide, 365-372-302

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-85

Supporting procedures

Procedure 14-12: Test function unit equipment protection switching

.................................................................................................................................................................................................................................

Overview

Use this procedure to test Metropolis

®

DMX Function unit 1+1 equipment protection switching for the low-speed electrical circuit packs.

Important! Metropolis

®

DMX does not support 1+1 equipment protection switching for low-speed OLIUs and Ethernet circuit packs.

Privilege level

You must log in as either a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure and verify that the protection group

AID is specified.

4. Verify that the Function unit to be tested contains a pair of identical circuit packs.

Step

1

2

3

4

Complete the following steps to test 1+1 equipment protection switching in a Function unit.

.................................................................................................................................................................................................

From the System View menu, select

View

→

Protection

.

Result:

The View Protection window opens.

.................................................................................................................................................................................................

Select the required 1+1 Equipment Protection Group according to the work instructions and click

Select

.

Result:

The Protection Group parameters appear.

.................................................................................................................................................................................................

Note the Active Unit (circuit pack) and click

Close

.

.................................................................................................................................................................................................

From the System View menu, select

Fault

→

Protection Switch

.

.................................................................................................................................................................................................................................

14-86 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-12: Test function unit equipment protection switching

5

6

7

Result:

The Switch Protection window opens.

.................................................................................................................................................................................................

Select the required 1+1 Equipment Protection Group according to the work instructions and click

Select

.

Result:

The protection switch parameters appear.

.................................................................................................................................................................................................

Important! If the protection slot is unequipped, has the wrong circuit pack type, or the circuit pack is failed, the protection switch request is denied.

In the

Protection Switch Mode

panel, select

Manual (Normal)

as the

Switch Type

from the pull-down menu. Then click

Apply

.

Result:

A warning appears asking you to confirm executing this command. Click

Yes

and

Close

.

.................................................................................................................................................................................................

Repeat

Step 1

through

Step 3

to verify that the protection switch was performed and the active/standby states have reversed for the circuit packs in the Protection Group.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-87

Supporting procedures

Procedure 14-13: Perform LED test

.................................................................................................................................................................................................................................

Overview

Use this procedure to test circuit pack LEDs.

Important! The LED test does not affect the LEDs on the fan unit.

Privilege level

You must log in as either a Privileged, General, or Maintenance user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Ensure that Metropolis

®

DMX is equipped with required circuit packs at the node being tested.

Step

1

Complete the following steps to perform the LED test.

.................................................................................................................................................................................................

Important! All LEDs on the shelf may be tested using the

Fault

→

Test

→

LED

command or the

ACO TEST

push-button on the SYSCTL circuit pack. The

Fault

→

Test

→

LED

command may also be used to test LEDs on an individual circuit pack. The LED test does not affect the LEDs on the fan unit.

If using the...

ACO TEST

push-button on the SYSCTL circuit pack,

Fault

→

Test

→

LED

command,

Then...

Continue with

Step 2 .

Proceed to

Step 4 .

2

.................................................................................................................................................................................................

Press and hold the

ACO TEST

push-button momentarily on the SYSCTL circuit pack.

Verify that all circuit pack LEDs light, and release the

ACO TEST

push-button. The

LEDs revert to their previous state.

If the

ACO TEST

push-button is pressed for two or more seconds and released, the

IND

display on the SYSCTL circuit pack faceplate shows the generic software version.

.................................................................................................................................................................................................................................

14-88 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-13: Perform LED test

3

.................................................................................................................................................................................................

Did the LED test pass?

If...

Yes

No

Then...

STOP! End of Procedure.

Contact your next level of support.

4

5

6

7

.................................................................................................................................................................................................

From the System View menu, select

Fault

→

Test

→

LED

.

.................................................................................................................................................................................................

Highlight

Shelf

(tests all shelf LEDs) or

CP xxx

(tests individual circuit pack LEDs) and click

Select

.

Result:

The Test LED window opens.

.................................................................................................................................................................................................

In the

Number of Iterations

field, enter a number from 1 to 10 from the pull-down menu to indicate the number of cycles during which the LED test should be repeated and click

OK

.

Important! On-site personnel must be physically in front of NE to witness the

LED test cycles.

Result:

For each iteration:

1. All LEDs for the specified address light.

2. After 10 seconds, all LEDs go off.

3. After another 10 seconds, all LEDs are updated to show the current status of the system.

.................................................................................................................................................................................................

Did the LED test pass?

If...

Yes,

No,

Then...

STOP! End of Procedure.

Contact your next level of support.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-89

Supporting procedures

Procedure 14-14: Retrieve software generic release and database information

.................................................................................................................................................................................................................................

Overview

Use this procedure to retrieve information about the active, previous, and dormant software generics and the active, previous, and backup databases present on the NVMs installed in the LNW2 SYSCTL.

Privilege level

Any user (Privileged, General, Maintenance, or Reports Only) can complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

Step

1

Complete the following steps to retrieve information about the active, previous, and dormant software generics and the active, previous, and backup databases present on the NVMs installed in the LNW2 SYSCTL.

.................................................................................................................................................................................................

Are you physically in front of the Metropolis

®

DMX for which you want to determine

ONLY the generic software version (not database information)?

If...

Yes,

No,

Then...

Continue with

Step 2 .

Proceed to

Step 5 .

2

.................................................................................................................................................................................................

Depress and hold the

ACO TEST

push-button on the LNW2 SYSCTL for about 4 seconds.

.................................................................................................................................................................................................................................

14-90 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-14: Retrieve software generic release and database information

3

4

5

6

Result:

All LEDs on the shelf light. A red, 35-segment (5 x 7) rectangle appears in the

IND

display on the SYSCTL. Since the

IND

display is a 35-segment display, this test indicates all segments are working.

.................................................................................................................................................................................................

Release the

ACO TEST

push-button on the LNW2 SYSCTL when the red rectangle disappears in the

IND

display.

Result:

The current software generic appears in the

IND

display on the LNW2

SYSCTL and the shelf LEDs return to their previous status.

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

Connect the PC and establish a WaveStar

®

CIT session.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

.................................................................................................................................................................................................

The active generic is displayed in title bar in the WaveStar

®

CIT System View window.

OR

From the System View, select

View

→

Software Generic

.

Result:

The View Software Generic screen appears. This screen displays information about the Software Generic(s) and Database(s).

Software generic

Displays the software generics available on the NVMs:

•

Active: The software generic running from the NVMs is composed of boot code, compressed SYSCTL code, uncompressed SYSCTL code, and compressed

SMART CP code.

•

Previous: When a new generic is applied, the Active generic is renamed

Previous and retains the same structure. If there is no Previous generic, “?” is displayed.

•

Dormant:

– A software generic was downloaded to the NE but not yet applied.

– A release for a compatible Product Type was downloaded to the NE. A

Metropolis

®

DMX 5.x generic or earlier is treated as a different product type because it cannot be applied on the LNW2.

When a valid Dormant generic is applied, the Active becomes the Previous and the

Dormant becomes the Active. Since after the Dormant is applied, there is no longer a Dormant generic, “?” is displayed.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-91

Supporting procedures Procedure 14-14: Retrieve software generic release and database information

Product Type

Displays the associated product type for each generic.

•

For the Active and Previous generics the only valid Product type is DMX.

•

For the Dormant software generic, the Product Type can be any of the following product types

– dmx = Metropolis

®

DMX

– dmxtend = Metropolis

®

DMXtend

– dmxpress = Metropolis

®

DMXpress

– dmxplore = Metropolis

®

DMXplore

– ddmoc3 = DDM OC-3

– ddmoc12 = DDM-2000 OC-12

– fbrrch = FIBER REACH

Databases

Displays available databases on the NVMs:

•

Active - When a new generic is installed, the Active database is saved and renamed Previous, the Active database is updated, and the security and history files are changed to record the APPLY command and any resulting messages.

The Active database release must match the Active generic release.

•

Previous - When a new generic is installed, the Active database is renamed

Previous. If there is no Previous database, “?” is displayed.

•

Backup - A backup database was downloaded to the NE but not selected to be the Active database.

When a valid Backup database is selected, the Active becomes the Previous and the Backup becomes the Active. Since after the Backup is selected, there is no longer a Backup database, “?” is displayed.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-92 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-15: Check -48 V DC office battery

.................................................................................................................................................................................................................................

Overview

WARNING

Electric shock hazard

-48 volt DC is present in the input power cables at the rear of the Metropolis

®

shelf.

DMX

Follow local practices to avoid electric shock.

CAUTION

Service disruption hazard

If system is in service, service interruption will occur if both power cables are disconnected.

Disconnected the power cables one at a time to avoid a service interruption.

Use this procedure to check the office battery voltage.

Required equipment

In addition to the equipment listed in

“Required equipment” (p. 14-3) , a multimeter

capable of measuring voltage in the 40 to 60 volt range is also required.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Verify that a multimeter is available.

4. Obtain the work instructions for this procedure.

Step

1

2

Complete the following steps to perform the office battery test.

.................................................................................................................................................................................................

Obtain multimeter for measuring the DC voltage.

.................................................................................................................................................................................................

Remove ONE of the input power cables at the rear of the Metropolis

®

DMX shelf.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-93

Supporting procedures Procedure 14-15: Check -48 V DC office battery

3

4

.................................................................................................................................................................................................

Use multimeter to measure DC voltage in the power cable connector. Place negative probe in power cable connector and positive probe to a solid chassis ground.

Result:

Voltage measurement is between -40.0 and -60.0 volts DC.

.................................................................................................................................................................................................

Was the requirement met?

If...

Yes,

No,

Then...

Proceed to

Step 7 .

Continue with

Step 5 .

5

6

7

.................................................................................................................................................................................................

Trouble in power feeder(s) or office battery distribution. Refer trouble to organization that installed the shelf.

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

Have both power cables been checked?

If...

Yes,

No,

Then...

Proceed to

Step 9 .

Continue with

Step 8 .

8

9

.................................................................................................................................................................................................

Reinstall power cable if removed. Remove other power cable and repeat this procedure from

Step 3

for other power cable.

.................................................................................................................................................................................................

Are both power cables installed?

If...

Yes,

No,

Then...

Proceed to

Step 11 .

Continue with

Step 10 .

.................................................................................................................................................................................................................................

14-94 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-15: Check -48 V DC office battery

10

11

.................................................................................................................................................................................................

Install BOTH power cables at rear of Metropolis

®

DMX shelf.

.................................................................................................................................................................................................

Is any circuit breaker tripped?

If...

Yes,

No,

Then...

Continue with

Step 12 .

Proceed to

Step 16 .

12

13

.................................................................................................................................................................................................

Reset circuit breaker.

.................................................................................................................................................................................................

Did circuit breaker trip again?

If...

Yes,

No,

Then...

Continue with

Step 14 .

Proceed to

Step 16 .

14

15

16

.................................................................................................................................................................................................

Trouble in backplane connector. Refer trouble to the organization that installed the shelf.

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

Are PWR A and B LEDs lighted?

If...

Yes,

No,

Then...

STOP! End of Procedure.

Continue with

Step 17 .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-95

Supporting procedures Procedure 14-15: Check -48 V DC office battery

17

.................................................................................................................................................................................................

Trouble in backplane connector. Refer trouble to the organization that installed the shelf.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-96 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-16: Operate/release facility or terminal loopbacks

.................................................................................................................................................................................................................................

Overview

CAUTION

Service disruption hazard

Executing this command may affect service. This command creates a terminal or facility loopback at the specified interface.

This command should only be used during pre-service testing of facilities and during fault diagnostics. The loopback request remains active until released; for example, by command, or until overridden by an NE initialization or repowering.

This procedure may be used to operate or release Facility or Terminal loopbacks.

Privilege level

You must log in as either a Privileged or General user to complete this procedure.

Facility loopbacks

A Facility loopback connects the incoming received signal to the transmitter in the return direction. Electrical signals are looped back intact, including BPVs. Optical signals are looped back after the optical to electrical conversion.

Figure 14-15, “Facility loopback example” (p. 14-97)

shows a facility loopback used in a test arrangement with an external test set.

Figure 14-15 Facility loopback example

External

Test

Set

Looped

Port/Line

Rx

Tx

Circuit Pack

Cross-

Connect

Cross-

Connect

Facility Loopback

Circuit Pack

Tx

Rx

AIS-P

MA-DMX-322

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-97

Supporting procedures Procedure 14-16: Operate/release facility or terminal loopbacks

Reference the following for additional information on facility loopbacks:

•

Establishing a facility loopback may cause switching in UPSR or 1+1 applications.

Anything not force switched to the looped-back side will switch, unless the other side is failed.

•

Optical facility loopbacks operate on an OC-n line AID.

•

Two Command Mode parameters (

NORM

[normal] or

FRCD

[forced]) are available for the

Fault

→

Analysis

→

Loopback

→

Facility

command. If the Command

Mode is NORM, the loopback is denied unless the OC-n line is NMON. If the

Command Mode is FRCD, the loopback is accepted (as long as the other parameters are valid).

•

If the Command Mode is

NORM

and the line is not in the NMON state, the command is denied.

•

If the Command Mode is

FRCD

and the line is not in the NMON state, an AIS-L alarm is generated and path or line switching requests are generated in UPSR and

1+1 applications.

Terminal loopbacks

A Terminal loopback is used to loop back the entire transmitted signal into the associated incoming receiver.

Figure 14-16, “Terminal loopback example” (p. 14-98)

shows a terminal loopback used in a test arrangement with an external test set.

Figure 14-16 Terminal loopback example

External

Test

Set

Rx Tx

Cross-

Connect

Cross-

Connect

Tx

Circuit Pack Circuit Pack

Terminal Loopback

= See table below for signal transmitted.

Rx

If interface type is...

DS1

DS3 (LNW19B)

DS3 (LNW16 and LNW19)

SONET

Ethernet

Data

Then signal transmitted is...

AIS

AIS

Bridged

Bridged

Open

Open

*

Looped

Port/Line

MA-DMX-323

.................................................................................................................................................................................................................................

14-98 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-16: Operate/release facility or terminal loopbacks

Reference the following for additional information on terminal loopbacks:

•

Establishing a terminal loopback may cause switching in UPSR or 1+1 applications. If all traffic is switched away from the side to be looped back, establishing the loopback is not initially service-affecting.

•

A line or path must be switched to the side with the loopback in order to see the effect of the loopback. In UPSR applications, it’s possible to isolate individual paths for testing by switching all traffic away from the looped-back line, then switching the path to be tested to the looped-back line.

•

Optical terminal loopbacks operate on an OC-n line AID.

•

The only valid value for the Command Mode in the

Fault

→

Analysis

→

Loopback

command is

FRCD

for OCn Terminal loopbacks

Loopback availability

The system supports Facility loopbacks for:

•

DS1, E1, DS3, and EC-1

•

Low-speed OC-3 (LNW37 and LNW45 OC-3 OLIUs only), OC-12, and OC-48

•

High-speed OC-12, OC-48, and OC-192

The system supports Terminal loopbacks for:

•

DS1, E1, DS3, and EC-1

•

Low-speed OC-3, OC-12, and OC-48

•

Ethernet LAN ports

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Refer to

“Facility loopbacks” (p. 14-97)

and

“Terminal loopbacks” (p. 14-98)

for related information.

4. Obtain the work instructions for this procedure and verify that the port AID is specified.

5. Verify that the port to be looped back is not part of a test access session. A loopback request is denied if the port is part of a test access connection.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-99

Supporting procedures

Step

Procedure 14-16: Operate/release facility or terminal loopbacks

1

2

3

4

Use this procedure to operate or release a facility loopback.

.................................................................................................................................................................................................

From the System View menu, select

Fault

→

Analysis

→

Loopback

.

Result:

The Loopback window opens.

.................................................................................................................................................................................................

Find and expand the details for the required circuit pack. Select (highlight) the port to be looped back, then click

Select

at the bottom of the window.

Result:

The loopback parameters appear.

.................................................................................................................................................................................................

Select

Operate

or

Release

, the

Loopback Type

(Terminal or Facility), and the

Command Mode

(NORM or FRCD), if available.

.................................................................................................................................................................................................

At the bottom of the window, click

Apply

to perform the selected operation.

Result:

Yes

A warning appears asking you to confirm executing this command. Click and

Close

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-100 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-17: Observe FTP progress

.................................................................................................................................................................................................................................

Overview

Use this procedure to observe the progress of a transfer via FTP.

Important! This procedure assumes that the WaveStar

®

CIT is your FTP Server and can only be performed if you selected

Enable WaveStar CIT FTP Server

during the WaveStar

®

CIT installation (refer to

Procedure 14-1: “Install generic and

WaveStar

®

CIT software on the PC” (p. 14-4) ). If you selected

Disable WaveStar

CIT FTP Server

, you cannot use this procedure.

Required equipment

Only a personal Computer (PC) with WaveStar

®

CIT software (with

Enable WaveStar

CIT FTP Server

selected) installed is required to perform this procedure.

Step

1

Complete the observe FTP progress.

.................................................................................................................................................................................................

From the Network View, either

• select

Administration

→

FTP Administration

.

or

• click on the rotating FTP icon in the lower left-hand corner of the Network View

Window.

Important! This step is executed from the Network View; most WaveStar

®

CIT activities are executed from the System View.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-101

Supporting procedures Procedure 14-17: Observe FTP progress

Result:

The following FTP Server window appears.

2

The FTP server may display multiple FTP sessions listed by ID 1, 2.... The active session is identified by a green check-mark and the Status: Active. Older sessions are identified by a red X and the Status: Disconnect.

.................................................................................................................................................................................................

Identify the ID for the Active session and click on the corresponding IDx tab to view the transmission progress. When the transmission is complete, the Status for that ID changes to Disconnect. Click

Close

when finished.

Important! If the FTP server fails to start, it could mean that another program using an FTP server is already running. Depending on what operating system you are using, you must go to the device file and disable the FTP server. Refer to

Procedure 14-18: “Disable an FTP server on your PC” (p. 14-103)

for instructions for each allowed operating system.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-102 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-18: Disable an FTP server on your PC

.................................................................................................................................................................................................................................

Overview

Use this procedure to disable an FTP server application that is running on the personal computer being used for the WaveStar

®

CIT.

Required equipment

Only a personal Computer (PC) with WaveStar

®

CIT software installed is required to perform this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

in this chapter

2. Because multiple FTP applications might be installed on this PC, you must be able to identify the program you wish to disable.

Step

1

Complete the following steps to backup and restore the system.

.................................................................................................................................................................................................

Which Windows Operating System are you using?

If...

Windows 2000

Windows NE

Windows XP

Then

Continue with

Step 2 .

Proceed to

Step 7 .

Proceed to

Step 12 .

2

3

4

.................................................................................................................................................................................................

For Windows 2000 operating systems, select

Start

→

Settings

→

Control Panel

.

.................................................................................................................................................................................................

Select

Administrative Tools

, then

Computer Management

, then

Services and Applications

, and then

Services

.

.................................................................................................................................................................................................

Locate the FTP file that is running and double click the FTP icon.

.................................................................................................................................................................................................

In the

Service Status:

field, click

Stop

.

5

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-103

Supporting procedures Procedure 14-18: Disable an FTP server on your PC

6

7

8

9

10

11

12

13

14

15

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

For Windows NT operating systems, select

Start

→

Settings

→

Control Panel

.

.................................................................................................................................................................................................

Double click the

Services

icon.

.................................................................................................................................................................................................

Locate the FTP service that is running and select it.

.................................................................................................................................................................................................

Click

Stop

, then

Yes

, then

Close

.

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

For Windows XP operating systems, select

Start

→

Control Panel

.

.................................................................................................................................................................................................

Click the

Performance and Maintenance

icon, then the

Administrative Tools

icon, and then

Services

.

.................................................................................................................................................................................................

Locate the FTP service that is running and select it.

.................................................................................................................................................................................................

Click

Stop

, then

Close

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-104 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-19: Reset the system

.................................................................................................................................................................................................................................

Overview

Use this procedure to perform a system reset. This procedure details resetting the system software by reinitializing/resetting the SYSCTL via the WaveStar

®

CIT

(preferred method) or reseating the SYSCTL (communication via the WaveStar

®

CIT failed).

Important! If a system (software) reset is required, the recommended method is via the WaveStar

®

CIT ( Step 2 ).

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

Step

1

Complete the following steps to reset the system.

.................................................................................................................................................................................................

Do you have WaveStar

®

CIT connectivity to the NE that you wish reset?

If...

Yes,

No,

Then...

Continue with

Step 2 .

Proceed to

Step 8 .

2

.................................................................................................................................................................................................

From the System View menu, select

Fault

→

Reset

→

System Controller

.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-105

Supporting procedures Procedure 14-19: Reset the system

3

4

5

6

7

8

Result:

The Reset System Controller window opens.

.................................................................................................................................................................................................

Select the appropriate option.

•

Reset the system software without changing parameters (Phase 3)

(

init-sys:3

) Existing cross-connections, TID, and current database information are retained.

Phase 3 is available to Privileged and General users.

•

Restore the system-level parameters to their default values (Phase 9)

(

init-sys:9

) The system controller defaults are restored. For example, only default logins exist and TCP/IP addresses return to their default state (none).

Phase 9 is only available to Privileged users.

The TID provisioning, transmission circuit pack provisioning, and cross-connection maps are retained.

.................................................................................................................................................................................................

Click

OK

.

Result:

A warning appears asking you to confirm executing this command.

.................................................................................................................................................................................................

Click

Yes

to execute the command.

Important! You will be logged off the system when the system resets.

Result:

You are logged off the system.

A flashing

b

in the

IND

display on the SYSCTL indicates that a boot is in progress.

During the boot, the

b

may extinguish for up to 20 seconds and then resume flashing.

.................................................................................................................................................................................................

Log back in the NE that was reset.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

If the pack is operational (not failed), initiate a ten-second countdown (9, 8, 7, 6, 5, 4,

3, 2, 1, 0) in the

IND

display on the SYSCTL by simultaneously depressing the

ACO TEST

and

SEL

buttons on the front of the SYSCTL.

Important! Removing the SYSCTL without initiating the ten-second countdown may result in unexpected and undesirable protection switches, incorrect circuit fault

.................................................................................................................................................................................................................................

14-106 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-19: Reset the system

9

10

11

indications, or incoming signal failure alarms. All SYSCTL functions are suspended during the countdown.

.................................................................................................................................................................................................

Unseat the SYSCTL circuit pack during the 10-second countdown.

.................................................................................................................................................................................................

Re-seat the SYSCTL circuit pack and allow a few minutes for the pack to complete initialization.

Result:

A flashing

b

in the

IND

display on the SYSCTL indicates that a boot is in progress. During the boot, the

b

may extinguish for up to 20 seconds and then resume flashing.

.................................................................................................................................................................................................

Connect PC and establish a WaveStar

®

CIT session to the reset NE.

Reference:

WaveStar

®

Procedure 14-2: “Connect Personal Computer (PC) and establish

CIT session” (p. 14-24)

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-107

Supporting procedures

Procedure 14-20: Reset smart circuit pack

.................................................................................................................................................................................................................................

Overview

Use this procedure to reset a smart circuit pack.

Smart circuit packs

Smart circuit packs have microprocessors and run software.

Metropolis

®

DMX supports the following smart circuit packs:

•

LNW6 28DS1

•

LNW7 28DS1PM

•

LNW8 56DS1/E1

•

LNW16 12DS3EC1

•

LNW18 TMUX

•

LNW19/LNW19B 48DS3/EC1

•

LNW63 GBE PL

•

LNW66 10/100T

•

LNW67 1GSX

•

LNW68 1GLX

•

LNW70 100/1G FS

•

LNW71 10/100-PL

•

LNW73/LNW73C FC

•

LNW74 10/100 T/F

•

LNW78 100/1G FSR

Privilege level

You must log in as a Privileged or General user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Obtain the work instructions for this procedure and/or determine the smart circuit pack to be reset.

.................................................................................................................................................................................................................................

14-108 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Step

Procedure 14-20: Reset smart circuit pack

1

2

3

Complete the following steps to reset a smart circuit pack.

.................................................................................................................................................................................................

From the System View select

Reports

→

Status Lists

→

Pack

. Click on Shelf and

Select

. Determine if the smart circuit pack to be reset is part of a protected pair of circuit packs. Observe the value of the Switch State parameter for the smart circuit pack to be reset. If the Switch State parameter is active, the circuit pack is the active circuit pack for transmission. Click

Close

.

.................................................................................................................................................................................................

Important! This step is optional. If the smart circuit pack to be reset is part of a protected pair of circuit packs and is the active circuit pack for transmission, then a manual switch must be performed before resetting the smart circuit pack. If the smart circuit pack to be reset is part of a protected pair of circuit packs and is not the active circuit pack for transmission, do not perform this step. If the smart circuit pack to be reset is not part of a protected pair of circuit packs, do not perform this step.

To perform a manual transmission switch, select

Fault

→

Protection Switch

. Click on the required protection group and

Select

. Select the Normal Switch Type and click

Apply

.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

.

.................................................................................................................................................................................................

CAUTION

Service disruption hazard

If the smart circuit pack to be reset is not part of a protected pair of circuit packs, the reset may cause loss of service.

If the smart circuit pack to be reset is part of a protected pair of circuit packs and the companion circuit pack is failed, the reset may cause loss of service.

To reset the smart circuit pack, select

Fault

→

Reset

→

Smart Pack

. Click on the smart circuit pack to be reset and

Select

.

Result:

A warning may appear asking you to confirm executing this command.

Click

Yes

to reset the smart circuit pack. A dialog box appears indicating a successful reset. Click

OK

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-109

Supporting procedures

Procedure 14-21: Change the network card selection

.................................................................................................................................................................................................................................

Overview

Use this procedure to change the network card selection.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

Step

1

2

3

4

Complete the following steps to change the network card selection.

.................................................................................................................................................................................................

From the Network View menu, select

Administration

→

OSI/Network Card

Assignment

.

.................................................................................................................................................................................................

Select the desired card number in the Network Card drop-down list.

.................................................................................................................................................................................................

Confirm the Network Card properties are correct in the text box display area.

.................................................................................................................................................................................................

Click

OK

to confirm your selection or

Cancel

to exit the dialog box without making any changes.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-110 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-22: Replace defective fan unit

.................................................................................................................................................................................................................................

Overview

Use this procedure to replace a fan unit.

Required equipment

The following equipment is required:

•

Wrist strap

•

Small phillips-head screwdriver

•

Small flat-blade screwdriver

Before you begin

Ensure that the replacement fan unit is the same type as the original fan unit.

Step

1

2

Complete the following steps to replace the fan unit.

.................................................................................................................................................................................................

Unscrew screw locks and disconnect power and alarm cable from fan unit on the

Metropolis

®

DMX shelf or the Metropolis

®

DMX high capacity shelf.

.................................................................................................................................................................................................

Back out the screws securing the fan unit and loosen mounting screws that attach the fan bracket to the frame.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-111

Supporting procedures Procedure 14-22: Replace defective fan unit

Reference:

Figure 14-17, “Metropolis

®

DMX fan unit screws” (p. 14-112)

illustrates the location of the screws on the Metropolis

®

DMX shelf.

Figure 14-17 Metropolis

®

DMX fan unit screws

Back These Screws Out To Remove

Fan Unit From Chassis

Rear View Of Fan Shelf

Back These Screws Out To Remove

Fan Unit From Chassis

Front View Of Fan Shelf nc-dmx-197

Figure 14-18, “Metropolis

®

DMX High Capacity shelf fan unit screws” (p. 14-112)

illustrates the location of the screws on the Metropolis

®

DMX High Capacity shelf.

Figure 14-18 Metropolis

®

DMX High Capacity shelf fan unit screws

Back these screws out to remove fan unit from chassis

Disconnect power cable before removing fan unit

Nidec

Rear view of fan shelf nc-dmx-216

3

.................................................................................................................................................................................................

Slide the old fan unit out from the fan chassis.

.................................................................................................................................................................................................................................

14-112 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-22: Replace defective fan unit

4

5

.................................................................................................................................................................................................

Slide the new fan unit back into the fan chassis. Tighten all screws located in the front and back of the fan unit for the Metropolis

®

DMX shelf or the Metropolis

®

DMX high capacity shelf.

Hand tighten the #4 steel thread fasteners until

″ snug tight

″ and then 1/2 turn with a wrench/screwdriver (torque should be approximately 8 in-lb).

.................................................................................................................................................................................................

Reconnect the power and alarm cable to the back of the fan shelf on the Metropolis

®

DMX shelf or the Metropolis

®

DMX high capacity shelf.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-113

Supporting procedures

Procedure 14-23: Establish test access session in the MON(E or EF) mode

.................................................................................................................................................................................................................................

Overview

Use this procedure to establish a new test access session in the following test access modes:

•

MONE

•

MONEF

A new test access session can be created only in the MONE or MONEF test access mode initially. To change the test access mode of an existing test access session, refer to

Procedure 14-25: “Change test access mode of test access session” (p. 14-127) .

Privilege level

You must log in as either a Privileged, General, or Maintenance user to complete this procedure.

MONE mode

The MONE mode is used to monitor the E Tributary input signal of a one-way cross-connection, a two-way cross-connection, or an idle E Tributary input signal (no cross-connection).

The following figure shows an example of the MONE mode used to monitor the E

Tributary input signal of a two-way cross-connection.

Network Element

A Direction

E

Tributary

B Direction

F

Tributary

Test Access

Tributary 1

Legend:

- No connection

Testing System

MA-DMX-373

If the F Tributary is entered, the F Tributary must be the destination of a one-way cross-connection that has the E Tributary as the source, or the F Tributary must be part of a two-way cross-connection that does not have any other test access sessions on it.

If the E Tributary is part of a two-way multicast cross-connection, entering the F

.................................................................................................................................................................................................................................

14-114 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-23: Establish test access session in the

MON(E or EF) mode

Tributary is optional. The system automatically retrieves the other end. The E Tributary or F Tributary cannot be on an Ethernet circuit pack.

MONEF mode

The MONEF mode is used to monitor the E Tributary input signal and the F Tributary input signal of a two-way cross-connection.

The following figure shows an example of the MONEF mode used to monitor two tributaries.

Network Element

A Direction

E

Tributary

B Direction

F

Tributary

Test Access

Tributary 1

Legend:

- No connection

Testing System

Test Access

Tributary 2

MA-DMX-375

The E Tributary, F Tributary, and two test access tributaries are required. If the E

Tributary is part of a two-way cross-connection, entering the F Tributary is optional.

The MONEF mode is not supported for tributaries that have one-way cross-connections or idle tributaries (no cross-connections). The E Tributary or F Tributary cannot be on an Ethernet circuit pack.

Supported VT1.5 rate test access configurations

The following table shows the E Tributaries and F Tributaries (VT1.5

cross-connections) and the supported Test Access Tributaries.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-115

Supporting procedures Procedure 14-23: Establish test access session in the

MON(E or EF) mode

Test Access Tributaries

A-D Slots A-G Slots

1

- Unprotected 1+1 Only

2

OC-3/12 OC-48 EC1 TMUX DS1/E1

LNW16

LNW19

LNW19B

LNW18 LNW6

LNW7

LNW8

LNW36

LNW37

LNW45

LNW46

LNW49

✓

LNW31

E

Tributary and F

Tributary

3

Main Add/Drop

VT1.5

Cross-Connection

5, 6 to:

FN A-D DS3/EC1

TMUX

4

✓

✓

✓

✓

✓

✓ ✓

✓

✓

DS1/E1

✓ ✓ ✓ ✓ ✓

E

Tributary and F

Tributary

3

DS1/EC1/TMUX

(FN A-D)

VT1.5 Hairpin

Cross-Connection

5, 6 to:

FN A-G

FN A-D

OC-3/12/48

✓

DS3/EC1

TMUX

DS1/E1

4

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

OC-3/12/48

(FN A-G)

VT1.5 Hairpin

Cross-Connection

5, 6 to:

FN A-G

FN A-D

OC-3/12/48

✓

DS3/EC1

TMUX

DS1/E1

4

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

FN A-G OC-3/12/48

✓ ✓ ✓ ✓ ✓

1

Test Access Tributary 1 and Test Access Tributary 2 are always connected to the same optical interface.

2

Intended for unprotected 1+1 interfaces (port Application parameter = 1+1) to locally-connected testheads only.

3

Main OLIUs with large VT switch fabric only. Restrictions apply to LNW26B, LNW28, LNW48, LNW50, LNW77, and

LNW121B-159B OLIU circuit packs.

4

EC-1 interfaces only.

5

Test Access of locked cross-connections restricted to electrical test access tributaries.

6

Test Access of UPSR Dual Ring Interworking cross-connections is not supported.

Supported STS-1 rate test access configurations

The following table shows the E Tributaries and F Tributaries (STS-1 rate cross-connections) and the supported Test Access Tributaries.

.................................................................................................................................................................................................................................

14-116 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-23: Establish test access session in the

MON(E or EF) mode

Test Access Tributaries

A-D Slots A-G Slots

1

- Unprotected 1+1 Only

2

DS3/EC1 OC-3/12 OC-48

LNW16

LNW19

LNW19B

LNW36

LNW37

LNW45

LNW46

LNW49

✓

LNW31

E Tributary and F

Tributary

Main Add/Drop

STS-1

Cross-Connection to:

3, 4

FN A-D

FN A-G

DS3/EC1

OC-3/12/48

5

✓

✓ ✓

✓

✓

Thru STS-1 Cross-Connection BLSR

✓ ✓ ✓

UPSR

✓

✓

✓

✓

✓

✓

E Tributary and F

Tributary

DS3/EC-1

(FN A-D)

STS-1 Hairpin

Cross-Connection to:

3, 4

FN A-D

FN A-G

DS3/EC1

OC-3/12/48

5

✓ ✓ ✓

OC-3/12/48

(FN A-G)

STS-1 Hairpin

Cross-Connection to:

3, 4

FN A-D

FN A-G

DS3/EC1

OC-3/12/48

5

✓

✓

✓

✓

✓

✓

1

Test Access Tributary 1 and Test Access Tributary 2 are always connected to the same optical interface.

2

Intended for unprotected 1+1 interfaces (port Application parameter = 1+1) to locally-connected testheads only.

3

Test Access of locked cross-connections restricted to electrical test access tributaries.

4

Test Access of UPSR Dual Ring Interworking cross-connections is not supported.

5

Test access of low-speed BLSR cross-connections is not supported.

Restrictions

The following restrictions apply when establishing a test access session in the MON(E or EF) mode.

•

A new test access session can be created only in the MONE or MONEF test access mode initially.

•

A new test access session is denied if a node or ring network upgrade is active

(node is in provisioned Ring Upgrade mode).

•

A new test access session is denied if a transmission test, loopback, or test access session is already active on an affected port.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-117

Supporting procedures Procedure 14-23: Establish test access session in the

MON(E or EF) mode

•

If the Main slots are equipped with LNW26B, LNW28, LNW48, LNW50, LNW77, or LNW121B-159B circuit packs, the VT1.5 test access cross-connection capacity is limited because of the small VT switch fabric. Therefore, it is recommended that you use only the MONE or SPLTE mode and avoid using ports on the LNW6 and

LNW7 circuit packs for the E Tributary, F Tributary, and Test Access Tributaries.

•

If the E Tributary or F tributary is part of a locked DSn cross-connection, the Test

Access Tributary connected to the optical side of the locked DSn cross-connection must be an idle tributary of an electrical interface with a matching rate.

•

Test Access of UPSR Dual Ring Interworking cross-connections is not supported.

•

Test Access of VT1.5 through cross-connections (UPSR/BLSR) is not supported.

CAUTION

Service disruption hazard

Service interruptions may occur on unintended tributaries if unsupported test access configurations are attempted.

Recheck the address (AID) of the tributary(ies) being tested and the test access tributary(ies). Do not attempt to establish unsupported test access sessions.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Verify that the work instructions identify the test access mode, test access rate, and the assigned addresses (AIDs) of the tributary(ies) to be tested and the test access tributary(ies).

5. If the work instructions specify optical test access tributaries are to be used, verify that unprotected 1+1 optical interfaces to locally-connected testheads exist. If required, refer to

Procedure 9-11: “Establish low-speed 1+1 unprotected linear optical extension” (p. 9-132)

to establish an unprotected 1+1 interface to the local testhead.

.................................................................................................................................................................................................................................

14-118 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-23: Establish test access session in the

MON(E or EF) mode

Step

1

2

3

4

5

6

7

Complete the following steps to establish a new test access session in the MON(E or

EF) mode.

.................................................................................................................................................................................................

Verify that the Test Access Tributary Tributary Monitoring Mode parameter is provisioned NMON. Select

View

→

Equipment

. Expand the required circuit pack and port details, highlight the required tributary, and click

Select

to obtain a list of tributary parameters.

.................................................................................................................................................................................................

If required, provision the Test Access Tributary Tributary Monitoring Mode parameter to NMON to avoid possible alarms. Select

Configuration

→

Equipment

. Expand the required circuit pack and port details, highlight the required tributary, and click

Select

.

Provision the Tributary Monitoring Mode parameter to NMON. Click

Apply

and

Close

.

.................................................................................................................................................................................................

If creating a new test access session between a low-speed electrical port (for example,

DS1 or DS3) and a Test Access Tributary, provision the low-speed electrical port Port

Monitoring Mode parameter to NMON to avoid possible alarms. Select

Configuration

→

Equipment

. Expand the required low-speed electrical circuit pack details, highlight the required low-speed electrical port, and click

Select

. Provision the Port Monitoring

Mode parameter to NMON. Click

Apply

and

Close

.

.................................................................................................................................................................................................

If creating a new test access session between a BLSR tributary and a Test Access

Tributary, disable Ring Circuit Audit Alarm reporting for the BLSR protection group.

Select

Configuration

→

Equipment

. Click on the Ptn Grp tab, highlight the required

2F BLSR protection group, and click

Select

. Disable the Ring Circuit Audit or Ring

Circuit Alarm Mode parameter. Then click

Apply

and

Close

.

.................................................................................................................................................................................................

From the System View menu select

Fault

→

Analysis

→

Test Access

.

Result:

The Test Access Wizard appears.

.................................................................................................................................................................................................

Click

Create a new test access session

and

Next

.

.................................................................................................................................................................................................

Follow the directions in the remaining Test Access Wizard screens to create a new test access session in the MONE or MONEF test access mode at the STS-1 or VT1.5 rate according to the work instructions.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-119

Supporting procedures Procedure 14-23: Establish test access session in the

MON(E or EF) mode

8

9

10

.................................................................................................................................................................................................

Important! A test access session remains in effect until deleted.

Verify the test access session parameters, then click

Finish

at the end of the Test

Access Wizard screens.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and the Test Access Wizard appears.

.................................................................................................................................................................................................

Click

View existing test access sessions

and

Next

.

.................................................................................................................................................................................................

Follow the directions in the remaining Test Access Wizard screens. If required, click

Browse

and select the circuit pack with the desired Test Access Tributary. Verify that the test access session was created and click

Close

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-120 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-24: Establish test access session in the SPLT(E or

EF) mode

.................................................................................................................................................................................................................................

Overview

Use this procedure to establish a new test access session in the following test access modes:

•

SPLTE

•

SPLTEF

Important! Initially, a test access session must be established in the MONE or

MONEF test access mode and then changed:

•

From MONE to SPLTE

•

From MONEF to SPLTEF

Privilege level

You must log in as either a Privileged, General, or Maintenance user to complete this procedure.

SPLTE mode

The SPLTE mode is used to test the E Tributary signal.

The following figure shows an example of the SPLTE mode used to test the E

Tributary signal of a two-way cross-connection.

E

Tributary

Network Element

A Direction

AIS

B Direction

F

Tributary

Test Access

Tributary 1

Legend:

- No connection

Testing System

MA-DMX-374

The E Tributary signal is split from the F Tributary signal. AIS is transmitted on the outgoing F Tributary signal and the incoming F Tributary signal is terminated. If there is a one-way cross-connection from the E Tributary to F Tributary, AIS is transmitted on the outgoing F Tributary signal. The E Tributary can also be idle (no cross-connection). The E Tributary or F Tributary cannot be on an Ethernet circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-121

Supporting procedures Procedure 14-24: Establish test access session in the

SPLT(E or EF) mode

SPLTEF mode

The SPLTEF mode is used to test the E Tributary signal and F Tributary signal.

The following figure shows an example of the SPLTEF mode used to test the E

Tributary signal and F Tributary signal of a two-way cross-connection.

Network Element

A Direction

E

Tributary

B Direction

F

Tributary

Test Access

Tributary 1

Testing System

Test Access

Tributary 2

MA-DMX-376

Two test access tributaries are required. If the E Tributary is part of a two-way cross-connection, entering the F Tributary is optional. The SPLTEF mode is not supported for tributaries that have one-way cross-connections or idle tributaries (no cross-connections). The E Tributary or F Tributary cannot be on an Ethernet circuit pack.

Supported VT1.5 rate test access configurations

The following table shows the E Tributaries and F Tributaries (VT1.5

cross-connections) and the supported Test Access Tributaries.

E

Tributary and F

Tributary

3

Main Add/Drop

VT1.5

Cross-Connection

5, 6 to:

FN A-D

FN A-G

DS3/EC1

4

✓

TMUX

✓

DS1/E1

✓

OC-3/12/48

✓

Test Access Tributaries

A-D Slots

EC1

LNW16

LNW19

LNW19B

TMUX

LNW18

✓

✓

✓

✓

✓

✓

✓

✓

DS1/E1

LNW6

LNW7

LNW8

A-G Slots

1

- Unprotected 1+1 Only

2

OC-3/12 OC-48

LNW31

✓

✓

✓

✓

LNW36

LNW37

LNW45

LNW46

LNW49

✓

✓

✓

✓

.................................................................................................................................................................................................................................

14-122 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-24: Establish test access session in the

SPLT(E or EF) mode

Test Access Tributaries

A-D Slots A-G Slots

1

- Unprotected 1+1 Only

2

OC-3/12 OC-48 EC1 TMUX DS1/E1

LNW16

LNW19

LNW19B

LNW18 LNW6

LNW7

LNW8

LNW36

LNW37

LNW45

LNW46

LNW49

LNW31

E

Tributary and F

Tributary

3

DS1/EC1/TMUX

(FN A-D)

VT1.5 Hairpin

Cross-Connection to:

5, 6

FN A-D DS3/EC1

TMUX

DS1/E1

4

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

OC-3/12/48

(FN A-G)

FN A-G

FN A-D

OC-3/12/48

✓

DS3/EC1

4

✓

✓

✓

✓

✓

✓

✓

✓

✓

TMUX

✓ ✓ ✓ ✓ ✓

VT1.5 Hairpin

Cross-Connection to:

5, 6

DS1/E1

✓ ✓ ✓ ✓ ✓

FN A-G OC-3/12/48

✓ ✓ ✓ ✓ ✓

1

Test Access Tributary 1 and Test Access Tributary 2 are always connected to the same optical interface.

2

Intended for unprotected 1+1 interfaces (port Application parameter = 1+1) to locally-connected testheads only.

3

Main OLIUs with large VT switch fabric only. Restrictions apply to LNW26B, LNW28, LNW48, LNW50, LNW77, and

LNW121B-159B OLIU circuit packs.

4

EC-1 interfaces only.

5

Test Access of locked cross-connections restricted to electrical test access tributaries.

6

Test Access of UPSR Dual Ring Interworking cross-connections is not supported.

Supported STS-1 rate test access configurations

The following table shows the E Tributaries and F Tributaries (STS-1 rate cross-connections) and the supported Test Access Tributaries.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-123

Supporting procedures Procedure 14-24: Establish test access session in the

SPLT(E or EF) mode

Test Access Tributaries

A-D Slots A-G Slots

1

- Unprotected 1+1 Only

2

DS3/EC1 OC-3/12 OC-48

LNW16

LNW19

LNW19B

LNW36

LNW37

LNW45

LNW46

LNW49

✓

LNW31

E Tributary and F

Tributary

Main Add/Drop

STS-1

Cross-Connection to:

3, 4

FN A-D

FN A-G

DS3/EC1

OC-3/12/48

5

✓

✓ ✓

✓

✓

Thru STS-1 Cross-Connection BLSR

✓ ✓ ✓

UPSR

✓

✓

✓

✓

✓

✓

E Tributary and F

Tributary

DS3/EC-1

(FN A-D)

STS-1 Hairpin

Cross-Connection to:

3, 4

FN A-D

FN A-G

DS3/EC1

OC-3/12/48

5

✓ ✓ ✓

OC-3/12/48

(FN A-G)

STS-1 Hairpin

Cross-Connection to:

3, 4

FN A-D

FN A-G

DS3/EC1

OC-3/12/48

5

✓

✓

✓

✓

✓

✓

1

Test Access Tributary 1 and Test Access Tributary 2 are always connected to the same optical interface.

2

Intended for unprotected 1+1 interfaces (port Application parameter = 1+1) to locally-connected testheads only.

3

Test Access of locked cross-connections restricted to electrical test access tributaries.

4

Test Access of UPSR Dual Ring Interworking cross-connections is not supported.

5

Test access of low-speed BLSR cross-connections is not supported.

Restrictions

The following restrictions apply when establishing a test access session in the SPLT(E or EF) mode.

•

A new test access session must be created only in the MONE or MONEF test access mode initially and then changed from MONE to SPLTE, or from MONEF to

SPLTEF.

•

A new test access session is denied if a node or ring network upgrade is active

(node is in provisioned Ring Upgrade mode).

•

A new test access session is denied if a transmission test, loopback, or test access session is already active on an affected port.

.................................................................................................................................................................................................................................

14-124 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-24: Establish test access session in the

SPLT(E or EF) mode

•

If the Main slots are equipped with LNW26B, LNW28, LNW48, LNW50, LNW77, or LNW121B-159B circuit packs, theVT1.5 test access cross-connection capacity is limited because of the small VT switch fabric. Therefore, it is recommended that you use only the MONE or SPLTE mode and avoid using ports on the LNW6 and

LNW7 circuit packs for the E Tributary, F Tributary, and Test Access Tributaries.

•

If the E Tributary or F tributary is part of a locked DSn cross-connection, the Test

Access Tributary connected to the optical side of the locked DSn cross-connection must be an idle tributary of an electrical interface with a matching rate.

•

Test Access of UPSR Dual Ring Interworking cross-connections is not supported.

•

Test Access of VT1.5 through cross-connections (UPSR/BLSR) is not supported.

CAUTION

Service disruption hazard

Service interruptions can occur on tributaries if they are accidentally tested. Service interruptions may also occur on unintended tributaries if unsupported test access configurations are attempted.

Recheck the address (AID) of the tributary(ies) being tested and the test access tributary(ies). Do not attempt to establish unsupported test access sessions.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Verify that the work instructions identify the test access mode, test access rate, and the assigned addresses (AIDs) of the tributary(ies) to be tested and the test access tributary(ies).

5. If the work instructions specify optical test access tributaries are to be used, verify that unprotected 1+1 optical interfaces to locally-connected testheads exist. If required, refer to

Procedure 9-11: “Establish low-speed 1+1 unprotected linear optical extension” (p. 9-132)

to establish an unprotected 1+1 interface to the local testhead.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-125

Supporting procedures

Step

Procedure 14-24: Establish test access session in the

SPLT(E or EF) mode

1

Complete the following steps to establish a new test access session in the SPLT(E or

EF) mode.

.................................................................................................................................................................................................

Important! Initially, a test access session must be established in the MONE or

MONEF test access mode and then changed from MONE to SPLTE or from

MONEF to SPLTEF.

Establish the required test access session in the MONE or MONEF test access mode.

If a test access session is required in the...

SPLTE mode,

SPLTEF mode,

Then establish a new test access session in the...

MONE test access mode.

MONEF test access mode.

2

Reference:

Procedure 14-23: “Establish test access session in the MON(E or EF) mode” (p. 14-114)

.................................................................................................................................................................................................

Change the test access mode of the test access session established in the previous step as required from:

•

MONE to SPLTE

•

MONEF to SPLTEF

Reference:

(p. 14-127)

Procedure 14-25: “Change test access mode of test access session”

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-126 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-25: Change test access mode of test access session

.................................................................................................................................................................................................................................

Overview

Use this procedure to change the test access mode of an existing test access session among the following groups of test access modes:

•

MONE, SPLTE

•

MONEF, SPLTEF

Privilege level

You must log in as either a Privileged, General, or Maintenance user to complete this procedure.

Restrictions

The following restrictions apply to test access.

•

A new test access session can be created only in the MONE or MONEF test access mode initially.

•

If the Main slots are equipped with LNW26B, LNW28, LNW48, LNW50, LNW77, or LNW121B-159B circuit packs, the VT1.5 test access cross-connection capacity is limited because of the small VT switch fabric. Therefore, it is recommended that you use only the MONE or SPLTE mode and avoid using ports on the LNW6 and

LNW7 circuit packs for the E Tributary, F Tributary, and Test Access Tributaries.

CAUTION

Service disruption hazard

Service interruptions can occur on tributaries if they are accidentally tested. Service interruptions may also occur on unintended tributaries if unsupported test access configurations are attempted.

Recheck the address (AID) of the tributary(ies) being tested and the test access tributary(ies). Do not attempt to establish unsupported test access sessions.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-127

Supporting procedures Procedure 14-25: Change test access mode of test access session

3. Obtain the work instructions for this procedure.

4. Verify that the work instructions identify the test access mode, test access rate, and the assigned addresses (AIDs) of the tributary(ies) to be tested and the test access tributary(ies).

Step

1

2

3

4

5

6

Complete the following steps to change the test access mode of an existing test access session.

.................................................................................................................................................................................................

From the System View menu select

Fault

→

Analysis

→

Test Access

.

Result:

The Test Access Wizard appears.

.................................................................................................................................................................................................

Click

Modify an existing test access session’s mode

and

Next

.

.................................................................................................................................................................................................

Important! The test access mode changes are limited between MONE and SPLTE or MONEF and SPLTEF.

Follow the directions in the remaining Test Access Wizard screens to change the test access mode of the test access session. If required, click

Browse

and select the circuit pack with the desired Test Access Tributary to be changed.

.................................................................................................................................................................................................

Important! A test access session remains in effect until deleted.

Verify the test access session parameters, then click

Finish

at the end of the Test

Access Wizard screens.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and the Test Access Wizard appears.

.................................................................................................................................................................................................

Click

View existing test access sessions

and

Next

.

.................................................................................................................................................................................................

Follow the directions in the remaining Test Access Wizard screens. If required, click

Browse

and select the circuit pack with the desired Test Access Tributary. Verify that the test access session was changed and click

Close

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-128 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-26: Delete test access session

.................................................................................................................................................................................................................................

Overview

Use this procedure to delete an existing test access session.

Privilege level

You must log in as either a Privileged, General, or Maintenance user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Verify that the work instructions identify the test access session(s) to be deleted.

Step

1

2

3

4

Complete the following steps to delete an existing test access session.

.................................................................................................................................................................................................

From the System View menu select

Fault

→

Analysis

→

Test Access

.

Result:

The Test Access Wizard appears.

.................................................................................................................................................................................................

Click

Delete an existing test access session

and

Next

.

.................................................................................................................................................................................................

Follow the directions in the remaining Test Access Wizard screens to delete the required test access session. If required, click

Browse

and select the circuit pack with the desired Test Access Tributary.

.................................................................................................................................................................................................

Verify the test access session parameters, then click

Finish

at the end of the Test

Access Wizard screens.

Result:

A dialog box appears asking you to confirm executing this command.

Click

Yes

and the Test Access Wizard appears. Click

Close

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-129

Supporting procedures

Procedure 14-27: View test access session(s)

.................................................................................................................................................................................................................................

Overview

Use this procedure to view the existing test access session(s) on a shelf on circuit pack.

Privilege level

You must log in as either a Privileged, General, or Maintenance user to complete this procedure.

Before you begin

Prior to performing this procedure:

1. Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

2. Refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter

1, “Safety” .

3. Obtain the work instructions for this procedure.

4. Verify that the work instructions identify the assigned addresses (AIDs) of the tributary(ies) to be tested and the test access tributary(ies).

Step

1

2

3

Complete the following steps to view an existing test access session(s) on a shelf on circuit pack.

.................................................................................................................................................................................................

From the System View menu select

Fault

→

Analysis

→

Test Access

.

Result:

The Test Access Wizard appears.

.................................................................................................................................................................................................

Click

View existing test access sessions

and

Next

.

Result:

The View Graphic Test Access window opens.

.................................................................................................................................................................................................

Important! The existing test access session(s) for the shelf or an individual circuit pack may be viewed.

Select (highlight) the Shelf or required circuit pack, then click

Select

at the bottom of the window to view the existing test access session(s). Then click

Close

.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

14-130 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-28: View reports

.................................................................................................................................................................................................................................

Overview

Use this procedure as reference for viewing the following reports that are accessible from the System View

Reports

menu:

•

Equipment Lists

•

Status Lists

•

Path Protection List

•

BLSR Protection Switch List

•

NE Alarm List

•

Remote NE Alarm List

•

VT XC Fabric Utilization

•

Backplane Bandwidth Utilization

•

NE History Log

•

NE Security Log

•

MAC Address List

•

GbE Line Utilization.

Privilege level

You must log in as a Privileged, General, Maintenance, or Reports Only user to complete this procedure.

Before you begin

Prior to performing this procedure, refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

Step

1

Use the sections in this procedure as reference for viewing reports that are accessible from the System View

Reports

menu only.

.................................................................................................................................................................................................

Reference the sections in this procedure to view the desired reports.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-131

Supporting procedures Procedure 14-28: View reports

Equipment lists

The Equipment Lists show the address identifiers (AIDs), hardware codes, and/or parameter values for circuit packs, pluggable transmission modules, ports, VCGs, tributaries and miscellaneous discretes.

The following commands are used to obtain Equipment Lists.

•

Reports

→

Equipment Lists

→

Pack

•

Reports

→

Equipment Lists

→

Pluggable Transmission Module

•

Reports

→

Equipment Lists

→

Port

•

Reports

→

Equipment Lists

→

VCG

•

Reports

→

Equipment Lists

→

Trib

•

Reports

→

Equipment Lists

→

Misc. Discretes

Status lists

The Status Lists show status/state information for circuit packs, pluggable transmission modules, ports, VCGs, and tributaries.

The following commands are used to obtain Status Lists.

•

Reports

→

Status Lists

→

Pack

•

Reports

→

Status Lists

→

Pluggable Transmission Module

•

Reports

→

Status Lists

→

Port

•

Reports

→

Status Lists

→

VCG

•

Reports

→

Status Lists

→

Trib

Path protection list

The Path Protection List shows the status of UPSR paths on the shelf. The

Reports

→

Path Protection List

command is used to obtain a Path Protection List.

BLSR protection switch list

The BLSR Protection Switch List shows the protection switch status of the BLSRs on the shelf. The

Reports

→

BLSR Protection Switch List

command is used to obtain a

BLSR Protection Switch List.

NE alarm list

The NE Alarm List shows detailed information about the current alarms on the shelf.

The

Reports

→

NE Alarm List

command is used to obtain an NE Alarm List.

The NE Alarm List may be filtered by Alarm Category, Alarm Level, Effect on

Service, and Alarm Entity Type.

.................................................................................................................................................................................................................................

14-132 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-28: View reports

Remote NE alarm list

If the remote network element status feature is enabled, the Remote NE Alarm List shows the highest alarm/status level for each network element in the alarm group. The

Reports

→

Remote NE Alarm List

command is used to obtain an Remote NE Alarm

List.

VT XC Fabric utilization

VT XC Fabric Utilization shows the VT cross-connect fabric utilization for the main and function packs on the shelf. The

Reports

→

VT XC Fabric Utilization

command is used to obtain a VT XC Fabric Utilization report.

Backplane bandwidth utilization

Backplane Bandwidth Utilization shows the backplane utilization for STS and VT cross-connections for any function packs on the shelf. The

Reports

→

Backplane

Bandwidth Utilization

command is used to obtain a Backplane Bandwidth Utilization report.

NE history log

The NE History Log shows the start and end of alarm and status conditions and all

CIT/OS activities that affect the state of the network element. This includes autonomous events such as alarms, protection switching, maintenance conditions, and network element status changes. The

Reports

→

NE History Log

command is used to obtain an NE History Log.

The network element stores up to 12,000 of the most recent events. All entries or only entries for a specified time interval may be retrieved.

NE security log

The NE Security Log shows all TL1 provisioning commands and security-related events. For example, user authentication attempts, attempts to access resources, user security changes, network element security changes, and system resets are shown. The

Reports

→

NE Security Log

command is used to obtain an NE Security Log.

The network element stores up to 10,000 of the most recent events. All entries or only entries for a specified time interval may be retrieved.

MAC address list

The MAC address list displays the source and destination addresses (stored in the

MAC address table) of data packets. Persistent and Filtered MAC addresses are entered manually via the

Configuration

→

Data

→

Create MAC Address

command and

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-133

Supporting procedures Procedure 14-28: View reports

Dynamic MAC addresses are learned when a packet enters the switch. The

Reports

→

MAC Address List

command is used to obtain the MAC Address List.

The MAC Address List may be filtered by VLAN/Port Tag ID, MAC Address, and/or

Address Type (Persistent, Filtered, Dynamic, or All).

GbE line utilization

The GbE line utilization report shows how much data bandwidth has been used per

Ethernet and VCG port. The information generated for the report is based on performance monitoring data. The

Reports

→

GbE Line Utilization

command is used to obtain a GbE Line Utilization report.

.................................................................................................................................................................................................................................

14-134 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures

Procedure 14-29: Clean optical pluggable transmission module

.................................................................................................................................................................................................................................

Overview

This procedure describes the Lucent recommended method for cleaning uninstalled optical pluggable transmission modules using specific tools and materials that have been proven to be effective in the assembly and testing of optical transmission equipment.

Important! Pluggable transmission modules are shipped with a dust plug installed into the optical ports to maintain cleanliness during storage and/or transportation. It is recommended that the dust plug be kept in place to maintain cleanliness until the optical fiber is connected. With proper care and handling, cleaning the pluggable transmission modules should not be necessary.

Because a major source of contamination is often a contaminated mating connector, it is extremely important to clean the connector ferrule end surface each time before making connections. To clean the connector ferrule end surface, refer to

Procedure 14-3: “Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs)” (p. 14-34) .

Required equipment

The following equipment is required to perform this procedure.

•

CLETOP stick cleaner (1.25 mm for LC connectors)

•

Canned dry nitrogen or air (electronics grade)

•

Stereo zoom scope with coaxial illumination (200x)

Before you begin

Prior to performing this procedure, refer to

“Laser safety” (p. 1-6)

and

“Electrostatic discharge” (p. 1-14)

in

Chapter 1, “Safety” .

Step

1

Complete the following steps to clean an optical pluggable transmission module.

.................................................................................................................................................................................................

Remove the protective dust plug from the pluggable transmission module. Keep the dust plug clean until reinstalled later, if required.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-135

Supporting procedures Procedure 14-29: Clean optical pluggable transmission module

2

.................................................................................................................................................................................................

CAUTION

Corrosive substance hazard

If the canned dry nitrogen or air is held upside down, inert gas may be released onto the connector surface. The inert gas leaves contamination on the connector surface that cannot be removed.

When performing this step hold the canned dry nitrogen or air upright.

3

4

While holding the canned dry nitrogen or air, position the tip of the nozzle extension as close as possible, but not close enough to make physical contact, to the sleeve inside the port receptacle and make three consecutive short blows (approximately one second each).

Repeat this step for the other port.

.................................................................................................................................................................................................

Using the stereo zoom scope, visually inspect the pluggable transmission module. If required, repeat

Step 2

up to two more times then go to the next step.

.................................................................................................................................................................................................

CAUTION

Equipment damage

Do not perform this step on the receive (RX) port. The receive (RX) port contains a lens for focusing a wide input. The lens is more easily scratched than cleaned.

This step should only be performed on the transmit (TX) port if the air blows did not work.

5

6

If required, insert a CLETOP stick into the transmit (TX) port sleeve until vertical force can be applied to the fiber stub end surface. Rotate the CLETOP stick five full rounds.

.................................................................................................................................................................................................

Using the stereo zoom scope, visually inspect the pluggable transmission module. If required, repeat

Step 4 .

.................................................................................................................................................................................................

Important! It is recommended that the dust plug be installed into the optical ports on the pluggable transmission module to maintain cleanliness until the optical fiber is connected.

.................................................................................................................................................................................................................................

14-136 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-29: Clean optical pluggable transmission module

If required, reinstall the dust plug into the optical ports to maintain cleanliness.

E

N D O F

S

T E P S

........................................................................................................................................................................................................................

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-137

Supporting procedures

Procedure 14-30: Connect modems to establish communication from remote CIT location

.................................................................................................................................................................................................................................

Overview

Use this procedure to connect modems and a Personal Computer (PC) to the

Metropolis

®

DMX for use in provisioning the system from a remote location.

This procedure is used only for modem access. For local access or access directly through a WAN or LAN network, refer to

Procedure 14-2: “Connect Personal

Computer (PC) and establish WaveStar

®

CIT session” (p. 14-24) .

This procedure presents two configurations:

•

Dial-up networking to a TCP/IP LAN/WAN network. See example in

Figure 14-19,

“Dial-Up networking to TCP/IP LAN/WAN network” (p. 14-143) .

This configuration could be a dial-up networking connection to a corporate

LAN/WAN network or an Internet connection using VPN tunneling to a corporate network. Once the connection to the TCP/IP LAN network is made, the connection to the network element is the same as being locally connected to the NE LAN port and using a TCP/IP connection type.

•

Modem-to-Modem connection. See example in

Figure 14-20, “Modem-to-Modem connection” (p. 14-143) .

The NE can be accessed remotely via dialup modems to the NE’s modem serial port, but not by the WaveStar

®

CIT software.

A PC with a terminal emulation software package, such as HyperTerminal, can be used for access to the modem serial port via dialup modems. The PC can use its internal modem or an external modem (as shown). This form of access supports

TL1 messages only, and can be used to access remote NEs with DCC connectivity to the NE with the modem connection.

Privilege level

You must login as a Privileged user to complete this procedure.

Before you begin

Refer to

“Before you begin” (p. 14-3)

and

“Required equipment” (p. 14-3)

in this chapter.

Ensure that the descriptions and syntax of the various features and parameters of the

Metropolis

®

DMX that may be set using the PC with the WaveStar

®

CIT program installed are understood prior to starting this procedure.

.................................................................................................................................................................................................................................

14-138 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-30: Connect modems to establish communication from remote CIT location

Ensure that the proper modem cable is available. Use the following table to determine the correct assembly:

Table 14-1 Modem cable assembly and pin connections

Description Cable Assembly # Cable Length

Modem Cable

Metropolis

®

DMX

Connections

J17 848756508

848756524

848756516

848756532

50 ft.

100 ft.

150 ft.

250 ft.

Connection

Modem Cable

J17

3

5

1

2

RJ-45 Connector

Pin #

6

Color

White-Orange

Brown

White-Black

Orange (and

Shielding)

Green

DB25 Connector

Pin #

3

7

8

20

2

Review the following generic parameters to be set for the modem(s):

•

1200, 2400, 4800, 9600, or 19,200 baud (9600 is the default and recommended

rate)

•

Full duplex

•

8 data bits

•

No parity bits

•

1 start bit

•

1 stop bit

•

No flow control

•

Transparent data mode - ON (Required for software download on some modems.)

•

Direct operating mode - ON (Required for software download on some modems.)

Important! Modems supporting a large set of options and error detection capabilities may require other options to be set before using the modems to download generic software. Refer to manufacture’s manuals for instructions on setting modem parameters.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-139

Supporting procedures

Step

Procedure 14-30: Connect modems to establish communication from remote CIT location

1

Complete the following steps to connect the modem(s) and establish communication from a remote WaveStar

®

CIT location.

.................................................................................................................................................................................................

At the Metropolis

®

DMX, is the connection being made through a direct modem-to-modem connection, or through dial-up networking using a TCP/IP LAN network?

If...

using dial-up networking to a

TCP/IP LAN network, using a modem-to-modem connection,

Then...

Continue with

Step 2 .

Proceed to

Step 9 .

2

3

4

5

6

.................................................................................................................................................................................................

At the Metropolis

®

DMX Location

Verify your network administrator has set up the TCP/IP network. Verify that a LAN port at the Metropolis

®

DMX is provisioned to accept TCP/IP connections and you know the IP address of your NE.

Reference:

Procedure 7-15: “Provision TCP/IP and Proxy ARP on an IAO LAN port” (p. 7-46)

.................................................................................................................................................................................................

At the Remote WaveStar

®

CIT Location

Ensure the modem parameters are set correctly. Refer to manufacturer’s manual for instructions on setting modem parameters.

.................................................................................................................................................................................................

If an external modem is being used at the remote WaveStar

®

CIT location, connect the modem to the WaveStar

®

CIT PC using the appropriate modem cable.

.................................................................................................................................................................................................

Verify the telephone line is plugged into the modem.

.................................................................................................................................................................................................

Refer to your local procedures for using dial-up networking to set up and establish a dial-up connection to your TCP/IP LAN network.

.................................................................................................................................................................................................................................

14-140 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-30: Connect modems to establish communication from remote CIT location

7

8

9

10

11

12

.................................................................................................................................................................................................

After you have connected to your TCP/IP LAN network, establish a WaveStar

®

session to the Metropolis

®

DMX the same way you would if you were locally

CIT connected to the

LAN

port and using a TCP/IP connection type.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

.................................................................................................................................................................................................

STOP! End of Procedure.

.................................................................................................................................................................................................

At the Metropolis

®

DMX Location, Modem-to-Modem Connection

Connect a PC to the modem. Use the PC communications software to set the generic modem parameters specified in the

“Before you begin” (p. 14-138)

section of this procedure. Set the modem to answer incoming calls.

Enter the following AT commands:

•

AT&D0 - tells modem to ignore DTR signal.

•

ATE0 - disables local command echo on the modem.

Important! The above AT commands are important and are standard from modem to modem. These AT commands may need to be set using DIP switches on your modem. Refer to modem’s owner manual for instructions.

For PC communications software such as HyperTerminal, “Echo typed characters locally” needs to be enabled since local command echo was disabled on the modem. For HyperTerminal, go to File

→

Properties

→

Settings

→

ASCII Setup.

.................................................................................................................................................................................................

Connect the modem to the rear WaveStar

®

CIT interface (CIT-2 [J17]) on the

Metropolis

®

DMX shelf using the proper Metropolis

®

DMX modem cable.

.................................................................................................................................................................................................

Plug the telephone line into the modem.

.................................................................................................................................................................................................

If not already performed, establish a WaveStar

®

CIT session with the Metropolis

®

DMX shelf.

Reference:

Procedure 14-2: “Connect Personal Computer (PC) and establish

WaveStar

®

CIT session” (p. 14-24)

13

.................................................................................................................................................................................................

From the System View menu, select

Administration

→

Data Communications

. Click on the

Serial Port

tab, set the options of the

CIT Port (cit-2)

serial port. Be sure to set

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-141

Supporting procedures Procedure 14-30: Connect modems to establish communication from remote CIT location

14

15

16

17

18

19

Echo Mode

to

Disable

. Click

Apply

, read the warning message, then click

Yes

to execute the command. Click

Close

to exit.

The Metropolis

®

DMX shelf has a default setting of 9600 baud for the serial port. If the modem is set for another baud rate (1200, 2400, 4800, or 19200), set the serial port baud rate to match that of the modem.

Reference:

Procedure 7-18: “Provision RS232 CIT (CIT-1) and/or MODEM

(CIT-2) serial port parameters” (p. 7-54)

.................................................................................................................................................................................................

At the Remote PC Location, Modem-to-Modem Connection

Use the PC communications software to set the generic modem parameters specified in the

“Before you begin” (p. 14-138)

section of this procedure. Refer to manufacture’s manual for instructions on setting modem parameters.

Enter the following AT commands:

•

AT&D2 - indicates the DTE controls DTR signal.

•

ATE0 - disables local command echo on the modem.

Important! The above AT commands are important and are standard from modem to modem. These AT commands may need to be set using DIP switches on your modem. Refer to modem’s owner manual for instructions.

.................................................................................................................................................................................................

If an external modem is being used at the remote PC location, connect the modem to the PC using the appropriate modem cable.

.................................................................................................................................................................................................

Verify the telephone line is plugged into the modem.

.................................................................................................................................................................................................

Refer to the PC and modem documentation, or use HyperTerminal, to establish a connection (place a call) to the modem at the Metropolis

®

DMX.

.................................................................................................................................................................................................

Once the modem at the Metropolis

®

DMX has answered, hit the Enter key twice and the TID of the NE should be displayed. Use TL1 commands to access the system.

Reference:

365-372-306

Metropolis

®

DMX Access Multiplexer TL1 Message Details,

.................................................................................................................................................................................................

STOP! End of Procedure.

E

N D O F

S

T E P S

.................................................................................................................................................................................................................................

14-142 365-372-301 R6.0

Issue 15, January 2006

Supporting procedures Procedure 14-30: Connect modems to establish communication from remote CIT location

Figure 14-19 Dial-Up networking to TCP/IP LAN/WAN network

Wave Star

CIT

®

Modem

Cable

External

Modem

Telephone

Line

TCP/IP Network

Rear IAO

LAN Port (J16)

Metropolis

DMX

®

10/100BaseT Ethernet

LAN Hub

TCP/IP

Rear IAO

LAN Port (J17)

Metropolis

DMX

tend

®

Front SYSCTL

LAN Port

Metropolis

DMX

plore

®

DMX = Metropolis DMX Access Multiplexer

DMX

DMX

plore tend

= Metropolis DMX

plore tend

Access Multiplexer

Access Multiplexer

MA-DMX-415

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

14-143

Supporting procedures

Figure 14-20 Modem-to-Modem connection

DTE

WaveStar

®

CIT PC

Echo = enabled

DCE

Modem

AT (attention) Commands:

–

–

DTE Data Terminal Equipment

DCE Data Communications Equipment

Procedure 14-30: Connect modems to establish communication from remote CIT location

Public

Switched

Telephone

Network

(PSTN)

DTE

Metropolis on CIT-2

DMX

J17 (CIT2)

Rear DTE Ready

Rear DCE Ready

Rear Received Data

Rear Transmitted Data

®

J17

(CIT-2)

Command Echo Disabled

3

4

1

2

7

8

5

6

RJ45

RDTR

RS232N

RRXD

GRD

RTXD

DCE

Modem

AT (attention) Commands:

–

–

Modem

RS-232 (DB25)

8

20

3

DCD

DTR

RD

Shielding

7

2 TD

Data Carrier Detect

Data Terminal Ready

Receive Data

Transmit Data

MA-DMX-406

.................................................................................................................................................................................................................................

14-144 365-372-301 R6.0

Issue 15, January 2006

Appendix A: Provisionable parameters

Overview

.................................................................................................................................................................................................................................

Purpose

This appendix identifies the provisionable parameters and the user settable values. The tables in this appendix include the TL1 commands and related WaveStar

®

CIT commands associated with each activity. For detailed information about TL1 commands refer to the Metropolis

®

DMX Access Multiplexer TL1 Message Details,

365-372-306.

Contents

Port parameters

Channel parameters

Ethernet parameters

Data parameters

Cross-Connection parameters

Synchronization parameters

Performance monitoring parameters

Operations parameters

Security parameters

Miscellaneous parameters

A-2

A-6

A-7

A-24

A-26

A-28

A-30

A-31

A-41

A-45

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-1

Provisionable parameters

Port parameters

.................................................................................................................................................................................................................................

The following table shows the provisionable port parameters.

Parameter

BPV to All Zeroes

Translation on Incoming

DS1 (bpv)

1,2

Table A-1 Port parameters

TL1

Commands

(Access)

(Note)

ENT-T1

(P, G)

Range

N,Y

SF, ESF, ESFN, UF DS1 Incoming Signal

Format (fmt)

DS1 Line Code

(linecde)

1

DS1 Line Buildout

(lbo)

1

AMI, B8ZS

20 (0-133 ft.),

40 (133-267 ft.),

60 (267-420 ft.),

80 (420-550 ft.),

100 (550-655 ft.)

E1, DS1 Interface Type (intftype)

ED-EQPT

(P, G)

E1 Signal Format (fmt)

ENT-E1

DS3 AIS

(P, G)

ENT-T3

DS3/EC1 Mode (eif)

(P, G)

ENT-T3

ENT-EC1

(P, G)

FAS, CRC4

Y, N

Applies to LNW8 only.

DS3, EC1

Default Related

WaveStar

®

CIT

Commands

N

ESF

AMI

20

CRC4

N

DS3

Configuration

→

Equipment

.................................................................................................................................................................................................................................

A-2 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters

Parameter

(linecde)

Table A-1 Port parameters (continued)

Line Buildout (lbo)

DS3 Line Coding

DS3 Frame Format

(frame)

TL1

Commands

(Access)

(Note)

ENT-EC1

ENT-T3

(P, G)

ENT-T3

(P, G)

Range

728A/B Cable:

IN (0-225),

OUT (225-450)

735A Cable:

IN (0-112),

OUT (112-225)

B3ZS, CCHAN

1

M13, CBIT, CCHAN

1

ON, OFF P-bit Violation Removal

(pbit)

DS3 Incoming Signal

Format (fmt)

PBIT, FMBIT, CPBIT

TCA Monitoring Mode

(tcamd)

Alarm Severity

Assignment Profile

(pfname)

ENT-E1

ENT-T1

ENT-T3

ENT-EC1

ENT-OC3

ENT-OC12

ENT-OC48

ENT-OC192

(P, G)

ENT-ASAP-

ASGNMT

(P, G)

ENABLE, DISABLE

DEFAULT ASAP

User-Created ASAP

Port parameters

Default Related

WaveStar

®

Commands

CIT

IN

Configuration

→

Equipment

B3ZS

M13

ON

PBIT

ENABLE

Performance

→

Prov PM Settings

DEFAULT

ASAP

Configuration

→

Equipment

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-3

Provisionable parameters

Parameter

Table A-1 Port parameters (continued)

Signal Degrade

Threshold (sfthr)

Primary State (pst)

Signal Degrade

Threshold (sfthr)

Signal Fail Threshold

(sfail)

Primary State (pst)

(low-speed slots)

PJC Monitor Point

(pjcmon)

TL1

Commands

(Access)

(Note)

ENT-E1

ENT-T1

ENT-T3

ENT-EC1

(P, G)

ENT-E1

ENT-T1

ENT-T3

ENT-EC1

(P, G)

ENT-OC3

ENT-OC12

ENT-OC48

ENT-OC192

(P, G)

ENT-OC3

ENT-OC12

ENT-OC48

ENT-OC192

(P, G)

ENT-OC3

ENT-OC12

ENT-OC48

(P, G)

ENT-OC3

ENT-OC12

ENT-OC48

ENT-OC192

(P, G)

Range

-3, -6, -7, -8

-3, -6, -7, -8

-4, -6

-3, -5, -6, -7, -8, -9

OOS-MA-AS (AUTO),

OOS (NMON)

-5, -6, -7, -8, -9

-3, -4, -5

OOS (NMON)

OOS-MA-AS (AUTO)

N (number of STSn tributary),

AUTO

AUTO-NO-TCA

Port parameters

Default Related

WaveStar

®

Commands

CIT

-3

-3

-6

-6

AUTO

-6

-3

Configuration

→

Equipment

AUTO

Configuration

→

Equipment

AUTO-

NO-TCA

Performance

→

Prov PM Settings

.................................................................................................................................................................................................................................

A-4 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters Port parameters

Parameter

(application)

(application)

(wlsel)

3 only)

Table A-1 Port parameters (continued)

Transmission Protection

(low-speed slots)

Transmission Protection

(high-speed slots)

Wavelength Selection

SS Bits (ssbits) (low speed OCn circuit packs

TL1

Commands

(Access)

(Note)

ENT-OC3

ENT-OC12

ENT-OC48

(P, G)

ENT-OC12

ENT-OC48

ENT-OC192

(P, G)

ENT-OC192

(P, G)

ED-EQPT

(P, G)

Range

0x1S1, 0x1S2, 1+1,

1+1_OPTM, 1+1_BIDIR,

UPSR,

2F (OC-48 ports only)

UPSR, 1+1, 1+1_OPTM,

1+1_BIDIR

2F (OC-48 and OC-192 ports only)

CH1, CH2, CH3, CH4

SS00, SS10

Default Related

1+1

UPSR

CH3

SS00

WaveStar

®

Commands

CIT

Configuration

→

Equipment

Socket Maintenance

State (mst) (pluggable transmission modules only)

Normal, Maintenance Normal

1

Does not apply to the TMUX circuit pack.

2

Does not apply to the LNW8 56DS1/E1 circuit pack.

3

Applies to the LNW523, LNW527, and LNW554 OC-192 OLIU circuit packs only.

Note: The TL1 command security access levels are Privileged (P), Administration (A), General (G),

Maintenance (M), and Reports-only (R).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-5

Provisionable parameters

Channel parameters

.................................................................................................................................................................................................................................

The following table shows the provisionable channel parameters.

Parameter

(tcamd)

Table A-2 Channel parameters

Primary State (pst)

TCA Monitoring Mode

Signal Degrade

Threshold (sfthr)

Signal Fail Threshold

(sfail)

Alarm Severity

Assignment Profile

(pfname)

TL1

Commands

(Access)

(Note)

ENT-STS1

ENT-STS3c

ENT-STS12c

ENT-STS48c

ENT-VT1

ENT-VC12

(P, G)

ENT-STS1

ENT-STS3c

ENT-STS12c

ENT-STS48c

ENT-VT1

ENT-VC12

(P, G)

ENT-STS1

ENT-STS3c

ENT-STS12c

ENT-STS48c

(P, G)

ENT-VT1

(P, G)

ENT-STS1

ENT-STS3c

ENT-STS12c

ENT-STS48c

(P, G)

ENT-ASAP-

ASGNMT

(P, G)

Range

OOS-MA-AS (AUTO),

OOS (NMON)

ENABLE, DISABLE

-5, -6, -7, -8, -9

-5, -6, -7, -8

-3, -4, -5

DEFAULT ASAP

User-Created ASAP

Default

NMON

ENABLE

-6

-6

-3

DEFAULT

ASAP

Related

WaveStar

®

Commands

CIT

Configuration

→

Equipment

Performance

→

Prov PM Settings

Configuration

→

Equipment

Note: The TL1 command security access levels are Privileged (P), Administration (A), General (G),

Maintenance (M), and Reports-only (R).

.................................................................................................................................................................................................................................

A-6 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters

Ethernet parameters

.................................................................................................................................................................................................................................

The following table shows the provisionable Ethernet parameters.

Parameter

Port Type

(porttype)

Table A-3 Ethernet parameters

TL1

Commands

(Access)

(Note)

ED-EPORT

(P, G)

Range

Boundary, Interior half, full, auto

Default

Boundary auto

Related

WaveStar

®

Commands

CIT

Configuration

→

Data

→

Provision

QoS Service

Configuration

→

Equipment

Duplex Mode

(dplxmd)

Ethernet Port

Monitoring Mode

(epmode)

Ethernet Port PM

Enabled (eppm)

Flow Control

Mode (fcmd)

Line Rate (lnrate)

Default Port Tag

(dftporttag)

Default Priority

(dftpri)

ED-EPORT

(P, G) auto, nmon enable, disable enable, disable, auto, drop auto

10m, 100m, auto

1 - 4093 or 0 auto enable auto

0

Performance

→

Prov PM Settings

Configuration

→

Equipment

Alarm Severity

Assignment Profile

(pfname)

Tag Filter

(tagfilter)

Add Port Tag ID

(addporttag)

Delete Port Tag ID

(delporttag)

ENT-ASAP-

ASGNMT

(P, G)

ED-EPORT

(P, G)

NA, high, low

LNW70: 0 - 3, NA

LNW78: 1 - 3

DEFAULT ASAP

User-Created ASAP

Enable, Disable

4

1 - 4093 (Up to 55 Port

Tag IDs in a single command)

1 - 4093

NA

0

1

DEFAULT

ASAP

Enable

None

None

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-7

Provisionable parameters

Parameter

Remote Client Fail

(rcf)

Table A-3 Ethernet parameters (continued)

TL1

Commands

(Access)

(Note)

ED-EPORT

(P, G)

Range

enable, disable

Remote Client Fail

Link Shutdown

(rcf_linkdown) enable, disable

Port Admin

Control (admin)

TCA Monitoring

Mode (tcamd)

ED-EPORT

(P, G) enable, disable enable, disable

Jumbo Frame

Support (jumbo)

MTU (Maximum

Transmission Unit)

Size (mtu_size) enable, disable

LNW63: 46 - 12222

LNW70:46 - 10222

LNW74: 1500 - 10222

LNW78: 46 - 10222 enable, disable Auto-Negotiation

(autoneg)

Crossover (mdix)

Ethernet Type

Field (ethertype)

Network Port AF

Queue Weighting

Factor

(qwt_ntwkAF)

ED-EPORT

(P, G) auto, mdix, mdi

0601 to FFFF

(hexadecimal)

1 - 100

Customer Port AF

Queue Weighting

Factor

(qwt_custAF)

Total Queue Size

(qsz)

1 - 100

0 - 256

Default

disable enable enable disable enable

1508 enable auto

FFFF

64

36

256

Ethernet parameters

Related

WaveStar

®

Commands

CIT

Configuration

→

Equipment

Performance

→

Prov Settings

Configuration

→

Equipment

Configuration

→

Equipment

.................................................................................................................................................................................................................................

A-8 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters

Parameter

Yellow Packet Min

Drop Threshold

(qminthldy)

Table A-3 Ethernet parameters (continued)

TL1

Commands

(Access)

(Note)

ED-EPORT

(P, G)

Range

0 - 100

0 - 100 Yellow Packet Max

Drop Threshold

(qmaxthldy)

Green Packet Min

Drop Threshold

(qminthldg)

0 - 100

0 - 100 CoS 0 Packets

Drop Probability

Mark (qdropwt0)

CoS 1 Packets

Drop Probability

Mark (qdropwt1)

CoS 2 Packets

Drop Probability

Mark (qdropwt2)

CoS 3 Packets

Drop Probability

Mark (qdropwt3)

ED-EPORT

(P, G)

0 - 100

0 - 100

0 - 100

Broadcast and

Multicast Rate

Limit (bcratelimit)

Traffic

Management Mode

(trafmgmtmd)

Higher Layer Class of Service

(hlayercos)

(LNW70 only)

ED-EPORT

(P, G)

0 - 1000000

NOTC, PORT, TAGPORT,

COSPORT,

COSTAGPORT

None, DSCP

Default

23

50

90

100

100

100

50

0

PORT

None

Ethernet parameters

Related

WaveStar

®

Commands

CIT

Configuration

→

Equipment

Configuration

→

Equipment

Configuration

→

Data

→

Provision

QoS Service

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-9

Provisionable parameters

Parameter

Spanning Tree Port

Priority (stpp)

Table A-3 Ethernet parameters (continued)

TL1

Commands

(Access)

(Note)

ED-EPORT

(P, G)

Range

0 - 255

(LNW70 only)

1 - 65535 Spanning Tree

Path Cost (stpcost)

(LNW70 only)

Spanning Tree

Hello Timer

(sthellotm)

(LNW70 only)

1 - 10 seconds enable, disable Ethernet Port

Spanning Tree

Status (epss)

(LNW70 only)

Spanning Tree

VLAN ID (stvid)

(LNW70 only)

Ethernet Frame

Check Sequence

Mode (ethfcs)

(LNW63 only)

0 - 4095 enable, disable

Default

128

65535

2 enable

4095 enable

Ethernet parameters

Related

WaveStar

®

Commands

CIT

Configuration

→

Equipment

.................................................................................................................................................................................................................................

A-10 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters

Parameter

Table A-3 Ethernet parameters (continued)

Spanning Tree

Group ID (stgrpid)

Virtual Switch ID

(vrtswid)

TL1

Commands

(Access)

(Note)

ENT-STGRP

ED-STGRP

(P, G)

Range

1-4095

1-4095

LNW70: 1-16

Spanning Tree

Root Priority (strp)

Spanning Tree

Max Age Timer

(stmaxage)

0 - 65535

6-255

4-255 Spanning Tree forward delay timer (stfdtm)

VCG AID List

(vcglist)

Ethernet Port AID

List (eplist)

Port Type

(porttype)

ED-VCG

(P, G)

An ampersand-separated list of VCG AIDs.

An ampersand-separated list of Ethernet port AIDs.

Boundry, Interior

Default

None

None

32768

255

15

None

None

Interior

Spanning tree port priority (stpp)

VCG Monitoring

Mode (vmode)

Alarm Severity

Assignment Profile

(pfname)

ENT-ASAP-

ASGNMT

(P, G)

0-255 auto, nmon

DEFAULT ASAP

User-Created ASAP

128 auto

DEFAULT

ASAP

Ethernet parameters

Related

WaveStar

®

Commands

CIT

Configuration

→

Data

→

Create

Spanning Tree

Group

Configuration

→

Ethernet Service

Configuration

→

Data

→

Provision

QoS Service

Configuration

→

Equipment

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-11

Provisionable parameters

Parameter

VCG PM Enable

(vpm)

Table A-3 Ethernet parameters (continued)

TL1

Commands

(Access)

(Note)

ED-VCG

(P, G)

Range

enable, disable

TCA Monitoring

Mode (tcamd)

ENABLE, DISABLE

Spanning Tree

Path Cost (stpcost)

Spanning Tree

Hello Timer

(sthellotm)

1 - 65535

1 - 10 seconds

0 - 4095 Spanning Tree

VLAN ID (stvid)

VCG Spanning

Tree Status (vss)

Default Priority

(dftpri)

Default Port Tag

(dftporttag) enable, disable

0-3, NA

1-4093 or 0

Ampersand separated list

(1-4093)

Ampersand separated list

(1-4093)

Valid Port Tag Add

List (addporttag)

Valid Port Tag

Delete list

(delporttag)

Pause control

(psctl)

Tag Filter

(tagfilter)

MTU (Maximum

Transmission Unit)

Size (mtu_size)

Ethernet Type

Field (ethertype)

Transparent, Local, None

Enable, Disable

46 - 10222

0601 to FFFF

(hexadecimal)

Default

enable

DISABLE

10

2

4095 enable

0

0

None

None

Local

Enable

1508

FFFF

Ethernet parameters

Related

WaveStar

®

Commands

CIT

Performance

→

Prov PM Settings

Configuration

→

Equipment

.................................................................................................................................................................................................................................

A-12 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters

Parameter

Table A-3 Ethernet parameters (continued)

GFP Frame Check

Sequence (gpf_fcs)

TL1

Commands

(Access)

(Note)

ED-VCG

(P, G)

Range

enable, disable

LCAS Mode

(lcasmd) enable, disable

Hold-Off Timer

(htmr)

Wait-To-Restore

(wtr)

0 - 10000

0 - 3600 enable, disable Virtual

Concatenation

Mode (vcat)

Network Port AF

Queue Weighting

Factor

(qwt_ntwkAF)

Customer Port AF

Queue Weighting

Factor

(qwt_custAF)

Total Queue Size

(qsz)

ED-VCG

(P, G)

1 - 100

1 - 100

0 - 256

Yellow Packet Min

Drop Threshold

(qminthldy)

Yellow Packet Max

Drop Threshold

(qmaxthldy)

0 - 100

0 - 100

Default

disable enable

200

5 enable

64

36

256

23

50

Ethernet parameters

Related

WaveStar

®

Commands

CIT

Configuration

→

Equipment

Configuration

→

Equipment

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-13

Provisionable parameters

Parameter

Green Packet Min

Drop Threshold

(qminthldg)

Table A-3 Ethernet parameters (continued)

TL1

Commands

(Access)

(Note)

ED-VCG

(P, G)

Range

0 - 100

0 - 100 CoS 0 Packets

Drop Probability

Mark (qdropwt0)

CoS 1 Packets

Drop Probability

Mark (qdropwt1)

0 - 100

0 - 100 CoS 2 Packets

Drop Probability

Mark (qdropwt2)

CoS 3 Packets

Drop Probability

Mark (qdropwt3)

Traffic

Management Mode

(trafmgmtmd)

Broadcast and

Multicast Rate

Limit (bcratelimit)

Ethernet FCS

Mode (ethfcs)

ED-VCG

(P, G)

0 - 100

NOTC

0 - 1000000 enable, disable

Default

90

100

100

100

50

NOTC

0 enable

Ethernet parameters

Related

WaveStar

®

Commands

CIT

Configuration

→

Equipment

Configuration

→

Data

→

Provision

QoS Service

Configuration

→

Equipment

.................................................................................................................................................................................................................................

A-14 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters Ethernet parameters

Parameter

Tagging Mode

(vlantagmd)

Table A-3 Ethernet parameters (continued)

TL1

Commands

(Access)

(Note)

ED-EQPT

(P, G)

Range

802.1TAG, TRANS,

NOTAG, SWITCHED

2

Default

Burst (brst)

Credit Interval

(cint)

Ethernet

Cross-Connect

Mode (eccmode)

VT Virtual

Concatenation

(vt_vcat)

Ethernet Port

Mode (enetmd)

ED-EQPT

(P, G)

1-255

1-4095

(524.29 µsec-2.15 sec)

STS1, STS3C

3

, STS12C

0, 12

802.1TAG:

10/100-TX

NOTAG:

1000-SX/LX

SWITCHED:

LNW78 only

5

125

(65.5 msec)

STS1

0

GX_FX LNW70:

GX_FX, GT_FX, FT_FX

LNW78: GX_FX

LNW63:

GX

String of 12 hexadecimal characters

1 - 4093

GX

None

None

MAC Address

(mac)

VLAN or Port Tag

(tag)

Address Type

(type)

Ethernet

LAN/VCG Port

AID (portaid)

RPR MAC Address

(rpr_mac)

ENT-MAC

(P, G)

Persistent, Filtered valid Port AID required

LNW78: String of 12 hexadecimal characters

None

None

None

Related

WaveStar

®

Commands

CIT

Configuration

→

Equipment

Configuration

→

Ethernet Service

Configuration

→

Equipment

Configuration

→

Equipment

Configuration

→

Data

→

Create

MAC Address

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-15

Provisionable parameters

Parameter

Table A-3 Ethernet parameters (continued)

Virtual Switch ID

(vrtswid)

TL1

Commands

(Access)

(Note)

ENT-VRTSW

(P, G)

Range

1 - 4095

LNW70: 1-16

LNW78: 1-8

LAN port list

(eplst)

VCG port list

(vcglst)

Virtual LAN

Tagging Mode

(tagmd)

Composite list of

LAN ports to be added to virtual switch (addep)

ED-VRTSW

(P, G)

Ampersand separated list of port AIDs

Ampersand separated list of port AIDs

802.1TAG, TRANS

Ampersand separated list of port AIDs

Composite list of

VCG ports to be added to virtual switch (addvcg)

Composite list of

LAN ports to be deleted from virtual switch

(delep)

Composite list of

LAN ports to be deleted from virtual switch

(delvcg)

Ampersand separated list of port AIDs

Ampersand separated list of port AIDs

Ampersand separated list of port AIDs

Default

None

None

None

802.1TAG

None

None

None

None

Ethernet parameters

Related

WaveStar

®

Commands

CIT

Configuration

→

Data

→

Create

Virtual Switch

Configuration

→

Ethernet Service

Configuration

→

Data

→

Provision

Virtual Switch

.................................................................................................................................................................................................................................

A-16 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters

Parameter

VLAN ID (vlanid)

ENT-VLAN

Virtual Switch ID

(vrtswid)

Table A-3 Ethernet parameters (continued)

TL1

Commands

(Access)

(Note)

(P, G)

Range

1- 4093 range

1 - 4095

LNW70: 1-16

LNW78: 1-8

Ethernet/LAN port list (eplst)

VCG/WAN port list (vcglst)

Default

Ethernet/LAN port list (dfeplst)

Default VCG/WAN port list (dfvcglst)

ED-VLAN

(P, G)

Ampersand separated list of port AIDs

Ampersand separated list of port AIDs

Ampersand separated list of port AIDs

Ampersand separated list of port AIDs

Ampersand separated list of port AIDs

Composite list of

LAN ports to be added to as VLAN members (addep)

Composite list of

VCG ports to be added as VLAN members (addvcg)

Ampersand separated list of port AIDs

Composite list of

LAN ports to be added to as VLAN default ports

(adddfep)

Composite list of

VCG ports to be added as VLAN default ports

(adddfvcg)

Ampersand separated list of port AIDs

Ampersand separated list of port AIDs

Default

None

None

None

None

None

None

None

None

None

None

Ethernet parameters

Related

WaveStar

®

Commands

CIT

Configuration

→

Data

→

Create

VLAN

Configuration

→

Ethernet Service

Configuration

→

Data

→

Provision

VLAN

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-17

Provisionable parameters

Parameter

Table A-3 Ethernet parameters (continued)

Composite list of

LAN ports to be deleted as VLAN members (delep)

TL1

Commands

(Access)

(Note)

ED-VLAN

(P, G)

Range

Ampersand separated list of port AIDs

Ampersand separated list of port AIDs

Composite list of

VCG ports to be deleted as VLAN members (delvcg)

Composite list of

LAN ports to be deleted as VLAN default ports

(deldfep)

Composite list of

VCG ports to be deleted as VLAN default ports

(deldfvcg)

Ampersand separated list of port AIDs

Ampersand separated list of port AIDs

Input Membership

(source) (inmbs)

Output

Membership (sink)

(outmbs)

ED-VCGTRIB

(P, G) disable, enable disable, enable

Tag ID (tagid)

Class of Service

(cos)

ENT-ERATE

ED-ERATE

(P, G)

1-4093

0-3

LNW78: 1-3

Committed Burst

Rate (cbs)

1-1024

LNW78: 1-256

0 -1000 Committed

Information Rate

(cir)

Peak Burst Size

(pbs)

1-1024

LNW78: 1-256

Default

None

None

None

None disable disable

None

None

10

0

20

Ethernet parameters

Related

WaveStar

®

Commands

CIT

Configuration

→

Data

→

Provision

VLAN

Configuration

→

Equipment

Configuration

→

Data

→

Provision

QoS Service

.................................................................................................................................................................................................................................

A-18 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters Ethernet parameters

Parameter

Peak Information

Rate (pir)

QoS Performance

Monitoring

(qospm)

Table A-3 Ethernet parameters (continued)

TL1

Commands

(Access)

(Note)

ENT-ERATE

ED-ERATE

(P, G)

Range

0-1000 enable, disable

0-3 Default Class of

Service

(dftpri2cos)

User Priority Bit

(userpri2cos)

String of 8 characters using 0 and 1

Differentiated

Services Code

Point to CoS Level

(dscp2cos)

ENT-ERATE

ED-ERATE

(P, G)

Default

1000 enable

0

Related

WaveStar

®

Commands

CIT

Configuration

→

Data

→

Provision

QoS Service

An ampersand-separated list of integers between 0 and 64. A dash (-) between 2 integers is allowed and represents a range. The value 64 is used to classify non-DSCP traffic to a CoS.

CoS 0:

01100000

CoS 1:

10010000

CoS 2:

00001100

CoS 3:

00000011

Defaults based on

RFC2474,

RFC2597, and

RFC2598.

1

Configuration

→

Data

→

Provision

QoS Service

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-19

Provisionable parameters

Parameter

Enhanced Bridging

Mode

(enh_brdgmd)

Table A-3 Ethernet parameters (continued)

TL1

Commands

(Access)

(Note)

ED-RPR

(P, G)

Range

enable, disable

1-200 msec Attribute

Discovery Timer

(atd_tmr)

RPR Protection

Wait-to-Restore

(prot_wtr)

0-1440 seconds

1-20 msec RPR Protection

Fast Timer

(prot_fasttmr)

RPR Protection

Slow Timer

(prot_slowtmr)

RPR Protection

Keep Alive Timer

(prot_katmr)

Primary Transit

Queue Size

(ptqsize)

ED-RPR

(P, G)

1-200 msec

2-50 msec

2000-51200

Secondary Transit

Queue Size

(stqsize)

Secondary Transit

Queue Full

Threshold

(stqfullthr)

Topology Stability

Timer (tstab_tmr)

Fairness Ramp

Coefficient

(fair_ramp)

2000 - 4194304

2000 - 4194304

10-100

4-9

Default

enable

20

0

10

20

3

5000

1800000

1795000

40

6

Ethernet parameters

Related

WaveStar

®

Commands

CIT

Configuration

→

Equipment

Configuration

→

Equipment

.................................................................................................................................................................................................................................

A-20 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters

Parameter

Fairness Low Pass

Coefficient

(fair_lp)

Table A-3 Ethernet parameters (continued)

TL1

Commands

(Access)

(Note)

ED-RPR

(P, G)

Range

4-11

1-40 Fairness

Advertisement

Ratio (fair_advert)

Fairness STQ High

Threshold

(fair_stqhi)

0-1000

0-1000 Fairness STQ Low

Threshold

(fair_stqlo)

Fairness Aging

Coefficient

(air_agec)

Reserved Class A

Add Rate (rsv_a)

Reserved Class B

Add Rate (rsv_b)

VCG Monitoring

Mode (vmode)

Alarm Severity

Assignment Profile

(pfname)

ED-VCG-RPR

(P, G)

ENT-ASAP-

ASGNMT

(P, G)

0-4

0-1200 Mb/s

0-1200 Mb/s auto, nmon

DEFAULT ASAP

User-Created ASAP

Default

6

5

250

500

2

0

0 auto

DEFAULT

ASAP

Ethernet parameters

Related

WaveStar

®

Commands

CIT

Configuration

→

Equipment

Configuration

→

Equipment

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-21

Provisionable parameters

Parameter

VCG PM Enable

(vpm)

Table A-3 Ethernet parameters (continued)

TL1

Commands

(Access)

(Note)

ED-VCG-RPR

(P, G)

Range

enable, disable

RPR IF Monitoring

Mode (ifmode) auto, NMON

Valid Port Tag Add

List (addporttag)

Valid Port Tag

Delete list

(delporttag)

Ampersand separated list

(1-4093)

Ampersand separated list

(1-4093)

Enable Tag Filter

(tagfilter)

MTU (Maximum

Transmission Unit)

Size (mtu_size)

Ethernet Type

Field (ethertype)

Virtual

Concatenation

Mode (vcat)

46 - 10222

0601 to FFFF

(hexadecimal) enable, disable

Default

enable auto

None

None

Enable

1508

FFFF enable

Ethernet parameters

Related

WaveStar

®

Commands

CIT

Performance

→

Prov PM Settings

Configuration

→

Equipment

.................................................................................................................................................................................................................................

A-22 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters Ethernet parameters

Parameter

Total Queue Size

(qsz)

Table A-3 Ethernet parameters (continued)

TL1

Commands

(Access)

(Note)

ED-VCG-RPR

(P, G)

Range

0 - 256 Kbytes

Yellow Packet Min

Drop Threshold

(qminthldy)

0 - 100%

0 - 100% Yellow Packet Max

Drop Threshold

(qmaxthldy)

Green Packet Min

Drop Threshold

(qminthldg)

0 - 100%

Default

256

33

50

90

Related

WaveStar

®

Commands

CIT

Configuration

→

Equipment

CoS 1 Packets

Drop Probability

Mark (qdropwt1)

CoS 2 Packets

Drop Probability

Mark (qdropwt2)

CoS 3 Packets

Drop Probability

Mark (qdropwt3)

0 - 100%

0 - 100%

0 - 100%

100

100

50

Note: The TL1 command security access levels are Privileged (P), Administration (A), General (G),

Maintenance (M), and Reports-only (R).

1

The default values are:

•

CoS 0: 0-9&11&13&15&26&28&30&34&36&38&44&50&52&54&58&60&62

•

CoS 1: 16-25&27&29&31

•

CoS 2: 10&12&14&32&33&35&37&39&40&43&45&47&64

•

CoS 3: 46&48&49&51&53&55-57&59&61&63

2

LNW70 and LNW78 circuit packs only.

3

LNW71 circuit packs only.

4

Disable does not apply to LNW78 circuit packs.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-23

Provisionable parameters

Data parameters

.................................................................................................................................................................................................................................

The following table shows the provisionable Data parameters.

Parameter

Data Type

(datatype)

Port Admin

(pfname)

Data Port

(epmode)

Table A-4 Data parameters

Control (admin)

Alarm Severity

Assignment Profile

Monitoring Mode

TL1

Commands

(Access)

(Note)

ED-EQPT

(P, G)

ED-DPORT

(P, G)

ENT-ASAP-

ASGNMT

(P, G)

ED-DPORT

(P, G)

Range

FC-FICON

ESCON enable, disable

DEFAULT ASAP

User-Created ASAP auto, nmon

FC, FICON, ASYNC-FC GFP Encapsulation

Type (gfptype)

Line Rate (lnrate)

Remote Client Fail

(rcf)

1G, 2G enable, disable enable, disable Remote Client Fail

Link Shutdown

(rcf_linkdown)

TCA Monitoring

Mode (tcamd)

Data Port PM

Enable (eppm)

Synchronous Ping

Enable (sync_ping)

Data Compression

(compr) enable, disable enable, disable enable, disable enable, disable

Default

FC-FICON enable

DEFAULT

ASAP auto

FC

1G disable enable disable enable disable disable

Related

WaveStar

®

Commands

CIT

Configuration

→

Equipment

Configuration

→

Equipment

Performance

→

Prov PM Settings

Configuration

→

Equipment

.................................................................................................................................................................................................................................

A-24 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters Data parameters

Parameter

Table A-4 Data parameters (continued)

VCG Monitoring

Mode (vmode)

VCG PM (vpm)

TL1

Commands

(Access)

(Note)

ED-VCG-

Data

(P, G)

Range

auto, nmon enable, disable

Default

auto enable

Related

WaveStar

®

Commands

CIT

Configuration

→

Equipment

Performance

→

Prov PM Settings

Configuration

→

Equipment

LCAS Mode

(lcasmd)

Hold-Off Timer

(htmr) enable, disable

0 - 10000 disable

200

Wait-To-Restore

(wtr)

Virtual

Concatenation

Mode (vcat)

0 - 3600 enable, disable

5 enable

Input Membership

(source) (inmbs)

Output

Membership (sink)

(outmbs)

ED-VCGTRIB

(P, G) disable, enable disable, enable disable disable

Configuration

→

Equipment

Note: The TL1 command security access levels are Privileged (P), Administration (A), General (G),

Maintenance (M), and Reports-only (R).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-25

Provisionable parameters

Cross-Connection parameters

.................................................................................................................................................................................................................................

The following table shows the provisionable cross-connection parameters.

Parameter

Table A-5 Cross-Connection parameters

TL1 Commands

(Access) (Note)

Range

VT1.5

Cross-Connect Type

(cct)

STS-1

Cross-Connect Type

(cct)

STS-3c

Cross-Connect Type

(cct)

STS-12c

Cross-Connect Type

(cct)

STS-48c

Cross-Connect Type

(cct)

Location A (loca)*

Location Z (locz)*

VT Location A

(vtloca)*

VT-Accessed STS-1

(vtacc)

ENT-CRS-VT1

ED-CRS-VT1

ENT-ROLL-VT1

(P, G)

ENT-CRS-STS1

ED-CRS-STS1

ENT-ROLL-STS1

(P, G)

ENT-CRS-STS3c

ED-CRS-STS3c

ENT-ROLL-STS3c

(P, G)

ENT-CRS-STS12c

ED-CRS-STS12c

ENT-ROLL-STS12c

(P, G)

ENT-CRS-STS48c

ED-CRS-STS48c

ENT-ROLL-STS48c

(P, G)

ENT-CRS-rr

ED-CRS-rr

ENT-ROLL-rr

(P, G)

1way

1waypr

Source Node TID

Destination Node TID

VT Source Node TID

YES

Default Related

WaveStar

®

Commands

CIT

None

Configuration

→

Cross-

Connections

Configuration

→

Ethernet Service

None

None

None

None

.................................................................................................................................................................................................................................

A-26 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters Cross-Connection parameters

Parameter

(chappl)

Circuit ID

(circuitid)

Table A-5 Cross-Connection parameters (continued)

TL1 Commands

(Access) (Note)

Range

Channel Application

ENT-CRS-rr

ED-CRS-rr

ENT-ROLL-rr

(P, G)

UNSWITCHED up to 36 ASCII characters

0-255

Default Related

WaveStar

®

Commands

CIT

None

None

Configuration

→

Cross-

Connections

Configuration

→

Ethernet Service

0 Cross-Connection

Application (xcappl)

Cross-Connection

Number (xcnum)

Any 9-digit number 000000000

* In Release 3.1 and later releases, if automatic squelch map generation is enabled, Location A and

Location Z are not required.

Note: The TL1 command security access levels are Privileged (P), Administration (A), General (G),

Maintenance (M), and Reports-only (R).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-27

Provisionable parameters

Synchronization parameters

.................................................................................................................................................................................................................................

The following table shows the provisionable synchronization parameters.

Parameter

Table A-6 Synchronization parameters

AIS Threshold

Level (aisthres)

TL1

Commands

(Access)

(Note)

SET-SYNCN

(P)

Range

LEVEL7, LEVEL6,

LEVEL5, LEVEL4,

LEVEL3, LEVEL2

SF, ESF DS1 Signal Frame

Format for

MAIN-1 Timing

(ds1_liof) and

MAIN-2 Timing

(ds1_2iof)

DS1 Timing

Reference Input

Line Code for

REF-1 (ds1_1ilc) and REF-2

(ds2_lilc)

AMI, B8ZS

DS1 Sync Output

Equalizer Value for

MAIN-1 Pack

(ds1_1equ) and for

MAIN-2 Pack

(ds1_2equ)

Mode Switch

(mdsw)

Synchronization

Mode (syncnmod)

1249C cable: 20 (90 ft.),

40 (180 ft.), 60 (270 ft.),

80 (360 ft.), 100 (450 ft.)

613C Cable: 20 (133 ft.),

40 (267 ft.), 60 (400 ft.),

80 (533 ft.), 100 (655 ft.)

REVERTIVE

NONREVERTIVE

FRNG, EXT,

EXT_SYNCOUT

1

, LINE

1

,

LINE_SYNCOUT

1

Default

LEVEL6

SF

AMI

20

REVERTIVE

EXT

Related

WaveStar

®

Commands

CIT

Configuration

→

Timing/Sync

.................................................................................................................................................................................................................................

A-28 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters Synchronization parameters

Parameter

Reference

Switching Mode

(refswmod)

Table A-6 Synchronization parameters (continued)

TL1

Commands

(Access)

(Note)

SET-SYNCN

(P)

Range

Revertive-1, Revertive-2,

Nonrevertive

Default

Nonrevertive

Related

WaveStar

®

Commands

CIT

Configuration

Timing/Sync

→

Synchronization

Source (src)

SynchAutoreconfiguration (auto)

Sync Messaging

(syncmsg)

MAIN-1-1 MAIN-2-1

Enabled, Disabled

MAIN-1-1

Disabled

Alarm Severity

Assignment Profile

(pfname)

ENT-OC3

ENT-OC12

ENT-OC48

ENT-OC192

(P, G)

ENT-ASAP-

ASGNMT

(P, G)

Sbyte, disabled

DEFAULT ASAP

User-Created ASAP

Sbyte

DEFAULT

ASAP

Configuration

→

Equipment

Note: The TL1 command security access levels are Privileged (P), Administration (A), General (G),

Maintenance (M), and Reports-only (R).

1

Does not apply to the LNW80 Switch circuit pack.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-29

Provisionable parameters

Performance monitoring parameters

.................................................................................................................................................................................................................................

The following table shows the provisionable performance monitoring parameters.

Table A-7 Performance monitoring parameters

Parameter

Monitored

Type

(montype)

Threshold

Level (thlev)

Location (locn)

Direction

(dirn)

Time period

(tmper)

TL1

Commands

(Access)

(Note)

SET-TH-E1

SET-TH-VC12

SET-TH-T1

SET-TH-T3

SET-TH-VT1

SET-TH-STS1

SET-TH-STS3c

SET-TH-STS12c

SET-TH-STS48c

SET-TH-EC1

SET-TH-OC3

SET-TH-OC12

SET-TH-OC48

SET-TH-OC192

SET-TH-FE

SET-TH-1GE

SET-TH-DATA

Range

FEND

1

, NEND

NULL, NA

15-MIN, 1-DAY, NONE

Default

NEND

NA

NA

Related

WaveStar

®

Commands

CIT

Performance

→

Prov Near-End

PM Threshold

Performance

→

Prov Far-End

PM Threshold

Format (fmt)

(P, G, M)

SET-TH-T1

SF, ESF ESF

(P, G, M)

SET-TH-T3

PBIT, FMBIT, CPBIT PBIT

(P, G, M)

Note: The TL1 command security access levels are Privileged (P), Administration (A), General (G),

Maintenance (M), and Reports-only (R).

1

Far End (FEND) does not apply to Fast Ethernet, Gigabit Ethernet, and Data interfaces.

.................................................................................................................................................................................................................................

A-30 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters

Operations parameters

.................................................................................................................................................................................................................................

The following table shows the provisionable operations parameters.

Parameter

Date

Time

Table A-8 Operations parameters

TL1

Commands

(Access)

(Note)

ED-DAT

(P)

Range

YY-MM-DD (00-01-01 —

99-12-31)

NE’s DCC Side

ENT-FECOM

(P)

HH-MM-SS (00-00-00 —

23-59-59)

NS (network side),

US (user side)

Default

70-01-01

00:00:00

Related

WaveStar

®

Commands

CIT

Administration

→

Set Date and Time

OSI

Communication

(com)

LAN Reset enabled, disabled lan-1, lan-2

(function of slot, dcc

AID and protection mode) enabled-front disabled-rear

Configuration

→

DCC Terminations

lan-1

IP Address of the

System (ipaddr)

ENT-ULS

(P)

None

Administration

→

Reset IAO LAN

Administration

→

Data

Communications

IP Default Router

Address (ipdrad)

IP Subnet Mask for IAO LAN

Ports (ipsnmk)

TCP/IP communication over the specified

IAO LAN port or

DCC port (tcpip)

Proxy ARP

(proxyarp)

ENT-ULS

(P)

32-bit IP address; 4 dot-separated decimal numbers from 0-255

32-bit IP address; 4 dot-separated decimal numbers from 0-255

32-bit IP address; 4 dot-separated decimal numbers from 0-255

Enabled, disabled

Enabled, Disabled

None

None disabled

Disabled

Administration

→

Data

Communications

Configuration

→

DCC Terminations

Administration

→

Data

Communications

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-31

Provisionable parameters Operations parameters

Parameter

Alarm Gateway

NE (agne)

Table A-8 Operations parameters (continued)

TL1

Commands

(Access)

(Note)

ENT-SYS

(P)

Range

Yes, No

Alarm Group

Number (almgrp)

1-255

Default

No

255

Remote NE Status

(rnestat)

FTAM-FTP

Gateway

(ftamftpgw) enabled, disabled, enable

Far-End

Enabled, disabled disabled disabled

Enabled, disabled enabled File Transfer

Protocol (ftp)

Security Log

Overflow

Message

(slogthrshid)

History Log

Overflow

Message

(hlogthrshid)

TL1 TCP/IP

Gateway NE

(tcpipgw)

Target Identifier

(TID)

Alarm Severity

Assignment

Profile (pfname)

ENT-ASAP-

ASGNMT

(P, G)

0% to 90%

(10% increments)

0% to 90%

(10% increments)

Enabled, disabled

20 alphanumeric or special characters:

″

-

″

(hyphen),

″

.

″

(period)

DEFAULT ASAP

User-Created ASAP

90%

90% disabled

LT-DMX

DEFAULT

ASAP

Related

WaveStar

®

Commands

CIT

Administration

→

Set NE

Administration

→

Data

Communications

Administration

→

Set TID

Configuration

→

Equipment

.................................................................................................................................................................................................................................

A-32 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters

Parameter

Network Time

Protocol (ntp)

Table A-8 Operations parameters (continued)

TL1

Commands

(Access)

(Note)

ENT-SYS

(P)

Range

Enabled, disabled, reset

Coordinated

Universal Time

Offset (utco)

Default

enabled

-24:00 to +24:00 exclusive 0

Network Element

Mode (nemode) normal, ring-upgrade normal

Contact person for NE None System Contact

(syscontact)

System Location

(syslocation)

SNMP

Authentication

Trap

(snmpauthtrap)

Idle Channel

Signal (Idle)

(Insert AIS or

Unequipped

Signal)

1+1 Protection

Switch Priority

(uniprotprio)

Wait to Rename

Timer (wtrename)

Autolock Count

(autolcnt)

Autolock Switch

Interval

(autolswint)

Autolock Release

Interval

(autolrelint)

Physical location of NE enable, disable ais, unequipped

FRCD, SFPROT

0 - 60 minutes

0 to 20

1 to 1440

1 to 1440

None enable ais

FRCD

5 minutes

0

25

1440

Operations parameters

Related

WaveStar

®

Commands

CIT

Administration

→

Set Network Time

Protocol

Configuration

→

Ring Upgrade

Mode

Administration

→

Data

Communications

Configuration

→

Equipment

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-33

Provisionable parameters

Parameter

Automatic Ring

Discovery (ard)

(BLSR only)

Table A-8 Operations parameters (continued)

TL1

Commands

(Access)

(Note)

ED-PROTN-

GRP

(P, G)

Range

enable, disable

Wait-to-restore

(wtr) (BLSR, 1+1, and 1+1_BIDIR)

0-12, 99 (BLSR)

0-12, (1+1 and

1+1_BIDIR)

Default

enable

5

0-12, 99 5 Wait-to-restore ()

(BLSR only)

Ring Circuit

Audit Enable

(rcae) (BLSR only) enable, disable enable enable, disable enable Ring Circuit

Alarm Mode

(rcamode) (BLSR only)

Ring Circuit

Mode (rcmode)

(BLSR only)

Inconsistent VT

BLSR Access

Alarm Level

(ivtbaalmlvl)

Revertive Mode

Enable (rme) (1+1 and 1+1_BIDIR only)

NUT Attribute

(nutatr)

NUT Rate

(nutrate)

Timeslot

(timeslot)

ED-PROTN-

ACC

(P, G) auto, Manual

NA, NR enable, disable

PROT, NOTPR, TNOTP

STS1, STS3c, STS12c,

STS48c

1 to 24 (for OC-48)

1 to 96 (for OC-192) auto

NA disable

None

STS1

None

Operations parameters

Related

WaveStar

®

Commands

CIT

Configuration

→

Equipment

.................................................................................................................................................................................................................................

A-34 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters

Parameter

New Target

Table A-8 Operations parameters (continued)

Identifier (newtid)

Target/Source

Identifier (sid)

TL1

Commands

(Access)

(Note)

ED-FETID

(P, G)

SET-SID

(P)

Range

20 alphanumeric or special characters:

″

-

″

(hyphen),

″

.

″

(period)

20 alphanumeric or special characters:

″

-

″

(hyphen),

″

.

″

(period)

Local Node ID

(localnid)

ED-MAP-RING

(P, G)

0 - 15

Ring Direction

(ringdir)

W, E

Default

None

None

None

E

Ring Node ID

List (rnids)

Ring TID List

(rtids)

List with 16 entries

(0- 15)

List of valid TIDs

None

None

Operations parameters

Related

WaveStar

®

Commands

CIT

Configuration

→

Change Far-End

NE Name

Administration

→

Set TID

Configuration

→

Configure Manual

Ring Map

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-35

Provisionable parameters Operations parameters

Parameter

Serial Port Echo

(echo)

Table A-8 Operations parameters (continued)

Serial Port Baud

Rate (baudrate)

TL1

Commands

(Access)

(Note)

ENT-CID-SECU

(P, A, G, M,

R)

Range

1200, 2400, 4800, 9600,

19200 enable, disable

OSI Level 2

Router (l3lv2is)

NSAP Address

(l3org, l3res, l3rd, l3area)

ENT-ULSDCC-

L3

(P) enable, disable

L3ORG, L3RES, L3RD,

L3AREA

Default

9600 enable disable

L3ORG:

000000

L3RES:

0000 L3RD:

0000

L3AREA:

0000

0 to 250 0 NSAP Threshold

Level (nsapthlev)

TARP Data Cache

(l4etdc) enable, disable enable

TARP Data Cache

Manual Entries

ENT-ULSDCC-

L4

(P)

ENT-ULSDCC-

L4

DLT-ULSDCC-

L4

(P)

None

Related

WaveStar

®

Commands

CIT

Administration

→

Data

Communications

.................................................................................................................................................................................................................................

A-36 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters Operations parameters

Parameter

TARP Lifetime

(l4tlif)

Table A-8 Operations parameters (continued)

TL1

Commands

(Access)

(Note)

ENT-ULSDCC-

L4

(P)

Range

1 - 65535

1 - 1440 minutes TARP Loop

Detection Buffer

Flush Timer

(l4lftm)

TARP Manual

Adjacency

TARP T1 Timer

(l4t1tm)

TARP T2 Timer

(l4t2tm)

ENT-ULSDCC-

L4

DLT-ULSDCC-

L4

(P)

ENT-ULSDCC-

L4

(P)

1 - 3600 seconds

1 - 3600 seconds

Default

100

5 minutes

None

15 seconds

25 seconds

1 - 3600 seconds 40 seconds TARP T3 Timer

(l4t3tm)

TARP T4 Timer

(l4t4tm)

TCP/IP Calling

Address

(tcpipaddr)

ENT-IPMAP

(P)

1 - 3600 seconds

32-bit IP address of the

OS; 4 dot-separated decimal numbers from

0-255

1-23 alphanumeric characters

20 seconds

0

TL1

PEERCOMM

ACID

(Application

Context ID) to be assigned to a

TCP/IP address or

IP Host

Host name assigned to a

TCP/IP address

(tcpiphost)

1-24 alphanumeric characters

None

Related

WaveStar

®

Commands

CIT

Administration

→

Data

Communications

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-37

Provisionable parameters Operations parameters

Parameter

Application

Table A-8 Operations parameters (continued)

Context Identifier

(acid)

TL1

Commands

(Access)

(Note)

ENT-

TL1MSGMAP

(P)

Range

TL1PEERCOMM

TL1MAINTENANCE

TL1MEMORY-

ADMINISTRATION

TL1TEST TL1OTHER1

TL1OTHER2

Default

None

TL1 Autonomous

Message Type

(msgtype)

ALM (REPT ALM)

ENV (REPT ALM ENV)

CON (REPT COND)

DB (REPT DBCHG)

EVT (REPT EVT)

PM (REPT PM)

SW (REPT SW)

None

Action

LINEn (n=1 -11)

ENT-BANNER

(P, A)

Application

Context Identifier

(acid)

ENT-OSACMAP

DLT-OSACMAP

(P) enabled, disabled

Max 11 lines (maximum of 60 characters per line)

Total banner size cannot exceed 360 characters.

TL1PEERCOMM

TL1MAINTENANCE

None

None

(function of

VC and

ED-IP-TUNNEL

(P)

TL1TEST TL1OTHER1

TL1OTHER2 TL1CR enable, disable disable TAP Learn Status

(tlearnstat)

TAP Advertise

Status (tadverstat)

TAP Group

Number

(tapgroup) enable, disable

0-65535 disable

0

Related

WaveStar

®

Commands

CIT

Administration

→

Set TL1 Message

Map

Administration

→

Change NE Login

Banner

Administration

→

Data

Communications

Administration

→

Data

Communications

.................................................................................................................................................................................................................................

A-38 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters Operations parameters

Parameter

Time Change

Threshold

(timechg)

Table A-8 Operations parameters (continued)

TL1

Commands

(Access)

(Note)

ED-NTP

(P)

Range

1 to 499 msec

Default

128 msec

16-16384 seconds and values are powers of two

64 seconds Minimum Poll

Interval to NTP

Server (minpinvl)

Maximum Poll

Interval to NTP

Server (maxpinvl)

16-16384 seconds and values are powers of two

1024 seconds

Maximum

Adjustment

Threshold

(maxadj)

IP Address of

NTP server(s)

(ipaddr)

ENT-NTP-

SERVER

DLT-NTP-

SERVER

(P)

ENT-IP-ROUTE

(P)

500 - 10000 msec

32 bit IP address

1000 msec

None

None Destination IP address

(DEST_IP)

Destination IP subnet mask

(dest_mask)

Next-Hop Port

Type (nxthopport)

32-bit IP address; 4 dot-separated decimal numbers from 0-255

32-bit IP subnet mask; 4 dot-separated decimal numbers from 0-255 lan,clnp_tunnel, DCC

None clnp_tunnel

Related

WaveStar

®

Commands

CIT

Administration

→

Set Network Time

Protocol

Administration

→

Data

Communications

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-39

Provisionable parameters Operations parameters

Parameter

Table A-8 Operations parameters (continued)

Next-Hop Address

(nxthopadr)

TL1

Commands

(Access)

(Note)

ENT-IP-ROUTE

(P)

Range

IP address (for LAN) or

NSAP address (for clnp_tunnel)

Not required for DCC.

Default

None

Yes, No

Not required for DCC.

Yes Tunnel Auto

Provisioning

(TAP) Advertise

(tapadver)

Tunnel Auto

Provisioning (tap)

Cost (tapcost)

Profile Type

(pftype)

0-65535

Not required for DCC.

20

None

Profile Name

(pfname)

Alarm Severity

Levels

1

ENT-ASAP-

PROF

ED-ASAP-

PROF

INIT-ASAP-

PROF

(P, G)

Bidirectional 1+1,

Optimized 1+1, BLSR,

DATA, DS1, DS3, E1,

EC1, Circuit Pack,

FELAN, GELAN, NVM,

OCN, Pluggable

Transmission Module,

STSN, System, System

Timing, VC, VCG,

VCGSTS, VCGVT, VT1.5

This is an alphanumeric character string (including the hyphen) with a maximum of 24 characters. The first character must be a letter.

The characters are case insensitive.

Critical (CR), Major (MJ),

Minor (MN), Not Alarmed

(NA), Not Reported (NR)

-

DEFAULT

Related

WaveStar

®

Commands

CIT

Administration

→

Data

Communications

Configuration

→

Alarms

→

Alarm

Severity

Assignment

Profile

Note: The TL1 command security access levels are Privileged (P), Administration (A), General (G),

Maintenance (M), and Reports-only (R).

1

Refer to Metropolis

®

DMX Access Multiplexer Alarm Messages and Trouble Clearing Guide,

365-372-302 for detailed information about ASAPs and default alarm severity levels.

.................................................................................................................................................................................................................................

A-40 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters

Security parameters

.................................................................................................................................................................................................................................

The following table shows the provisionable security parameters.

Parameter

Table A-9 Security parameters

TL1 Commands

(Access) (Note)

Range Default

Password (pid)

User Access

Privilege (uap)

ENT-USER-SECU

ED-USER-SECU

(P, A)

At least one alphabetic and at least three non-alphabetic characters. Of the three nonalphabetic characters, at least one must be a numeric character and at least one must be a symbolic character. The third non-alphabetic character can be either a numeric or a symbolic character.

None

PRIVILEGED

ADMINISTRATION

GENERAL

MAINTENANCE

REPORTS-ONLY

None

0 (disabled), 7-999 days 0

Related

WaveStar

®

CIT

Commands

Administration

→

Security

→

Provision User

Logins

Password Aging

Interval (page)

Inactivity Timeout

Period (tmout)

Allow Login

(alw_login)

0-999 minutes

Enabled, Disabled

30 minutes

Enabled

Administration

→

Security

→

Provision User

Logins

Administration

→

Security

→

Enable

User Login

Administration

→

Security

→

Disable User

Login

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-41

Provisionable parameters

Parameter

Table A-9 Security parameters (continued)

TL1 Commands

(Access) (Note)

Range

New User ID

(new_uid)

ED-USER-SECU

(P, A)

New Password

(new_pid)

Default

case-sensitive alphanumeric string of

5-10 characters

At least one alphabetic and at least three non-alphabetic characters. Of the three nonalphabetic characters, at least one must be a numeric character and at least one must be a symbolic character. The third non-alphabetic character can be either a numeric or a symbolic character.

Enable Login

None

None

None Lockout Status

(lockout_status)

Old Private

Identifier/ password (old_pid)

ED-PID

(P, A, G, M, R)

New Private

Identifier/ password

(new_pid)

At least one alphabetic and at least three non-alphabetic characters. Of the three nonalphabetic characters, at least one must be a numeric character and at least one must be a symbolic character. The third non-alphabetic character can be either a numeric or a symbolic character.

None

Security parameters

Related

WaveStar

®

Commands

CIT

Administration

→

Security

→

Provision User

Logins

Administration

→

Change Password

.................................................................................................................................................................................................................................

A-42 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters

Parameter

Table A-9 Security parameters (continued)

TL1 Commands

(Access) (Note)

Range

Security State

(state)

ENT-CID-SECU

(P)

IS (no lockout),

LO (Lockout)

User ID Aging

Period (usrage)

Failed Login

Attempts Lockout

Period (intrvl)

Failed Login

Attempts Lockout

Threshold (thrshld)

Failed Login

Attempts Lockout

Aging Period (age)

Minimum Waiting

Period before

Changing Password

(pidwpd)

Change Password

Status

(chg_pwd_stat)

ED-NE-SECU

(P, A)

0 - 999 Days

0 - 99 Minutes

2 - 99

1 - 999 Minutes

0 - 30 Days enable, disable

60

20 disable

Security parameters

60

10

Default

IS

Related

WaveStar

®

Commands

CIT

Administration

→

Security

→

Enable

Lockout Security

State

Administration

→

Security

→

Disable Lockout

Security State

Administration

→

Security

→

Provision NE

Security

5

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-43

Provisionable parameters Security parameters

Parameter

Community

Identifier for

SNMP user

(ucomid)

Table A-9 Security parameters (continued)

User IP address

(uipadr)

Request

Functionality

(reqfnct)

TL1 Commands

(Access) (Note)

ENT-SNMP-USER

(P)

Range

alphanumeric string of 6 to 20 characters

32-bit IP address

Enabled, Disabled

Default

None

None

Enabled

Related

WaveStar

®

Commands

CIT

Administration

→

Security

→

Provision SNMP

Users

Trap Functionality

(trapfncts)

Enabled, Disabled Enabled

Note: The TL1 command security access levels are Privileged (P), Administration (A), General (G),

Maintenance (M), and Reports-only (R).

.................................................................................................................................................................................................................................

A-44 365-372-301 R6.0

Issue 15, January 2006

Provisionable parameters

Miscellaneous parameters

.................................................................................................................................................................................................................................

The following table shows miscellaneous provisionable parameters.

Parameter

Alarm Clear Delay

(clrdel)

Table A-10 Miscellaneous parameters

TL1

Commands

(Access)

(Note)

SET-ATTR-

ALM

(P, G)

Range

0-30 sec.

0-30 sec.

Incoming Signal

Alarm Delay (almdel)

Miscellaneous

Discrete Alarm

Notification Code

(ntfcncde)

SET-ATTR-

ENV

(P, G)

CR, MJ, MN, NA

Default

10

2

1-14: MN

15: MJ

16-19: MN

Related

WaveStar

®

Commands

CIT

Configuration

→

Alarms

→

Alarm

Configuration

Configuration

→

Misc. Discretes

Miscellaneous

Discrete Alarm Type

(almtype)

Miscellaneous

Discrete Alarm

Message (almmsg)

Miscellaneous

Discrete Control Type

(conttype)

SET-ATTR-

CONT

(P, G)

1-10 alphanumeric characters

Up to 26 alphanumeric and symbolic characters

(case-sensitive)

Up to 26 alphanumeric and symbolic characters

(case-sensitive)

1-14: MISC

15: not provisionable

16-19: MISC

1-14: environment

15: not provisionable

16-19: environment control (1-4)

Note: The TL1 command security access levels are Privileged (P), Administration (A), General (G),

Maintenance (M), and Reports-only (R).

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

A-45

Glossary

.................................................................................................................................................................................................................................

Numerics

1+1 (bidirectional)

The bidirectional 1+1 protection switching architecture protects against failures of the optical transmit/receive equipment and their connecting fiber facility. One bidirectional interface (two fibers plus associated OLIUs on each end) is designated

″ service,

″ and the other is designated

″ protection.

″

In each direction, identical signals are transmitted on the service and protection lines (

″ dual-fed

″

). The receiving equipment monitors the incoming service and protection lines independently, and selects traffic from one line

(the

″ active

″ line) based on performance criteria and technician/OS control. In bidirectional 1+1 switching the network elements are not independent. When a protection switch is requested at a network element, both network elements perform protection switching.

1+1 (unidirectional)

The unidirectional 1+1 protection switching architecture protects against failures of the optical transmit/receive equipment and their connecting fiber facility. One bidirectional interface (two fibers plus associated OLIUs on each end) is designated

″ service,

″ and the other is designated

″ protection.

″

In each direction, identical signals are transmitted on the service and protection lines (

″ dual-fed

″

). The receiving equipment monitors the incoming service and protection lines independently, and selects traffic from one line

(the

″ active

″ line) based on performance criteria and technician/OS control. In unidirectional 1+1 both service and protection lines could be active at the same time

(service in one direction, protection in the other).

1xN, 1x1

1xN protection switching pertains to circuit pack protection that provides a redundant signal path through the DMX 2.5G Multiplexer (it does not cover protection switching of an optical facility; see

″

1+1

″

). In 1xN switching, a group of N service circuit packs share a single spare protection circuit pack. 1x1 is a special case of 1xN, with N=1. In

1x1 only one is active at a time.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-1

Glossary

802.1Q Mode

In 802.1Q Mode, a circuit pack can be provisioned to use an incoming frame’s VLAN tag, to add a VLAN tag associated with the port for untagged frames, or to drop an incoming frame if its VLAN tagging does not meet provisioned specifications. The priority bits in an incoming frame’s VLAN tag can also be used to affect the handling of the frame.

.................................................................................................................................................................................................................................

A ABN

Abnormal (status condition)

AC

Alternating Current

Active

Active identifies any protected entity which is currently selected by the receiver at either end as the payload carrying signal that is currently carrying service. (See Standby).

Adaptive Rate

See Pipe Mode.

Add/Drop Multiplexer (ADM)

The term for a synchronous network element capable of combining signals of different rates and having those signals added to or dropped from the stream.

ADM

Add/Drop Multiplexer

ADR

Add/Drop Ring

Aging

The filtering database entries are automatically removed after an aging period (300 seconds).

AGNE

Alarm Gateway Network Element

AIS

Alarm Indication Signal

Alarm

Visible or audible signal indicating that an equipment failure or significant event/condition has occurred.

Alarm Cut-Off (ACO)

A button on the SYSCTL used to silence audible alarms.

.................................................................................................................................................................................................................................

GL-2 365-372-301 R6.0

Issue 15, January 2006

Glossary

Alarm Gateway Network Element (AGNE)

A defined NE in an alarm group through which members of the alarm group exchange information.

Alarm Indication Signal (AIS)

A code transmitted downstream in a digital network that shows that an upstream failure has been detected and alarmed.

Alarm Severity Assignment Profile (ASAP)

A user provisioned mechanism to control an alarm level.

Alternate Mark Inversion (AMI)

A line code that employs a ternary signal to convey binary digits, in which successive binary ones are represented by signal elements that are normally of alternating, positive and negative polarity but equal in amplitude, and in which binary zeros are represented by signal elements that have zero amplitude.

American Standard Code for Information Interchange (ASCII)

A standard 7-bit code that represents letters, numbers, punctuation marks, and special characters in the interchange of data among computing and communications equipment.

AMI

Alternate Mark Inversion

ANSI

American National Standards Institute

APD

Avalanche PhotoDiode

APS

Automatic Protection Switch

APS Channel

The signalling channel carried in the K1 and K2 bytes of the SONET overhead on the protection line. It is used to exchange requests and acknowledgments for protection switch actions.

ASAP

Alarm Severity Assignment Profile

ASCII

American Standard Code for Information Interchange

ASN.1

Abstract Syntax Notation 1

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-3

Glossary

Asynchronous Transfer Mode (ATM)

A high-speed transmission technology characterized by high bandwidth and low delay. It utilizes a packet switching and multiplexing technique which allocates bandwidth on demand.

ATM

Asynchronous Transfer Mode

Auto

Automatic

Auto

One possible state of ports, lines, and channels. In this state, the port, line, or channel will automatically be put

″ in service

″ if a good signal is detected coming from the DSX panel.

Automatic Protection Switch

A feature that allows another source to be automatically selected and reconfigured in the event of a source failure or network change, for example, a fiber cut.

Autonomous Message

A message transmitted from the controlled Network Element to the ITM-SC which was not a response to an ITM-SC originated command. (Does not apply to DMX)

Avalanche Photodiode (APD)

A diode that increases its electrical conductivity by a multiplication effect when hit by light. APDs are used in lightwave receivers because the APDs have a greater sensitivity to weakened light signals (for example, those which have traveled long distances over fiber).

.................................................................................................................................................................................................................................

B B3ZS

Bipolar 3-Zero Substitution

B8ZS

Bipolar 8-Zero Substitution

Backbone Ring

A host ring.

Backout

Refers to backing out of an upgrade in progress. A backout returns a node(s) to the pre-upgrade state.

Backup

The backup and restoration features provide the capability to recover from loss of NE data because of such factors as human error, power failure, and NE design flaws.

.................................................................................................................................................................................................................................

GL-4 365-372-301 R6.0

Issue 15, January 2006

Glossary

Bandwidth

The difference in Hz between the highest and lowest frequencies in a transmission channel. The data rate that can be carried by a given communications circuit.

Baud Rate

Transmission rate of data (bits per second) on a network link.

BDFB

Battery Distribution and Fuse Bay

BER

Bit Error Rate

Bidirectional Line

A transmission path consisting of two fibers that handle traffic in both the transmit and receive directions.

Bidirectional Line-Switched Ring (BLSR)

A bidirectional ring in which protection switching is accomplished by switching working traffic into protection time slots in the line going in the opposite direction around the ring.

Bidirectional Ring

A ring in which both directions of traffic between any two nodes travel through the same network elements (although in opposite directions).

Bidirectional Switch

Protection switching performed in both the transmit and receive directions.

BIP

Bit Interleaved Parity

Bipolar 8-Zero Substitution (B8ZS)

A line coding technique that replaces eight consecutive zeros with a bit sequence having special characteristics accomplishing two objectives: First, this bit sequence accommodates the density requirements of the ones for digital T1 carrier; Second, the sequence is recognizable at the destination (due to deliberate bipolar violations) and is removed to produce the original signal.

Bit

The smallest unit of information in a computer, with a value of either 0 or 1.

Bit Error Rate (BER)

The ratio of error bits received to the total number of bits transmitted.

Bit Error Rate Threshold

The point at which an alarm is issued for bit errors.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-5

Glossary

Bit Interleaved Parity-N(BIP-N)

A method of error monitoring over a specified number of bits (BIP-3 or BIP-8).

BITS

Building Integrated Timing Supply

BITS clock

A BITS (Building Integrated Timing Source) clock is a clock within a central office that distributes timing to all the equipment in that central office. The BITS clock is tied to an external, stable timing source, such as a GPS (global positioning satellite).

Blocking

The state in which an Ethernet port does not participate in frame relay. The forwarding process discards received frames.

BLSR

Bidirectional line-switched ring

BPDU

Bridge protocol data unit

Bridge Cross-Connection

Setting up a cross-connection leg with the same input tributary as that of an existing cross-connection leg, forming a 1:2 bridge from an input tributary to two output tributaries.

Broadband

Any communications channel with greater bandwidth than a voice channel; sometimes used synonomously with wideband.

Burst Size

The provisioned burst size determines the length or size of the data burst that is allowed by the peak information rate policer. This affects policing for all VLANs (in 802.1Q

mode), all port tags (in transparent mode). and all Private line services (in Private Line or No Tag mode) on the LNW66, LNW67, and LNW68 Ethernet circuit packs.

Byte

Refers to a group of eight consecutive binary digits.

.................................................................................................................................................................................................................................

C C-Bit

A framing format used for DS3 signals produced by multiplexing 28 DS1s into a DS3.

This format provides for enhanced performance monitoring of both near-end and far-end entities.

CC

Clear Channel

.................................................................................................................................................................................................................................

GL-6 365-372-301 R6.0

Issue 15, January 2006

Glossary

CCITT

Comité Consultatif International Télégrafique & Téléphonique

(International Telephone and Telegraph Consultative Committee)

CCITT - International Telephone and Telegraph Consultative Committee

An international advisory committee under United Nations’ sponsorship that has composed and recommended for adoption worldwide standards for international communications. Recently changed to the International Telecommunications Union

Telecommunications Standards Sector (ITU-TSS).

CD-ROM

Compact Disk, Read-Only Memory

Channel

A logical signal within a port. For example, for an EC-1 port, there is one STS-1 channel and sometimes 28 VT1.5 channels. See Port.

Channel State Provisioning

A feature that allows a user to suppress reporting of alarms and events during provisioning by supporting multiple states (automatic, in-service and not monitored) for

VT1.5 and STS-n channels. See Port State Provisioning.

Circuit

A set of transmission channels through one or more network elements that provides transmission of signals between two points, to support a single communications path.

CIT

Craft Interface Terminal

Clear Channel (CC)

A provisionable mode for the DS3 output that causes parity violations not to be monitored or corrected before the DS3 signal is encoded.

CLEI

Common Language Equipment Identifier

Client Signal Fail (CSF)

The local NE sends a Client Signal Fail (CSF) signal to the far-end equipment when a defect is detected in the ingress client signal. (Ethernet/Data protocol)

CLK

Clock

CMISE

Common Management Information Service Element

CO

Central Office

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-7

Glossary

Coding Violation (CV)

A performance monitoring parameter indicating that bipolar violations of the signal have occurred.

Collocated

System elements that are located in the same location.

Concatenation

A procedure whereby multiple virtual containers are associated one with each other resulting in a combined capacity that can be used as a single container across which bit sequence integrity is maintained.

Constituent Signals

List of received signals for an adaptive rate (pipe mode) optical port.

Cost

Cost is used to help determine the efficiency of any given path. Cost is provisioned for a port (depending on speed of transmission) and calculated automatically for a path (sum of the port costs for the path).

CP

Circuit Pack

CPE

Customer Premises Equipment

CR

Critical (alarm status)

Craft Interface Terminal (CIT)

The user interface terminal used by craft personnel to communicate with a network element.

Credit Interval

The provisioned interval for adding tokens to the token bucket used by the peak information rate policer. This affects policing for all VLANs (in 802.1Q mode), all port tags (in transparent mode), and all Private line services (in Private Line or No Tag mode).

Critical (CR)

Alarm that indicates a severe, service-affecting condition.

Cross-Connect Capacity

The total bandwidth of cross-connections as measured by the bandwidth of input and output tributaries. A system with N STS-1 equivalent input tributaries and N STS-1 equivalent output tributaries (referred to as

″

NxN

″

) provides a cross-connection capacity of N STS-1 equivalents. This system could provide N one-way point-to-point cross-connections or N

2 two-way point-to-point cross-connections at the equivalent rate

.................................................................................................................................................................................................................................

GL-8 365-372-301 R6.0

Issue 15, January 2006

Glossary of STS-1.

Cross-Connect Loopback

A cross-connection from an input tributary to the output of that same tributary via the cross-connect fabric.

Cross-Connect Rate

The attribute of a cross-connection that defines the constituent signal rate(s) it can carry.

For a cross-connection with an STS-3

″ pipe

″ cross-connection rate, the constituent signals carried by the cross-connection can be either an STS-3c signal or three STS-1 signals. Similarly, for a cross-connection with an STS-12

″ pipe

″ cross-connection rate, the constituent signals carried by the cross-connection can be either an STS-1 signal or an allowed mix of STS-12c signals and STS-3c signals.

CSF

Client Signal Fail

CTL

Controller

CTS

Customer Technical Support; now known as Technical Support Services (TSS)

Cut-Through

Refers to a simple ASCII interface to an NE. It enables the user to send TL1 messages directly to the NE with no interpretation or assistance provided by the WaveStar CIT.

CV

Coding Violation

CVFE

Coding Violation Far End

.................................................................................................................................................................................................................................

D DACS

Digital Access Cross-Connect System

DACS III-2000

Digital Access and Cross-Connect System that provides clear channel switching at either the DS3 or the STS-1 rates, eliminating the need for manual DSXs.

DACS IV-2000

Digital Access and Cross-Connect System that provides electronic DS3/STS-1 or

DS1/VT1.5 cross-connect capability, eliminating the need for manual DSXs.

Data Communications Channel (DCC)

The embedded overhead communications channel in the synchronous line, used for end-to-end communications and maintenance. The DCC carries alarm, control, and status

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-9

Glossary information between network elements in a synchronous network.

Data Communications Equipment (DCE)

The equipment that provides signal conversion and coding between the data terminating equipment (DTE) and the line. The DCE may be separate equipment or an integral part of the DTE or of intermediate equipment. A DCE may perform other functions usually performed at the network end of the line.

Data Terminating Equipment (DTE)

The equipment that originates data for transmission and accepts transmitted data.

dB

Decibels

DC

Direct Current

DCC

Data Communications Channel

DCE

Data Communications Equipment

DDM-2000

Lucent’s SONET multiplexers that multiplex DS1, DS3, or EC-1 inputs into EC-1, OC-1,

OC-3, or OC-12 outputs.

Default Provisioning

The parameter values that are preprogrammed as shipped from the factory.

Demultiplexing

A process applied to a multiplexed signal for recovering signals combined within it and for restoring the distinct individual channels of these signals.

DEMUX

Demultiplexer

DEMUX - Demultiplexer

The DEMUX direction is from the fiber toward the DSX.

Dense Wavelength Division Multiplexing (DWDM)

Transmitting two or more signals of different wavelengths simultaneously over a single fiber.

Digital Cross-Connect Panel (DSX)

A panel designed to interconnect to equipment that operates at a designated rate. For example, a DSX-3 interconnects equipment operating at the DS3 rate.

.................................................................................................................................................................................................................................

GL-10 365-372-301 R6.0

Issue 15, January 2006

Glossary

Digital Multiplexer

Equipment that combines time-division multiplexing several digital signals into a single composite digital signal.

Digital Signal Levels 0, 1, 3 (DS0, DS1, DS3)

An ANSI-defined signal or service level corresponding to the following: DS0 is 64 Kb/s,

DS1 is 1.544 Mb/s (equivalent to T1), and DS3 is 44.736 Mb/s (equivalent to 28 T1 channels or T3).

Directory Services Network Element (DSNE)

A designated network element that is responsible for administering a database that maps network element names (TIDs) to addresses (NSAPs - network service access points) in an OSI subnetwork. There can be one DSNE per ring. Can also be a GNE.

Disable admin

An Ethernet port that does not participate in the spanning tree. The port is disabled by management.

Disable failure

A port in this state does not participate in the spanning tree. The port is disabled due to a hardware or software failure.

DLC

Digital Loop Carrier

DRI

Dual Ring Interworking

DS1

Digital Signal Level 1

DS3

Digital Signal Level 3

DS3 Format

Specifies the line format of a DS3 interface port, such as M23 or C-bit parity.

DSCP

Differentiated Services Code Point

DSLAM

Digital Subscriber Line Access Multiplexer

DSNE

Directory Services Network Element

DSX

Digital Cross-Connect Panel

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-11

Glossary

DTE

Data Terminating Equipment

Dual Homing

A network topology in which two OC-3, OC-12, or OC-48 shelves serve as hosts.

DWDM

Dense Wavelength Division Multiplexing

.................................................................................................................................................................................................................................

E E1

E1 is an SDH/PDH (Synchronous Digital Hierarchy/Pleiseosynchronous Digital

Hierarchy, the European equivalent of SONET/DSx) electrical signal comparable to (but slightly faster than) a DS1. E1 is also sometimes called CEPT-1 (Conference of

European Posts and Telecommunications) and is at 2.048 Mbps.

EC-1

Electrical Carrier Level 1

EC-1, EC-n - Electrical Carrier

The basic logical building block signal with a rate of 51.840 Mb/s for an EC-1 signal and a rate of n times 51.840 Mb/s for an EC-n signal. An EC-1 signal can be built in two ways: A DS1 can be mapped into a VT1.5 signal and 28 VT1.5 signals multiplexed into an EC-1 (VT1.5 based EC-1), or a DS3 can be mapped directly into an EC-1 (DS3 based EC-1).

ECI

Equipment Catalog Item

EEPROM

Electrically-Erasable Programmable Read-Only Memory

EIA

Electronic Industries Association

Electromagnetic Compatibility (EMC)

A measure of equipment tolerance to external electromagnetic fields.

Electromagnetic Interference (EMI)

High-energy, electrically induced magnetic fields that cause data corruption in cables passing through the fields.

Electronic Industries Association (EIA)

A trade association of the electronic industry that establishes electrical and functional standards.

Electrostatic Discharge (ESD)

Static electrical energy potentially harmful to circuit packs and humans.

.................................................................................................................................................................................................................................

GL-12 365-372-301 R6.0

Issue 15, January 2006

Glossary

EMC

Electromagnetic Compatibility

EMI

Electromagnetic Interference

Enterprise Systems Connection (ESCON)

A 200-Mbps data signal used in storage area networking applications.

EOOF

Excessive Out of Frame

EPORT

Ethernet Port

EPROM

Erasable Programmable Read-Only Memory

EQ

Equipped (memory administrative state)

EQPT

Equipment

Equipment Catalog Item (ECI)

The bar code number on the faceplate of each circuit pack used by some inventory systems.

Errored Seconds (ES)

A performance monitoring parameter.

ES

Errored Seconds

ESD

Electrostatic Discharge

ESF

Extended Super Frame

EST

Environmental Stress Testing

Establish

A user initiated command, at the WaveStar CIT, to create an entity and its associated attributes in the absence of certain hardware. (Does not apply to Metropolis

®

DMX

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-13

Glossary

Event

A significant change. Events in controlled Network Elements include signal failures, equipment failures, signals exceeding thresholds, and protection switch activity. When an event occurs in a controlled Network Element, the controlled Network Element will generate an alarm or status message and send it to the management system.

Extended Superframe Format (ESF)

A T1 format that uses the framing bit for non-intrusive signaling and control. A T1 frame is sent 8,000 times a second, with each frame consisting of a payload of 192 bits, and with each frame preceeded by a framing bit. Because ESF only requires 2,000 framing bits for synchonization, the remaining 6,000 framing bits can be used for error detection.

Externally Timed

An operating condition of a clock in which it is locked to an external reference and is using time constants that are altered to quickly bring the local oscillator’s frequency into approximate agreement with the synchronization reference frequency.

Extra traffic

Unprotected traffic that is carried over protection channels when their capacity is not used for the protection of working traffic. However, the extra traffic is unprotected and is preempted (lost) if a protection switch is activated. Preempted traffic is reestablished when the protection switch clears.

.................................................................................................................................................................................................................................

F Facility

A one- or two-way circuit that carries a transmission signal.

Facility Loopback

A facility loopback is where an entire line is looped back.

Facility Roll

The disconnection of the circuit cross-connecting input tributary to an output tributary followed, within the required completion time, by a cross-connection of an input tributary to an output tributary.

Failures in Time (FIT)

Circuit pack failure rates per 10

9 hours as calculated using the method described in

Reliability Prediction Procedure for Electronic Equipment, Telcordia Method I, Issue 5,

September 1995.

Far End (FE)

Any other network element in a maintenance subnetwork other than the one the user is at or working on. Also called remote.

.................................................................................................................................................................................................................................

GL-14 365-372-301 R6.0

Issue 15, January 2006

Glossary

Far-End Receive Failure (FERF)

An indication returned to a transmitting Network Element that the receiving Network

Element has detected an incoming section failure. Also known as RFI (Remote Failure

Indication).

Fault

Fault Management

Collecting, processing, and forwarding of autonomous messages from network elements.

FC

Term used when a circuit pack has a hard (not temporary) fault and cannot perform its normal function.

Fibre Channel

FC - 1G

Fibre Channel - 1 Gigabit

FC -2G

Fibre Channel - 2 Gigabit

FCC

Federal Communications Commission

FE

Far End

FE

Fast Ethernet

FE ACTY

Far End Activity

FEBE

Far End Block Error

FEC

Forward Error Correction

FEPROM

Flash EPROM

Fibre Channel - 1G (FC-1G)

A Fibre Channel 1.0625 Gbps data signal.

Fibre Channel -2G (FC-2G)

A Fibre Channel 2.1250 Gbps data signal.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-15

Glossary

Fibre Connection (FICON)

A 1.0625 Gbps data signal.

File Transfer and Access Management (FTAM)

FTAM is the Open Systems Interconnection (OSI) standard for file transfer, file access, and file management.

Filtering database

The filtering database maintains a dynamic list of paths to which packets should be routed based on the destination address. The database entries are created, updated, and removed by the learning process.

FIT

Flash EPROM

A technology that combines the nonvolatility of EPROM with the in-circuit reprogrammability of EEPROM (electrically-erasable PROM).

FN

Failures in 10

9 hours of operation.

Function Unit

Forced

Term used when a protected entity (either working or protection) has been locked into a service-providing state by user command.

Forced Switch to Protection

The WaveStar CIT command that forces the protection group to be the

″

Active Unit.

″

The clear command is required to remove the Forced Switch state. While in the Forced

Switch state the system may not switch the active unit either automatically, by means of the WaveStar CIT Forced Switch, or Manual Switch command.

Forwarding

The state in which an Ethernet port participates in frame relay.

Free Running

An operating condition of a clock in which its local oscillator is locked to an internal synchronization reference and is using no storage techniques to sustain its accuracy.

FT-2000

A Lucent SONET OC-48 Lightwave System.

FTAM

File Transfer and Access Management

FTAM-FTP Gateway

In Release 3.0 and later releases, the Metropolis

®

DMX supports an FTAM-FTP gateway function. This is also referred to as file transfer translation device (FTTD). The FTTD

.................................................................................................................................................................................................................................

GL-16 365-372-301 R6.0

Issue 15, January 2006

Glossary translates FTAM over OSI presentation to FTP over TCP/IP.

Function Unit (FN)

Refers to any one of a number of different circuit packs that can reside in the A, B, C, or D function unit slots on the DMX 2.5G Multiplexer.

.................................................................................................................................................................................................................................

G Gateway Network Element (GNE)

A network element that passes information between other network elements and management systems through a data communication network.

GB

Gigabytes

Gb/s

Gigabits per second

GbE

Gigabit Ethernet

Generic Framing Procedure (GFP)

The Generic Framing Procedure, described in ITU-T G.7041/Y1303, provides a generic mechanism to adapt traffic from higher-layer client signals over a SONET network.

GFP

Generic Framing Procedure

GHz

Gigahertz

GNE

Gateway Network Element

GR-XXX

Telcordia Technologies (Bellcore) General Requirement-XXX

GUI

Graphical User Interface

.................................................................................................................................................................................................................................

H Hairpin Routing

A cross-connection between function units (inter-function unit). For example, function unit C to function units A, B, or D. Also, a cross-connection within the same function unit (intra-function unit). Cross-connections go through Main, but no bandwidth or time slots are taken from the backbone ring. Eliminates need for another shelf.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-17

Glossary

Hashed FTP

In Release 3.0 and later releases, the hashed FTP (digital signature) capability prevents tampering with a downloadable software image.

Holdover

An operating condition of a network element in which its local oscillator is not locked to any synchronization reference but is using storage techniques to maintain its accuracy with respect to the last known frequency comparison with a synchronization reference.

HS

High Speed

Hz

Hertz

I

.................................................................................................................................................................................................................................

I/O

Input/Output

IAO LAN

Intraoffice Local Area Network

ID

Identifier

IEC

International Electrotechnical Commission

IEEE

Institute of Electrical and Electronics Engineers

IMF

Infant Mortality Factor

In-Service (IS)

A memory administrative state for ports. IS refers to a port that is fully monitored and alarmed.

INC

Incoming Status

Insert

To physically insert a circuit pack into a slot, thus causing a system-initiated restoral of an entity into service and/or creation of an entity and associated attributes.

Intermediate Reach (IR)

A term used to describe distances of 15 to 40 km between optical transmitter and receiver without regeneration. See long reach.

.................................................................................................................................................................................................................................

GL-18 365-372-301 R6.0

Issue 15, January 2006

Glossary

IP

Internet Protocol

IR

Intermediate Reach

IS

In Service

ISDN

Integrated Services Digital Network

ISO

International Standards Organization

ISP

Internet Service Provider

.................................................................................................................................................................................................................................

J Jitter

Timing jitter is defined as short-term variations of the significant instants of a digital signal from their ideal positions in time.

Jumbo frame

Jumbo frames increase network efficiency by reducing the number of frames to be processed.

.................................................................................................................................................................................................................................

K Kb/s

Kilobits per second

.................................................................................................................................................................................................................................

L LAN

Local Area Network

LAPD

Link Access Procedure

″

D

″

LBC

Laser Bias Current

LBO

Lightguide Build Out

LCAS

Link Capacity Adjustment Scheme

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-19

Glossary

LCN

Local Communications Network

LEC

Local Exchange Carrier

LED

Light-Emitting Diode

LFD

Loss of Frame Delineation

LGX

Lightguide Cross-Connect

Light Emitting Diode (LED)

Used on a circuit pack faceplate to show failure (red) or service state. It is also used to show the alarm and status condition of the system.

Lightguide Build-Out (LBO)

An attenuating (signal-reducing) element used to keep an optical output signal strength within desired limits.

Lightguide Cross-Connect (LGX)

A SONET device that contains ports for optical fiber connections to an optical network element (NE). An LGX is used to make and change connections to an NE without changing the cabling on the NE itself.

Line

A transmission medium, together with the associated equipment, required to provide the means of transporting information between two consecutive network elements. One network element originates the line signal; the other terminates it.

Line Timing

The capability to directly derive clock timing from an incoming OC-N signal while providing the user the capability to provision whether switching to an alternate OC-N from a different source (as opposed to entering holdover) will occur if the OC-N currently used as the timing reference for that NE becomes unsuitable as a reference.

For example, intermediate nodes in a linear network are line timed. See Loop Timing.

Link Capacity Adjustment Scheme (LCAS)

LCAS is an enhancement to SONET/SDH Virtual Concatenation that allows adding or removing Virtual Concatenation Group (VCG) members, to vary its bandwidth, by management command. It also automatically removes and restores failed members.

Listening

The state in which an Ethernet port is preparing to participate in frame relay. In the listening state, frame relay is disabled. This is an interim state between blocking and

.................................................................................................................................................................................................................................

GL-20 365-372-301 R6.0

Issue 15, January 2006

Glossary learning.

LOA

Loss of Alignment

Local

See Near-End.

Local Area Network (LAN)

A communications network that covers a limited geographic area, is privately owned and user administered, is mostly used for internal transfer of information within a business, is normally contained within a single building or adjacent group of buildings, and transmits data at a very rapid speed.

Locked DSn Cross-Connections

Locked DSn cross-connections add/drop traffic to/from only one rotation of a UPSR.

Path switching is disabled. Timeslots can be reused at different nodes around the UPSR.

LOF

Loss of Frame

Long Reach (LR)

A term used to describe distances of 40 km or more between optical transmitter and receiver without regeneration. See Intermediate Reach.

Loopback

Type of diagnostic test used to compare an original transmitted signal with the resulting received signal. A loopback is established when the received optical or electrical external transmission signal is sent from a port or tributary input directly back toward the output.

LOP

Loss of Pointer

LOS

Loss of Signal

Loss of Alignment (LOA)

One or more STS-1s that compose a VCG are out of multiframe alignment because of excess delay difference.

Loss of Frame (LOF)

A failure to synchronize to an incoming signal.

Loss of Frame Delineation (LFD)

Lack of sufficient bandwidth that is reported when there is a mismatch in the number of

STS tributaries.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-21

Glossary

Loss of Pointer (LOP)

A failure to extract good data from an STS-n payload.

Loss of Signal (LOS)

The complete absence of an incoming signal.

LPBK

Loopback

LR

Long Reach

LS

Low Speed

.................................................................................................................................................................................................................................

M M23-Format

A standard framing format used for DS3 signals produced by multiplexing 28 DS1s into a DS3 (sometimes referred to as M13-format, without C-bit parity).

Main

The two slots (M-1 and M-2) on a Metropolis

®

DMX shelf in which the OC-48 or

OC-192 high speed OLIU circuit packs are installed.

Maintenance Condition

An equipment state in which some normal service functions are suspended, either because of a problem or to perform special functions (copy memory) that can not be performed while normal service is being provided.

Major

Indicates a service-affecting failure, main or unit controller failure, or power supply failure.

MB

Megabytes

Mb/s

Megabits per second

Minor (MN)

Indicates a non-service-affecting failure of equipment or facility.

Miscellaneous Discrete Interface

Allows an operations system to control and monitor equipment collocated within a set of input and output contact closures.

MJ

Major Alarm

.................................................................................................................................................................................................................................

GL-22 365-372-301 R6.0

Issue 15, January 2006

Glossary

MM

Multimode

MML

huMan-Machine Language

MN

Minor Alarm

MPEG

Moving Picture Experts Group

MTBF

Mean Time Between Failures

MTBMA

Mean Time Between Maintenance Activities

Mult

Multipling

Multiplexer

A device (circuit pack) that combines two or more transmission signals into a combined signal on a shared medium.

Multiplexing

The process of combining multiple signals into a larger signal at the transmitter by a multiplexer. The large signal is then split into the original smaller signals at the receiver by a demultiplexer.

MUX

Multiplex

.................................................................................................................................................................................................................................

N NA

Not Applicable

NARTAC

North American Regional Technical Assistance Center

NE

Near End

NE

Network Element

NE ACTY

Near-End Activity

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-23

Glossary

Near End

The network element the user is at or working on. Also called local.

NEBS

Network Equipment-Building System

Network Element (NE)

A node in a telecommunication network that supports network transport services and is directly manageable by a management system.

Network Element (NE)

The basic building block of a telecommunications equipment within a telecommunication network that meets SONET standards. Typical internal attributes of a network element include: onr or more high- and low-speed transmission ports, built-in intelligence, synchronization and timing capability, and access interfaces for use by technicians and/or operation systems. In addition, a network element may also include a time slot interchanger.

Network Service Access Point (NSAP) Address

Network Service Access Point Address (used in the OSI network layer 3). An automatically assigned number that uniquely identifies a Network Element for the purposes of routing DCC messages.

Network Time Protocol

Network time protocol is an easy, accurate, and automatic method to get and synchronize date/time.

nm

Nanometer (10

-9 meters)

NMA

Network Monitoring and Analysis

NMON

Not Monitored (provisioning state)

No Request State

This is the routine-operation quiet state in which no external command activities are occurring.

Node

A network element in a ring or, more generally, in any type of network. In a network element supporting interfaces to more than one ring, node refers to an interface that is in a particular ring. Node is also defined as all equipment that is controlled by one system controller. A node is not always directly manageable by a management system.

.................................................................................................................................................................................................................................

GL-24 365-372-301 R6.0

Issue 15, January 2006

Glossary

Non-preemptible unprotected traffic (NUT)

Traffic carried on (working and/or protection) BLSR channels for which protection switching has been provisioned as disabled. NUT must be employed when using an alternate protection scheme for data such as RSTP. As the name implies, NUT is unprotected and not preempted in the event of a protection switch. NUT carried on non-preemptible unprotected channels affords a higher level of survivability as compared to extra traffic, which is preempted during a protection switch, but a lower level of survivability as compared to working traffic, which is carried on its corresponding protection channel during a protection switch.

Non-Revertive Switching

In non-revertive switching, an active and standby line exist on the network. When a protection switch occurs, the standby line is selected to support traffic, thereby becoming the active line. The original active line then becomes the standby line. This status remains in effect even when the fault clears. That is, there is no automatic switch back to the original status.

Non-Volatile Memory (NVM)

Memory that retains its stored data after power has been removed. An example of NVM would be a hard disk.

Not Monitored (NMON)

A provisioning state for equipment that is not monitored or alarmed.

NR

Not Reported

NRZ

Nonreturn to Zero

NSA

Not Service Affecting

NSAP Address

Network Service Access Point Address (used in the OSI network layer 3)

NTF

No Trouble Found

NTP

Network time protocol

NUT

Nonpreemptible unprotected traffic

NVM

Non-Volatile Memory

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-25

Glossary

.................................................................................................................................................................................................................................

O OAM&P

Operations, Administration, Maintenance, and Provisioning

OC, OC-n - Optical Carrier

The optical signal that results from an optical inversion of an STS signal; that is, OC-1 from STS-1 and OC-n from STS-n.

OC-1

Optical Carrier, Level 1 Signal (51.84 Mb/s)

OC-1

Optical Carrier Level 1 Signal (51.844 Mb/s).

OC-12

Optical Carrier, Level 12 Signal (622.08 Mb/s)

OC-12

Optical Carrier Level 12 Signal (622 Mb/s).

OC-192

Optical Carrier, Level 192 Signal (9953.28 Mb/s) (10 Gb/s)

OC-192

Optical Carrier Level 192 Signal (9953 Mb/s).

OC-3

Optical Carrier, Level 3 Signal (155.52 Mb/s)

OC-3

Optical Carrier Level 3 Signal (155 Mb/s).

OC-48

Optical Carrier Level 48 Signal (2488 Mb/s).

OC48

Optical Carrier, Level 48 Signal (2488.32 Mb/s) (2.5 Gb/s)

OI

Operations Interworking

OLIU

Optical Line Interface Unit

OOF

Out of Frame

.................................................................................................................................................................................................................................

GL-26 365-372-301 R6.0

Issue 15, January 2006

Glossary

OOL

Out of Lock

OOS

Out-of-Service

Open Systems Interconnection (OSI)

Referring to the OSI reference model, a logical structure for network operations standardized by the International Standards Organization (ISO).

Operations Interface

Any interface providing you with information on the system behavior or control. These include the equipment LEDs, SYSCTL faceplate, WaveStar CIT, office alarms, and all telemetry interfaces.

Operations Interworking (OI)

The capability to access, operate, provision, and administer remote systems through craft interface access from any site in a SONET/SDH network or from a centralized operations system.

Operations System (OS)

A central computer-based system used to provide operations, administration, and maintenance functions.

OPS/INE

Operations System/Intelligent Network Element

OS

Operations System

OSI

Open Systems Interconnection

OSMINE

Operations Systems Modifications for the Integration of Network Elements

OSP

Outside Plant

.................................................................................................................................................................................................................................

P P-bit

Performance Bit

Pass Through

Paths that are cross-connected directly across an intermediate node in a ring network.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-27

Glossary

Path

A logical connection between the point at which a standard frame format for the signal at the given rate is assembled, and the point at which the standard frame format for the signal is disassembled.

Path Protection Group

The part of a cross-connection topology that is provisioned to provide path-level protection switching for all the constituent signals carried by the cross-connection. A path protection group can be identified as an entity by its logical output tributary and its cross-connection rate. A path protection group consists of one or more constituent path selectors.

PC

Personal Computer

PCMCIA

Personal Computer Memory Card International Association

Peak Information Rate Policer

The peak information rate policer meters packet traffic leaving the internal packet switch and going toward the SONET network. If the packets exceed the provisioned peak information rate, the packets are dropped.

Performance Monitoring (PM)

Measures the quality of service and identifies degrading or marginally operating systems

(before an alarm would be generated).

PID

Program Identification

Pipe Mode

Metropolis

®

DMX supports cross-connections on adaptive rate OC-n ports (pipe mode).

The signal rates adapt to the supported set of signal rates. Cross-connections may be provisioned at any cross-connection rate that is supported for the tributaries associated with the OC-n ports. A cross-connection can carry any set of constituent signals; however, the total of the constituent signal rates must not exceed the cross-connection rate. Fault monitoring and performance monitoring occur on the accepted incoming rates.

PIR

Peak information rate

PJC

Pointer Justification Count

Plesiochronous Network

A network that contains multiple maintenance subnetworks, each internally synchronous and all operating at the same nominal frequency, but whose timing may be slightly different at any particular instant. For example, in SONET networks, each timing

.................................................................................................................................................................................................................................

GL-28 365-372-301 R6.0

Issue 15, January 2006

Glossary traceable to their own Stratum 1 clock are considered plesiochronous with respect to each other

PLL

Phase-Locked Loop

PM

Performance Monitoring

POP

Points of Presence

Port (also called Line)

The physical interface, consisting of both an input and output, where an electrical or optical transmission interface is connected to the system and may be used to carry traffic between network elements. The words

″ port

″ and

″ line

″ may often be used synonymously.

″

Port

″ emphasizes the physical interface, and

″ line

″ emphasizes the interconnection. Either may be used to identify the signal being carried.

Port Protection Group

A user provisioned association of protected optical interface ports. This association is used for line protection. The group of ports represent both a protection switching entity and also a set of lines that carry services to/from another network element. The port protection groups also determine the set of logical tributaries from and to which cross-connections can be provisioned.

Port State Provisioning

A feature that allows a user to suppress alarm reporting and performance monitoring during provisioning by supporting multiple states (automatic, in-service, and not monitored) for low-speed ports.

POTS

Plain Old Telephone Service

Proactive Maintenance

Refers to the process of detecting degrading conditions not severe enough to initiate protection switching or alarming, but indicative of an impending signal fail or signal degrade defect (for example, performance monitoring).

Protection

Extra capacity (channels, circuit packs) in transmission equipment that is not intended to be used for service, but rather to serve as backup against failures.

Protection Group

A logical grouping of ports or circuit packs that share a common protection scheme, for example, UPSR switching or 1+1 line.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-29

Glossary

PROTN

Protection

Provisioning

The modification of certain programmable parameters that define how the node functions with various installed entities. These modifications are initiated locally or remotely by either a CIT or an OS. They may arrive at the node via the IAO LAN, CIT port, or any

DCC channel. The provisioned data is maintained in NVM and/or hardware registers.

PTM

Pluggable Transmission Module

PWR

Power

.................................................................................................................................................................................................................................

R RAI

Remote Alarm Indication

RAM

Random Access Memory

RDI

Remote Defect Indication

Reactive Maintenance

Refers to detecting defects/failures and clearing them.

Remote

See Far-End (FE).

Remote Defect Indication (RDI)

An indication returned to a transmitting terminal that the receiving terminal has detected an incoming section failure. [Previously called far-end-receive failure (FERF).]

Remote Network Element

Any Network Element that is connected to the referenced Network Element through either an electrical or optical link. It may be the adjacent node on a ring, or N nodes away from the reference. It also may be at the same physical location but is usually at another (remote) site.

Revertive

A protection switching mode in which, after a protection switch occurs, the equipment returns to the nominal configuration (that is, the service equipment is active, and the protection equipment is standby) after the clearing of any failure conditions that caused a protection switch to occur or after any external switch commands are reset. See

Non-Revertive.

.................................................................................................................................................................................................................................

GL-30 365-372-301 R6.0

Issue 15, January 2006

Glossary

RFI

Remote Failure Indication

Ring

A configuration of nodes comprised of network elements connected in a circular fashion.

Under normal conditions, each node is interconnected with its neighbor and includes capacity for transmission in either direction between adjacent nodes. Path switched rings use a head-end bridge and tail-end switch. Line switched rings actively reroute traffic over a protection line.

Ring (0x1) Low-Speed Interface

Formerly referred to as dual 0x1 or single 0x1. In ring applications, the DMX 2.5G

Multiplexer may use a 0x1 interface, meaning both fibers carry service, as opposed to a linear (1+1) low-speed interface where one fiber is used for service and other for protection. See 1+1.

Root node

The node from which path cost to any other node is measured.

RSTP

Rapid Spanning Tree Protocol

RTAC

Lucent Regional Technical Assistance Center (1-800-225-RTAC)

RTRV

Retrieve

RU

Rack Unit

RZ

Return to Zero

.................................................................................................................................................................................................................................

S SA

Service Affecting

SARB

Status All Resources Busy

SARB Error

This error response indicates the condition “Status, All Resources Busy.”

SD

Signal Degrade

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-31

Glossary

SEFS

Severely Errored Frame Seconds

Self-Healing

Ring architecture in which two or more fibers are used to provide route diversity. Node failures only affect traffic dropped at the failed node.

Service

The operational mode of a physical entity that indicates that the entity is providing service. This designation will change with each switch action.

SES

Severely Errored Seconds

Severely Errored Seconds (SES)

This performance monitoring parameter is a second in which a signal failure occurs, or more than a preset amount of coding violations (dependent on the type of signal) occur.

SF

Super Frame (format for DS1 signal)

SFP

Small Form-factor Pluggable

Shelf ID

A switch-settable parameter with values from 1 to 8. Used to log into a selected shelf in a bay using the CIT. (Does not apply to Metropolis

®

DMX)

Shelf View

A graphical depiction of one shelf. Selectable objects in this view are the shelf, the slots/circuit packs, and the ports.

SID

System Identification

Site ID

A switch-settable parameter with values from 1 to 8. Displayed on the SYSCTL circuit pack to indicate to which site the faceplate alarms and LEDs apply. (Does not apply to

Metropolis

®

DMX)

Slot

A physical position in a shelf for holding a circuit pack and connecting it to the backplane. This term is also used loosely to refer to the collection of ports or tributaries connected to a physical circuit pack placed in a slot.

SM

Single Mode

.................................................................................................................................................................................................................................

GL-32 365-372-301 R6.0

Issue 15, January 2006

Glossary

SMC

SONET Minimum Clock

SNMP

Simple Network Management Protocol

Software Backup

The process of saving an image of the current network element’s databases, which are contained in its NVM, to a remote location. The remote location could be the WaveStar

CIT or an OS.

Software Download

The process of transferring a software generic from a remote entity to the target network element’s memory. The remote entity may be the WaveStar CIT or an OS. The download procedure uses bulk transfer to move an uninterpreted binary file into the network element.

SONET

Synchronous Optical NETwork

Spanning Tree Group

Nodes can be provisioned to belong to a spanning tree group. Only the nodes within that group participate in the spanning tree for the group.

SPE

Synchronous Payload Envelope

Squelch Map

This map contains information for each cross-connection in a ring and indicates the source and destination nodes for the low-speed circuit that is part of the cross-connection. This information is used to prevent traffic misconnection in rings with isolated nodes or segments.

SRD

Software Release Description

Standby

Standby identifies a protected entity which is not currently selected by the receiver at either end as the payload carrying signal hat is not currently carrying service. See Active.

Standing Condition

A standing condition (SC) is either an event (usually user initiated such as a switch request) or an alarm that is provisioned NA (Not Alarmed).

Status

The indication of a short-term change in the system.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-33

Glossary

STQ

Secondary Transit Queue

Stratum 3 Timing Generator

The timing generator circuit pack, located in the high-speed OLIU circuit pack, that generates clock signals for distribution to the transmit circuits. It operates in the free-running, line-timing, externally times, and holdover modes.

STS, STS-n

Synchronous Transport Signal

STS, STS-n - Synchronous Transport Signal

The basic building block signal with a rate of 51.840 Mb/s for an STS-1 signal and a rate of n times 51.840 Mb/s for an STS-n signal.

STS-1 SPE

STS-1 Synchronous Payload Envelope

STS-1 SPE - STS-1 Synchronous Payload Envelope

A 125-microsecond frame structure composed of STS path overhead and the STS-1 payload.

STS-12c

Synchronous Transport Level 12 Concatenated Signal

STS-3c

Synchronous Transport Level 3 Concatenated Signal

STS-3c

Synchronous Transport Level 3 Concatenated Signal. See OC-3c.

STS-48c

Synchronous Transport Level 48 Concatenated Signal

STU

Synchronized - Traceability Unknown

Subnetwork

A group of interconnected/interrelated Network Elements. The most common connotation is a synchronous network in which the Network Elements have data communications channel (DCC) connectivity.

Superframe Format (SF)

A DS1 framing format in which 24 DS0 timeslots plus a coded framing bit are organized into a frame which is repeated 12 times to form the superframe.

Suspend

Suspend refers to temporarily stopping an upgrade in progress.

.................................................................................................................................................................................................................................

GL-34 365-372-301 R6.0

Issue 15, January 2006

Glossary

Synchronization Messaging

SONET synchronization messaging is used to communicate the quality of network timing, internal timing status, and timing states throughout a subnetwork.

Synchronous Network

The synchronization of transmission systems with synchronous payloads to a master

(network) clock that can be traced to a reference clock.

Synchronous Optical Network (SONET)

The North American standard for the rates and formats that defines optical signals and their constituents.

Synchronous Payload

Payloads that can be derived from a network transmission signal by removing integral numbers of bits from every frame. Therefore, no variable bit-stuffing rate adjustments are required to fit the payload in the transmission signal.

Synchronous Payload Envelope (SPE)

The combined payload and path overhead of an STS-1, STS-3c, STS-12c or STS-48c signal.

SYSCTL

System Controller (circuit pack)

SYSCTL - System Controller

The system controller circuit pack that provides overall administrative control of the terminal.

System View

A graphical depiction of the entire Network Element. Selectable objects in this view are the bays and shelves.

.................................................................................................................................................................................................................................

T T1

A carrier system that transmits at the rate of 1.544 Mb/s (a DS1 signal).

T1X1 and T1M1

The ANSI committees responsible for telecommunications standards

T2

A carrier system that transmits at the rate of 6.312 Mbps (a DS2 signal).

T3

A carrier system that transmits at the rate of 44.736 Mbps (a DS3 signal).

TA

Telcordia Technologies Technical Advisory

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-35

Glossary

Target Identifier (TID)

A provisionable parameter that is used to identify a particular Network Element within a network. It is a character string of up to 20 characters where the characters are letters, digits, or hyphens (-).

TARP

Target Identifiers Address Resolution Protocol

TBD

To Be Determined

TCA

Threshold-Crossing Alert

TCP/IP

Transmission Control Protocol/Internet Protocol

TDC

TARP Data Cache

TDM

Time Division Multiplexing

Telcordia Technologies

Telcordia Technologies (formerly Bellcore) is a well-recognized telecommunications’ standards organization.

Test Access

A set of cross-connection topologies used in conjunction with a testing system to monitor and

″ split

″ signal paths for purposes of fault isolation.

Threshold-Crossing Alert (TCA)

A message type sent from a Network Element that indicates that a certain performance monitoring parameter has exceeded a specified threshold.

Through (or Continue) Cross-Connection

A cross-connection within a ring, where the input and output tributaries have the same tributary number but are in lines opposite each other.

Through Timing

Refers to a network element that derives its transmit timing in the east direction from a received line signal in the east direction and its transmit timing in the west direction from a received line signal in the west direction.

THz

Terahertz (10

12

Hz)

.................................................................................................................................................................................................................................

GL-36 365-372-301 R6.0

Issue 15, January 2006

Glossary

TID

Target Identifier

Time Division Multiplexing (TDM)

A technique for transmitting a number of separate data, voice, and/or video signals simultaneously over one communications medium by interleaving a portion of each signal one after another.

Time Slot Assignment (TSA)

A capability that allows any tributary in a ring to be cross-connected to any tributary in any lower-rate, non-ring interface or to the same-numbered tributary in the opposite side of the ring.

Time Slot Interchange (TSI)

A set of nodes configured as a ring with paths established in both directions of the ring.

Switching occurs per-path at the drop nodes.

TIRKS

Trunks Integrated Records Keeping System

TL1

Transaction Language 1

TR

Telcordia Technologies Technical Requirement

Transaction Language One (TL1)

The permission level associated with each user login that defines which commands the user can execute.

Transparent Mode

In Transparent Mode, port tags (which are actually VLAN tags with a TPID value other than 8100hex) are used to separate traffic for different customers. A port tag is added to each incoming frame at the ingress LAN port. The port tag contains a provisionable customer ID and priority level.

Tributary

A path-level unit of bandwidth within a port, or the constituent signal(s) being carried in this unit of bandwidth, for example, an STS-1 tributary within an OC-N port.

TSA

Time Slot Assignment

TSI

Time Slot Interchange

TSO

Technical Support Organization

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-37

Glossary

.................................................................................................................................................................................................................................

U UAS

Unavailable Seconds

Unavailable Seconds (UAS)

In performance monitoring, the count of seconds in which a signal is declared failed or in which 10 consecutively severely errored seconds (SES) occurred, until the time when

10 consecutive non-SES occur.

Unidirectional Path-Switched Ring (UPSR)

Path-Switched rings employ redundant fiber optic transmission facilities in a pair configuration, with one fiber transmitting in one direction (for example, East) and the backup fiber transmitting in the other direction (for example, West). If the primary ring fails, then the protection ring takes over.

UPD/INIT

Update/Intialize

UPD/INIT

A push-button on the SYSCTL faceplate.

UPSR

Unidirectional Path Switched Rings

User Privilege

Permits a user must perform on the computer system on which the system software runs.

.................................................................................................................................................................................................................................

V VAC

Volts Alternating Current

VCG

Virtual Concatenation Group

VDC

Volts Direct Current

Virtual LAN (VLAN)

A virtual LAN (VLAN) is a subset of a LAN. A VLAN is created by putting VLAN IDs in packets that indicate membership to a VLAN of that ID. A Local Area Network

(LAN) can have multiple VLANs within it, up to the number of IDs available. Members

(ports) of different VLANs do not see the traffic of VLANs of which they are not members. A port may be a member of many VLANs (LAN ports in 802.1Q mode, WAN ports). In the Transparent mode, a LAN port is typically assigned membership to a single VLAN.

In Transparent mode, VLANs are assigned to ports using Port Tag (ed-eport and ed-vcg.

In 802.1Q mode, VLANs are assigned to ports using VLAN IDs (ent-vlan/ed-vlan).

.................................................................................................................................................................................................................................

GL-38 365-372-301 R6.0

Issue 15, January 2006

Glossary

A VLAN tag is the specific field of information in a packet that carries the VLAN ID number.

Virtual Switch

A virtual switch is a grouping of ports on an Ethernet switch that results in partitioning of the switch into multiple

″ logical

″ switches. A port may only be a member of one virtual switch.

Virtual Tributary (VT)

A structure designed for transport and switching of sub-STS-1 payloads. There are currently four sizes: VT1.5 (1.728 Mb/s), VT2 (2.304 Mb/s), VT3 (3.456 Mb/s), and

VT6 (6.912 Mb/s).

VLAN

Virtual Local Area Network

VM

Violation Monitor

VMR

Violation Monitor and Removal

VoIP

Voice over Internet Protocol

VPN

Virtual Private Network

vslot

Virtual Slot

VT

Virtual Tributary

VT-G - Virtual Tributary Group

A 9-row by 12-column SONET structure (108 bytes) that carries one or more VTs of the same size. Seven VT groups (756 bytes) are byte-interleaved within the VT-organized

STS-1 synchronous payload envelope

VT1.5

Virtual Tributary 1.5 (1.728 Mb/s)

VT1.5 Tributary

A SONET logical signal with a data rate of 1.728 Mbps. In the 9-row structure of the

STS-1 SPE, a VT1.5 occupies three columns. VT-structured STS-1 SPEs are divided into seven VT groups. Each VT group occupies twelve columns of the 9-row structure and, for VT1.5s, contains four VTs per group.

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

GL-39

Glossary

.................................................................................................................................................................................................................................

W Wait to Restore Time (WRT)

Corresponds to the time to wait before switching back after a failure has cleared (in a revertive protection scheme). The WRT can be between 0 and 12 minutes, in increments of one minute.

Wait-to-Rename

Wait to Rename timer for Optimized 1+1 optical line protection. After a protection switch clears, the system waits the provisioned length of time before renaming the working section 1 and working section 2 as Primary and Secondary.

WAN

Wide Area Network

Wavelength Division Multiplexing (WDM)

A means of increasing the information-carrying capacity of an optical fiber by simultaneously transmitting signals at different wavelengths.

WDCS

Wideband Digital Cross-Connect System

WDM

Wavelength Division Multiplexing

Wide Area Network (WAN)

A communication network that uses common-carrier provided lines and covers an extended geographical area.

Wizard

A form of user assistance that automates a procedure through a dialog with the user.

WTR

Wait to Restore Time

.................................................................................................................................................................................................................................

Z Zero Code Suppression

A technique used to reduce the number of consecutive zeros in a line-codes signal

(B3ZS for DS3 signals and B8ZS for DS1 signals).

.................................................................................................................................................................................................................................

GL-40 365-372-301 R6.0

Issue 15, January 2006

Index

Symbols

-48 V DC, battery test,

14-93

point-to-point, BLSR protected,

11-106

audience, UOG,

xxxv

autolock,

6-7

.............................................................

point-to-point, UPSR protected,

11-18

automatic backup, schedule

Numerics

FTP,

2-123

point-to-point, UPSR/BLSR protected,

11-134

FTTD,

2-135

1+1 bidirectional protection priority,

6-7

resilient packet ring,

11-313

.............................................................

autonomous messages disable/enable,

7-24

establish system,

9-3

A

accept autoreconfiguration, synchronization,

6-16

linear cross-connections,

10-26

end-to-end system,

3-9

.............................................................

stand-alone shelf,

3-3

protection priority,

6-7

B

back out activate software,

2-120

5.x to 6.0.x upgrade add node to UPSR/BLSR,

9-29

high-speed OC-48 OLIU upgrade,

12-19

FTAM,

2-40

administration parameters,

7-4

FTP,

2-72

AGNE,

7-28

OC-12 UPSR to OC-48

UPSR upgrade,

12-93

6.0 to 6.0.x upgrade

FTAM,

2-40

alarm OC-3 UPSR to OC-12

UPSR upgrade,

12-42

configuration,

6-33

FTP,

2-72

group/gateway,

7-28

OC-48 BLSR to OC-192

BLSR upgrade,

12-262

FTTD,

2-109

100/100 FE circuit packs alarm severity assignment profile (ASAP)

OC-48 UPSR to OC-192

UPSR upgrade,

12-182

install,

4-50

assign,

6-41

backplane bandwidth provision,

4-59

change existing,

6-36

evaluate utilization,

6-44

802.1q Mode delete,

6-39

optimize,

6-46

MAC address,

11-228

provision new,

6-34

backup, database packet ring,

11-37 ,

11-46 ,

11-64

alarm-clear delay,

6-33

FTAM,

2-150

alarm-generate delay,

6-33

FTP,

2-123

apply software,

2-120

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

IN-1

Index

FTTD,

2-135

barred-hand symbol,

1-16

baud rate, serial ports,

7-54

BLSR bridge,

10-48

bridge, Ethernet,

11-305

DRI,

10-56

dual-homed,

10-39

terminations, provision,

6-13

dedicated multiple point, UPSR protected,

11-140

delete upgrade,

12-4 ,

12-223

without NUT, establish

Ethernet packet ring,

11-55

bridge cross-connections,

10-48 ,

11-305

hairpin,

10-22

locked DSN,

10-64

provisionable parameters,

A-26

roll,

10-48

alarm severity assignment profile (ASAP),

SNMP user, user login, disable

7-20

7-12 ,

6-39

7-12

burst size (brst),

11-96

.............................................................

roll, Ethernet,

11-305

single-homed,

10-32

AGNE,

7-28

autonomous messages,

7-24

C

change

STS-1 for Ethernet service,

11-195 ,

11-207

FTAM-FTP gateway,

7-28

FTP,

7-28

alarm severity assignment profile (ASAP),

6-36

circuit pack mode,

4-84

normal/enhanced jumper setting,

4-84

STS-1 for SAN transport service,

11-280

STSN/VT1.5,

10-16

LAN ports,

TCP/IP,

7-39

7-46

TCP/IP gateway,

7-49

SNMP user login,

7-20

system TID,

7-38

user login,

7-12

channel parameters,

A-6

customer comments,

xli

.............................................................

D

danger, potential sources of,

1-4

data cache entries, TARP,

7-43

user logins, discontinue

7-16

DS1/E1 service,

,

7-59

10-7

DS3/EC-1 service,

10-13

circuit pack mode, change,

4-84

CIT-1/CIT-2 parameters,

7-54

data port provision,

4-77

node from UPSR/BLSR,

9-48

clean, fibers and LBOs,

14-34

clear TCA counts,

8-17

comcodes,

xxxix

provisionable parameters,

A-24

data type,

11-271

documentation, set,

xxxix

download software remotely,

2-115

commenting,

xli

controller, install SYSCTL,

4-4

conventions used,

xxxvii

CoS,

11-238 ,

11-323

database backup/restore

FTAM,

FTP,

2-123

FTTD,

2-150

2-135

wizard, FTAM,

2-3

wizard, FTP,

2-21

DRI, cross-connections,

DS1

10-56

create, login banner,

7-26

credit interval (cint),

11-96

cross-connections database information,

14-90

date and time, set,

DCC

7-33

circuit pack, install,

4-39

circuit pack, provision, discontinue service,

4-42

10-7

1+1 linear,

10-26

BLSR, VT1.5,

10-71

IP routes,

9-113

static IP routes,

7-52

establish service,

10-3

locked cross-connections,

10-64

.................................................................................................................................................................................................................................

IN-2 365-372-301 R6.0

Issue 15, January 2006

Index test transmission,

14-67

electrical circuit packs Ethernet service,

11-5

DS3 DS1/E1, install,

4-39

hairpin cross-connections,

10-22

discontinue service,

10-13

DS1/E1, provision,

4-42

high-speed system,

9-3

DS3/EC1 circuit pack, install,

4-32

DS3/EC1, install,

4-32

IP routes,

9-113

DS3/EC1, provision,

4-37

DS3/EC1 circuit pack, provision,

4-37

upgrade,

12-318

low-speed 1+1 unprotected optical extension,

9-132

establish service,

10-10

electrostatic discharge,

1-4 ,

1-14

low-speed optical extension,

9-69

locked cross-connections,

10-64

enable

AGNE,

7-28

OC-48 0x1 unprotected extension,

9-93

test transmission,

14-74

autonomous messages,

7-24

single-homed network,

9-76

dual-homed cross-connections,

10-39

FTAM-FTP gateway,

7-28

STSN/VT1.5

cross-connections,

10-16

.............................................................

FTP/FTTD,

7-28

E

E1

IP routes on DCC links,

7-52

subtending low-speed

UPSR/BLSR,

9-98

circuit pack, install,

4-39

circuit pack, provision,

4-42

LAN ports,

7-39

Ethernet cross-connect mode

(eccmode),

11-96

discontinue service,

10-7

Level 2 routing capabilities,

7-40

Ethernet packet ring,

11-37

establish service,

10-3

TCP/IP,

7-46

802.1q Mode,

11-46

test transmission,

14-67

TCP/IP gateway,

7-49

add Fast Ethernet,

11-150

EC-1 user logins,

7-16 ,

7-59

BLSR without NUT,

11-55

circuit pack, provision,

4-37

end-to-end system, accept,

3-9

Transparent Mode,

11-51

discontinue service,

10-13

Enhanced Fast Ethernet, private line,

11-257

Ethernet port configuration

(enetmd),

11-96

DS3/EC1 circuit pack, install,

4-32

DS3/EC1 circuit pack, provision,

4-37

enhanced jumper

(LNW26B-type circuit packs),

4-84

Ethernet service establish,

11-5

loopbacks,

11-235

establish service,

10-10

test transmission,

14-80

enter

SNMP user,

7-20

provision DATA port parameters,

11-273

echo mode, serial ports,

7-54

user login,

7-12

provision DATA VCG parameters,

11-277

edit

ESCON,

11-265 ,

11-271

login banner,

7-26

ESD,

1-14

provision Ethernet LAN port parameters,

11-72

SNMP user login, user login,

7-12

7-20

establish

DS1/E1 service,

10-3

provision Ethernet VCG parameters,

11-86

DS3/EC-1 service,

10-10

provision ports,

4-59

dual-homed network,

9-84

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

IN-3

Index provisionable parameters,

A-7

spanning tree,

11-216 ,

11-223

STS-1 cross-connections,

11-195 ,

11-207

video broadcast,

11-168 ,

11-185 ,

11-287

evaluate bandwidth utilization,

6-44

external timing,

6-16

.............................................................

F

fan filter, replace,

13-3

Fast Ethernet packet ring,

11-150

private line,

11-160

fibers, optical clean,

14-34

connect,

14-44

Fibre Channel circuit pack install,

4-74

provision,

4-77

transport service

FC-DPORT,

11-265

FICON,

11-265 ,

11-271

free-running,

6-16

FTAM database backup/restore,

2-150

generic upgrade,

2-40

initial software download,

2-3

FTAM-FTP gateway,

7-28

FTP database backup/restore,

2-123

G

disable server,

14-103

generic upgrade,

2-72

initial software download,

2-21

observe progress,

14-101

FTP/FTTD,

7-28

FTTD database backup/restore,

2-135

enable,

7-28

generic upgrade,

2-109

Function Slots

100/100 FE circuit packs,

4-50

install DS1/E1 circuit pack,

4-39

install DS3/EC1 circuit pack,

4-32

install Fibre Channel circuit packs,

4-74

install Gigabit Ethernet circuit packs,

4-54

install low-speed OCN circuit packs,

4-14

install Resilient Pack Ring

(RPR) circuit packs,

4-54

install TMUX circuit pack,

4-45

provision OCN circuit packs,

4-22

unprotected,

4-26

.............................................................

gateway

FTAM-FTP,

7-28

TCP/IP,

7-49

.................................................................................................................................................................................................................................

IN-4 365-372-301 R6.0

Issue 15, January 2006

GbE circuit packs

802.1q Mode,

11-18 ,

11-106 ,

11-134

dedicated multiple point,

11-140

install,

4-54

NOTAG Mode,

11-11 ,

11-99

provision,

4-59

Transparent Mode,

11-28 ,

11-115

generic upgrade

FTAM,

2-40

FTP,

2-72

FTTD,

2-109

GNE, TCP/IP,

7-49

ground strap, ESD,

1-14

guidelines password,

7-10

TID,

7-38

user login,

7-12

.............................................................

H

hairpin cross-connections

Ethernet,

11-150

TDM,

10-22

high-density electrical circuit packs,

4-37 ,

4-42

history log,

7-28

.............................................................

I

IAO LAN ports disable/enable OSI,

7-39

provision,

7-46 ,

7-49

idle channel signal,

6-7

inhibit, autonomous messages,

7-24

Index initial installation

FTAM,

FTP, initialize

2-3

2-21

OC-48 LNW26B-type circuit packs),

4-84

.............................................................

L

LAN ports disable/enable,

7-39

low-speed electrical circuit packs upgrade,

12-318

optical line test,

14-64

.............................................................

circuit pack,

14-108

SYSCTL,

14-105

install

100/100 FE circuit packs,

4-50

DS1/E1 circuit pack,

4-39

DS3/EC1 circuit pack,

4-32

Fibre Channel circuit pack,

4-74

enable/disable,

11-237

lasers classes,

1-10

eye damage,

1-10

safety,

1-6

warning labels,

1-12

LBOs

M

MAC address,

11-228

main controller, install,

4-4

maintenance state, pluggable transmission module,

13-25

manual adjacencies, TARP,

7-43

manual ring map,

9-63

GbE circuit packs,

4-54

high-speed OCN circuit packs,

4-7

high-speed switch circuit packs,

4-72

LBOs,

14-54

low-speed OCN circuit packs,

4-14

pluggable transmission module,

4-62

Resilient Pack Ring (RPR) circuit packs,

4-54

switch circuit packs,

4-72

SYSCTL,

4-4

clean,

14-34

install,

7-40

line timing, linear cross-connections,

LNW2 circuit pack, install,

10-64

14-54

LC adapters, clean,

14-34

LCAS,

11-249

LED test,

14-88

Level 2 routing capabilities,

6-16

10-26

4-4

locked DSN cross-connections, manuals,

xxxix

miscellaneous discretes,

6-11

mode switching, timing,

6-16

modem, modify

14-138

SNMP user login,

7-20

user login,

7-12

.............................................................

N

network card, change,

14-110

network element login, change,

7-12

password, change own,

7-10

network layer,

7-40

TMUX circuit pack,

4-45

WaveStar CIT,

14-4

IP over DCC,

IP routes,

9-113

IP tunneling,

6-13

9-113

.............................................................

J

jumper settings

DS3/EC1 circuit pack,

4-32

lockout nonprivileged user logins,

7-16

threshold, log out, user, loopbacks

Ethernet,

7-61

7-63

login banner, create/edit, logs, security/history,

11-235

7-26

7-28

network synchronization,

6-16

network time protocol,

7-33

network turnup add node to UPSR/BLSR,

9-29

discontinue node from

UPSR/BLSR,

9-48

equip,

5-3

establish dual-homed network,

9-84

operate/release,

14-97

optical,

14-56

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

IN-5

Index establish high-speed 1+1/

UPSR/BLSR, network,

9-76

9-3

establish low-speed 1+1 protected optical extension,

9-69

establish low-speed 1+1 unprotected optical extension,

9-132

establish OC-48 0x1 unprotected extension,

9-93

establish single-homed establish subtending low-speed UPSR/BLSR,

9-98

provision manual ring map,

9-63

normal jumper (LNW26B-type circuit packs),

4-84

NOTAG Mode,

11-11 ,

11-99

NSAP address,

7-40

NUT, packet ring,

11-124

NVMs, SYSCTL,

4-82

.............................................................

O

OC-12 UPSR to OC-48 UPSR upgrade,

12-52

OC-3 UPSR to OC-12 UPSR upgrade,

12-32

OC-3/12 dual-homed,

10-39

single-homed,

10-32

OC-48 BLSR to OC-192 BLSR upgrade,

12-223

OC-48 UPSR to OC-192 UPSR upgrade,

12-144

OCN circuit packs install high-speed OCN circuit packs,

4-7

.............................................................

P

install low-speed OCN circuit packs,

4-14

optical line test,

14-61

provision,

4-22

optical facility, verification,

14-44

optical fibers clean,

14-34

connect,

14-44

optical loopbacks,

14-97

optimize backplane bandwidth,

6-46

OS types define,

7-57

serial ports,

7-54

OSI LAN management,

OSI over DCC, packet ring

6-13

7-39

802.1q Mode,

11-46 ,

11-64

BLSR protected,

11-124

establish,

11-37 ,

11-51 ,

11-55 ,

11-313

hairpin,

11-150

Transparent Mode,

11-68

password, change,

7-10

path cost,

11-223

performance monitoring clear TCA counts,

8-17

initialize PM registers,

8-5

provision PM settings,

8-8

provision PM thresholds,

8-4

provisionable parameters,

A-30

schedule PM reports,

8-14

view PM reports,

8-11

view PM settings,

8-7

view PM thresholds,

8-3

pluggable transmission module clean,

14-135

enter/exit maintenance state,

13-25

install,

4-62

provision,

4-80

point-to-point, BLSR protected

802.1q Mode,

11-106 ,

11-134

NOTAG Mode,

11-99

Transparent Mode,

11-115

point-to-point, UPSR protected

802.1q Mode,

11-18 ,

11-134

NOTAG Mode,

11-11

private line,

11-160 ,

11-257

Transparent Mode,

11-28

port configuration,

11-96

port, provisionable parameters,

A-2

potential sources of danger,

1-4

private line Ethernet service

10/100-PL,

10/100-T/F,

BLSR,

11-160

11-99

11-257

point-to-point,

11-11

propagation, TARP,

7-43

protection priority,

6-7

provision

0x1S1 or 0x1S2 unprotected application,

4-26

.................................................................................................................................................................................................................................

IN-6 365-372-301 R6.0

Issue 15, January 2006

Index alarm severity assignment profile (ASAP),

6-34

DATA port parameters,

11-273

DATA VCG parameters,

11-277

DS1/E1 circuit pack,

4-42

DS3/EC-1 port,

4-37

Ethernet circuit pack,

4-59

Ethernet LAN port parameters,

11-72

Ethernet VCG parameters,

11-86

Fibre Channel circuit pack,

4-77

manual ring map,

9-63

NVMs,

4-82

OCN circuit packs,

4-22

pluggable transmission modules,

4-80

PM settings,

8-8

PM thresholds,

8-4

RPR parameters,

11-301

RPR VCGs,

11-297

static IP routes on DCC links,

7-52

STS-n/VT1.5,

4-83

synchronization,

6-16

TCP/IP,

7-46

TCP/IP gateway,

7-49

TMUX ports,

4-48

unprotected OCN ports,

4-26

unprotected operation in a low-speed Function group,

4-26

provisionable parameters channel,

A-6

cross-connection,

A-26

Data,

A-24

Data circuit packs,

11-271

Ethernet circuit packs,

11-96

Ethernet QoS,

11-244

Ethernet/VLAN,

A-7

operations,

A-31

optional,

A-45

performance monitoring,

A-30

port,

A-2

security,

A-41

synchronization,

A-28

.............................................................

Q

Q in Q,

11-230

QoS provision,

11-238 ,

11-323

provisionable parameters,

11-244

.............................................................

R

remote NE status,

7-28

remove, LBOs,

14-54

replace fan filter,

13-3

SYSCTL,

12-325

reset circuit pack,

14-108

system,

14-105

resilent packet ring,

11-313

Resilient Pack Ring (RPR) install circuit pack,

4-54

Resilient Packet Ring (RPR) parameters,

11-301

VCG parameters,

11-297

restore, database

FTAM,

2-150

FTP,

2-123

FTTD,

2-135

roll cross-connections,

10-48 ,

11-305

.............................................................

S

safety instructions electrostatic discharge,

1-14

enclosed systems,

1-11

general notes,

1-4

important,

1-17

laser,

1-6 ,

1-12

special,

1-4

SAN transport service

FC-DPORT SAN,

11-265

STS-1 cross-connections,

11-280

schedule automatic backup

FTP,

2-123

FTTD,

2-135

schedule PM reports,

8-14

security lockout logins,

7-16

log,

7-28

provisionable parameters,

A-41

user login/password,

7-10

serial ports,

7-54

set date and time,

7-33

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

IN-7

Index

NE defaults,

7-28

system TID,

7-38

shelf parameters,

6-7

test,

3-3

signal degrade/threshold settings,

6-7

single-homed cross-connections,

10-32

SNMP edit/delete/enter users,

7-20

provision management functions,

7-17

software apply,

2-120

copy,

14-4

FTAM, initial installation,

2-3

FTAM, upgrade,

2-40

FTP, initial installation,

2-21

FTP, upgrade,

2-72

FTTD, upgrade,

2-109

remote, copy generic,

2-115

view release,

14-90

spanning tree change configuration,

11-223

create,

11-216

packet ring,

11-37 ,

11-51 ,

11-55

stand-alone shelf, accept,

3-3

STS-1 cross-connections

Ethernet service,

11-195 ,

11-207

SAN transport service,

11-280

UPSR,

10-16

suspend

OC-12 UPSR to OC-48

UPSR upgrade,

12-130

OC-48 BLSR to OC-192

BLSR upgrade,

12-294

OC-48 UPSR to OC-192

UPSR upgrade,

12-214

switch circuit packs, install,

4-72

synchronization date and time,

7-33

provision,

6-16

provisionable parameters,

A-28

SYSCTL install,

4-4

replace,

12-325

system date and time,

7-33

login banner,

7-26

NE defaults,

7-28

parameters,

6-3

password,

7-10

reports,

14-131

TCP/IP gateway,

7-49

test,

3-9

TID,

7-38

.............................................................

T

TARP,

7-43

TCA counts, clear,

8-17

TCP/IP,

7-46

TCP/IP gateway,

7-49

test end-to-end system,

3-9

.................................................................................................................................................................................................................................

IN-8 365-372-301 R6.0

Issue 15, January 2006

LEDs,

14-88

protection switching,

14-86

stand-alone shelf,

3-3

test access change existing session,

14-127

delete session,

14-129

establish session in MONEF mode,

14-114

establish session in SPLT(E or EF) mode,

14-121

view session,

14-130

thresholds, NSAP count,

7-40

TID, set,

7-38

time and date, set,

7-33

timeout, serial ports,

7-54

timing, system,

6-16

TL1 autonomous message map,

7-57

types, serial ports,

7-54

TMUX circuit pack install,

4-45

provision ports,

4-48

transmission tests

DS1/E1,

14-67

DS3,

14-74

EC-1,

14-80

Transparent Mode dedicated multiple point,

11-140

MAC Address,

11-228

packet ring,

11-37 ,

11-51 ,

11-68

point-to-point, BLSR protected,

11-115

Index point-to-point, UPSR protected,

11-28

resilient packet ring,

11-313

turnup node,

5-3

.............................................................

U

unprotected, OCN ports,

4-26

upgrades back out high-speed OC-48

OLIU upgrade,

12-19

back out OC-12 UPSR to

OC-48 UPSR upgrade,

12-93

back out OC-3 UPSR to

OC-12 UPSR upgrade,

12-42

back out OC-48 BLSR to

OC-192 BLSR upgrade,

12-262

back out OC-48 UPSR to

OC-192 UPSR upgrade,

12-182

high-speed OC-48 OLIUs in

UPSR/BLSR,

12-4

low-speed electrical circuit packs,

12-318

OC-12 UPSR to OC-48

UPSR,

12-52

OC-3 UPSR to OC-12

UPSR,

12-32

OC-48 BLSR to OC-192

BLSR,

12-223

OC-48 UPSR to OC-192

UPSR,

12-144

suspend OC-12 UPSR to

OC-48 UPSR upgrade,

12-130

suspend OC-48 BLSR to

OC-192 BLSR upgrade,

12-294

suspend OC-48 UPSR to

OC-192 UPSR upgrade,

12-214

UPSR

10/100-PL,

11-160

10/100-T/F,

11-257

cross-connections,

10-16

establish Ethernet packet ring,

11-37 ,

11-51

establish resilent packet ring,

11-313

user login disable/enable,

7-59

edit/delete/enter,

7-12

enable/lockout all,

7-16

lockout aging period,

7-61

lockout threshold,

7-61

log out,

7-63

.............................................................

V

video broadcast

BLSR,

11-185

multi-channel,

11-287

UPSR,

11-168

view

PM reports,

8-11

PM settings,

8-7

PM thresholds,

8-3

virtual concatenation (vt_vcat),

11-96

VLAN provisionable parameters,

A-7

VLAN tagging modes

(vlantagmd),

11-96

VT1.5 cross-connections,

10-16 ,

10-71

.............................................................

W

warning labels, laser,

1-12

WaveStar CIT connect and establish session,

14-24

install,

14-4

using,

xxxviii

.................................................................................................................................................................................................................................

365-372-301 R6.0

Issue 15, January 2006

IN-9