nortel tn-16

323-1211-224

SDH Transmission

TN-16XSystem Expansion Procedures

Release 4.2 Standard March 1997

323-1211-224 Release 4.2 Standard TN-16X System Expansion Procedures

SDH Transmission

TN-16X

System Expansion Procedures

Copyright Coypright statement Country of printing NT confidential NTE disclaimer Trademarks

Copyright

1994 - 1997 Northern Telecom

The copyright of this document is the property of Northern Telecom. Without the written consent of Northern Telecom, given by contract or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person whatsoever.

Printed in England

NORTHERN TELECOM CONFIDENTIAL:

The information contained in this document is the property of Northern Telecom. Except as specifically authorized in writing by Northern Telecom, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation, and maintenance purposes only.

So far as Northern Telecom is aware the contents of this document are correct. However, such contents have been obtained from a variety of sources and Northern Telecom can give no warranty or undertaking and make no representation as to their accuracy. In particular, Northern Telecom hereby expressly excludes liability for any form of consequential, indirect or special loss, and for loss of data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein or any third party arising out of the contents of this document.

Document Number: 323-1211-224Document Status: StandardProduct Release Number: 4.2Date: March 1997

iii

Publication historyMarch 1997

Release 4.2 Standard introduces the following TN-16X features:

• 34Mbit/s unprotected tributary card which maps three 34Mbit/s pleisochronous signals to a single AU4 signal.

• VC3 Drop and Continue

• Path Trace functionality at VC3 level which enables path overhead validation at the signal termination point.

• OSI (Q3) interface extended to support 34M (or VC3) equipment provisioning.

Recovery Procedures, 323-1211-545, Routine Maintenance Procedures, 323-1211-546 and Module Replacement Procedures, 323-1211-547 have been combined into a single NTP Replacement and Recovery Procedures, 323-1211-547.

October 1996Release 4.1 Standard includes the TN-16X features listed below for the preliminary release.

One new NTP has been added to the document set; Planning and Ordering Information 323-1211-152.

May 1996Release 4.1 Preliminary introduces the following TN-16X features:

• Optical tributaries at the STM-1 rate with 1+1 protection

• OSI (Q3) interface (for STM-1o) to an external Operation System Function

• A new OPC tool, Release installation utility, used during in-service upgrades of the system software.

• The minimum time period for performance monitoring statistics is now 15 minutes

• Earthquake protected rack


iv

April 1996Release 3.1 Standard introduces the following TN-16X features:

• 1:N Linear protection shelf with extra traffic on the protection channel

• Orderwire on linear systems

• STM-16e Receiver and Transmitter interfaces

• Optical tributaries at the STM4 rate with 1+1 protection.

• External synchronisation interface at 2 MHz.

• OSI Q3 interface to an external Operation System Function.

One new NTP has been added to the document set; OSI (Q3) Interface description 323-1211-191.

November 1995Release 3 Standard introduces the following TN-16X features:

• High performance transmitters on ring and regenerator nodes

• Optical post amplifiers on ring and regenerator node

The Master Topical Index, 323-1211-002 and List of Terms, 323-1211-850 have been incorporated into the About the TN-16X Documentation Suite, 323-1211-090 NTP.

June 1995Release 2 Standard introduces the following TN-16X features:

• VC4e tributary card supporting either 140Mbit/s pleisochronous or STM1e SDH signals.

• Regenerator shelves for SP Ring configurations at 1557 and 1310 nm.

• Interoperability between TN-16X and TN-1X products at the OSI network layer.

• Ring transmitter with 1310 nm optics.

Two new NTPs have been added to the document set; System expansion procedures, 323-1211-224 and Common procedures, 323-1211-846.

December 1994Release 1 Standard.

End of chapter file

TN-16X System Expansion Procedures 323-1211-224 Release 4.2 Standard

v

ContentsAbout this document ixAudience ixEMC conformance ix

Technical support and information xv

Chapter 1: Observing safety guidelines 1-1Circuit packs 1-2

Static electricity 1-2Handling, installing, or replacing circuit packs 1-2Storing circuit packs 1-3Transporting circuit packs 1-3

Software tapes 1-3Single-fibre cables 1-3Safety performance 1-4Equipment warning label 1-5

Chapter 2: Pre- and post-expansion system verification 2-1Task list 2-1

Chapter 3: OPC span-of-control expansion procedures 3-1Spans of control, CNet, and SDH SDCC 3-1Adding new spans of control for existing systems 3-2Adding a network element to an existing span of control 3-3Deleting network elements from spans of control 3-3Span-of-control add/delete list 3-3Procedure list 3-4

Chapter 4: Expansion of a TN-16X ring 4-1Renumbering a TN-16X ring ADM 4-1Equipment used in an MS SPRing 4-2Summary of processes 4-2

Chapter 5: Adding and removing tributaries 5-1Provisioning rules for tributaries 5-1Task lists 5-3

Adding a new STM-1e or STM-1e/140M interface to an in-service system 5-3Adding a new 34M interface to an in-service system 5-3Converting between STM-1e and STM-1e/140M tributaries 5-3Adding a new STM-1o interface to an in-service system 5-3Adding a new STM-4o interface to an in-service system 5-4Converting a quadrant from STM-4o to another tributary type 5-4


vi

Contents

Chapter 6: Expansion of a 1:N linear system 6-1Adding a working channel to an existing 1:N system 6-1

Chapter 7: Converting to the 2MHz ESI circuit pack 7-1General description 7-1

Equipment 7-1Required equipment 7-1Preparations 7-21.5 Mbit/s to 2 MHz ESI replacement procedures 7-2

Action 7-7

Index 8-1

FiguresFigure 4-1 Operate forced switches on span A-B 4-6Figure 4-2 ADM node fiber cabling 4-11Figure 4-3 Example 1: Regenerators between the new ADM node and the

ring 4-12Figure 4-4 Operate forced switches on span A-B 4-32Figure 4-5 ADM node fiber cabling 4-33Figure 4-6 Example 2: Regenerators between ADM nodes A and D 4-34Figure 4-7 Operating forced switches on span A-B 4-38Figure 4-8 Regenerator fiber cabling 4-40Figure 4-9 Cabling in a new regenerator between ADM nodes 4-42Figure 4-10 Cabling in a new regenerator between regenerators 4-42Figure 4-11 Removing a regenerator 4-47Figure 4-12 Remove the regenerator 4-50Figure 4-13 Cabling a regenerator between ADM nodes 4-51Figure 4-14 Cabling two regenerators between ADM nodes 4-51Figure 5-1 An example of the test setup when adding 140M or STM-1e

tributaries to an TN-16X system 5-6Figure 5-2 An example of the test setup when adding STM-1o or STM-4o

tributaries to a TN-16X system 5-19

TablesTable 4-1 Adding an ADM node 4-2Table 4-2 Deleting an ADM node 4-3Table 4-3 Adding a regenerator 4-3Table 4-4 Deleting a regenerator 4-4Table 4-5 Replacing a regenerator with an ADM node 4-5Table 5-1 Group, and quadrant mapping for 140M, STM-1e, STM-1o and

STM-4o equipment 5-31Table 6-1 Task list——Adding a working channel to a 1:N system 6-1Table 7-1 Required equipment 7-1

ProceduresProcedure 2-1 Performing the pre-expansion system verification 2-2Procedure 2-2 Performing the post-expansion system verification 2-7Procedure 3-1 Determining OPC and Network element software loads 3-5Procedure 3-2 Adding a network element to an existing span of control 3-8Procedure 3-3 Moving an in-service network element to a new span of

control 3-12


Contents

vii

Procedure 3-4 Moving an OPC to another shelf location 3-18Procedure 3-5 Decommissioning a network element 3-25Procedure 4-1 Adding a new ADM node into an existing in-service ring 4-8Procedure 4-2 Removing an ADM node from an in-service ring 4-23Procedure 4-3 Adding a new regenerator into an in-service ring 4-39Procedure 4-4 Removing a regenerator from a ring 4-48Procedure 5-1 Setting up the equipment for the STM-1e or 140M tributary

tests 5-8Procedure 5-2 Measuring the 140M or STM-1e end-to-end timed bit error rate

(BER) 5-11Procedure 5-3 Converting between STM1e and VC4e tributaries 5-15Procedure 5-4 Measure optical output power 5-17Procedure 5-5 Setting up the equipment for testing STM-1o or STM-4o

tributaries 5-21Procedure 5-6 Testing continuity on equipped STM-1 or STM-4 interface

slots 5-24Procedure 5-7 Converting a quadrant to use STM-4o tributaries 5-26Procedure 5-8 Converting a quadrant from STM-4o to any other tributary

type 5-29Procedure 6-1 Connecting a new shelf into a protection loop 6-5Procedure 7-1 Converting a shelf which uses BITS timing 7-3Procedure 7-2 Converting a shelf which uses Line timing 7-7Procedure 7-3 Recovering from a failed 2 Mhz ESI upgrade 7-9


ix

About this documentThis document provides recommended expansion procedures for existing in-service TN-16X network elements. The procedures are designed to add equipment to or remove equipment from the system without interrupting service. It covers such procedures as the following:

• changing spans of control for the operations controller (OPC)

• adding add-drop multiplexer (ADM) nodes and regenerators to (and removing them from) an existing MS SPRing

• adding tributaries to an existing system and converting from one type of tributary to another

Flowcharts and task lists provided in the revelant chapters to describe the basic process that is followed during an in-service upgrade. These procedures assume that any new equipment required for expansion has been installed according to Installation Procedures, 323-1211-201.

AudienceThis document is intended for the following people:

• installers

• system lineup and test (SLAT) engineers/technicians

• provisioners

• maintenance engineers

EMC conformance

This product/product family complies with the provisions of the low voltage directive 73/23/EEC, and essential protection requirements of the EMC Directive 89/336/EEC as amended by 92/31/EEC and 93/68/EEC, when it is properly installed and maintained and when it is used for the purposes for which it is intended.


Code: AG5293Issue: 2

Template: v4;961216

S

WSe

S

S

Th

S

S

D

Po

Si

D

Thm

Th

S

DN

8 9 7 9

Declaration of Conformity

uppliers Name & Address: Nortel Limited, of Doagh Road, Newtownabbey,County Antrim, Northern Ireland, BT36 6XA

e hereby declare that the products identified in Section 1 comply with the standards listed in ction 2 and fulfil our obligations under the EU Directives listed in Section 3.

ection 1 - Products Covered

ection 2 - Standards Applied

e Product(s) described above is in conformity with the following standards:

ection 3 - European Union Directives

ection 4 - Authority of Issuer

eclaration Issued By: Peter Schuddeboom John Freebairn

sition of Issuer: AVP, Technology ITN Manufacturing Quality Manager

gned:

ate:

e instructions for installation, use and maintenance form part of the product compliance and ust be observed.

Product Name Product TypeFibreWorld TN-16x ADM / LTE Permissible configurations which use TN-16x

Shelf Assembly NTFW50AA mounted in Rack NTFW70AA or NTFW70AB

tdsRef

Standard Number Edition Subject of Standard

1 EN55022 1995 Emissions from IT Equipment1 EN50082-1 1992 Generic Immunity2 EN60950 1992 Safety of IT equipment2 EN60825-1 1994 Safety of Laser Products

irectiveumber

Abbreviated Directive Title StdsRef

CE Marking Information

(if applicable)9/336/EEC EMC Directive 1 n/a2/31/EEC Amendment to EMC Directive n/a n/a3/23/EEC Low Voltage Directive 2 973/68/EEC CE Marking Amending Directive n/a n/a

is declaration has been made in accordance with ISO/IEC Guide 22, General criteria for suppliers' declaration of conformity

Code: AG5294Issue: 2

Template: v4;961216

Declaration of Conformity

Suppliers Name & Address: Nortel Limited, of Doagh Road, Newtownabbey,County Antrim, Northern Ireland, BT36 6XA

We hereby declare that the products identified in Section 1 comply with the standards listed in Section 2 and fulfil our obligations under the EU Directives listed in Section 3.

Section 1 - Products Covered

Section 2 - Standards Applied

The Product(s) described above is in conformity with the following standards:

Section 3 - European Union Directives

Section 4 - Authority of Issuer

Declaration Issued By: Peter Schuddeboom John Freebairn

Position of Issuer: AVP, Technology ITN Manufacturing Quality Manager

Signed:

Date:

The instructions for installation, use and maintenance form part of the product compliance and must be observed.

Product Name Product TypeFibreWorld TN-16x REGEN Permissible configurations which use TN-16x

Shelf Assembly NTFW51AA mounted in Rack NTFW71AA or NTFW71AB

StdsRef

Standard Number Edition Subject of Standard

1 EN55022 1995 Emissions from IT Equipment1 EN50082-1 1992 Generic Immunity2 EN60950 1992 Safety of IT equipment2 EN60825-1 1994 Safety of Laser Products

DirectiveNumber

Abbreviated Directive Title StdsRef

CE Marking Information

(if applicable) 89/336/EEC EMC Directive 1 n/a 92/31/EEC Amendment to EMC Directive n/a n/a 73/23/EEC Low Voltage Directive 2 97 93/68/EEC CE Marking Amending Directive n/a n/a

This declaration has been made in accordance with ISO/IEC Guide 22, General criteria for suppliers' declaration of conformity

xv

Technical support and informationNortel provides a comprehensive technical support service for its customers. The Nortel Service Desk may be contacted between the hours of 8 30 am and 5 pm (UK local time), Monday to Friday, using the following FAX or telephone numbers:

United KingdomFreephone: 0800 626 881Telephone 0181 361 4693FAX: 0181 945 3456

InternationalTel: +44 181 361 4693FAX: +44 181 945 3456

Access to assistance from the Customer Service Desk 24-hour helpline can be provided and is subject to a suitable Support Agreement being in place.

To discuss Technical Support services, please contact the Technical Support Hotline on 0181 945 3525.

End of chapter file


1-1

1

Chapter 1: Observing safety guidelinesThis chapter contains safety guidelines that should be followed for personal safety and for the proper handling and operation of equipment.

Warnings and safety precautionsTo avoid injury, follow all warning notices provided with this product, as well as the safety procedures established by your company.

To avoid damage to equipment or service interruptions, follow all caution notices provided with this product, as well as the safety procedures established by your company.

In this documentation, warning and caution notices look like the following.

WARNINGA warning notice with this symbol indicates a risk of personal injury.

WARNINGA warning notice with this symbol indicates a risk of personal injury due to an electrical hazard.

WARNINGA warning notice with this symbol indicates a risk of personal injury due to a laser hazard.


1-2

Observing safety guidelines

Circuit packsAll circuit packs are subject to damage by rough handling or from electrostatic discharge. Adhere to the following procedures to avoid damaging the circuit packs.

Static electricityIt is usual for static electricity charges to build up on your body if you walk a short distance. This buildup of static electricity is sufficient to damage a circuit pack. Therefore, when working on a shelf, on cables connected to a circuit pack, or on a circuit pack itself, always wear a skin-contact ground strap or other suitable personal grounding device.

Ground straps can be the expandable-wrist type; connect the grounding cord to the ground plug provided on the local craft access panel (LCAP).

FW00445A

Alternatively, your company may provide antistatic protection by mounting the bays on conductive floor coverings, and providing conductive shoes or heel grounders to all personnel.

Handling, installing, or replacing circuit packsWhen handling, installing, or replacing circuit packs, you must observe the following precautions:

• Wear a wrist strap or other static-grounding device before removing a circuit pack from its package or from a shelf.

CAUTIONA caution notice with this symbol indicates that there is a risk to equipment or loss of data.

CAUTIONA caution notice with this symbol alerts you to use anti-static protection to avoid damaging circuit packs.

ESD Groundjack



1-3

1

• Place each circuit pack in an antistatic bag when it is not mounted in a shelf.

• Handle each circuit pack by the faceplate or stiffener.

• Do not touch the solder side of the circuit pack, the pin connector, or the components.

• Do not stack circuit packs on or against each other.

• Do not force circuit packs into their packaging material.

• Protect all optical connectors of the transmit and receive optical circuit packs by covering them with clean dust caps at all times.

Storing circuit packsSpare circuit packs must be left in the original shipping container until required. To prevent damage to circuit packs while in storage, you must observe procedures that prevent the following:

• accumulation of dirt or dust on the pin connectors

• damage to the board or its components

• board warpage (to boards stored in areas where the humidity can exceed 95% and the temperature can exceed 70°C)

Transporting circuit packsWhen transporting circuit packs, pack each circuit pack in its original antistatic shielding bag, padding, and box. If the original material is lost, use other suitable material to prevent damage in transit.

Software tapesAll software tapes are subject to damage by rough handling or from electrostatic discharge. When handling or installing software tapes, you must observe the following precautions:

• Wear a wrist strap or other static-grounding device before removing a software tape from its package or from an OPC.

• Place each software tape in its case when it is not mounted in an OPC tape drive.

• Do not touch the bare tape in the cassette.

• Inspect all tape cassettes for damage before sliding them into the OPC tape drive.

• Do not force tape cassettes into the OPC tape drive.

• Before inserting any cassette tape into an OPC tape drive, allow the cassette tape to come to room temperature.

Single-fibre cables The following precautions must be taken when working with single-fibre cables:

• Safety glasses must be worn when installing optical fibres.


1-4


• Small bits of glass fibre are almost invisible. After handling single fibre cables, hands should always be wiped clean or washed before making any contact with the eyes.

• Handle optical fibres carefully and always position them in a safe and secure location during installation.

• Do not handle pieces of cut fibre with bare fingers. Use tweezers, or the sticky side of a piece of vinyl tape, to pick up and discard any loose fibre ends.

• All fibre cuttings should be placed in a plastic bottle provided for that purpose.

• Single-fibre optical connectors must be protected by dust caps at all times.0

Safety performance Under normal operating conditions the transmit interface circuit packs comply with EN60825 Class 3A.These regulations ensure that no personnel hazards exist, as a result of the laser transmitter, when the system is in its normal operating configuration.

Under certain fault conditions laser radiation within the limits of Class 3A may be present. This level of radiation is of sufficient magnitude to cause injury to personnel and caution must be exercised to avoid exposure. This precaution applies to any point in the system where the laser signal can be ‘accessed’ (for example, at the optical connectors of the receive interface circuit packs).

WARNINGRisk of personal injuryIf there is any suspicion of a glass chip in your eye, seek medical attention at once.

A label similar to this is located on all optical interface packs, near the optical connector.

WarningAvoid direct exposure to beam. Invisible light can blind. Keep all optical connectors capped.

TN-16X System
Expansion Procedures 323-1211-224 Release 4.2 Standard


1-5

1

Equipment warning label The equipment warning label is located in the top left corner of the back cover. To allow for worst case fault conditions, the equipment is labelled as Class 3A as follows:

End of chapter file

LASER RADIATIONDO NOT STARE INTO BEAM OR VIEW

DIRECTLY WITH OPTICAL INSTRUMENTSCLASS 3A LASER PRODUCT


2-1

2

Chapter 2: Pre- and post-expansion system verification

This chapter provides verification checks that must be done before and after major system expansion activities. The pre-expansion checks verify that there are no problems on the system prior to the expansion activity that might cause the expansion procedures to fail. The post-expansion checks verify the system after the new equipment or functionality has been added or removed.

Task list

Task Reference

Perform the pre-expansion verification checks Procedure 2-1

Follow the appropriate task list in a subsequent chapter of this document for the expansion process you are doing

Chapters 3 to 5

Perform the post-expansion verification checks Procedure 2-2


2-2 Pre- and post-expansion system verification

Procedure 2-1Performing the pre-expansion system verification 2-1

Use this procedure to verify the existing in-service system before beginning system expansion procedures that involve adding new network elements to the system or removing them from the system. These procedures include the following:

• adding ADM nodes to an in-service ring (see Chapter 4)

• adding regenerators to an in-service ring (see Chapter 4)

• removing ADM nodes from an in-service ring (see Chapter 4)

• removing regenerators from an in-service ring (see Chapter 4)

• adding a working channel to a 1:N system (see Chapter 6)

• upgrading an in-service 1:N system to include extra traffic on the protection channel (see Chapter 6)

RequirementsBefore starting this procedure, you must do the following:

• Connect a VT100-compatible terminal to the primary OPC as described in Common Procedures, 323-1211-846.

• Obtain a userID and password for each network element that is part of the expansion. (The default userID is “admin” with password “admin”.)

• Log in to the primary OPC at the slat security level as described in Common Procedures, 323-1211-846. (The default userID is “slat” with password “slat”.)

• Open the NE Login Manager tool (see Common Procedures, 323-1211-846).

Action

Procedure 2-1Performing the pre-expansion system verification 2-1

Step Action

1 Open the OPC Status tool from the Open Tools list in the User Session Manager window of the OPC. Check that the primary OPC is active and that the backup OPC is inactive. If this is not the case, contact your next level of support or your Nortel Support group.

2 Return to the User Session Manager by pressing Ctrl_T 0.

—continued—


Pre- and post-expansion system verification 2-3

2
3 Check the bottom left corner of the primary OPC’s user interface window.
Ensure that there is no question mark (?) displayed, that is, all associations with the network elements in the span of control are active.

4 Verify that the time and date of the primary and backup OPCs is correct and synchronized. On the OPC user interface, the time is provided in the bottom right corner of the screen. To check the date, use the OPC Date tool.If you need to change the date or time or do not know how to use the OPC Date tool, see Commissioning and Testing Procedures, 323-1211-220, or System Administration Procedures, 323-1211-302.

5 The date and time at the network element is synchronized to that of the OPC, adjusted for a time-zone parameter set at the network element. Using the OPC’s NE Login Manager, log into each network element involved in the upgrade in turn and verify that the date and time of each network element involved in the upgrade are correct (see Commissioning and Testing Procedures, 323-1211-220). The network element time is shown in the bottom left corner of the screen.If the time is Then go tonot correct step 6correct step 7

6 Edit the time zone by entering:equipmnt sh ↵edit ↵timezone <timezone> ↵yes ↵

where<timezone> is the time zone in which the network element is

located. A table with the different time zones isgiven in Commissioning Procedures, 323-1211-220.

7 Verify that the system is alarm free and that there are no active protection switches (that is, the banner line at the bottom of the primary OPC user interface screen shows no counts next to C, M, m, w and ActProt). Clear all active alarms on the system according to Alarm and Trouble Clearing Procedures, 323-1211-543.

8 Using the OPC Event Browser, check whether there have been any transient alarms on any of the network elements in the system during the previous two weeks. A transient alarm is one that is raised and then clears by itself. Look especially for alarms relating to protection switches related to crossed performance-monitoring thresholds. If you don’t know how to use the Event Browser, see Network Surveillance and Monitoring Procedures, 323-1211-510.

—continued—

Procedure 2-1Performing the pre-expansion system verification (continued) 2-1

Step Action



9 Using the OPC NE Login Manager tool, log into each terminal or ADM node in the system and check the performance-monitoring counts for the previous three days. Also check the last 32 15-min timed intervals. Any threshold crossings can indicate a faulty circuit pack or connection. For instructions on how to use the NE Login Manager, see Common Procedures, 323-1211-846. For instructions on how to view performance-monitoring statistics, see Performance Monitoring Procedures, 323-1211-520.Note: You don’t have to check the performance-monitoring statistics at regenerators, except as an aid in troubleshooting the line should you find a problem at an associated terminal or ADM node.

10 Check the data communications performance-monitoring and error statistics for each network element in the system. For instructions, see Performance Monitoring Procedures, 323-1211-520.

11 Using the NE Login Manager, check all network elements for logs that might affect the expansion procedure, particularly any equipment (EQP), software trap, and software error (SWERR) logs. The following are guidelines for taking action on logs:

• Logs with 300-series numbers indicate trouble. For log definitions and corresponding actions to take, see Log Report Procedures, 323-1211-840.

• Any software trap logs present will have an associated “Software trap” alarm. You can query individual network elements for trap logs by entering :logutil ↵ open trap ↵If the system responds with anything other than “log empty”, contact your next level of support or your Nortel support group.

• If any SWERR logs are present, contact Nortel before beginning the expansion procedure. You can query individual network elements for SWERR logs by entering the following commands at the main level of the network element user interface:

open swerr ↵If the system responds with anything other than “log empty”, contact your next level of support or your Nortel support group.

• Correlate any trouble logs with the alarm and performance-monitoring histories to help you understand the problem area. For example, you can correlate a SWERR log with the performance-monitoring history in the same time frame.

—continued—


Step Action



2
12 If you are expanding an existing multishelf 1:N system with extra traffic
being carried on the protection channel, disable the extra traffic according to Commissioning Procedures, 323-1211-220. The STM-16 portion of the protection exerciser routine is not run if the protection channel is carrying extra traffic.

13 Run the protection-switching exerciser for each network element in the system and verify that it runs successfully. The results of the exerciser run are indicated by an EQP603 log. For instructions on how to run the exerciser, see Protection Switching Procedures, 323-1211-311.

14 To check the EQP603 log, enter the following:logutil ↵ open eqp ↵

15 After running the exerciser, disable the automatic exerciser so that a scheduled exerciser run won’t occur during the expansion process (see Protection Switching Procedures, 323-1211-311). If the exerciser runs when the system is in a transitional phase of the process, it might cause unpredictable behavior, possibly affecting traffic.

Note: For the same reason, during the expansion process, do not run the exerciser manually unless explicitly instructed to do so by the expansion procedures

16 If this is a ring, run a ring configuration audit as described in Provisioning and Operations Procedures, 323-1211-310.

17 If the STM connections for the system have been provisioned using the OPC Connection Manager tool (but not the OSI provisioning interface), run a connection audit as described in Provisioning and Operations Procedures, 323-1211-310.

18 Using the NE Login Manager, back up the configuration data to the primary OPC from each network element by entering:equipmnt sh ↵backupdb ↵yes ↵

19 From the Connection Manager tool, transfer the network element data to the OPC. Display the Utilities menu by pressing Ctrl_L T and select the Transfer data to backup OPC command.

20 Clean the tape drive head in for the primary OPC. For instructions, see Routine Maintenance Procedures, 323-1211-546.

—continued—


Step Action



21 Save the primary OPC data to tape. For instructions, see Common Procedures, 323-1211-846.

22 If there has been a recent problem with the primary or backup OPC or if you are adding a span of control, verify the functioning of both OPCs. First check the data on the backup OPC and then shut it down. Then do the same for the primary OPC. For instructions, see Common Procedures, 323-1211-846.

Note: It is recommended that this OPC shutdown verification only be done in the explicit circumstances noted in step 22. This is because OPC shutdowns cause a switch of the monitoring point for the system and add a significant amount of time to the expansion procedure.

—end—


Step Action



2

Procedure 2-2Performing the post-expansion system verification 2-2

Use this procedure to verify system integrity after completing major system expansions such as adding new network elements or removing them from the system.



• Obtain a userID and password for each network element that is part of the expansion. (The default userID is “admin” with password “admin”.)

• Log in to the primary OPC at the slat security level as described in Common Procedures, 323-1211-846. (The default userID is “slat” with password “slat”.)

• Open the NE Login Manager tool, see Common Procedures, 323-1211-846.

Action

Procedure 2-2Performing the post-expansion system verification 2-2

Step Action

1 Check that there are no active alarms or protection switches on the system. If there are, clear them according to Alarm and Trouble Clearing Procedures, 323-1211-543. (The banner line on the bottom of the OPC user interface should show no counts against C, M, m, w, or ActProt.)

2 Open the OPC Status tool from the Open Tools list in the User Session Manager window of the OPC. Check that the primary OPC is active and that the backup OPC is inactive.

3 Check the bottom left corner of the OPC user interface window. Ensure that there is no question mark (?) displayed, that is, all associations with the network elements in the span of control are active.

4 Verify that the date and time of the primary and backup OPCs are correct and synchronized. For instructions, see Common Procedures, 323-1211-846.

5 Run the protection-switching exerciser for each terminal or ADM node in the system and verify that it runs successfully. The results of the exerciser run are indicated by an EQP603 log. For instructions on how to run the exerciser, see Protection Switching Procedures, 323-1211-311.

—continued—



6 To check the EQP603 log, enter the following:logutil ↵ open eqp ↵

7 Using the OPC Event Browser, check whether there are any trouble logs in the third column (Class). If there are trouble logs, resolve them according to Log Report Manual, 323-1211-840. If you don’t know how to use the Event Browser, see Network Surveillance and Monitoring Procedures, 323-1211-510.

8 If you have just expanded a multishelf 1:N system and extra traffic is to be carried on the protection channel, enable the extra traffic according to Commissioning Procedures, 323-1211-220.

9 If you disabled the exerciser scheduler as instructed in the pre-expansion checks, reenable it now , see Protection Switching Procedures, 323-1211-311.

10 If this is a ring, run a ring configuration audit as described in Provisioning and Operations Procedures, 323-1211-310.

11 If the STM connections for the system have been provisioned using the OPC Connection Manager tool (but not the OSI provisioning interface), run a connection audit as described in Provisioning and Operations Procedures, 323-1211-310.

12 Using the NE Login Manager, back up the configuration data to the primary OPC from each network element by entering:equipmnt sh ↵backupdb ↵yes ↵Note: The system maintains two backups, which are overwritten in turn as backups are done (that is, performing a backup overwrites one backup and performing a second backup for that network element causes the second backup copy to be overwritten by the first).

13 Check the logs buffer at each network element to ensure that the backups were successful by entering.logutil ↵ open fwdb ↵ he FWDB logs show the status of the database backup. An FWDB300-series log indicates a problem with the backup.

14 Transfer the OPC data to the inactive (backup) OPC (that is, synchronize the OPCs). For instructions, see Common Procedures, 323-1201-846.

—continued—

Procedure 2-2Performing the post-expansion system verification (continued) 2-2

Step Action



2

End of chapter file

15 Copy the OPC data to tape as described in Common Procedures, 323-1201-846.

16 If there has been a recent problem with the primary or backup OPC, verify the functioning of both OPCs. First check the data on the backup OPC and then shut it down. Then do the same for the primary OPC. For instructions, see Common Procedures, 323-1211-846.Note: Perform step 16 only if one of the OPCs, particularly the primary OPC, is suspected of potentially malfunctioning during the expansion process. This is because OPC shutdowns cause a switch of the monitoring point for the system and add a significant amount of time to the expansion procedure.

—end—

Procedure 2-2Performing the post-expansion system verification (continued) 2-2

Step Action


3-1

3
Chapter 3: OPC span-of-control expansion procedures
This chapter provides procedures related to the span of control of an operations controller (OPC). A span of control is the total number of network elements managed by a single OPC (or primary and backup OPC pair) for operations, administration, maintenance, and provisioning (OAM&P). The following span-of-control expansion tasks can be done using this chapter:

• add network elements to an existing OPC span of control, with the network elements remaining in service

• move an OPC to a different network element

• connect independent systems by way of a SDH data communications channel (DCC) bridge or the control network (CNet)

When adding network elements to a system, a new span of control might have to be established. In such a case, a new primary OPC (and optionally, a backup OPC) must be commissioned.

Each TN-16X shelf can accommodate one OPC. The primary and backup OPCs can be installed in any TN-16X shelf, although engineering rules might suggest that it is better to use one shelf than another in a particular system configuration. For example, in systems interconnected by a SDH DCC bridge, it is suggested that the primary and backup OPCs be installed in the network elements farthest apart. Detailed configuration rules are provided in Technical Specifications, 323-1211-180.

When adding a new span of control, the existing span-of-control configuration might have to be modified. These changes should be done prior to actually adding the new network elements in the expansion procedures discussed in other chapters of this document.

It might be necessary to move the existing OPCs to conform to the final span-of-control configuration. If necessary, the existing OPCs are shut down and moved as the last step of the expansion process.

Spans of control, CNet, and SDH SDCCA span of control can include one or more TN-16X systems.To belong to a single span of control, the network elements must either be interconnected by a SDH section data communications channel (SDCC) over a SDH link or by a


3-2 OPC span-of-control expansion procedures

Fiberworld TN-16X local-area network called the control network (CNet). A CNet connection between two independent systems (that is, systems not interconnected by fiber) is called a SDH DCC bridge.

The SDH DCC is supported over the STM-16 transport line between TN-16X network elements. SDH DCCs can also be enabled for STM-1o or STM-4o tributaries on multiplex section terminating shelves.

CNet connections are used to link all the terminals at one site of a multishelf 1:N system (which is defined as a 1:N protection group). The CNet ensures that OAM&P access is available to all terminals, including during protection switches. CNet connections are also used to link otherwise unconnected network elements at a single site.

As well as linking unrelated systems, CNet connections can provide OAM&P access to regenerator shelves equipped only with STM-16 high performance transmitters and optical amplifier circuit packs, which otherwise cannot access the SDH overhead for OAM&P purposes.

For detailed configuration rules for OPC spans of control, CNets, and SDH SDCCs, refer to Technical Specifications, 323-1211-180.

Adding new spans of control for existing systemsAs existing in-service systems are expanded or as new systems are installed, it can be necessary to add a new span of control.

For each new OPC span of control, you must set up the OPC and enter the system-level data as described in Commissioning and Site Testing Procedures, 323-1211-220. The system-level data includes the system name, network name, OPC (primary and backup) addresses, and network element addresses (for that span of control). When the data has been entered, the primary and backup OPC databases must be synchronized.

If the new span of control contains only existing network elements that must be deleted from another span of control, all commissioning can be performed at the site of the primary OPC. These actions should be performed from the OPC that is designated as the primary OPC for the new span of control. Then perform Procedure 3-3 in this chapter to move the network elements from the old to the new span of control.

If the new span of control contains new network elements (network elements that are not in service and do not belong to an existing span of control), the portable OPC (or, if no portable is available, the primary or backup or a spare OPC) is brought to the site of each new network element. This OPC is used to commission the new network element and download software for the first time. When the network element has been commissioned and tested, add it to the new span of control using Procedure 3-2.


OPC span-of-control expansion procedures 3-3

3

Adding a network element to an existing span of controlTypical conditions under which a network element is added to an existing span of control are the following:

• Connection of two or more independent TN-16X Fiberworld systems under a single OPC span of control. The two systems are connected by a SDH DCC bridge (using CNet connections).

• Converting a non-diversely routed link between network elements to a diversely routed link (that is, the protection fiber uses a different route than the working fiber). The regenerators added for the second route must be added to an OPC span of control.

• Adding a working channel to an existing 1:N protection system. The new terminals and regenerator/optical amplifier shelves must be added to a span of control.

• Adding an add-drop multiplexer (ADM) node to an existing MS SPRing.

• Adding a regenerator/optical amplifier shelf to a system (whether equipped with regenerator circuit packs, STM-16 high-performance transmitters, optical line amplifiers, or any combination of these circuit packs).

All network element shelves being added must have access to an OPC either by way of the SDH overhead from a SDH link (TN-16X, TN-4X or TN-1X) or by a CNet connection and must have a unique network element number within the span of control.

A network element is added in four steps:

• The network element is commissioned according to Commissioning and Site Testing Procedures, 323-1211-220.

• The primary and backup OPC modules are synchronized.

• The commissioning data is backed up to tape.

• If required, the OPCs are moved to a new location.

Deleting network elements from spans of controlNetwork elements can be deleted from spans of control for a number of reasons, such as when a regenerator is replaced with an add-drop multiplexer node or a ring is reconfigured. Removing a network element from a span of control is called decommissioning it. For a procedure on how to decommission a network element, see Procedure 3-5.

Span-of-control add/delete list When reconfiguring spans of control, the network elements being added to and removed from a given span of control should be noted in the add/delete list.



Procedure list

Procedure Reference

Determining OPC and network element software loads

Procedure 3-1 on page 5

Adding a network element to an existing span of control


Moving an in-service network element to a new span of control


Moving an OPC to another shelf location Procedure 3-4 on page 18

Decommissioning a network element Procedure 3-5 on page 24

Add/delete list for a span of control

Primary OPC name:

Current network elements

Network elements to be deleted

Network elements to be added

Current network elements

Network elements to be deleted

Network elements to be added

1 18

2 19

3 20

4 21

5 22

6 23

7 24

8 25

9 26

10 27

11 28

12 29

13 30

14 31

15 32

16 33

17 34



3

Procedure 3-1Determining OPC and network element software loads 3-1

Use this procedure to determine the software loads that are running on the OPCs and all network elements.


• Connect a VT100-compatible terminal to the primary OPC as described in Commissioning and Site Testing Procedures, 323-1211-220.

• Obtain a userID and password for each network element that is commissioned. (The default userID is “admin”, with password “admin”.)

• Log in to the primary OPC at the slat security level as described in Commissioning and Site Testing Procedures, 323-1211-220. (The default userID is “slat”, with password “slat”.)

Action

Procedure 3-1Determining OPC and Network element software loads 3-1

Step Action

1 Open the OPC Commissioning Manager tool. If you don’t know how to do this, see Common Procedures, 323-1211-846.

2 A screen similar to the following is displayed.FW00217A

—continued—

C 0 M 0 m 1 w 2 FailProt0 Lckt0 ActProt0 PrfAlrt0 12:50

1. [ Clear commissioning data ♦ 1]

> .

NE

16

Commissioned network elements:

Utilities

17

System: pp OPC Serial Number: A173e345

2. [ Edit system data ♦ 2]

3. [ Commission new network element ♦ 3]

Type

STM16STM16

Function

Ring ADMRing ADM

Serial Number OPC

A2 4 Occ3c39A2 2 Occ3c48

Primary

4. [ Transfer data to Primary OPC (from SLAT OPC) ♦ 1]

=>

OPC Commissioning Manager (Version OPCAL17AW)

A2 9 Occ3c23Ring ADMSTM1618



The version of software currently running on the OPC is displayed in the top line of the OPC Commissioning Manager screen in the format OPCALxxyy, where xx are numbers and yy are letters. Lower letters and numbers represent older releases of software.

Note: If an older software load is present, upgrade the OPC software load to the new software prior to expansion. See your Nortel representative for the necessary Change Application Procedures (CAPs).

3 Close the OPC Commissioning Manager tool. If you don’t know how to do this, see Common Procedures, 323-1211-846.

4 Log in to one of the network elements that is part of the expansion process as described in Common Procedures, 323-1211-846.

5 Press the return key twice.

A line similar to the following is displayed on the screen:

89/04/01 01:01 ==== TN16XL02AM====

This information indicates the release of the software load on the network element.

Note: 1 The network element software load is presented in the format TN16XLxxyy, where xx are numbers and yy are letters, and lower numbers and letters represent older releases of software. The minimum release of network element software acceptable is TN16XL01AR.

Note: 2 If an older software load is present, upgrade the OPC to the new software prior to expansion.

6 Log out from the network element by entering:

logout ↵

7 Repeat steps 4 through 6 for all existing network elements.

8 Repeat steps 1 through 6 for all existing spans of control that are part of the expansion.

—end—

Procedure 3-1Determining OPC and Network element software loads (continued) 3-1

Step Action



3

Procedure 3-2Adding a network element to an existing span of control 3-2

Use this procedure to add a network element to an existing span of control.


• Consider the OPC engineering rules (and all CNet connections), as described in the Technical Specifications, 323-1211-180.

• Ensure that the new network element is assigned a unique number (1 through 9999). It is important to plan for expected future expansion when assigning numbers, as connections using CNet or STM links can bridge systems. All network elements in the network must have a unique network element number.

• Connect a VT100-compatible terminal to the primary OPC in the new span of control according to Common Procedures, 323-1211-846.

• Obtain a userID and password for each network element that is to be moved. (The default userID is “admin”, with password “admin”.)

• Log in to the primary OPCs at the slat security level in both spans of control according to Common Procedures, 323-1211-846. (The default userID is “slat” with password “slat”.)

Note 1: All the terminal shelves in a protection group of a 1:N system must be connected by way of a control network (CNet) local-area network. Similarly, the regenerator/optical amplifier shelves at each regenerator site must be interconnected by CNet. In a 1:N system, the protection shelf is an independent network element that must also be part of the span of control for the 1:N protection groups.

Note 2: If the new network element does not have CNet access to the primary OPC (such as in the case of a new network element being added to a ring, you can use the backup, a spare, or a portable OPC to do the commissioning.

CAUTIONRisk of service interruptionThe network element that is to be added to the span of control cannot be in service. Performing this procedure on an in-service network element can result in a service interruption.



Tools

Action

1 portable OPC

1 blank DDS tape

as required CNet cable, 9-pin D-sub (Male) to 9-pin D-sub (Male)

1 CNet terminator plugs

1 VT100-compatible terminal with user interface cable

Procedure 3-2Adding a network element to an existing span of control 3-2

Step Action

1 If the network element that is to be commissioned is at the same site as the primary OPC and a CNet connection exists (for example, a CNet cable is used to connect the new network element to the shelf in which the primary OPC is located), continue with step 2. Otherwise, proceed to step 4.

2 Connect a VT100-compatible terminal to the primary OPC as described in Common Procedures, 323-1211-846.

3 Log into the primary OPC using the “slat” userID (with the default password “slat”). Proceed to step 9.

4 If the new network element does not have CNet access to the primary OPC, it is necessary to take the backup, a spare, or a portable OPC to the site to commission the new network element. If you are using a spare or a portable OPC, ensure that it contains the current software release. For instructions on how to download software, see Software Administration Procedures, 323-1211-304.

5 If the primary OPC is not yet commissioned, enter the system-level data for the OPC as described in Commissioning Procedures, 323-1201-220.

6 Take the backup, spare, or portable OPC to the site of the new network element.

7 Set up the backup, spare, or portable OPC to commission the new site. That is, either insert the backup or spare OPC in the dedicated OPC slots of the new network element shelf (or a shelf with available slots that is connected to the new network element shelf by a CNet cable) or connect the portable OPC to the shelf as described in Common Procedures, 323-1211-846.

—continued—



3

8 Log into the backup, spare, or portable OPC using the “slat” userID (with the default password “slat”).

9 Select the OPC Commissioning Manager from the Available Tools list.

The OPC Commissioning Manager main window is displayed. FW00217A

10 Commission the new network element as described in Commissioning and Site Testing Procedures, 323-1211-220.

Note; Ensure that the network element number assigned to the new network element is unique within the span of control. You can view the list of network element numbers already used in the span of control by typing listnodes from the network element user interface.

11 Download the software to the new network element as described in Commissioning and Site Testing Procedures, 323-1211-220.

12 Do the basic provisioning of the network element facilities and other features as described in Commissioning and Site Testing Procedures, 323-1211-220.

13 Save the new commissioning data to a backup tape, as described in Common Procedures, 323-1211-846.

14 If you are using the backup, a spare, or a portable OPC, shut it down and remove it from the network element as described in Common Procedures, 323-1211-846.

—continued—

Procedure 3-2Adding a network element to an existing span of control (continued) 3-2

Step Action



> .

NE

16


Utilities

17




Type

STM16STM16

Function

Ring ADMRing ADM

Serial Number OPC


Primary


=>





15 Record the commissioning data changes on the Commissioning Data Record form for the site. If there is no existing form which you can update, you can use a copy of the blank form at the end of this chapter.

16 Perform the necessary site tests for the new network element according to Site Testing Procedures, 323-1211-220.

17 If there is another network element to add to the span of control, repeat steps 1 to 16 for that network element.

18 If so directed by the task list for the overall expansion or upgrade process you are following, perform the necessary system tests for the new network element.

19 As soon as data communications association is established between the new network element and the primary OPC, perform a manual backup of the network element database to the primary OPC by entering at the network element user interface:

equipmnt sh ↵ backupdb ↵ yes ↵

20 If you used a portable, spare, or backup OPC and all new network elements have been commissioned, return to the site of the primary OPC and manually enter the new network element commissioning data for the new network element or network elements in the Commissioning Manager tool of the primary OPC as described in Commissioning and Site Testing Procedures, 323-1211-220.

Note: Although this repeats the network element commissioning procedure done at the site, it ensures that any data changes made on the primary OPC database for other purposes while the commissioning task was ongoing are not overwritten. That is, rather than overwrite the complete database of the primary OPC with the data from the spare, backup, or portable OPC, the new data is just added to the primary OPC’s database by manually entering it.

21 Synchronize the primary and backup OPC databases by copying the primary OPC database to the backup OPC, as described in Common Procedures, 323-1211-846.

—end—

Procedure 3-2Adding a network element to an existing span of control (continued) 3-2

Step Action



3

Procedure 3-3 Moving an in-service network element to a new span of control 3-3

Use this procedure to move an in-service network element from one span of control to another.

When adding network elements to a system, some of the existing network elements may have to be moved from one span of control to another. To move a network element between spans of control, you must delete it from the original span of control and then add it to the new span of control.


• Connect a VT100-compatible terminal to the primary OPC in the original span of control. In addition, you must connect a similar terminal to the primary OPC in the new span of control. For instructions, see Common Procedures, 323-1211-846.

• Enter the system-level information for the span of control to which the network element is to be moved according to Commissioning and Site Testing Procedures, 323-1211-220.

• All network elements that are moved must be visible to the span of control to which they are being moved. Ensure that there is a CNet connection between the two spans of control. Connect a SDH DCC bridge between the two spans of control (that is, CNet cables must be in place at all sites, and end-to-end continuity must exist between the terminating sites on at least one STM16 channel). See Commissioning and Site Testing Procedures, 323-1211-220.

• All the terminal shelves in a protection group of a 1:N system must be connected by way of a CNet local-area network. Similarly, the regenerator/optical amplifier shelves at each regenerator site must be interconnected by CNet cables. In a 1:N system, the protection shelf is an independent network element that must also be part of the span of control for the 1:N protection groups.

• You must have administrator level of access for each network that is to be moved. (The default userID is “admin”, with password “admin”.)

• You must log in to the primary OPCs at the root security level in both spans of control, as described in Common Procedures, 323-1211-846.

Note 1: Use the add and delete list (which was prepared before starting the expansion process) for reference. This list shows which network elements are to be deleted from or added to each span of control.

Note 2: It is not recommended to move a network element containing the primary or backup OPC to a different span of control.



Tools

Action

as required CNet cable, 9-pin D-sub (Male) to 9-pin D-sub (Male)

1 CNet terminator plugs


Procedure 3-3Moving an in-service network element to a new span of control 3-3

Step Action

1 Before beginning the procedure, verify the functioning of both OPCs. First check the data on the backup OPC and then shut it down. Then do the same for the primary OPC. For instructions, see Common Procedures, 323-1211-846.

2 Log in to the primary OPC on the original span of control to display its User Session Manager. If you don’t know how to do this, see Common Procedures, 323-1211-846.

3 Select the OPC Commissioning Manager from the Open Tools list. If you don’t know how to do this, see Common Procedures, 323-1211-846.

The OPC Commissioning Manager dialog is displayed.FW00217A

4 Tab to the list of commissioned network elements and select the first network element that must be moved.

—continued—



> .

NE

16


Utilities

17




Type

STM16STM16

Function

Ring ADMRing ADM

Serial Number OPC


Primary


=>





3

5 Display the list menu by pressing Ctrl_L / (or Keypad 3)

6 Tab to the Edit button and select it by pressing Ctrl_A (or Keypad 0).

7 Write down the network element number, type, function, and serial number. You need this data in step 28.

8 Repeat steps 4 to 7 for all network elements that you are moving to the new span of control.

9 On the primary OPC on the original span of control, open the UNIX shell. If you don’t know how to do this, see Common Procedures, 323-1211-846.

The “OPC>” prompt is displayed.

10 Enter the following command:

pmstate ↵

A menu of available commands is displayed. These commands include query and change commands and an exit command that are used to alter the state of the performance-monitoring tool on the OPC.


11 Turn off the collection of all OPC performance statistics by entering:

3 ↵

A note is displayed, indicating the consequences of the command.

12 To confirm the change, enter:

y ↵

A note is displayed, indicating the results of your action.


13 Exit the pmstate command by entering:

5 ↵The “OPC>” prompt is displayed.

14 Exit the UNIX shell by entering:

exit ↵

The UNIX shell is terminated and the User Session Manager is displayed.

15 Go to the site of the primary OPC in the new span of control.

16 Log in to the primary OPC in the new span of control to display its User Session Manager.

—continued—

Procedure 3-3Moving an in-service network element to a new span of control (continued) 3-3

Step Action



17 Repeat steps 9 through 14 for the primary OPC in the new span of control.

18 Return to the Commissioning Manager tool opened in step 3 from the OPC in the original span of control.

19 Tab to the Commissioned network elements table.

20 Move the cursor to the first network element that you want to remove and select it by pressing Ctrl_A (or Keypad 0).

21 Open the list menu by pressing Ctrl_L / (Keypad 3).

22 Tab to the Delete command on the list menu to delete the network element from the list of commissioned network elements.

23 Press Space (or Keypad Enter) to select the Delete command.

Note: It may take up to 2 min for the association to be taken down between the network element and the OPC.

24 Repeat steps 20 to 23 for all network elements that must be moved from this original span of control.

25 Go to the site of the primary OPC in the new span of control. (If there is a CNet connection between the two spans of control, you can log in remotely.)

26 Select the OPC Commissioning Manager from the Open Tools list.

A screen similar to the following is displayed.FW00217A

—continued—


Step Action



> .

NE

16


Utilities

17




Type

STM16STM16

Function

Ring ADMRing ADM

Serial Number OPC


Primary


=>





3

27 Tab to the Commission new network element button and select it by pressing Space (or Keypad Enter).

The Network Element Commissioning Data dialog is displayed.FW00218A

28 Add the commissioning data that you collected in step 7.

Note: The network element number must not be changed. All commissioning data entered must be the same as that collected. However, you must ensure that the network element number is unique within the span of control. You can view the list of network element numbers already used in the span of control by typing listnodes from the network element user interface.

29 Open the Reboot/Load Manager tool and wait until the question mark in front of the newly added network element disappears.

It may take up to 2 min for the association between the network element and the OPC to come up.

30 Log in to the new network element from the OPC in its new span of control. If you don’t know how to do this, see Common Procedures, 323-1211-846.

31 Copy the network element data to the primary OPC by entering:

equipmnt sh ↵backupdb ↵yes ↵The backup process can take up to 5 min to complete.

—continued—


Step Action

Network Element Commissioning Data

[ OK ♦ Return ] [ Cancel ♦ Del ]

Network element number:

Shelf type:Shelf function:

Transmission rate:>Shelf serial number:

Software release:

This network element contains:

>

>>

>

>

(♦ ) no OPC( ) Primary OPC( ) Backup OPC



32 Confirm the backup by checking the log buffer, by entering:

logutil ↵open fwdb ↵The FWDB logs show the status of the database backup. A FWDB300-series log indicates a problem with the backup.


logout ↵

34 Press the return key to return to the OPC Session Manager.

35 Open the Backup/Restore Manager tool.

36 Verify that the backups have been sent to the primary OPC. Do this by selecting the Options menu by pressing Ctrl_L T (or Keypad period).

37 Move to the Query all backups option and select it by pressing Space (or Keypad 0).

The Query all backups dialog is displayed.FW00219A

38 Ensure that the network element is shown with a backup that corresponds to the time and date that you did the backup.

39 To close the dialog, tab to the Done button and select it by pressing Ctrl_A (or Keypad 0).

The dialog is cleared from the screen.

40 Display the window menu by pressing Ctrl_L W (or Keypad 6).

41 Select Exit by pressing Space (or Keypad 0).

The tool closes.

—continued—


Step Action

Network Element

641 Belfast FWP04

Release

641 Belfast FWP04

[ Done ♦ Return ]

Time Date Status

07:

08:19 28 Feb 92 -

Query All Backups

Shelf Backup Name

1 FWP04.backup

FWP04.current1

28 Feb 92



3

42 Repeat steps 26 to 41 for each network element that you are adding to the new span of control.

43 If necessary, add the configuration data for the added network elements to the primary OPC of each span of control. For example, if the two terminals of a linear system are no longer in the same span of control, the linear configuration data must be entered into the primary OPC for both spans of control. In a MS SPRing, all the ADM nodes should be in the same span of control (although this is not always possible, such as in cases in which two operating companies have ADM nodes in a shared ring). For further provisioning rules and instructions, see Provisioning and Operations Procedures, 323-1211-310

44 For any connections that traverse terminals or ADM nodes in different spans of control, manually add the connection data to the OPC for each span of control. If the connections are not appropriately defined in each span of control, misconnections might result. For further provisioning rules and instructions, see Provisioning and Operations Procedures, 323-1211-310.

45 Copy the data from the primary OPC to the backup OPC for each span of control, as described in Commissioning and Site Testing Procedures, 323-1211-220.

46 Log out from both primary OPCs and log in again using the slat security level (the default userID is “slat,” with password “slat”).

47 Select the Network Summary tool from the Available Tools list. If you don’t know how to do this, see Commissioning and Site Testing Procedures, 323-1211-220.

48 Verify that the network elements shown in the two spans of control correspond to the changes made, and verify that none of the network elements have a question mark (?) next to them. The alarm status on each network element should be the same as prior to starting the move procedure.

49 Repeat steps 9 to 17, entering 2 instead of 3 at step 11 to turn on the collection of all OPC performance statistics.

50 Close all open OPC tools and log off from both OPCs.

—end—


Step Action



Procedure 3-4 Moving an OPC to another shelf location 3-4

Use this procedure to move an OPC from one network element shelf to another.


• Connect a VT100-compatible terminal to the OPC according to Common Procedures, 323-1211-846.

• Obtain a userID and password that allow you access to the OPC.

• If the primary OPC is moved, log in to the OPC at the slat security level according to Common Procedures, 323-1211-846. (The default userID is “slat” with password “slat”.)

• If the backup OPC is moved, log in to the OPC at the root security level according to Common Procedures, 323-1211-846.

• Obtain a userID and password for the network element from which the OPC is to be removed.

Tools

Action


Procedure 3-4Moving an OPC to another shelf location 3-4

Step Action

1 Log in to the primary OPC using the “slat” userID (the default is userID is “slat” and the default password is “slat”). If you don’t know how to log in, see Common Procedures, 323-1211-846.

2 Using the NE Login Manager tool, log in to the network element from which the OPC is to be removed. If you don’t know how to use this tool, see Common Procedures, 323-1211-846.

—continued—



3

3 Access the OPC equipment screen by entering

equipmnt opc ↵The OPC equipment screen is displayed.

FW00220A

4 Place the OPC out of service by entering:

chgstate oos ↵ yes ↵

The OPC State field changes to OOS.

5 Delete the OPC from the network by entering:

delete ↵ yes ↵The OPC State field changes to NULL.


logout ↵

7 If Then go to

the backup OPC is to be moved step 8

the primary OPC is to be moved step 10

8 Log in to the backup OPC, using the root userID. If you don’t know how to log in, see Common Procedures, 323-1211-846.

—continued—

Procedure 3-4Moving an OPC to another shelf location (continued) 3-4

Step Action

Critical Major minor warning FailProt Lockout ActProt PrfAlrtNetwork View1 Belfast

NE 1

Time 23:59

OPC Equipment

.

...

.

...

.

....

.

..

State: IS

Location: ShPos 1

Shelf: 1

OP Ctl NT7E24BA Slot 41:44

STM1e Equip023456789

101112131415161718

Quit

ListAlmsAlmRpt

ChgState

AddDelete

Help

Query

Circuit Pack:



9 When the OPC UNIX shell prompt is displayed, start the User Session Manager by entering:

opcui ↵The User Session Manager appears, listing the available tools.

FW00221B

10 Shut down the OPC as described in Common Procedures, 323-1211-846.

11 Remove the OPC from the shelf and move it to its new location.

12 Install the OPC in the new location as described in Commissioning and Site Testing Procedures, 323-1211-220.

13 Log in to the primary OPC, using the slat userID as described in Common Procedures, 323-1211-846.

—continued—


Step Action

> User Session Manager : admin

Available tools

Toolset/Tools

Reboot/Load Manager

Open tools

ID State Tool

2 > OK Status : Primary/Active

.

.

[ Logout ]

C 0 M 0 m 0 w 0 FailProt 0 Lckt 0 ActProt 0 PrfAlrt 0 11:09

Software Admin

Backup/Restore MngrEvent BrowserNetwork Upgrade Mngr

OPC Admin

Centralized User AdminOPC Save and RestoreOPC ShutdownOPC DatePort ConfigurationUnix Shell

Network Admin

OPC PM Coll.Filter

1:N Protection Manager



3

14 Open the Commissioning Manager tool.

The Commissioning Manager screen is displayed.FW00217A

15 Tab to the Commissioned network elements list and move to the network element which you logged in to at step 2 (that is, the network element that originally contained the OPC).

16 Select the network element by pressing Space (or Keypad 0).

17 Display the list item menu by pressing Ctrl_L (or Keypad Enter).

18 Select the Edit menu by pressing Space (or Keypad 0).


—continued—


Step Action



> .

NE

16


Utilities

17




Type

STM16STM16

Function

Ring ADMRing ADM

Serial Number OPC


Primary


=>








Software release:


>

>>

>

>




19 Tab to the field containing the three OPC buttons (no OPC, Primary OPC, and Backup OPC).

20 Using the arrow keys, move to the No OPC button, and select it by pressing Ctrl_A (or Keypad 0).

A mark is displayed between the brackets beside No OPC.

21 Tab to the OK button to confirm the entry.

The dialog closes and the Commissioning Manager main window is displayed.

22 In the Commissioned network elements list, move to the network element to which the OPC has been moved and select it by pressing Space (or Keypad 0).


23 If that network element Then go to

contains the backup OPC step 24

contains the primary OPC step 27

24 Tab to the Backup OPC button, and select it by pressing Ctrl_A (or Keypad 0).

A mark is displayed between the brackets beside backup OPC, and the button is disabled for the commissioning of subsequent network elements.



26 Go to step 29.

—continued—


Step Action






Software release:


>

>>

>

>




3

27 Tab to the Primary OPC button, and select it by pressing Ctrl_A (or Keypad 0).

A mark is displayed between the brackets beside primary OPC, and the button is disabled for the commissioning of subsequent network elements.



29 Record the commissioning data change for this network element on the Commissioning Data Record form at the end of this chapter.

30 To complete the entry of commissioning data for this network element, tab to the OK button, and select it by pressing Ctrl_A (or Keypad 0).

31 Press Ctrl_T 0 to return to the User Session Manager.

The Commissioning Manager main window closes.

32 Close the Commissioning Manager tool. If you don’t know how to do this, see Common Procedures, 323-1211-846.

33 Reinstall the OPC port cabling as required.

—end—


Step Action



Procedure 3-5Decommissioning a network element 3-5

Use this procedure to remove a network element from an OPC span of control.


• All other tasks associated with removing the network element from the in-service system must be complete.

• Ensure that there are no active OPC trouble logs. Check the Event Browser tool of the primary OPC (trouble logs may have been recently raised and cleared).

• Connect a VT100-compatible terminal to the OPC port (port B) of the primary OPC as described in Common Procedures, 323-1211-846.

• Log in to the primary OPC at the admin security level as described in Common Procedures, 323-1211-846. (The default userID is “admin”, with password “admin”.)

Tools

as required VT100-compatible terminals (one at the ADM site and one at the primary OPC)

2 NT7E44RA or RB cable for terminal to primary OPC port B connection

as required NT7E44FA or FB cable for terminal to network element port 2 connection



3

Action

Procedure 3-5Decommissioning a network element 3-5

Step Action

1 On the primary OPC user interface, open the Commissioning Manager. If you don’t know how to do this, see Common Procedures, 323-1211-846.

A display similar to the following is displayed.FW00217A

2 Tab to the Commissioned Network Elements list and move to the network element you plan to decommission. Select it by pressing Ctrl_A (or Keypad 0).


4 Move to the Delete command and select it by pressing Space (or Keypad 0).

The Delete Network Element Confirmation dialog is displayed.FW00222A

—continued—



> .

NE

16


Utilities

17




Type

STM16STM16

Function

Ring ADMRing ADM

Serial Number OPC


Primary


=>



Warning: This operation will remove the commissioning

[ Yes ♦ Return ]

Do you wish to continue?

data for the selected network elements.

[ No ♦ ]



5 Tab to the OK button and select it by pressing Ctrl_A (or Keypad 0). The network element is removed from the list.

6 Verify on the OPC user interface bottom banner line that there are no alarms and that all associations between the OPC and the network elements in its span of control are up (that is, a question mark is not displayed).


8 Transfer the data to the backup OPC as described in Commissioning and Site Testing Procedures, 323-1211-220.

9 Close the Commissioning Manager tool. If you don’t know how to do this, see Commissioning and Site Testing Procedures, 323-1211-220.

10 If the network element was removed from an in-service system, complete all the final verification checks outlined in the post-expansion verification procedure of Chapter 2.

—end—

Procedure 3-5Decommissioning a network element (continued) 3-5

Step Action



3

End of chapter file

Commissioning Data RecordDate:

Use a copy of this form to keep a permanent record of all commissioning data

Network name: Time zone:

System name: Time zone:

Primary OPC serial number: OPC alias:

Backup OPC serial number: OPC alias:

NE number Shelf type and function

Shelf serial number

NE name NE location GMT offset


4-1

4

Chapter 4: Expansion of a TN-16X ring This chapter describes how to perform in-service modifications to an existing TN-16X ring. The processes in this chapter show you how to do the following:

• add an ADM node to a TN-16X ring

• delete an ADM node from a TN-16X ring

• add a regenerator to a TN-16X ring

• delete a regenerator from a TN-16X ring

To upgrade a regenerator to an ADM node, you must remove the regenerator from the TN-16X ring and then add an ADM node to the TN-16X ring.

Before starting any of the processes, you must perform the pre-expansion verification, as described in Chapter 2. Use the tables on the following pages as a guide for the overall process. Each of the processes consists of a number of individual procedures and references to other documents where appropriate.

Note 1: TN-16X ring nodes (ADM nodes and regenerators) can have their optical circuit pack groups connected in any combination (G1 to G1, G2 to G2, and G1 to G2). The examples in this chapter reflect this flexibility, which allows network expansion without taking down live traffic.

Note 2: The requirement for regenerators can be reduced by using STM-16 high performance transmitters and optical amplifiers to extend the reach of the optical signal. For configuration information and specifications for the link budgets for these options, refer to Technical Specifications, 323-1211-180.

Renumbering a TN-16X ring ADMA TN-16X ADM node cannot be given a different network element number while it is in service. This is because it is necessary to decommission the network element (that is, remove it from the OPC span of control) and then add it back to the span of control with a new number.

When you decommission the node and recommission it, the provisioned STM connections are not automatically duplicated after autoprovisioning, and there are no default STM connections. The STM connections must then be manually recreated using the OPC Connection Manager which supports flexible timeslot assignment (TSA). Alternatively, the STM connections can be provisioned using the OSI provisioning interface.


4-2 Expansion of a TN-16X ring

Equipment used in an MS SPRingThe equipment used in an MS SPRing is the same as is used for the linear TN-16X systems, with the following exception:

• The ring requires ring transmit interface (NTFW01) and ring demultiplexer (NT8E06) circuit packs.

Summary of processesTables 4-1 to 4-5 provide a task list for each process.

Table 4-1Adding an ADM node 4-1

Task Reference

Before beginning the expansion procedures, verify the integrity of the existing in-service system

Chapter 2

Install the ADM node (including connections for the external synchronization interface and any external equipment)

Rack Installation Procedures, 323-1211-201

Commission the new ADM node, including setting ESI provisioning parameters (for example, the clock source must be set to ESI)

Note 1: A spare or portable OPC is taken to the site and used to commission the new network element and to perform the initial download of software to the shelf. (If no spare or portable OPC is available, you can remove the backup OPC and take it to the site.) The commissioning data is then manually reentered into the primary OPC. However, if a CNet connection can be established from a collocated network element in the same span of control, the commissioning and software download can be done remotely from the primary OPC. (Procedure 3-2, “Adding a network element to an existing span of control”, provides an overview of these methods.)

Note 2: If more than one ADM node is to be added, they can all be commissioned and site tested, and have the fiber connections between them tested through the progressive end-to-end tests before being cabled in to the existing ring.

Commissioning and Site Testing Procedures, 323-1211-220

Commissioning and Site Testing Procedures, 323-1211-220.

Perform the site-testing procedures appropriate for the new ADM node Commissioning and Site Testing Procedures, 323-1211-220

Cable the new node into the ring, verify the new optical circuit packs and fiber links, and add the new ADM node to the ring using the Configuration Manager tool


Perform the system tests for the new ADM node Commissioning and Site Testing Procedures, 323-1211-220

Perform the post-expansion verification procedure to verify system integrity

Chapter 2


Expansion of a TN-16X ring 4-3

4

Table 4-2Deleting an ADM node 4-2

Table 4-3Adding a regenerator 4-3

Task Reference

Before beginning the expansion procedures, verify the integrity of the existing in-service ring

Chapter 2

Remove the ADM node from the ring Procedure 4-2 on page 22

Decommission the ADM node using the primary OPC, and copy the data to the backup OPC and to the backup tape

Chapter 3


Chapter 2

Task Reference

Before beginning the expansion procedures, verify the integrity of the existing in-service system (pre-expansion system verification)

Chapter 2

Install the regenerator Rack Installation Procedures, 323-1211-202

Commission the new regenerator

Note: A spare or portable OPC is taken to the site and used to commission the new network element and to perform the initial download of software to the shelf. (If no spare or portable OPC is available, you can remove the backup OPC and take it to the site.) The commissioning data is then manually reentered into the primary OPC. However, if a CNet connection can be established from a collocated network element in the same span of control, the commissioning and software download can be done remotely from the primary OPC. (Procedure 3-2, “Adding a network element to an existing span of control”, provides an overview of these methods.)


Perform any other commissioning tasks required for your system configuration


Cable in the new regenerator Procedure 4-3 on page 38

Perform the system tests for the new ADM node Commissioning and Site Testing Procedures, 323-1211-220


Chapter 2



Table 4-4Deleting a regenerator 4-4

Task Reference


Chapter 2

Cable out the regenerator and reconnect the cables in the new configuration. Check the received signal optical levels and the performance monitoring counts to ensure integrity of the laser modules and fibers in the new configuration.


Decommission the regenerator using the primary OPC, and copy the data to the backup OPC and to the backup tape

Chapter 3


Chapter 2



4

Table 4-5 Replacing a regenerator with an ADM node 4-5

Task Reference


Chapter 2

Install the ADM node (including connections for the external synchronization interface and any external equipment)

Rack Installation Procedures, 323-1211-201

Commission the new ADM node, including setting ESI provisioning parameters (for example, the clock source must be set to ESI)

Note 1: A spare or portable OPC is taken to the site and used to commission the new network element and to perform the initial download of software to the shelf. (If no spare or portable OPC is available, you can remove the backup OPC and take it to the site.) The commissioning data is then manually reentered into the primary OPC. However, if a CNet connection can be established from a collocated network element in the same span of control, the commissioning and software download can be done remotely from the primary OPC. (In Chapter 3, Procedure 3-2, “Adding a network element to an existing span of control”, provides an overview of these methods.)

Note 2: If you are upgrading an existing out-of-service TN-16X terminal to an ADM ring node, ensure that the TN-16X terminal shelf is running the current software release.


Change Application Procedures (CAPs) available from Nortel

Perform the site testing procedures Commissioning and Site Testing Procedures, 323-1211-220

Cable out the regenerator Procedure 4-4

Decommission the regenerator using the primary OPC, and copy the data to the backup OPC and to the backup tape

Chapter 3

Deprovision all facilities on the new node, set up default STM connections, cable the new node into the ring, verify the performance of the new optical circuit packs and fiber links, and configure the new ADM node into the ring using the Configuration Manager tool

Procedure 4-1


Chapter 2



Procedure 4-1Adding a new ADM node into an existing in-service ring 4-1

Use this procedure to add an ADM node to an existing ring. If you are replacing a regenerator with an ADM node, you must delete the regenerator from the ring (see Procedure 4-4) before proceeding with this procedure.

As shown in Figure 4-1, to insert the new ADM node in an existing ring, a forced switch must be applied at each of the two ADM nodes adjacent to the new node (that is, the neighbouring nodes). Each of these forced switches causes a traffic hit of less than 50 ms. The traffic through the fibers on this span is diverted and the fibers can be disconnected and the new ADM node cabled in.

If you are replacing a regenerator with an ADM node and you have completed Procedure 4-4, the forced switches should still be in place.

Figure 4-1Operate forced switches on span A-B 4-1

FW00223A

In this procedure, the new node that is physically connected to the ring is configured on the OPC using the Configuration Manager and the Connection Manager tools. This allows it to carry traffic and to communicate with the other nodes in the ring. The OSI provisioning interface can be used as an alternative to provisioning the connections with the OPC Connection Manager.


• Ensure that the pre-expansion system checks and all other prerequisite tasks as outlined in Table 4-1 or Table 4-5 have been done.

G1 G2

Node C

Node A Node B

Node D

Forced switchon G2

Forced switchon G1

FW-2645G2 G1 G2 G1

G1 G2 G1 G2

Span A-B

Traffic rerouted Traffic rerouted

New ADM node



4

• Commission the new ADM node as described in Commissioning and Site Testing Procedures, 323-1211-220, using the OPC of the ring system in which you are adding the node (or nodes). The network element number of each new ADM node must be unique within the span of control.

• ESI must be equipped on the node.

• Complete the site testing procedures on the node as described in Commissioning and Site Testing Procedures, 323-1211-220.

• Each of the new ring ADM nodes must be running the current software release.

• If you are replacing a regenerator with an ADM node, complete Procedure 4-4.

• Connect a VT100-compatible terminal to the OPC port (port B) of the primary OPC. See Common Procedures, 323-1211-846.


• Connect a VT100-compatible terminal to the user interface port 2 of the new ADM node according to Common Procedures, 323-1211-846.

• Log in to the new ADM node at the admin security level as described in Common Procedures, 323-1211-846. (The default userID is “admin”, with password “admin”.)

• At least three technicians are needed to perform fiber cabling changes (one at each site).

Tools

Note: For measuring the output from optical amplifiers and high performance transmitters, a calibrated attenuator (for example, 10 or 15 dB) can be used with an optical power meter rated for lower levels.

as required

VT100-compatible terminals (one at each new ADM site and at the primary OPC)

2 NT7E44RA or RB cable for terminal to primary and spare OPC port B connection

as required

NT7E44FA or FB cable for terminal to network element port 2 connection

as required

optical test cords with mVOAs

1 Optical power meter rated for up to +3 dBm at 1310 and 1550 nm (such as the Photodyne 12XE) or, for measuring output from optical amplifiers and high performance transmitters, rated for more than +11 dBm at 1550 nm (such as the Exfo FOT-22A-X) (see Note)

as required

Patchcords. Four patchcords are required to cable a new ADM node to the fiber patch panel in a central office



When using a calibrated attenuator, the level of attenuation must be added to the actual optical power meter reading to obtain the true optical power.

Action

Procedure 4-1Adding a new ADM node into an existing in-service ring 4-1

Step Action

Preparing the new ADM node

1 Except for the STM-16 and ESI alarms, ensure no alarms are raised. Refer to Alarm and Trouble Clearing Procedures, 323-1211-543, to clear any alarm

2 If any STM1e, 140M, STM-1o or STM4 facilities are equipped, to avoid numerous alarms on the existing system when the new node is added to the existing system, ensure that all of those facilities are in the out of service (OOS) state by entering the following commands at the new ADM node:

facility <facility type> all ↵chgstate oos ↵yes ↵yes ↵

where<facility type> is stm1e , 140m, stm1o or stm4

3 Set up default passthrough STM connections on the ADM node by entering the following commands:

config ↵addnode ↵yes ↵Default STM connections are established.

If Then go to

you are just adding a new ADM node step 3

you are replacing a regenerator with step 7an ADM node (that is, continuing from Procedure 4-4)

Protecting the traffic of the neighbouring nodes

4 Open the NE Login Manager tool on the primary OPC. If you do not know how to do this, see Common Procedures, 323-1211-846.

5 Log in to one of the two neighbouring ADM nodes to the new ADM node (Node A or Node B in the example in Figure 4-1). To log in to a network element from the OPC, see Common Procedures, 323-1211-846.



4

6 Operate a forced switch by entering:

protectn ↵dtlprot stm16 ↵forced op <circuit pack group> ↵yes ↵yes ↵

where<circuit pack group> is g1 or g2 (in the example

given, enter g2 for Node A)

A traffic hit of less than 50 ms occurs when this command is issued. The TN-16X Protection screen displays an asterisk (*) beside the affected circuit pack group in the Forced column.

7 Repeat steps 4 and 5 for the second adjacent node (in the example in Figure 4-1, operate a forced switch on G1 for node B).

Connecting the new ADM node

Procedure 4-1Adding a new ADM node into an existing in-service ring (continued) 4-1

Step Action

WARNINGRisk of eye injuryAvoid direct exposure to laser beam or fibre. Invisible light that can blind is present. Keep all connectors capped.

CAUTIONRisk of damaging equipmentAvoid touching any components on the printed circuit board. Electrostatic sensitive devices can be damaged by electrostatic discharge. Always ground yourself before handling the circuit pack.



8 When the traffic is protected on the span that is to be split, the new node can be added by connecting the fibers to the new node as follows (see the example in Figure 4-2):

• Ensure that the fiber connectors are clean before making the final connections to the circuit packs or fiber patch panels. Refer to Common Procedures, 323-1211-846, for the fiber cleaning procedure.

• Ensure that you do not connect the disconnected fibers between nodes A and B to interface circuit packs that have their active LEDs lit (in the example, node A G2 and node B G1).

• The received optical level must meet the guaranteed receive levels before the final connections are made. Therefore, first make the transmit connections, then, using a power meter, measure the associated received optical level at the adjacent site. If necessary, adjust it using an mVOA to within normal operating levels (for example, to −17 dBm). Refer to Technical Specifications, 323-1211-180, for detailed specifications on optical receive levels.

• Connect the STM16 G1 circuit packs of the new ADM node to the STM16 circuit packs on one of the adjacent ADM nodes. In the example in Figure 4-2, the G1 transmit interface at node X is connected to the G2 receive interface at node A, and the G1 receive interface at node X is connected to the G2 transmit interface at node A.

• Similarly connect the STM16 G2 circuit packs on the new ADM node to the STM16 circuit packs of the other adjacent ADM node. In the example in Figure 4-2, the G2 transmit interface at node X is connected to the G1 receive interface at node A, and the G2 receive interface at node X is connected to the G1 transmit interface at node A.

• You can connect the STM16 circuit pack groups in any of the arrangements of G1 to G1, G2 to G2, or G1 to G2 (the transmit interface and receive interface with a demultiplexer make up a circuit pack group).

• If there are regenerators between node A and node X for example, the fiber connections should be as shown in Figure 4-3.


Step Action



4

Figure 4-2ADM node fiber cabling 4-2

FW00224A

“Invalid K-bytes” alarms are raised at each of the added ADM nodes.


Step Action

Node C

Node A Node B

Node D

Forced switchon G2

Forced switchon G1

FW-2646G2 G1 G2 G1

G1 G2 G1 G2

Span A-X


Node X(new node)

Span B-XG1 G2



Figure 4-3Example 1: Regenerators between the new ADM node and the ring 4-3

FW00225A

Verifying the newly connected optical links integrity

9 Log in to the new ADM node from the VT100-compatible terminal connected to the node as described in Common Procedures, 323-1211-846.

10 Verify that the receive optical links (for both G1 and G2) on the new node are error free by checking the performance-monitoring line coding violation counters by entering:

perfmon ↵facperf stm16 g1 ↵


Step Action

G1Rx

G1Tx

G2Tx

G2Rx

G1Rx

G1Tx

G2Tx

G2Rx

G1Rx

G1Tx

G2Tx

G2Rx

G2RxE

G2TxE

G2RxW

G2TxW

Regenerator

9 10 11 12

6 8 9 11 6 8 9 11

6 8 9 11

ADMNode A

To Node C

To Node D

ADMNode B

New Node

FW-2647



4


11 Verify that the MsCV and the RsCV counters do not detect any errors for the current 15 minute timed interval counters. The screen might display counts but it must not accumulate any new counts. Wait until a new interval is completed and ensure that no new counts are displayed on the screen (if a question mark is displayed next to a count, this count is not valid; wait for the next valid count).

12 Select G2 by entering:

select g2 ↵

13 Repeat step 11 for this circuit pack group.

14 When more than one ADM node is added, repeat steps 9 to 13 for each of the new ADM nodes.

15 Log in to one of the nodes adjacent to the new node using the NE Login Manager form the VT100-compatible terminal connected to the OPC. If you do not know how to do this, see Common Procedures, 323-1211-846.

16 Repeat steps 10 through 13 for the two ADMs (or regenerators) adjacent to the new node.


Step Action

Critical Major minor warning FailProt Lockout ActProt PrfAlrtNetwork View

FP Stats0 Quit2 Select3 4 5 Clear6 StartUnt7 8 9

10 11 12 1314 15 16 History17 Threshld18 Help

NE 1

Time 00:38 >

STM16 Performance Statistics Shelf: 1

.

...

.

...

**

.

....

.

1 Belfast

Unit: STM16 G1

Untimed Start: 00:35 2 Apr15Min

Curr Last0.0.

0.

0.0.

123.123.

123.

1234.1234.

RsCVRsES

RsSEFSMsCVMsESMsSES

RsSES 0. 123.

1234.0.

Curr Last10 ?10 ?

10 ?

100 ?100 ?

10 ?

100 ?

Rx Near

Day

MsUASMsFC

0.0.

1234.1234.

100 ?100 ?

123.123.

123.

1234.1234.

123.

1234.

1234.1234.

Curr133.133.

133.

1234.1234.

133.

1234.

1234.1234.

Untimed



Configuring the new ring ADM node on the OPC

17 Open the Configuration Manager tool on the primary OPC. If you don’t know how to do this, see Common Procedures, 323-1211-846.

The Configuration Manager main window is displayed.FW00227A

18 Move (using the arrow keys) to the ring to which you want to add an ADM node and select it by pressing Ctrl_A (or Keypad 0).

The ring is highlighted.


The list item menu is displayed.

20 Select the Edit Configuration command by pressing Space (or Keypad 0).

A confirmation dialogue is displayed.

21 In the confirmation dialogue, tab to the Yes button and select it by pressing Ctrl_A (or Keypad 0).


Step Action


> Configuration Manager Create.

Name

Configurations sorted by name

Type Topology Rate

Ring 1 TransportNode Fiber Ring STM16



4

The confirmation dialogue is removed and the Configuration Manager: Ring window appears, displaying all the ADMs in the ring

FW00228A

22 Select the Configure a Ring ADM button by pressing Ctrl_A (or Keypad 0).

The Configure a ring ADM dialogue is displayed.FW00229A

23 Tab to the Network Element field and display the chooser menu by pressing Ctrl_L / (or Keypad 3).

The chooser menu is displayed.


Step Action

2 [ Provision pass-through connections (added ADM(s) only ♦ 2]

C 0 M 0 m 1 w 2 FailProt 0 Lckt 0 11:40

=>1

> Configuration Manager: Ring Utilities.

[Configure a ring ADM ...♦ 1]

Configured Ring ADM

121011

3 [ Save and send configuration data ♦ 3]

Procedure: None selected.

Configured ADMS: Valid ring sorted 12. G1 in ring order.

121011

101212

111110

APS ID G1 Neighbor ADM G2 Neighbor ADM

Name: Ring 1 Type: TransportNode Fiber Topology: Ring Rate: STM16

Configure a ring ADM:

[ OK ♦ Return ]

Network Element:

Ring ADM APS ID: >

This ADM’s STM-16 CPG G1 fibres connect to neighbor

ADM:

This ADM’s STM-16 CPG G2 fibres connect to neighbor

ADM:

STM-16 CPG:

STM-16 CPG:

[ Cancel ♦ Del ]

<



24 Using the arrow keys, move to the ring ADM to be added and select it by pressing Ctrl_A (or Keypad 0).

The network element number is displayed in the Network Element field

25 Tab to the Ring ADM APS ID field and display the chooser menu by pressing Ctrl_L / (or Keypad 3).

26 Move to the ring APS ID for the new ADM node and select it by pressing Space (or Keypad 0). (Each ring ADM node must have a unique APS ID in the range 0 to 15).

The APS ID is displayed in the field.

27 Tab to the ADM field (for the G1 neighbor) and display the chooser menu by pressing Ctrl_L / (or Keypad 3).

28

Move to the ADM that connects to the G1 circuit pack group and select it by pressing Space (or Keypad 0).

The network element number and name appear in the field.

29 To enter the circuit pack group that connects to the first neighbouring ADM, tab to the STM16 circuit pack group field and enter either G1 or G2.

Note: In the example shown in Figure 4-1 on page 6, the first neighbouring node to the new ADM node is Node A. The circuit pack group connected to the new node G1 is Node A G2.

30 Tab to the ADM field (for the G2 neighbour) and display the chooser menu by pressing Ctrl_L / (or Keypad 3).

31 Move to the ADM that connects to the G2 circuit pack group and select it by pressing Space (or Keypad 0).

The network element number and name appear in the field.

32 To enter the circuit pack group that connects to the second neighbouring ADM, tab to the STM16 circuit pack group field and enter either G1 or G2.

Note: In the example shown in Figure 4-1, the second neighbouring node to node X is Node B. The circuit pack group connected to node X G2 is Node B G1.

—continued—


Step Action

CAUTIONRisk of service interruptionThe data entered in the Configuration Manager must reflect the physical fiber connection in the network.



4

33 Tab to the OK button and select it by pressing Ctrl_A (or Keypad 0).

If the circuit pack group connections form a closed loop, the Configured ADMs field above the list displays “Valid ring”.

34 If the OSI interface is used to provision STM connections then provision passthrough connections for the connections that carry traffic using the OSI provisioning interface (refer to OSI Interface Description, 323-1201-191)

otherwise go to step 34

35 Tab to the Provision pass-through connections button (added ADMs only) and select it by pressing Ctrl_A (or Keypad 0).

The following dialogue is displayed.FW00230A

36 Tab to the Yes button and select it by pressing Ctrl_A (or Keypad 0).

When the provisioning operation is completed, the following dialogue is displayed.

FW00231A

37 Tab to the Done button and select it by pressing Ctrl_A (or Keypad 0).

—continued—


Step Action

This operation will provision pass-through

[ Yes ♦ Return ]


connections for the new ring ADM(s) configured.

[ No ♦ ]

The pass-through connections for the new

[ Done ♦ Return ]

ADM(s) were provisioned successfully.

CAUTIONRisk of service interruptionThe dialogue closes and the cursor is moved to the Save and Send configuration data button. Do not select it while the forced switches are still active. This affects the forced switches, causing a hit on traffic.



38 When more than one ADM node is added, in the Configuration Manager, move to the Configure a Ring ADM button and repeat steps 21 to 36 for each of the new ADM nodes.

39 Leave the tool open and return to the user session manager by pressing Ctrl_T 0.

40 Open the NE Login Manager tool and access one of the two network elements bounding the new ADM node (Node A or Node B in the example in Figure 4-1 on page 6).

41 Log in to the network element using the admin userID.

42 Release the forced switches by entering:

protectn ↵dtlprot stm16 ↵forced re <circuit pack group> ↵yes ↵

where

<circuit pack group> is g1 or g2 (in the example given,it is g2 for Node A)

43 Repeat steps 40 through 42 for the second neighbour node (in the example in Figure 4-1, release the forced switch on G1 for node B).

A traffic hit of less than 50 ms occurs when this command is issued.

—continued—


Step Action

CAUTIONRisk of service interruptionIf releasing the forced switches causes traffic to be lost, immediately operate the two forced switches that were released in step 38 and call Nortel technical support



4

44 Using the Configuration Manager tool, save and send the new configuration data (node maps) to all nodes in the ring. Move to the Save and send configuration data button and select it by pressing Ctrl_A (or Keypad 0).

The following confirmation dialogue is displayed.FW00232A


The following dialogue is displayed, displaying the results of the operation.FW00233A

46 Select the Done button by pressing Ctrl_A (or Keypad 0).

The dialogue is removed.

47 Verify that there is consistency between the data that has been sent to the ADM nodes and the OPC by running a configuration audit from the Configuration Manager tool. If you don’t know how to do this, see Provisioning and Operations Procedures, 323-1211-310.

Note: If you cannot run the audit successfully, verify that the network element and OPC associations in the OPC span of control are active. That is, check the bottom left-hand corner of the OPC user interface and ensure that there is no question mark (?). Also, ensure that all network elements in the span of control are operating properly and communicating with the OPC. Contact Nortel if the problems cannot be corrected.


—continued—


Step Action

1. Save the configuration data to the OPC database.

[ Yes ♦ Return ]

2. Send the configuration data to the ring ADMs.

You are about to:


[ No ♦ - ]

Information The configuration data was saved to the OPC

[ Done ♦ Return ]

database and sent to the ring ADM(s) successfully andthe OPC connection data was built successfully.



49 Close the Configuration Manager: Ring window by selecting the Exit button and pressing Space (or Keypad 0).

A confirmation dialog is displayed, prompting you to transfer any configuration changes to the backup OPC.

Tab to the Yes button and select it by pressing Ctrl_A (or Keypad 0).

The confirmation dialog closes. An information dialog is displayed, indicating that the current configuration data is being transferred to the backup OPC.

To remove the dialog, select the OK button by pressing Ctrl_A (or Keypad 0).

The dialog closes and the Configuration Manager main window is displayed.


51 Close the Configuration Manager tool by selecting the Exit button and pressing Space (or Keypad 0).

52 To ensure that the connections for the ring have been properly provisioned and sent to each ADM node, perform a connection audit. If you don’t know how to do this, see Provisioning and Operations Procedures, 323-1211-310.

Note: If the audit cannot be run successfully, verify the network element-to-OPC associations in the OPC span of control. Ensure that all network elements in the span of control are operating properly and communicating with the OPC. Contact Nortel if the problems cannot be corrected.

53 Close the Connection Manager tool. If you don’t know how to do this, see Common Procedures, 323-1211-846.

54 On each new ADM node in the ring, access the network element using the primary OPC and perform a data backup to the primary OPC by entering from each network element:

equipmnt sh ↵backupdb ↵yes ↵

55 When a database backup has been completed for each node, return to the OPC user interface by pressing Ctrl_T 0.


57 Transfer the data to the backup OPC as described in Common Procedures, 323-1211-846.

—continued—


Step Action



4

58 Log off the OPC as described in Common Procedures, 323-1211-846.

59 Perform the system test applicable to the new ADM node according to Commissioning and Site Testing Procedures, 323-1211-220.

60 Complete all the final verification checks outlined in the post-expansion verification procedure of Chapter 2. You do not have to perform another network element database backup, nor save OPC data to tape, nor transfer the OPC data to the backup OPC.

—end—


Step Action



Procedure 4-2Removing an ADM node from an in-service ring 4-2

Use this procedure to remove an ADM node from an existing in-service ring. All add-drop traffic must be removed from the node for it to be taken out of service. This procedure describes how to remove all facilities, all connections, and then cable out the ADM nodes.


• Consider how the removal of the ADM node will affect the timing scheme for the ring, particularly if the neighbour nodes are using line or loop timing. For example, if the neighbour nodes derive timing from the node to be deleted (line timing), removing the node without establishing another timing source will result in a timing loop. If necessary, make the appropriate changes to the ring timing. For an overview of the external synchronization interface (ESI) feature, see System Description, 323-1211-100.

• Check that the ADM node that is to be removed from the existing ring does not have any tributary traffic that is dropped or added. You must consider how the removal of this node affects the routing of connections, and reprovision the connections accordingly. For information on provisioning connections, see Provisioning and Operations Procedures, 323-1211-310.

• Perform the pre-expansion system checks and all other prerequisite tasks as outlined in the appropriate task list at the beginning of this chapter.

• Check that the ADM nodes to be removed from the existing ring do not contain an OPC. If one does, move the OPC to a new shelf location as described in Chapter 3.

• Connect a VT100-compatible terminal to the OPC port (port B) of the shelf that contains the primary OPC. See Common Procedures, 323-1211-846.


Note: At least three technicians are required to perform fiber cabling changes (one at each site).



4

Tools

Action

as required

VT100-compatible terminals (one at each site)

as required

NT7E44RA or RB cable for terminal to primary and spare OPC port B connection

as required

NT7E44FA or FB cable for terminal to network element port 2 connection

Procedure 4-2Removing an ADM node from an in-service ring 4-2

Step Action

Deprovisioning all facilities

1 Before the add/drop connections are deleted from the primary OPC, all facilities must be deprovisioned. To get a list of these facilities, open the Connection Manager tool from the User Session Manager. If you don’t know how to do this, see Common Procedures, 323-1211-846.

The following is an example of the Connection Manager screen.FW00234A

2 Using the information in the Connection list window, note the facilities that must be deleted. This information is shown in the rows for tributary connections for which the network element number of the node being deleted appears in the End NE A or End NE Z columns. Write down the facility data as follows:

• For STM-1e, 140M, STM-1o and STM-4 facilities, record the circuitpack group.

—continued—

Connection Id

[ Add ]


End NE A

fourth

first

STM1e connections sorted by End NE A

Showing: All connections

> Connection Manager View Utilities.

Tributary Ch

secondthird

12121212131313

End NE Z Tributary

STM1e G2STM1e G3STM1e G5STM1e G6STM1e G1STM1e G1STM1e G1

12121313121213

4657123

STM1e G8STM1e G3STM1e G5STM1e G6STM1e G1STM1e G1STM1e G7t



3 From the OPC User Session Manager, open the NE Login Manager and access the ADM node that is to be deleted.

4 Access the facility screen and place the in-service facilities (as noted in step 2) in the out-of-service (OOS) state by entering:

facility <service type> <circuit pack group> ↵chgstate oos ↵yes ↵ )

where

<service type> is

<circuit pack group> is as noted in step 2

5 Select all other facilities in turn and place them out of service by entering the following commands:

select <circuit pack group> ↵chgstate oos ↵yes ↵

where


6 Each facility being deactivated at the local ADM node must also be deactivated at the remote node where its far-end termination is added or dropped. To select the remote ADM node for each facility, enter:

selectne <NE number> ↵where

<NE number> is the network element number(a value from 1 to 9999)

The screen in context remains the same when the SelectNE command is used.

7 For each remote node, access the facility screen and place the in-service facilities (noted in step 2) out of service by entering:

facility <service type> <circuit pack group> ↵chgstate oos ↵yes ↵

where

<service type> is stm1e, 140M, stm1o or stm4


If all the traffic on the STM-4 facility at the remote node is coming from a node being deleted, theSTM-4 facility must also be deactivated at the remote node where the traffic is added or dropped. Otherwise, the STM-4 facility at the remote node should not be deleted.

—continued—

Procedure 4-2Removing an ADM node from an in-service ring (continued) 4-2

Step Action



4

8 Repeat step 7 for each facility to be deleted.

9 On each ADM node, any tributary interface that has its facility in the OOS state should also have its equipment provisioning in the OOS state. Query all the facilities in turn by accessing each node and entering the following commands:

facility <service type> all ↵query all ↵

where

<service type> is stm1e or 140M

10 Note any tributary circuit pack groups that have a facility in the OOS state as the result of step 7. If there are any such circuit pack groups, place them out of service by accessing the node and entering the following, as required, at each node:

eq <service type> <circuit pack group> ↵ chgstate oos ↵yes ↵

where

<service type> is VC4e, stm1e, stm1o or stm4


11 Repeat steps 6 through 10 for all other ADM nodes that terminate tributary interfaces as noted in step 2.

Deprovisioning connections

12 The add and drop STM connections that are terminating at the ADM nodes to be deleted can now be deleted from the primary OPC. Return to the User Session Manager by pressing Ctrl_T 0 and select the Connection Manager tool by pressing Ctrl_A (or Keypad 0).

13 In the Connection list, move to the connection you want to delete (that is, any connection for which the network element number appears in the End NE A or End NE Z columns).

14 Display the List Item menu by pressing Ctrl_L (or Keypad Enter).

—continued—


Step Action



15 Move to the Delete command and select it by entering by pressing Ctrl_A (or Keypad 0).The following dialogue is displayed.

FW00235A

16 In the dialogue box, ensure that either End NE A or End NE Z is the ADM node number of the ADM to be deleted. Tab to the Yes button and select it by pressing Ctrl_A (or Keypad 0).

17 Repeat steps 13 through 16 for the other connections that are terminating at the ADM node to be deleted.

18 Once the update is completed, display the window menu by pressing Ctrl_L W (or Keypad 6).

19 Close the Connection Manager tool as follows:

Select the Exit button by pressing Space (or Keypad 0).

A confirmation dialog is displayed, prompting you to transfer any connections changes to the backup OPC.


The confirmation dialog closes. An information dialog is displayed, indicating that the current connection data is being transferred to the backup OPC.

21 To remove the dialog, select the OK button by pressing Ctrl_A (or Keypad 0).

The dialog closes and the main window of the tool closes.

Deleting the ADM nodes from the OPC Configuration Manager

22 Open the Configuration Manager tool by pressing Ctrl_A (Keypad 0).

The Configuration Manager main window is displayed.

—continued—


Step Action

[Yes ¨♦ Return ]

You are about to delete this STM1e connection.

[ No ♦ - ]N

Configuration : Ring1Connection ID : fourth

End NE A : 12

End NE Z : 13

Any traffic provisioned on this STM1e connectionwill be lost.




4

23 Move to the ring from which you want to delete the ADM node and select it by pressing Ctrl_A (or Keypad 0).

The ring is highlighted.


The list item menu is displayed.

25 Select the Edit Configuration command by pressing Space (or Keypad 0).

A confirmation dialogue is displayed.

26 In the confirmation dialogue, tab to the Yes button and select it by pressing Ctrl_A (or Keypad 0).

The confirmation dialogue is removed and the Configuration Manager: Ring window appears, displaying all ADMs in the ring.

27 Move the ring ADM that is to be deleted and display the list item menu by pressing Ctrl_L (or Keypad 2).

The list item menu is displayed.FW00236A

—continued—


Step Action

2 [ Provision pass-through connections (added ADM(s) only ♦ 2]

C 0 M 0 m 1 w 2 FailProt 0 Lckt 0 11:40

=>1

> Configuration Manager: Ring Utilities.

[Configure a ring ADM ...♦ 1]

Configured Ring ADM

121011

3 [ Save and send configuration data ♦ 3]

Procedure: None selected.

Configured ADMS: Valid ring.

121011

101212

111110

APS ID G1 Neighbor ADM G1 Neighbor ADM1 Details2 Edit... >>3 Delete

4 Audit5 Send6 Info on last command

7 Select8 Deselect9 Sort list >>

10 Help ♦ H

Name: Ring 1 Type: TransportNode Fiber Topology: Ring Rate: STM16



28 Move to the Delete command and select it by pressing Space (or Keypad 0).


29 Ensure that the network element number displayed is the network element number of the ADM that you want deleted. Tab to the Yes button and select it by pressing Ctrl_A (or Keypad 0).

30 Repeat steps 27 to 29 for any other ADM node to be deleted.

31 In the main menu, the cursor is returned to the Save and Send configuration data button. Select it by pressing Ctrl_A (or Keypad 0).




33 Select the Done button by pressing Ctrl_L/ (or Keypad 3).

The STM connections on the working channels are still being passed through by the node that you want to delete.

34 Leave the Configuration Manager tool open. It is used again in step 37.

—continued—


Step Action

[ Yes ♦ Return ]

Do you wish to delete network element

[ No ♦ - ]

12 from the list?

1. Save the configuration data to the OPC database.

[ Yes ♦ Return ]

2. Send the configuration data to the ring ADMs.

You are about to:


[ No ♦ - ]

[ Done ♦ Return ]

The configuration data was saved to the OPC

D

Informationdatabase and sent to the ring ADMs successfully.



4

35

Connect a VT100-compatible terminal to the network element port 2 of the ADM node to be deleted. If you do not know how to do this, see Common Procedures, 323-1211-846.

36 Log in to the network element at the admin security level as described in Common Procedures, 323-1211-846. (The default userID is “admin”, with password “admin”.)

37 From the VT100-compatible terminal connected to the node to be deleted, enter the following:

quit all ↵config ↵deletenode ↵yes ↵quit ↵An “ADM in single-node configuration” alarm is raised at the deleted node .

38 To view the alarms, enter:

mapci ↵fwpuialarms ↵

Configuration Manager audit

39 Verify that there is consistency between the data that has been sent to the ADM nodes and the OPC by running a configuration audit from the Configuration Manager tool. If you don’t know how to do this, see Provisioning and Operations Procedures, 323-1211-310.

Note: If you cannot run the audit successfully, verify that the network element and OPC associations in the OPC span of control are active. That is, check the bottom left-hand corner of the OPC user interface and ensure that there is no question mark (?). Also, ensure that all network elements in the span of control are operating properly and communicating with the OPC. Contact Nortel if the problems cannot be corrected.


—continued—


Step Action

CAUTIONRisk of service interruptionPerform the following steps as soon as possible. The time delay between deleting the node on the OPC and deleting the node on the network element should be minimized.



41 Close the Configuration Manager: Ring window as follows:

Select the Exit button by pressing Space (or Keypad 0).

A confirmation dialog is displayed, prompting you to transfer any connections changes to the backup OPC.

Tab to the Yes button and select it by pressing Ctrl_A (or Keypad 0).

The confirmation dialog closes. An information dialog is displayed, indicating that the current connection data is being transferred to the backup OPC.

To remove the dialog, select the OK button by pressing Ctrl_A (or Keypad 0).

The dialog closes and the Connection Manager tool’s main window closes.


43 Close the Configuration Manager tool by selecting the Exit button and pressing Space (or Keypad 0).


Step Action



4

Connection Manager audit

44 To ensure that the STM connections for the ring have been properly provisioned and sent to each ADM node, perform a connection audit. If you don’t know how to do this, see Provisioning and Operations Procedures, 323-1211-310.

Note: If the audit cannot be run successfully, verify the network element-to-OPC associations in the OPC span of control. Ensure that all network elements in the span of control are operating properly and communicating with the OPC. Contact Nortel if the problems cannot be corrected.

Data synchronization with the backup OPC

45 Using the Connection Manager tool, transfer the network element data to the OPC. Display the Utilities menu by pressing Ctrl_L T + (or Keypad , 9) and select the Transfer data to backup OPC command.

46 Close the Connection Manager tool. If you don’t know how to do this, see Common Procedures, 323-1211-846.

47 On the OPC user interface, open the Event Browser tool and verify that the primary to backup OPC data transfer completed successfully (log STBY612). If you do not know how to open the Event Browser, see Network Surveillance Procedures, 323-1211-510.

48 If this log has not been recorded, verify that all network element-to-OPC associations are up in the system. Open the Configuration Manager tool and repeat the transfer of data to the backup OPC per step 45.

Perform forced switches to move traffic away from the ADM node

49 Using the NE Login Manager tool, access one of the two network elements bounding the ADM node (Node A or Node D in the example in Figure 4-4).

Note: Steps 49 through 67 can be carried out simultaneously on both the nodes adjacent to the node being deleted.

50 As shown in Figure 4-4, to remove the ADM node physically from a ring (node B in the example), forced switches must be applied at the two ADM nodes adjacent to this node (that is, neighbor nodes A and D) to divert traffic from the node being removed.


Step Action



Perform a forced switch for the first ADM node by entering:


where

<circuit pack group> is g1 or g2 (in the example givenin Figure 4-4 on page 32, enter g2for node A)


Figure 4-4Operate forced switches on span A-B 4-4

FW00238A

51 Repeat steps 47 and 48 for the second adjacent node (in the example in Figure 4-4, operate a forced switch on G2 for node D).

Cable out the ADM node

52 Once the traffic is protected on the span that is to be split, the nodes being removed can be cabled out by disconnecting its fibers as shown in Figure 4-5.


Step Action

Node C

Node A Node B

Node D

Node to beremoved

G1 G2 G1 G2

G1 G2 G1 G2

Span A-B

Forced switch(reroute traffic)

Forced switch(reroute traffic)



4

Figure 4-5ADM node fiber cabling 4-5

FW00239A

53

In the example shown in Figure 4-5, at node A, remove the fibers from the STM16 transmit interface and receive interface circuit packs (or at the fiber patch panel) on the channel (G2) from which the forced switch was operated. The green active LEDs should be off on the circuit packs being removed.

54 Similarly, at Node D, remove the fiber from the STM16 transmit and receive circuit packs (or fiber patch panel) on which the second forced switch was operated.


Step Action

Node C

Node A

Node D

Forced switch

Forced switchG1 G2 G1 G2

G1 G2

Traffic rerouted

Traffic rerouted

G1 G2

Node B

New span

WARNINGRisk of eye injuryAvoid direct exposure to laser beam or fiber. Invisible light that can blind is present. Keep all optical connectors capped.

CAUTIONRisk of eye injuryAvoid touching any components on the printed circuit board. Electrostatic sensitive devices can be damaged by electrostatic discharge. Always ground yourself before handling the circuit pack



55 Make the following connections (in the example given):

• Node A STM16 G2 Tx to node D STM16 G2 Rx

• Node D STM16 G2 Tx to node A STM16 G2 Rx

If there are regenerators between node A and node D, the fiber connections must be as shown in Figure 4-6.

The received optical levels must be measured from the regenerator transmit circuit pack at the regenerator site and on the receive interface circuit pack at the regenerator site.

The “Invalid K-bytes” alarms are cleared.

Figure 4-6Example 2: Regenerators between ADM nodes A and D 4-6

FW00240A

56 Ensure that the fiber connectors are clean before making the final connections to the circuit packs or fiber patch panels. Refer to Common Procedures, 323-1211-846, for the fiber cleaning procedure.


Step Action

G1Rx

G1Tx

G2Tx

G2Rx

G1Rx

G1Tx

G2Tx

G2Rx

G1Rx

G1Tx

G2Tx

G2Rx

G2RxE

G2TxE

G2RxW

G2TxW

Regenerator

9 10 11 12

6 8 9 11 6 8 9 11

6 8 9 11

ADMNode C

FW-2650

ADMNode D

ADMNode A



4

57 The received optical level must meet the guaranteed receive levels before the final connections are made. Therefore, first make the transmit connections, then, using a power meter, measure the associated received optical level at the adjacent site. If necessary, adjust it using an mVOA to within normal operating levels (for example, to −17 dBm). Refer to Technical Specifications, 323-1211-180, for detailed specifications on optical receive levels.

Note: If the circuit pack is receiving from an optical amplifier or high performance transmitter, the receive level must be set to −20 dBm. To set the receive level, adjust the output of the optical amplifier or high performance transmitter.

58 You must verify that the receive optical links for both G1 and G2 on the two network elements (ADM nodes or regenerators) adjacent to the deleted ADM nodes are error free by checking the performance-monitoring MS and RS coding violation counters (MsCV and RsCV). Begin by accessing the network element user interface for one of the two network elements (using the NE Login Manager tool, with the admin userID and password) and entering:

perfmon ↵facperf stm16 <circuit pack group> <east/west>↵

where

<circuit pack group> is g1 or g2

<east/west> is e or w (for regenerators)



Step Action




NE 1

Time 00:38 >


.

...

.

...

**

.

....

.

1 Belfast

Unit: STM16 G1


Curr Last0.0.

0.

0.0.

123.123.

123.

1234.1234.

RsCVRsES

RsSEFSMsCVMsESMsSES

RsSES 0. 123.

1234.0.

Curr Last10 ?10 ?

10 ?

100 ?100 ?

10 ?

100 ?

Rx Near

Day

MsUASMsFC

0.0.

1234.1234.

100 ?100 ?

123.123.

123.

1234.1234.

123.

1234.

1234.1234.

Curr133.133.

133.

1234.1234.

133.

1234.

1234.1234.

Untimed



59 Verify that the MsCV and the RsCV counters do not detect any errors for the current 15 minute timed interval counters. The screen might display counts, but it must not accumulate any new counts. Wait until a new interval is completed and ensure that no new counts are displayed on the screen (if a question mark is displayed next to a count, this count is not valid; wait for the next valid count).

60 Repeat steps 58 and 59 for G2 at ADM nodes or for the other direction for regenerators.

61 Repeat steps 58 to 61 for the other ADM (or regenerator). To access the network element, use the NE Login Manager tool from the OPC user interface. Log in to the network elements by using the admin userID and password.

62 Do not log out

If any of the removed ADM nodes is to be deployed in another ring go to step 63 otherwise go to step 66.

63 If the ADM node is to be deployed in another ring, log on to it using a VT100-compatible terminal connected to user interface port 2. If you do not know how to do this, see Common Procedures, 323-1211-846.

64 Remove the special single-node configuration established by the deletenode command (and clear the associated “ADM node in single node configuration” alarm) by entering:

quit all ↵config ↵createnode ↵yes ↵

65 Leave the command interpreter by entering:

quit ↵mapci↵fwpui↵

66 Open the NE Login Manager tool and access one of the two network elements bounding the new ADM node (Node A or Node D in the example in Figure 4-5 on page 33).



Step Action



4

68 Release the forced switches at nodes A and D by entering:

protectn ↵dtlprot stm16 ↵forced re ↵yes ↵

where

<circuit pack group> is g1 or g2 (in the example givenin Figure 4-5, enter g2 for node A)

Repeat steps 66 through 68 for the second adjacent node (in the example in Figure 4-5, release the forced switch on G2 for node D).

A traffic hit of less than 50 ms occurs when this command is issued. When the forced switches are released on the nodes adjacent to the new node, the newly created span carries live traffic

69 Decommission the ADM node according to the appropriate procedure in Chapter 3.

70 Complete all the final verification checks outlined in the post-expansion verification procedure of Chapter 2.

—end—


Step Action

CAUTIONRisk of service interruptionIf releasing the forced switches causes traffic to be lost, immediately operate the two forced switches that were released in step 68 and call Nortel technical support.



Procedure 4-3Adding a new regenerator into an in-service ring 4-3

Use this procedure to add a regenerator to an existing ring.

As shown in Figure 4-7, to insert the new regenerator on a given TN-16X span, a forced switch must be applied at each of the two ADM nodes terminating the TN-16X line served by the new regenerator. The traffic through the fibers on this span is diverted, so the fibers can be disconnected and the new regenerator cabled in. Once the forced switches are released on the nodes adjacent to the new regenerator at the end of this procedure, the regenerator will carry live traffic. The new configuration data is then saved in the configuration data on the OPC.

Figure 4-7Operating forced switches on span A-B 4-7

FW00241A


• Ensure that the pre-expansion system checks and all other prerequisite tasks as outlined in the appropriate task list have been done.

• Commission the new regenerator as described in Commissioning and Site Testing Procedures, 323-1211-220.

• Connect a VT100-compatible terminal to port B of the primary OPC according to Common Procedures, 323-1211-846.


• Connect a VT100-compatible terminal to user interface port 2 of the new regenerator according to Common Procedures, 323-1211-846.

G2W G2E

Node C

Node A Node B

Node D

Forced switchon G2

Forced switchon G1

FW-2651G1 G2 G1 G2

G1 G2 G1 G2

Span A-B


New regenerator node



4

• Log in to the new regenerator at the admin security level as described in Common Procedures, 323-1211-846. (The default userID is “admin”, with password “admin”.)

Note 1: At least three technicians are required to perform fiber cabling changes (one at each site).

Note 2: Four patchcords are required to cable a new regenerator to the fiber patch panel in a central office. The receive and the regenerator/transmitter cards are installed in the right side of the shelf

Note 3: This procedure can be carried out simultaneously on both the nodes adjacent to the new regenerator.

Note 4: A regenerator shelf used in a ring is equipped for route diversity. That is, only the G2 TN-16X circuit pack group is equipped. This includes two TN-16X receive interface circuit packs and two regenerator/transmit circuit packs on the right side of the shelf (when looking at the shelf from the front).

Tools

Action

as required VT100-compatible terminals (one at each new ADM site and at the primary OPC)

2 NT7E44RA or RB cable for terminal to primary and spare OPC port B connection

as required NT7E44FA or FB cable for terminal to network element port 2 connection

Procedure 4-3Adding a new regenerator into an in-service ring 4-3

Step Action

1 Open the NE Login Manager tool and access one of the two ADM nodes adjacent to the new regenerator (node A or B in the example in Figure 4-7).




3 Operate a forced switch by entering:


where

<circuit pack group> is g1 or g2 (in the example givenin Figure 4-7, enter g2 for node A)


4 Repeat steps 2 and 3 for the second adjacent ADM node (in example in Figure 4-7, operate a forced switch on G1 for node B).

5 Once the traffic on the span that is to be split is protected, the new regenerator can be added by connecting the fibers to the ADM nodes as shown in Figure 4-8.

Figure 4-8Regenerator fibre cabling 4-8

FW00242A

Procedure 4-3Adding a new regenerator into an in-service ring (continued) 4-3

Step Action

Node C

Node A Node B

Node D

Forced switchon G2

Forced switchon G1

FW-2652G1 G2 G1 G2

G1 G2 G1 G2

Span A-X


Node X(new regenerator node)

Span B-XG2W G2E



4

6

In the example shown in Figure 4-8, at node A, remove the fibers from theSTM16 transmit interface and receive interface circuit packs (or at the fiber patch panel) on the channel (G2) from which the forced switch was operated. The green active LEDs should be off on the circuit packs being removed.

7 Similarly, at node B, remove the fiber from the STM16 transmit and receive interface circuit packs (or fiber patch panel) on which the second forced switch was operated.

8 Cable in the new regenerator as shown in Figure 4-9 or Figure 4-10 and as described in steps 9 and 11.


Step Action

WARNINGRisk of eye injuryAvoid direct exposure to laser beam or fiber. Invisible light that can blind is present. Keep all optical connectors capped.




Figure 4-9Cabling in a new regenerator between ADM nodes 4-9

FW00243A

Figure 4-10Cabling in a new regenerator between regenerators 4-10

FW00244A


Step Action

G1Rx

G1Tx

G2Tx

G2Rx

G1Rx

G1Tx

G2Tx

G2Rx

G2RxE

G2TxE

G2RxW

G2TxW

Regenerator

9 10 11 12

6 8 9 11 6 8 9 11

To Node C To Node D

ADMNode B

FW-2656

ADMNode A

G2RxE

G2TxE

G2RxW

G2TxW

Existing regenerator

9 10 11 12

FW-2657

G2RxE

G2TxE

G2RxW

G2TxW

New regenerator

9 10 11 12



4

9 Ensure that the fiber connectors are clean before making the final connections to the circuit packs or fiber patch panels. Refer to Common Procedures, 323-1211-846, for the fiber cleaning procedure.

10 First make the transmit interface connections.

11 Then, at the corresponding receive interface circuit packs, measure the receive level using a power meter. If necessary, adjust it using an mVOA to within normal operating levels (for example, to −17 dBm). Refer to Technical Specifications, 323-1211-180, for detailed specifications on optical receive levels.

Note: If the receive interface circuit pack is receiving from an optical amplifier or high performance transmitter, the receive level must be set to −20 dBm. To set the receive level, adjust the output of the optical amplifier or high performance transmitter.

SDH DCC link fail” alarms are raised against the two adjacent ADM nodes and are cleared after a short period of time (approximately 5 min).

12 On the OPC, open the NE Login Manager tool, and log in to the new regenerator.


Step Action

CAUTIONRisk of service interruptionMonitor the alarms on the OPC after installation of the fibers. If the “Invalid K-bytes” alarm appears, it is likely that you have accidently crossed the fibers at the regenerator. Check the fiber connections.



13 Verify that the receive optical links (for both G2E and G2W) on the new regenerator are error free by entering:

perfmon ↵facperf stm16 g2 e ↵A screen similar to the following is displayed.

FW00226A

14 Verify that the MsCV and the RsCV counters do not detect any errors for the current 15-min timed interval. The screen might display counts but it must not accumulate any new counts. Wait until a new interval is completed and ensure that no new counts are displayed on the screen (if a question mark is displayed next to a count, this count is not valid; wait for the next valid count).

15 Select TN-16X circuit pack group G2 by entering:

select g2 w ↵

16 Repeat step 14 for G2.

17 Repeat steps 13 through 16 for the two ADMs (or regenerators) adjacent to the new regenerator. To access the network element user interface for each of these network elements, use the NE Login Manager tool from the OPC user interface. Log in to the network elements using the admin userID and password.

18 Do not log out of the network elements when completed.


Step Action




NE 1

Time 00:38 >


.

...

.

...

**

.

....

.

1 Belfast

Unit: STM16 G1


Curr Last0.0.

0.

0.0.

123.123.

123.

1234.1234.

RsCVRsES

RsSEFSMsCVMsESMsSES

RsSES 0. 123.

1234.0.

Curr Last10 ?10 ?

10 ?

100 ?100 ?

10 ?

100 ?

Rx Near

Day

MsUASMsFC

0.0.

1234.1234.

100 ?100 ?

123.123.

123.

1234.1234.

123.

1234.

1234.1234.

Curr133.133.

133.

1234.1234.

133.

1234.

1234.1234.

Untimed



4

19 From any node in the ring, log in to the local network element user interface. Issue a remote log in request to the OPC by typing:

quit all ↵rlogin <opc> ↵

where

<opc> is the OPC name

20 Log in to the OPC interface using the netsurv userID and password.

21 Open the Alarm Monitor tool as described in Commissioning and Site Testing Procedures, 323-1211-220.

22 Check that there are no unexpected alarms on the nodes.

Expect to see the following alarms:

• “Forced switch request” (on the two neighboring ADM nodes)

• “Protection switch complete” (on the two neighboring ADM nodes)

Clear any other active alarms. If they cannot be cleared, call your Nortel representative.

23 Open the NE Login Manager tool and access one of the two ADM nodes bounding the new regenerator (node A or B in the example in Figure 4-8 on page 40).


25 Release the forced switches at nodes A and D by entering the following commands.


where

<circuit pack group> is g1 or g2 (in the example given inFigure 4-8, enter g2 for Node A)

A traffic hit of less than 50 ms occurs when this command is issued. When the forced switches are released on the nodes adjacent to the new node, the newly created span carries live traffic.


Step Action



26 Repeat steps 23 through 25 for the second adjacent node (in the example in Figure 4-8 on page 40, release the forced switch on G1 for node B).

27 On each new regenerator in the ring, access the network element by way of the primary OPC, and back up the configuration data to the primary OPC by entering from each network element:

equipmnt sh ↵backupdb ↵yes ↵

28 When a database backup has been completed for each node, return to the OPC user interface by pressing Ctrl_T 0.


30 Transfer the data to the backup OPC as described in Common Procedures, 323-1211-846.

31 Close any open OPC tools and log out from the OPC as described in Common Procedures, 323-1211-846.


—end—


Step Action

CAUTIONRisk of service interruptionIf releasing the forced switches causes traffic to be lost, immediately operate the two forced switches that were released in step 25 and call Nortel technical support.



4

Procedure 4-4Removing a regenerator from an TN-16X ring 4-4

Use this procedure to remove a regenerator from a ring (see Figure 4-11). This procedure requires that you reroute traffic over new optical connections.

To physically remove the regenerator without interrupting traffic, you must operate forced switches on the two ADM nodes terminating the line that the regenerator serves. You can then remove the fibers from the regenerator and reconnect the cables in the new arrangement. When you release the forced switches, traffic is carried on the new fiber connections. The maximum traffic hit for each forced switch is 50 ms.

You then decommission the regenerator (that is, remove it from the OPC span of control).

Figure 4-11Removing a regenerator 4-11

FW00245A



• Check that the regenerator to be removed from the existing ring does not contain an OPC. If it does, move the OPC to a new shelf location as described in Chapter 3.

• Connect a VT100-compatible terminal to the OPC port (port B) of the shelf that contains the primary OPC. See Common Procedures, 323-1211-846.

Node C

Node A

Regeneratorto be removed

Node D

Forced switchon G2

Forced switchon G1

FW-2653

G2 G1 G2 G1

G1 G2

Traffic rerouted

Traffic rerouted

G2W G2E




Note: At least three technicians are required to perform fiber cabling changes (one at each site).

Tools

Action

1 Spare OPC running TN-16X Rel 2 software (a portable OPC or the backup OPC can be used).

1 Blank DDS tape to save the OPC data

as required

VT100-compatible terminals (one at each site)

as required

cable for terminal to primary and spare OPC port B connection

as required

cable for terminal to network element port 2 connection

Procedure 4-4Removing a regenerator from a ring 4-4

Step Action

1 From the User Session Manager, open the NE Login Manager and access one of the two network elements bounding the A-D span, as shown in the example in Figure 4-11 on page 47 (that is, from node A to node D).

2 Log in to the network element using the admin userID. If you don’t know how to do this, see Common Procedures, 323-1211-846.

3 Perform a forced switch by entering:


where

<circuit pack group> is g1 or g2 (in the example given inFigure 4-11 on page 47, enter g2 fornode A)


4 Repeat steps 2 and 3 for the second adjacent node (in the example shown in Figure 4-11, operate a forced switch on G1 for node D).



4

5 Disconnect the regenerator fiber cables.

If Then

Replacing the regenerator decommission the regeneratorwith an ADM node according to the appropriate

procedure in Chapter 3, and connectthe ADM node as described inProcedure 4-1

Otherwise continue with step 6

6 Refer to Figure 4-11 on page 47 and Figure 4-12 for steps 7 to 11.

7 At node A, remove the fibers from the STM16 transmit interface and receive interface circuit packs (or fiber patch panel) on which the forced switch was operated (G2). The green LEDs should not be lit on the circuit packs from which the fibers are removed.

8 Similarly, at node D, remove the fiber from the STM16 transmit interface and receive interface circuit packs (or fiber patch panel) on which the second forced switch was operated (G1).

Procedure 4-4Removing a regenerator from a ring (continued) 4-4

Step Action




Figure 4-12Remove the regenerator 4-12

FW00246A

9 The fiber connectors must be clean before making the final connections to the circuit packs in the new cabling arrangement. Refer to Common Procedures, 323-1211-846, for the fiber-cleaning procedure.

10 The received optical level must meet the guaranteed receive levels before the final connections are made. Therefore, first make the transmit connections, then, using a power meter, measure the associated received optical level at the corresponding receive interface circuit pack. If necessary, adjust the receive level using an mVOA to within normal operating levels (for example, to −17 dBm). Refer to Technical Specifications, 323-1211-180, for detailed specifications on optical receive levels.

Note: If the receive interface circuit pack is receiving from an optical amplifier or high performance transmitter, the receive level must be set to −20 dBm. To set the receive level, adjust the output of the optical amplifier or high performance transmitter

11 Make the following connections:

• Node A STM16 G2 Tx to node D STM16 G1 Rx

• Node D STM16 G1 Tx to node A STM16 G2 Rx

Note: If there are regenerators between node A and node D, they must be connected as shown in Figure 4-13 and Figure 4-14. The received optical level must be measured for the receive interface circuit pack connected to the regenerator transmit interface circuit pack at the regenerator site.

SDH DCC link fail alarms are raised against the two adjacent ADM nodes and are cleared after a short period of time (approximately 5 min)


Step Action

Node C

Node A

Regeneratorto be removed

Node D

Forced switchon G2

Forced switchon G1

FW-2654

G2 G1 G2 G1

G1 G2

Traffic rerouted

Traffic rerouted

G2W G2E



4

Figure 4-13Cabling a regenerator between ADM nodes 4-13

FW00250A

Figure 4-14Cabling two regenerators between ADM nodes 4-14

FW00887A

12 Log in to one of the adjacent network elements from the NE Login Manager tool on the OPC.


Step Action

G1Rx

G1Tx

G2Tx

G2Rx

G1Rx

G1Tx

G2Tx

G2Rx

G2RxE

G2TxE

G2RxW

G2TxW

Regenerator

9 10 11 12

6 8 9 11 6 8 9 11

To Node C To Node C

ADMNode D

FW-2656.1

ADMNode A

G2RxE

G2TxE

G2RxW

G2TxW

9 10 11 12 FW-2657.1

G2RxE

G2TxE

G2RxW

G2TxW

9 10 11 12


13 Verify that the newly connected receive optical links are error free by checking the performance monitoring line coding violation counters (from the network element user interface) by entering:

perfmon ↵facperf stm16 <circuit pack group> ↵

where<circuit pack group> is g1 or g2

A screen similar to the following is displayed:FW00226A

14 Verify that the MsCV and the RsCV counters do not detect any errors for the current 15 minute timed interval. Wait 15 min and ensure that no new counts are displayed on the performance screen. The screen might display counts but it must not accumulate any new counts. Wait until a new interval is completed and ensure that no new counts are displayed on the screen (if a question mark is displayed next to a count, this count is not valid; wait for the next valid count).

15 Repeat steps 12 to 14 for the other neighbor node.

16 From the local network element user interface of any node in the ring, remotely log into the OPC by entering:

quit all ↵rlogin <opc> ↵

where

<opc> is the OPC name

17 Log in to the OPC interface using the netsurv userID and password.

18 Open the Alarm Monitor tool as described in Common Procedures, 323-1211-846.


Step Action




NE 1

Time 00:38 >


.

...

.

...

**

.

....

.

1 Belfast

Unit: STM16 G1


Curr Last0.0.

0.

0.0.

123.123.

123.

1234.1234.

RsCVRsES

RsSEFSMsCVMsESMsSES

RsSES 0. 123.

1234.0.

Curr Last10 ?10 ?

10 ?

100 ?100 ?

10 ?

100 ?

Rx Near

Day

MsUASMsFC

0.0.

1234.1234.

100 ?100 ?

123.123.

123.

1234.1234.

123.

1234.

1234.1234.

Curr133.133.

133.

1234.1234.

133.

1234.

1234.1234.

Untimed


4

End of chapter file

19 Check that there are no unexpected alarms on the nodes.

Expect to see the following alarms:

• “Forced switch request” (on the two adjacent ADM nodes)

• “Protection switch complete” (on the two adjacent ADM nodes)

Clear any other active alarms. If they cannot be cleared, call your Nortel representative.

20 Open the NE Login Manager tool and access one of the two ADM nodes bounding the new regenerator (Node A or Node B in the example in Figure 4-12 on page 50).


22 Release the forced switches at nodes A and D by entering the following commands.


where

<circuit pack group> is g1 or g2 (in the example given in Figure 4-12, enter g2 for node A)

A traffic hit of less than 50 ms occurs when this command is issued. When the forced switches are released on the nodes adjacent to the new node, the newly created span carries live traffic.

23 Repeat steps 21 and 22 for the second adjacent node (in the example in Figure 4-12 on page 50, release the forced switch on G1 for node D).

24 Decommission the regenerator as described in the procedure on decommissioning network elements in Chapter 3.


—end—


Step Action

CAUTIONRisk of service interruptionIf releasing the forced switches causes traffic to be lost, immediately operate the two forced switches that were released in step 22 and call Nortel support.


5-1

5

Chapter 5: Adding and removing tributaries

This chapter describes how to add new 34Mbit/s, STM-1e/140M, STM-1o and STM-4o facilities and tributaries to an in-service TN-16X system. It covers the following situations:

• adding a new 34Mbit/s, STM-1o, STM1e or STM1e/140M interface circuit pack

• replacing a STM1e tributary card with a STM1e/140M tributary and vice versa

• converting a quadrant to use STM-4o tributaries

• converting a quadrant from STM-4o tributaries

Provisioning rules for tributariesTributaries are equipped on a per-quadrant basis on TN-16X terminal shelves. STM-1o, STM1e or STM1e/140M tributaries can be provisioned in any tributary slot in each of the four quadrants of the shelf. However, for growth flexibility, there are advantages in filling the left-most quadrants of the shelf (G1 to G8) before filling the right-most quadrants (G9 to G16). In general, any tributary type can be installed in any quadrant, but there are some restrictions in terms of mixing different tributary types within the same quadrant as follows:

• STM-1e/140M and STM-1o tributaries can be mixed in the same quadrant.

• STM-4o tributaries cannot be mixed with other tributary types in the same quadrant.

• 34Mbit/s tributaries can only be installed in quadrant 4 (G13 to G16)

• If an installation with a greater than half-fill of STM-1o tributaries is provided then a special fibre channel is fitted to the left side of the rack to accommodate the additional optical fibres required.

• If you intend using a combination of STM-1e and optical tributaries in a shelf, install the optical tributaries in quadrants in the following order of priority:


5-2 Adding and removing tributaries

FW01175A

This will minimise the extent of cable reorganisation required.

If STM-1o tributary units are to be fitted to quadrant 2, the existing coax cables must be rerouted to allow space for the optical fibres. Remove the coax cables feeding quadrant 2 and stow the cables in the fibre channel. Secure the cables using a tyrap.

If you are fitting STM-1o cards to quadrants 2 and 4, remove the 4-way cable routing mouldings fitted to the top of the card frame (above the tributary area), to provide space for the fibres.

1 2 3 4 5 6 7 8 9 10 11 12 1314 15 16 17 18 19 20

21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44

QuadrantNo. 1

Priority 1

QuadrantNo. 3

Priority 2

QuadrantNo. 2

Priority 3

QuadrantNo. 4

Priority 4


Adding and removing tributaries 5-3

5

Task listsAdding a new STM-1e or STM-1e/140M interface to an in-service system

If you are adding a new STM-1e or STM-1e/140M interface circuit pack, you must install the required equipment and perform the tests relevant to the circuit pack as outlined in the following task list.

Adding a new 34M interface to an in-service systemIf you are adding a new 34M interface circuit pack, major traffic disruption can occur due to issues involved in the transfer of PDH signals to an SDH environment. If you wish to expand your system to include 34M tributaries. please contact you Nortel representative.

Converting between STM-1e and STM-1e/140M tributariesIf you are converting a tributary from a STM-1e to a STM-1e/140M tributary (or vice versa), you must perform the tasks as outlined in the following task list.

Adding a new STM-1o interface to an in-service systemIf you are adding a new STM-1o interface circuit pack, you must install the required equipment and perform the tests as outlined in the following task list.

Task Reference

Install the cables and circuit packs, as required Installation Procedures, 323-1211-201

Setting up the equipment for the STM-1e/140M tributary tests

Procedure 5-1

Measuring the STM-1e/140M end-to-end timed bit error rate (BER)

Procedure 5-2

Task Reference

Converting between STM1e and VC4e tributaries Procedure 5-3

Task Reference


Measuring optical output power Procedure 5-4

Setting up the equipment for testing new STM-1o or STM-4o tributaries

Procedure 5-5

Testing the continuity/BER on equipped STM-1o and STM-4o tributary slots

Procedure 5-6



Adding a new STM-4o interface to an in-service systemIf you are adding a new STM-4o interface circuit pack, you must install the required equipment and perform the tests as outlined in the following task list.

Converting a quadrant from STM-4o to another tributary typeIf you are converting a quadrant from STM-4o to any other tributary type, you must perform the tasks as outlined in the following task list.

Task Reference

Converting a quadrant to use STM-4o tributaries Procedure 5-7


Measuring optical output power Procedure 5-4

Setting up the equipment for testing new STM-1o or STM-4o tributaries

Procedure 5-5

Testing the continuity/BER on equipped STM-1o and STM-4o tributary slots

Procedure 5-6

Task Reference

Converting a quadrant from STM-4o to any other tributary type

Procedure 5-8



5

Procedure 5-1Setting up the equipment for the STM-1e/140M tributary tests 5-1

Use this procedure to set up the test sets and the equipment to test the operation of new STM-1e/140M tributary circuit packs.

In the case of both STM-1e and 140M interfaces being added, all the 140M interfaces should be tested and then all the STM-1e interfaces.

Figure 5-1 shows an example of the test setup as used with a linear, point-to-point system. One network element (NE) is considered the near end, to which the test set is connected. The other NE is considered the far end, on which loopbacks are established.

This example applies for either a STM-1e or 140M tributary being added at the terminal designated NE 1 (that is, the near-end terminal). The far-end terminal (NE 2) shows a loopback also at the STM-1e/140M level, using any available tributary (typically, you would use the tributary intended to terminate this signal in actual operation). However, for testing purposes, any available tributary can be used.

In a ring, the test setup is similar except that the far-end loopback is made at any available tributary at any add-drop multiplexer (ADM) node in the ring. The tributary being added can be defined as a passthrough STM-1e connection at any number of nodes in the ring before being terminated and looped back, including at a different tributary at the originating node. (In a bidirectional ring, a tributary cannot be routed so that it terminates at itself, as this would form only a unidirectional connection.) More information on testing STM connections in rings is provided in Commissioning and Site Testing Procedures, 323-1211-220.

The procedures in this chapter assume that the loopback uses the same type of tributary as the one being added.

RequirementsThis procedures assumes that the system is in service and carrying traffic (otherwise, follow the site-testing procedures for a new system as described in Commissioning and Site Testing Procedures, 323-1211-220). Before you can do this procedure, the STM-1e/140M interface circuit packs and cabling must be installed as described in Installation Procedures, 323-1211-201.

To minimize travelling time when setting up loopbacks, two technicians are required to perform the procedures in this chapter (one technician at each NE). Voice communication is also required between the sites.



Network element user interfaceYou must have a userID and password for the network element user interface for each NE to which the STM-1e/140M tributaries are being added. (The default userID is “admin” with password “admin”.)

You must be logged in to the network element user interface of the near-end NE. The procedures assume that you are beginning at the main menu level. You can log into the network element user interface either directly from a VT100-compatible terminal or through the OPC. Connection instructions for the VT100-compatible terminal and OPC setup instructions are provided in Common Procedures, 323-1211-846.

Provisioning connectionsThe Connection Manager on the OPC is used to provision connections. If you are unfamiliar with the Connection Manager, refer to Provisioning and Operations Procedures, 323-1211-310.

Figure 5-1An example of the test setup when adding 140M or STM-1e tributaries to an TN-16X system 5-1

FW00249A

Test set

TN-16XNE 1

TN-16X TN-16XNE 2regenerator

Loop backtrib facilitiesunder test

STM-16 traffic

Mini-variable optical attenuator

Ground shielded cable



5

Test apparatus

1 140M digital transmission test set (such as the Tau-Tron S5200D transmitter unit and the S5200E receiver unit), if testing 140M tributaries

1 HP 37704A SDH test set, or equivalent, if testing STM-1 tributaries

1 Variable optical attenuators (VOA) (for example, HP8158B) with single-mode optical test cords or single-mode optical test cords equipped with in-line mini-variable optical attenuators (mVOA)

2 Coaxial test cables with appropriate connectors (to connect the test set to the termination panel

as required Coaxial test cables with appropriate connections (to set up daisy chains and loopbacks)

1 Optical power meter (for example, Photodyne 12XE for 1310 nm)


CAUTIONRisk of service interruptionThis procedure assumes that the network element is carrying live traffic. Take care when making cabling connections that you do not remove or otherwise affect existing cable connections, or traffic might be affected.

CAUTIONRisk of damaging equipmentObserve the safety precautions specified in Chapter 1.



Action

Procedure 5-1Setting up the equipment for the STM-1e or 140M tributary tests 5-1

Step Action

1 If you are testing 140M tributaries, set the 140M test set parameters as follows:

Receiver• 140M unframed• PRBS (Pseudo-random binary sequence)• untimed• total bit errors

Transmitter• 140M unframed• PRBS• error free

2 If you are adding STM-1e tributaries and you are using an HP 37704A SDH test set, set the parameters of the test set as follows:

Receiver• Receive signal: STM-1• Payload: STM-1• Pattern: 223−1 (this is a PRBS signal—pseudo-random binary

sequence)

Transmitter• Transmit signal: STM-1• Clock synchronization: STM1-Rx• Payload: STM-1• Pattern: 223−1 (this is a PRBS signal)

3 If both 140M and STM-1e tributaries are being added, first perform steps 4 through 9 for the 140M tributaries, then repeat those steps for the STM-1 tributaries.

4 At the LTE under test (LTE 1 in Figure 5-1), connect the 140M (or SDH) test set transmitter to the input of the first 140M (or STM-1) facility being added (for example, to 140M or STM-1e circuit pack group G14 Rx).

5 Connect the test set to the output of the new facility. For example, if in step 4 you connected the test set transmitter to G14 Rx, now connect the test receiver to G14 Tx.

6 At the far-end (shown in Figure 5-1 as LTE 2), establish a loopback for the 140M or STM-1e facility being added at LTE 1. That is, the output of that 140M or STM-1e facility must be fed back into its input using a patchcord. Any available 140M or STM-1e port can be used for the loopback. For example, if G3 Rx is available, then G3 Tx should be connected to G3 Rx.



5

7 Using the OPC Connection Manager tool, establish connections for the facilities being added at LTE 1 and for the far-end loopbacks at LTE 2. In a ring, passthrough connections must also be defined at passthrough ADM nodes. The STM connections must agree with the physical cabling. For instructions on how to use the OPC Connection Manager tool, refer to Provisioning and Operations Procedures, 323-1211-310.

8 Reset the 140M (or SDH) test set.The test set displays no bit errors, thereby ensuring that traffic continuity has been established.

9 Ensure that no minor, major, or critical alarms are present on the system. To clear alarms, refer to Alarm and Trouble Clearing Procedures, 323-1211-543.

10 If another 140M or STM-1e interface is being added, repeat steps 4 through 9 for the next circuit pack (leave the daisy chains and loopbacks in place for the bit-error-rate tests, and just move the test set connections).

11 Proceed to Procedure 5-2.

—end—

Procedure 5-1Setting up the equipment for the STM-1e or 140M tributary tests (continued) 5-1

Step Action



Procedure 5-2Measuring the STM-1e/140M end-to-end timed bit error rate (BER) 5-2

Use this procedure to confirm that the bit error rate for the STM-1e/140M tributary over a path between terminals or ADMs is within specification. The procedure can be applied to either a single facility or for a daisy chain of all facilities of a single tributary type (that is, all the new STM-1e or 140M facilities). If both STM-1e and 140M facilities are being added, the two types should be tested separately.

RequirementsBefore starting this procedure, you must ensure that the following requirements are met:

• You must complete Procedure 5-1 and the test setup remains in place.

• You must have userID and password for each network element to which facilities are to be added. (The default userID is “admin” with password “admin”.)

• You must log on to the network element under test as described in Common Procedures, 323-1211-846.

Note 1: To speed up this test, one technician with one set of test equipment should be located at each site.

Note 2: To ensure accurate results, clean the optical connectors as specified in Common Procedures, 323-1211-846. Verify the calibration of the optical meter. Ensure positive mating of fibers in optical connectors.

Test apparatusThe test apparatus required for this procedure are as specified in Procedure 5-1.



5

Action

Procedure 5-2Measuring the 140M or STM-1e end-to-end timed bit error rate (BER) 5-2

Step Action

1 Verify that the 140M (or STM-1e) facilities are in service (IS). Display the facility screen from the main menu and display the active 140M (or STM-1e) channels by entering the following command:

facility <service type> <circuit pack group> ↵

where<service type> is 140M or stm1e<circuit pack group> is g1 to g16 or all


2 If the facility or facilities to be tested are in the null or out of service (OOS) state, activate them by entering the following commands:

facility <service type> <circuit pack group> ↵add ↵

where<service type> is 140M or stm1e<circuit pack group> is g1 to g16 or all

3 If you had to activate the facilities in step 2, establish STM connections for the facilities using the OPC Connection Manager.

4 Access the NE Transport Protection screen and list the active protection events by entering:

protectn ↵listprot ↵


140M Fac0 Quit2 Select3 Query4 5 ListAlms6 AlmRpt7 Loopback8 ChgState9 10 11 Edit12 13 Add14 Delete15 Equipmnt16 17 AlmProv18 Help

NE 1

Time 09:55 >

BiDir 140M Facility Shelf: 1

.

...

.

...

.

....

.

.

State: IS

.

Facility ID:SD Threshold:

< ><1.0E-6>

Unit: VC4e G3

Loopback: None

State: IS

Add

Drop

Facility ID:SD Threshold:

< ><1.0E-6>

Loopback: None

Framing: On

Framing: OffFWPUI:FACILITY:



A screen similar to this one displays system protection status.FW00251A

5 If there are any active protection events, clear the conditions causing them by troubleshooting the active alarms according to Alarm and Trouble Clearing Procedures, 323-1211-543.

6 If you are adding Then go to

a single 140M or stm-1e interface step 9more than one 140M or stm-1e interface step 7

7 If you are adding two or more 140M or stm-1e interfaces, daisy chain all the new facilities together at the terminal under test. In Procedure 5-1, the facilities on each new 140M or stm-1e interface were separately daisy chained and tested. These daisy chains and their associated loopbacks should be still in place from Procedure 5-1, except for the ports that were connected to the test set, so you just have to complete the daisy chain.

For example, if you added 140M or STM-1e circuit pack groups G9, G14, and G15, the daisy chain at the LTE under test (LTE 1 in Figure 5-1) is as follows:

Test set transmitter Tx 140M or STM-1e G9 Rx140M or STM-1e G9 Tx 140M or STM-1e G14 Rx140M or STM-1e G14 Tx 140M or STM-1e G15 Rx140M or STM-1e G15 Tx 140M or STM-1e receiver IN

Procedure 5-2Measuring the 140M or STM-1e end-to-end timed bit error rate

Step Action


Protectn0 Quit23 4 5 ListProt6 7 8 9

10 DtlProt11 12 TrefProt13 14 15 16 17 18 Help

NE 1

Time 17:35 >

NE Transport Protection Shelf: 1

.

...

.

...

.

....

.

..

NE ID

1 Belfast

Low Bandwidth High Bandwidth

ListProt

Fail Lockout Active Fail Lockout Active. . . . . .

Sh

11

Type

STM16ESI

Provisioned

G1G2

G2

CPG Fail

00

Lckt

00

Act

00

Req

00



5

8 Verify that all the loopbacks are still in place from Procedure 5-1. As described in the introduction to Procedure 5-1, the loopbacks do not have to be at matching facilities or even at the same tributary type, as long as existing in-service traffic is not affected. For simplicity, however, corresponding facilities can be used, just as the following example corresponds to the example in step 7:

140M or STM-1e G9 Tx 140M or STM-1e G9 Rx140M or STM-1e G14 Tx 140M or STM-1e G14 Rx140M or STM-1e G15 Tx 140M or STM-1e G15 Rx

9 Using the OPC Connection Manager tool, verify that the connections established in Procedure 5-1 reflect the current daisy-chain and loopback configuration. If not, define the appropriate connections according to Provisioning and Operations Procedures, 323-1211-310.

10 On the 140M (or SDH) test set, operate the single-bit inject error three times.Three bit errors are displayed on the test set. Note: This applies to errors in the PRBS payload, not B1, B2 or B3.

11 Reset the receiver test set and monitor for 1 h. The specifications in the following table should be met

Total number of sites in the path Errored bits2 to 11 Less than 212 to 32 Less than 5

Note: Less than 2 errored bits corresponds to a BER better than 10−11. Less than 5 errored bits corresponds to a BER better than 3.1 x 10−11.

If the limits are not exceeded, record the actual reading and give it to your system administrator.

12 If the limits are exceeded, troubleshoot the condition according to the active alarms (see Alarm and Trouble Clearing Procedures, 323-1211-543). If necessary, sectionalize the daisy chain until the troubled line is found. This is done by halving the daisy chain, determining which half has the fault, and halving again until the faulty 140M is found.

When the trouble is cleared, repeat the 1 h test. If further resolution is required, monitor at each terminal. This provides transmission performance statistics for each direction of the TN-16X multiplex section.

13 If the system is configured as 1:N, repeat steps 1 to 12 for each working channel for which you are adding new tributaries.


Step Action



14 After you complete this test, configure the equipment as required for system operation. That is, remove the test sets, cable the new tributaries as required for in-service traffic, and delete all the test connections. Instructions on how to delete connections provisioned by the OPC Connection Manager are provided in Provisioning and Operations Procedures, 323-1211-310.

—end—


Step Action



5

Procedure 5-3Converting between STM1e and VC4e tributaries 5-3

Use this procedure to replace the STM1e tributary with a VC4e tributary or to replace a VC4e tributary with a STM1e tributary.

Requirements To carry out this procedure, you must:

• have a VT100-compatible terminal connected at the network element (see Common Procedures, 323-1211-846)

• log in to the network element and be at the main menu level (see Common Procedures, 323-1211-846)

Action

CAUTIONElectrostatic sensitive devicesAvoid touching any components on the printed circuit board. Electrostatic sensitive devices can be damaged by electrostatic discharge. Always ground yourself before handling the unit.

Procedure 5-3Converting between STM1e and VC4e tributaries 5-3

Step Action

1 Remove the shelf cover. Refer to Common Procedures, 323-1211-846.

2 From the Network Element Status screen, change the state of the STM1e or 140M facility by entering:

facility <type> <cpg> ↵where:

<type>is stm1e or 140M<cpg> is g1 to g16

chgstate ↵oos ↵yes ↵

3 Delete the facility by entering:

delete ↵yes ↵



4 From the corresponding facility screen, change the state of the STM1e or VC4e equipment:

equipment ↵chgstate ↵oos ↵yes ↵

5 Delete the equipment:

delete ↵yes ↵

6 Remove the circuit pack fully and slide the new circuit pack partially into the shelf, but do not connect it with the backplane. Wait at least 20 seconds between removing and inserting a unit.

7 Complete the circuit pack insertion by firmly pushing the unit so that it connects with the backplane connector.

8 The STM1e (VC4e) circuit pack is now autoprovisioned in STM-1e mode.

Note: If you wish to provision the card as a140M tributary, you must manually change the mode. Refer to the procedure ‘Changing the mode of the VC4e equipment’ in Chapter 2 of Provisioning and Operations Procedures, 323-1211-310.

9 Install the shelf cover. Refer to Common Procedures, 323-1211-846.

—end—

Procedure 5-3Converting between STM1e and VC4e tributaries (continued) 5-3

Step Action



5

Procedure 5-4Measuring optical output power 5-4

Use this procedure to measure the output power from an STM-1 or STM-4 optical interface. Keep a record of the results of this test. Prior to carrying out this test, clean all optical connectors (on optical interface and test cord).

Procedure 5-4Measure optical output power 5-4

Step Action

1 Locate the STM-1o or STM-4o Interface circuit pack that you are going to test and remove the optical fibres if these are connected.

2 Set the optical power meter to measure the appropriate wavelength of the transmitter, as shown on the circuit pack or in the table given in step 4.

3 Connect one end of the optical test cord to the optical power meter and the other end to the transmit optical connector on the circuit pack.

4 Measure and record the indicated optical power meter reading. The measured power should be within the optical power range specified in the following table:

If the requirement is not met:a. Disconnect and reconnect both connectors and repeat steps 3 to 4.b. Replace the optical test cord and repeat steps 3 to 4.c. Clean all optical connectors and repeat steps 3 to 4.d. Replace the circuit pack and repeat steps 3 to 4.

5 Disconnect the optical test cord from the transmit optical connector on the circuit pack.

—end—

WARNINGRisk of eye injuryAvoid direct exposure to laser beam or fibre. Invisible light that can blind is present. Keep all optical connectors capped.

STM-4 Optical Interface Wavelength (nm) Optical power reading (connector loss included)

NT7E02LD (SC connector) 1310 -4.5 dBm to +0.7 dBm

NT7E02LC (PC connector) 1310 -4.5 dBm to +0.7 dBm

STM-1 Optical Interface

NTFW11BD (SC connector) 1310 -8.0 dBm to -15 dBm



Procedure 5-5Setting up the equipment for testing new STM-1o or STM-4o tributaries 5-5

Use this procedure to set up the test sets and the equipment to test the operation of new STM-1o or STM-4o tributary circuit packs.

Figure 5-1 shows an example of the test setup as used with a linear, point-to-point system. One network element (NE) is considered the far end, to which the test set is connected. The other NE is considered the near end, on which loopbacks are established.

This example applies for either a STM-1o or STM-4o tributary being added at the terminal designated NE 1 (that is, the near-end terminal). NE 1 shows a loopback at the STM-1o or STM-4o level.

At the far-end (NE2) the SDH test set is connected to any available tributary . However, for the purposes of these procedures it is assumed that an STM-1o tributary is used.

In a ring, the test setup is similar except that the SDH test set is connected at any available tributary at any add-drop multiplexer (ADM) node in the ring. The tributary being added can be defined as a passthrough STM-1 connection at any number of nodes in the ring before being terminated and looped back, including at a different tributary at the originating node. (In a bidirectional ring, a tributary cannot be routed so that it terminates at itself, as this would form only a unidirectional connection.) More information on testing STM connections in rings is provided in Commissioning and Site Testing Procedures, 323-1211-220.

RequirementsThis procedure assumes that the system is in service and carrying traffic (otherwise, follow the site-testing procedures for a new system as described in Commissioning and Site Testing Procedures, 323-1211-220). Before you can do this procedure, the STM-1o or STM-4o interface circuit packs and cabling must be installed as described in Installation Procedures, 323-1211-201.

To minimize travelling time when setting up loopbacks, two technicians are required to perform the procedures in this chapter (one technician at each NE). Voice communication is also required between the sites.

Network element user interfaceYou must have a userID and password for the network element user interface for each NE to which the STM-1o or STM-4o tributaries are being added and for the NE to which the test set is connected. (The default userID is “admin” with password “admin”.)



5

You must be logged in to the network element user interface of the near-end NE. The procedures assume that you are beginning at the main menu level. You can log into the network element user interface either directly from a VT100-compatible terminal or through the OPC. Connection instructions for the VT100-compatible terminal and OPC setup instructions are provided in Common Procedures, 323-1211-846.

Provisioning connectionsThe Connection Manager on the OPC is used to provision connections. If you are unfamiliar with the Connection Manager, refer to Provisioning and Operations Procedures, 323-1211-310.

Figure 5-2An example of the test setup when adding STM-1o or STM-4o tributaries to a TN-16X system 5-2

FW00249A

Test set

TN-16XNE 2

TN-16X TN-16XNE 1regenerator

Loop backSTM-16 traffic

Mini-variable optical attenuator

Trib facilityunder test



Test apparatus

1 HP 37724A SDH test set, or equivalent

1 Variable optical attenuators (VOA) (for example, HP8158B) with single-mode optical test cords

2 Single-mode optical test cords with appropriate connectors (to connect the test set to the termination panel

1 Optical power meter (for example, Photodyne 12XE for 1310 nm)


CAUTIONRisk of service interruptionThis procedure assumes that the network element is carrying live traffic. Take care when making cabling connections that you do not remove or otherwise affect existing cable connections, or traffic might be affected.

CAUTIONRisk of damaging equipmentObserve the safety precautions specified in Chapter 1.



5

Action

Procedure 5-5Setting up the equipment for testing STM-1o or STM-4o tributaries 5-5

Step Action

1 If an HP 37724A SDH test set is being used for these tests, set the following parameters (or set the equivalent parameters of other types of SDH test set):ReceiverReceive signal: STM-1 Payload: VC4eFraming: BulkPattern: 223−1 (this is a PRBS signal—pseudo-random binary sequence)TransmitterTransmit signal: STM-1 Clock synchronization: ExternalPayload: VC4Framing: BulkPattern: 223−1 (this is a PRBS signal)K2: 0001 0000 (when testing odd-numbered tributary circuit pack groups, that is, G1, G3, G5, and G7)K1: 0010 0001 (when testing even-numbered tributary circuit pack groups, that is, G2, G4, G6, and G8)K2: 0001 0101 (if testing circuit pack group G8)

2 If a building-integrated timing supply (BITS) is available at the site, connect the BITS to the SDH test set. Otherwise, set the SDH test set to loop-timing mode.

3 Connect a test cable with a VOA or in-line mVOA to the transmitter (OUT) of the SDH test set. Connect the other end to the optical power meter.

4 Using the optical power meter, adjust the VOA/mVOA so that the receive level is within the normal operating range for STM-1o interface. See table below:

5 Disconnect the test cable from the optical power meter and connect it to the receiver of the STM-1o tributary.

6 Connect another test cable from the transmitter of the same STM-1o tributary to the receiver (IN) of the SDH test set. Refer to Figure 5-2.

7 At the far-end (shown in Figure 5-1 as LTE 2), establish a loopback for the STM-1o or STM-4o tributary being added at LTE 1. That is, the output of that STM-1o or STM-4o tributary must be fed back into its input using a test cable with a VOA or in-line mVOA.

STM-1 circuit packs Normal operating rangeNTFW11BD - 1310 nm, intermediate reach with SC connector

-28.0 ≤ optical power ≤ -8.0 dBm (for example, -15.0 dBm)



8 Using the OPC Connection Manager tool, establish connections for the far-end loopbacks at LTE 1 and for the facilities being added at LTE 2. In a ring, passthrough connections must also be defined at passthrough ADM nodes. The STM connections must agree with the physical cabling. For instructions on how to use the OPC Connection Manager tool, refer to Provisioning and Operations Procedures, 323-1211-310.

9 Ensure that the STM-1o or STM-4o tributaries to be tested are active, by entering the following command at the TN-16X network element under test: protectn ↵ dtlprot <service type> <circuit pack group> ↵

A screen displays the STM-1 or STM-4 tributary protection status.

10 If the traffic for the STM-1 or STM-4 tributary under test is on the protection channel (that is, G2, G4, G6, or G8 for STM-4 tributaries or G1B to G16B for STM-1o tributaries), operate a manual switch to the corresponding working channel:manual op <circuit pack group> ↵

The STM-1 or STM-4 protection screen indicates that the working circuit pack (for example, G1) is active (that is, “On” is shown under the Traffic Tx and Rx fields) and the protection circuit pack (for example, G2) is the standby (that is, “Off” is shown under the Traffic Tx and Rx fields). Note: Two STM-4 circuit packs are paired for each quadrant of the TN-16X network element that is equipped for STM-4 service, a working and a standby circuit pack. Although the STM-4 protection scheme is 1+1 (non-revertive), by convention the odd-numbered circuit packs are used as the working circuit packs and the even-numbered circuit packs act as standby circuit packs. Thus, G1 is paired with G2, G3 with G4, G5 with G6, and G7 with G8 as working and standby circuit packs, respectively. These site-testing procedures use G1 and G2 as an example.

Procedure 5-5Setting up the equipment for testing STM-1o or STM-4o

Step Action

where

<service type> is stm1 or stm4

<circuit pack group> is g1 to g8 for STM-4is g1 to g16 for STM-1

where

<circuit pack group> is g2, g4, g6, or g8 (for STM-4o protection tributaries). For example, to switch from G2 to G1, enter g2.or g1b to g16b (for STM-1o protection tributaries). For example, to switch from G1B to G1A, enter g1b.



5

11 Reset the SDH test set.The test set displays no bit errors, thereby ensuring that traffic continuity has been established.

12 Ensure that no minor, major, or critical alarms are present on the system. To clear alarms, refer to Alarm and Trouble Clearing Procedures, 323-1211-543.

13 Perform the continuity tests in Procedure 5-6.

14 On completion of the tests, remove all STM-1o and STM-4o connections from the OPC, and remove all physical loops from the STM-1o and STM-4o tributaries.

—end—

Procedure 5-5Setting up the equipment for testing STM-1o or STM-4o tributaries (continued)5-5

Step Action



Procedure 5-6Testing the continuity/BER on equipped STM-1o and STM-4o tributary slots 5-6

Use this procedure to test the continuity of all equipped STM-1 and STM-4 optical interface slots of a terminal shelf in a linear system and an ADM in a ring system.

Note: If protection tributaries are equipped for either STM-1o or STM-4o tributary groups, on completion of this test, remove the working tributaries and replace them with the the protection tributaries in order that they may be tested.

Procedure 5-6Testing continuity on equipped STM-1 or STM-4 interface slots 5-6

Step Action

1 Ensure that the system is set up according to Procedure 5-5, “Setting up the equipment for testing STM-1o or STM-4o tributaries”.

2 Access the STM-1 or STM-4 Protection screen and perform a lockout on the circuit pack group under test by entering:protectn ↵ dtlprot <service type> <circuit pack group> ↵ lockout op <circuit pack group> ↵ yes ↵

3 Use the SDH test set to test the continuity. Monitor the signal for 5 minutes.The display indicates zero bit errors.

where


<circuit pack group> is g1 to g16 for stm4is g1a/b to g16a/b for stm1



5

4 Access the STM-1 or STM-4 Protection screen and release the lockout on the interface under test by entering:protectn ↵ dtlprot <service type> <circuit pack group> ↵ lockout re ↵ yes ↵

5 Continue to monitor the signal for 30 minutes.The display indicates zero bit errors.

6 If there are errors on any of the tests, troubleshoot the problems according to Alarm and Trouble Clearing Procedures, 323-1211-543.

7 Repeat this test on any protection tributaries (if equipped), by installing them in place of the working tributaries.On completion, move all units back to their original slot positions.

—end—

Procedure 5-6Testing continuity on equipped STM-1 or STM-4 interface slots (continued) 5-6

Step Action

where


<circuit pack group> is g1 to g16 for stm4is g1a/b to g16a/b for stm1



Procedure 5-7Converting a quadrant to use STM-4o tributaries 5-7

Use this procedure to change a quadrant equipped with STM-1e/140M or STM-1o, tributaries to use STM-4o tributaries.


• Remove all traffic from the affected facilities.

• Connect a VT100-compatible terminal to the network element, as described in Common Procedures, 323-1211-846.

• Log in to the network element as described in Common Procedures, 323-1211-846.

Tools• VT100-compatible terminal

• NT7E44RA or RB cable for terminal to primary OPC port B connection

• NT7E44FA or FB cable for terminal to network element port 2 connection

Action


Step Action

1 0

Using the OPC Connection Manager, delete the connections for the STM-1o, STM-1e/140M tributaries that are to be taken out of service. For instructions on how to use the OPC Connection Manager, see Provisioning and Operations Procedures, 323-1211-310.

0

CAUTIONRisk of Service InterruptionAll traffic must be removed from the affected facilities before starting this procedure. Otherwise, traffic is lost.



5

2 Place the STM-1o, STM-1e/140M facilities (in the quadrant that is to be converted) out of service by entering:facility <facility type> <circuit pack group> ↵chgstate oos ↵yes ↵

3 Delete the facilities by entering:delete ↵yes ↵

4 Repeat steps 2 and 3 for all the circuit packs in the quadrant .

5 Repeat steps 2 to 4 for all quadrants being converted.

6 Place the equipment (that is, the circuit packs) out of service by entering:equipmnt <equipment type> <circuit pack group> ↵chgstate oos ↵yes ↵

7 Delete the equipment by entering:delete ↵yes ↵

8 Repeat steps 6 and 7 for all circuit packs in the quadrant.


10 Remove the appropriate circuit packs from the shelf.


Step Action

0

where

<facility type> is stm1o, stm1e or 140M

<circuit pack group> is g1 to g16 for stm1e or 140M facilitiesis g1a to g16b for stm1o facilities

0

where

<equipment type> iis stm1o, stm1e or 140M

<circuit pack group> is g1 to g16 for stm1e or 140M equipmentis g1a to g16b for stm1o, equipment



11 Insert the STM-4o circuit pack for the left-most slot of the quadrant (that is, the working circuit pack). When the green LED of the circuit pack is lit, insert the protection STM-4o circuit pack into the right-hand position of the quadrant (if protection is to be equipped). Refer to Table 5-1 for the slot numbers for each quadrant.The circuit packs are automatically provisioned to the in-service state.“STM-4o Rx loss of signal” alarms are raised because the fibers are not connected.For unprotected STM-4o tributaries, the circuit pack must be equipped in the left-most slot of the quadrant (that is, G1, G3, G5, or G7).

12 Install the cables for the new STM-4o tributaries according to Installation Procedures, 323-1211-201.

13 Test the STM-4o tributaries according to Procedure 5-5.

—end—


Step Action



5

Procedure 5-8Converting a quadrant from STM-4o to any other tributary type 5-8

Use this procedure to change a quadrant equipped withSTM-4o tributaries to STM-1o, STM-1e or 140M tributaries.


• Remove all traffic from the affected facilities.

• Connect a VT100-compatible terminal to the network element, as described in Common Procedures, 323-1211-846.

• Log in to the network element as described in Common Procedures, 323-1211-846.

Tools• VT100-compatible terminal

• NT7E44RA or RB cable for terminal to primary OPC port B connection

• NT7E44FA or FB cable for terminal to network element port 2 connection

Action


Step Action

1 0

Using the OPC Connection Manager , delete the STM connections for the STM-4o tributaries that are to be taken out of service. For instructions on how to use the OPC Connection Manager, see Provisioning and Operations Procedures, 323-1211-310.

0

CAUTIONRisk of Service InterruptionAll traffic must be removed from the affected facilities before starting this procedure. Otherwise, traffic is lost.



2 Place the STM-4o facilities (in the quadrant that is to be converted) out of service by entering:facility <facility type> <circuit pack group> ↵chgstate oos ↵yes ↵

3 Delete the facilities by entering:delete ↵yes ↵

4 Repeat steps 2 and 3 for all the circuit packs in the quadrant .


6 Place the equipment (that is, the circuit packs) out of service by entering:equipmnt <equipment type> <circuit pack group> ↵chgstate oos ↵yes ↵

7 Delete the equipment by entering:delete ↵yes ↵

8 Repeat steps 6 and 7 for all circuit packs in the quadrant.


10 Remove the appropriate circuit packs from the shelf.

—end—


Step Action

0

where

<facility type> is stm4

<circuit pack group> is g1 to g8 for stm4o facilities

0

where

<equipment type> is stm4

<circuit pack group> is g1 to g8 for stm4o equipment



5

End of chapter file

Table 5-1Group, and quadrant mapping for 140M, STM-1e, STM-1o and STM-4o equipment 5-1

Slot number Quadrant STM-1o or STM-1e/140M

circuit pack group

STM-4o circuit pack group

2 1 1 1

3 1 2 -

4 1 3 2

5 1 4 -

21 2 5 3

22 2 6 -

23 2 7 4

24 2 8 -

12 3 9 5

13 3 10 -

14 3 11 6

15 3 12 -

36 4 13 7

37 4 14 -

38 4 15 8

39 4 16 -


6-1

6

Chapter 6: Expansion of a 1:N linear system

This chapter describes how to make the following in-service changes relating to multishelf 1:N linear systems:

• add a working channel to a 1:N system

Before any expansion, you must consider the implications to the span of control for the operations controller (OPC) managing the affected network elements. These considerations are described in Chapter 3.

Adding a working channel to an existing 1:N system

This expansion process is used when an additional working channel is added to an existing in-service 1:N system. See the task flowchart in Figure 6-1 and the task list showing the order in which you must carry out the various procedures to effect this expansion in Table 6-1.

Table 6-1 Task list——Adding a working channel to a 1:N system 6-1

Task Reference

Pre-expansion system verification


Chapter 2

Installing the equipment

Install the new network element shelves and cabling Installation Procedures, 323-1211-201

If a new span of control is required, install the new OPC in a network element

Installation Procedures, 323-1211-201, and Commissioning and Site Testing Procedures, 323-1211-220

If required, move the existing primary or backup OPC to a new shelf location

Chapter 3

Preparing the network elements for commissioning

Power up the shelves and set the hardware option settings Commissioning and Site Testing Procedures, 323-1211-220


6-2 Expansion of a 1:N linear system

Save all primary OPC data to tape for all spans of control that are having network elements removed from or added to them

Common Procedures, 323-1211-846

Commissioning a new OPC span of control

Initialize the new primary OPC (and backup OPC, if equipped) Commissioning and Site Testing Procedures, 323-1211-220

Enter the system-level commissioning data for the primary OPC for the new span of control


Move any existing network elements that must now appear in the new span of control

Chapter 3

Copy (synchronize) the commissioning data from the primary to the backup OPC


Adding network elements to existing spans of control

Add the new network elements to an existing span of control Chapter 3

Copy (synchronize) the commissioning data from the primary to the backup OPC


Commissioning the new network elements

Commission each new network element, ensuring that the protection scheme is revertive and the protection-switching mode is bidirectional


Site test each new network element, including any regenerator/optical amplifier shelves on the protection channel or new working channels. While site testing, connect the fiber cables for the new channels between sites, but do not yet connect the STM-16e cables or fibers for the protection loop. Make sure you clean the fiber connectors and set the receive levels before making fiber connections.


Provisioning 1:N protection groups

Determine the channel number that will be assigned to the new channel (for example, if N=1, the next channel added is 2)

Lock out all the working channels in the 1:N system (protection for the in-service channels is unavailable for the duration of the lockouts)

Procedure 6-1

Connect the new shelves into the protection loops at both terminal sites

Procedure 6-1

Modify the protection groups at both terminating ends of the 1:N system

Protection Switching Procedures, 323-1211-311

Define a linear configuration for the new STM-16 working channel


Table 6-1(continued)Task list——Adding a working channel to a 1:N system 6-1

Task Reference


Expansion of a 1:N linear system 6-3

6

Release the lockouts on all the working channels Procedure 6-1

If required, force data consistency between the primary OPC (or primary OPCs, if more than one span of control is required for the 1:N system)

Protection Switching Procedures, 323-1211-311

Making backup copies of 1:N provisioning data

Copy (synchronize) the 1:N provisioning data from the primary to the backup OPC


Save the OPC data to tape Common Procedures, 323-1211-846

Testing the 1:N system

If extra traffic is equipped on the protection channel, disable it for the duration of the system tests. Otherwise, the extra traffic is lost during STM-16 protection switches of the tests. Also, the STM-16 portion of the protection-switching exerciser routine does not run if extra traffic is enabled.


Perform the system tests on the new channel, making certain that the existing in-service traffic is not affected (for example, do not connect test sets to the existing in-service channels or perform protection switching on the existing channels). For the new channels only, perform the protection-switching tests, long-term bit-error-rate tests, and any feature tests applicable to the added network elements (for example, STM-4 tributary and ESI tests).


Post-expansion system verification

Before adding new in-service traffic, verify the system integrity Chapter 2

Provisioning the facility parameters and STM connections

Provision the facility parameters and traffic-carrying STM connections for the system

Provisioning and Operations Procedures, 323-1211-310

—end—

Table 6-1(continued)Task list——Adding a working channel to a 1:N system 6-1

Task Reference



Figure 6-1Task flowchart—Adding a working channel to a multishelf 1:N system

FW-1798

Site test the new network elements(323-1211-221)

Commissionnew

network elements

Rearrange the OPCspan of control(if necessary)

Lock outall TN-16Xchannels

Check the 1:Nprovisioning

data

Release thelockouts

Move the OPC

(if necessary)

Save thedata totape

Transfer the datato the backup

OPC

Test the new channel(323-1211-222)

Connect the newchannel to theprotection loop

Install new 1:N shelves, as required. See NTP 323-1211-201.

Do not touch or change existing in-service equipment. Power up and prepare the new network elements

for commissioning, but do notcommission them.

Perform the pre-expansion

verification (Chapter 2)

If required, reenable the extra traffic

Add the new channelto the protection

groupsProvision the

traffic-carrying STS connections

(323-1211-310)Establish a linear

configuration for the new channel

Perform the post-expansion

verification (Chapter 2)



6

Procedure 6-1Connecting a new shelf into a protection loop 6-1

When adding a new channel to an existing 1:N system, use this procedure to connect the protection loop cabling to the new terminal shelves at both terminal sites.

Note: STM-16 protection switching is not available for the in-service traffic until this procedure and the 1:N provisioning procedures have been completed at both terminal sites and the lockouts on all STM-16 working channels have been released.




• Log in to the primary OPC at the slat security level as described in Common Procedures, 323-1211-846. (The default userID is “slat”, with password “slat”.)

• Obtain a userID and password for the network elements you are going to add to the protection loop. (The default userID is “admin”, with password “admin”.)

• To minimize the time that STM-16 protection switching is not available, a technician must be present at both terminating sites.

• At least 90-min access to the system is required to complete the expansion procedures and to restore STM-16 protection switching.

Action


Step Action

1 Using the OPC NE Login Manager tool, log in to one of the terminals for the first working channel in the system and perform a lockout by entering the following commands:

protectn ↵ dtlprot stm16↵ lockout op ↵ y ↵



2 Access the STM-16 protection-switching screen by entering:

protectn ↵dtlprot stm16 ↵The STM-16 protection switching screen is displayed.

FW00945A

3 Operate a lockout by entering:

lockout op ↵

A prompt for confirmation is displayed.

y ↵

The channel is now locked out and any request for a protection switch is denied.

4 Repeat steps 1 to 3 to operate lockouts on all channels that are part of the 1:N system, including the new shelf that is being connected to the protection loop.

You can use the OPC NE Login Manager tool to log in to the first terminal from the primary OPC. You can then use the selectne command to log in to each successive terminal in the protection group. If you don’t know how to use these commands, see Common Procedures, 323-1211-846.

5 Close the STM-16 Protection screen by entering:

quit ↵

6 Close the OPC NE Login Manager tool. If you don’t know how to do this, see Common Procedures, 323-1211-846.

7 Connect the protection loop STM-16e coaxial, as described in Installation Procedures, 323-1211-201.


Step Action

Critical Major minor warning FailProt Lockout ActProt PrfAlrt Network View • • 1 2 • • • * 1 St.John's • • 1 1 • • • • STM16 Prot 0 Quit STM16 Protection Shelf: 1 2 Protectn Grp: 1 Exerciser: Off 3 Protectn Scheme: 1:N 4 Traffic 5 ListAlms State Protectn Lckt Forced Auto Manual Tx Rx 6 AlmRpt G1 IS Active • • • • On On 7 Lockout G2 IS Standby - • • • Off Off 8 Forced Note: For non-diversely routed 1:1/1+1 configurations, terminal 9 Manual STM16 G1 is connected to regenerator STM16 G2 and terminal 10 STM16 G2 is connected to regenerator STM16 G1. Refer to 11 the on-line configuration diagrams (enter 'Help'). 12 - Default Working - - Default Protection - 13 Terminal - STM16 G1: Slots 6,7,8 STM16 G2: Slots 9,10,11 14 Regenerator - STM16 G2E: Slots 9,10 STM16 G1E: Slots 5,6 15 Equipmnt STM16 G2W: Slots 11,12 STM16 G1W: Slots 7,8 16 Facility 17 18 Help NE 1 Time 17:35 >



6

End of chapter file

8 Continue with the tasks in Table 6-1. When directed by the task list to release the lockouts, log in to one of the terminals for each working channel in turn and enter the following commands:

protectn ↵dtlprot stm16 ↵ lockout release ↵ yes ↵

—end—


Step Action


7-1

7

Chapter 7: Converting to the 2MHz ESI circuit pack

General descriptionThis document details the procedures to replace a pair of 1.5 Mbit/s External Synchronisation Interface (ESI) (NT7E27AA or NT7E27BA) circuit packs with a pair of 2 MHz ESI circuit packs (NTFW27AA).

EquipmentThis procedure applies to TN-16X ADM or terminal shelves which are running Release 3.1 (or later) software. Regenerator nodes do not require ESI circuit packs to be fitted.

Required equipmentTable 7-1 details the equipment which is required in order to complete the procedure:

0

Table 7-1Required equipment 7

Qty. Description Suitable models or part No.

2 2 MHz ESI circuit pack NTFW27AA

1 120 Ω terminator (required if ESI is being used in 75 Ω mode)

NTFW5072

1 VT100 terminal or PC with VT100 emulator (with connecting cable)

DIGITAL VT100

—end—


7-2 Converting to the 2MHz ESI circuit pack

PreparationsCarry out the following actions before replacing the ESI circuit packs:

• Obtain the current node timing information for each ADM and terminal in the system. If this information is not available, it will be necessary to interrogate each TN-16X ADM or terminal node (using a VT100 terminal) to determine the following:

— Shelf clock source (this should be esi)

— Primary input timing reference source

— Secondary input timing reference source

— ESI target filter mode

— ESI G1out and G2out timing distribution source settings (if applicable)

• On all 2 MHz ESI circuit packs, set jumpers J4 and J5 to either 75 Ω or 120 Ω as required. The 75 Ω option uses BT type 43 connectors, and the 120 Ω option uses a 15-way D-type connector (the connectors are located on the shelf side panel).

• If the 75 Ω option is being used, ensure that a 120 Ω terminator (NTFW5072) is available for each NE before starting the upgrade.

0

1.5 Mbit/s to 2 MHz ESI replacement proceduresUse one of the two following procedures to replace the ESI circuit packs:

• For shelves which are externally timed (BITS timed) use Procedure 7-1.

• For shelves which are line timed (stmA or stmB) use Procedure 7-2.

Recovery procedureIn the event of the new 2 MHz circuit pack not provisioning correctly, use Procedure 7-3 to repeat the upgrade.


Converting to the 2MHz ESI circuit pack 7-3

7

Procedure 7-1Converting a shelf which uses BITS timing 7-1

Use this procedure to convert an ADM or terminal shelf which is configured to receive its timing from an external timing source, connected to the BITSA input, the BITSB input or to both inputs.

Action

Procedure 7-1Converting a shelf which uses BITS timing 7

Step Action/response

1 Confirm that the initial shelf conditions are as follows:1.5 Mbit/s DS1 signal connected to BITSA and BITS B.PRI = BITSA.SEC = BITSB.ESI G1 = Active, Normal.ESI G2 = Standby, Normal.NE clock source = ESI.

2 Put the secondary timing reference to null by entering:eq esi g1 ↵trefprot ↵sectsrc null ↵yes ↵

3 Put ESI cards current mode into holdover by entering:eq esi g1 ↵edittarg holdover ↵G1 current mode changes to holdover.eq esi g2 ↵G2 current mode changes to holdover.

4 Lockout protection on G1 by entering:dtlprot ↵lockout op g1 ↵yes ↵Asterisk appears in Lockout column of G1.An ESI G1 equipment lockout alarm is raised.



5 Put facilities BITSA, BITSB, G1OUT and G2OUT out of service by entering:fa esi bitsa ↵chgstate oos ↵yes ↵fa esi bitsb ↵chgstate oos ↵yes ↵fa esi g1out ↵chgstate oos ↵yes ↵fa esi g2out ↵chgstate oos ↵yes ↵Each facility becomes OOS.A primary timing reference fail alarm is raised.

6 Put the G2 card out of service and then delete it by entering:eq esi g2 ↵chgstate oos ↵yes ↵delete ↵yes ↵

7 Detach the DS1 input cable from the BITS connector.

8 Remove the ESI G2 card from the shelf. Wait 30 seconds and then insert the new 2MHz ESI card in the G2 slot.G2 autoprovisions with a 2MHz ESI NTFW27AA circuit pack.G2 enters holdover mode.An ESI G2 subunit incompatible alarm is raised.

If G2 does not autoprovision as stated, remove the new ESI circuit pack, wait 30 seconds and then re-insert it.If G2 does provision but does not enter holdover mode, or if either of the LEDs on the G2 circuit pack turn ON, follow the recovery procedure detailed in Procedure 7-3.

9 Access the ESI Facility screen by entering:fa esi bitsa ↵BITSA screen still refers to DS1 features.

If you are using Then go to

a 75 Ω BITS source step 10

a 120 Ω BITS source step 11





7

10 Insert a 120 Ω terminator (NTFW5072) into the 120 Ω BITS subrack connector and then connect a 75 Ω 2 MHz clock signal to the 75 Ω BITSA subrack input.Wait 60 seconds.Go to step 12.

11 Insert the 15-way D-type connector (carrying both the BITSA and BITSB signals) into the 120 Ω BITS subrack connector.Wait 60 seconds.

12 Put the BITSA facility in-service by entering:chgstate is ↵BITSA shows IS (still refers to DS1 features).(BITSA may also show IS Mtce-Facility Fail and the BITSA Bipolar Violation alarm may be raised. These effects can be ignored and will clear down when the G1 card is deleted in step 18.

13 Set G2 target mode = normal (see note) by entering:eq esi g2 ↵edittarg normal ↵G2 proceeds to Normal mode.If G2 does not proceed to normal mode, follow the recovery steps detailed in Procedure 7-3.

Note: G1/G2 target modes temporarily separate during upgrade.

14 Wait 1 hour for G2 to stabilise.

15 Release G1 lockout by entering:dtlprot ↵lockout re g1 ↵yes ↵Asterisk clears from G1 lockout indicator.

16 Perform a manual switch from G1 to G2 by entering:manual op g1 ↵yes ↵Manual switch completes such that G1 → Standby, G2 → Active.

17 Lockout G2 by entering:lockout op g2 ↵yes ↵Lockout asterisk on G2.





18 Put ESI G1 out of service and delete it by entering:eq esi g1 ↵chgstate oos ↵yes ↵G1 shows OOS.delete ↵yes ↵

19 Remove the ESI G1 card from the shelf. Wait 30 seconds and then insert the new 2MHz ESI card in the G1 slot.G1 autoprovisions with a 2MHz ESI NTFW27AA circuit pack.G1 target mode autoprovisions to Normal.G1 proceeds to Normal mode.The ESI G2 subunit incompatible alarm is cleared (raised in step 8).


21 Remove G2 lockout by entering:dtlprot ↵lockout re g2 ↵yes ↵G2 lockout removed.G2 stays Active, G1 stays Standby.

22 Access the BITSB ESI Facility screen by entering:fa esi bitsb ↵

23 If you are using the 75 Ω BITSB input, connect a 75 Ω 2 MHz clock signal to the 75 Ω BITSB subrack input.BITSB changes from OOS Mtce-Facility Fail to OOS (typically 30 second delay).

Note: If you are using the 120 Ω inputs, BITSB should be already connected, and will already be OOS.

24 Put the BITSB facility in-service by entering:chgstate is ↵BITSB shows IS.

25 Put BITSB as the secondary ESI timing reference input by entering:trefprotsectsrc bitsbyesSEC shows "BITSB IS Standby".

—end—





7

Procedure 7-2Converting a shelf which uses Line timing 7-2

Use this procedure to convert an ADM or terminal shelf which is configured to receive its timing from one of its STM-16 optical circuit pack groups (stmA or stmB).

Action

Procedure 7-2Converting a shelf which uses Line timing 7


1 Confirm that the initial shelf conditions are as follows:PRI = STMA or STMB.SEC = Null (see Note).BITSA and BITSB OOS.ESI G1 = Active, Normal.ESI G2 = Standby, Normal.NE clock source = ESI.

Note: To avoid timing loops in ring ADM configurations in which line timing is used, the primary reference must be provisioned to either STMA or STMB and the secondary reference must be provisioned to Null.

2 Lockout protection on G1 by entering:eq esi g1 ↵dtlprot ↵lockout op g1 ↵yes ↵Asterisk appears in Lockout column of G1.

3 Put facilities G1OUT and G2OUT out of service by entering:fa esi g1out ↵chgstate oos ↵yes ↵fa esi g2out ↵chgstate oos ↵yes ↵Each facility becomes OOS.

4 Put the ESI G2 card out of service and delete it by entering:eq esi g2 ↵chgstate oos ↵yes ↵delete ↵yes ↵



5 Remove the ESI G2 card from the shelf. Wait 30 seconds and then insert the new 2MHz ESI card in the G2 slot.G2 autoprovisions with a 2MHz ESI NTFW27AA circuit pack.G2 proceeds to Normal mode.

If G2 does not autoprovision as stated, remove the new ESI circuit pack, wait 30 seconds and then re-insert it. If G2 does provision but does not enter normal mode, or if either of the LEDs on the G2 circuit pack turn ON, follow the recovery procedure detailed in Procedure 7-3.


7 Release G1 lockout by entering:dtlprot ↵lockout re g1 ↵yes ↵Asterisk clears from G1 lockout indicator.

8 Perform a manual switch from G1 to G2 by entering:manual op g1 ↵yes ↵Manual switch completes such that G1 → Standby, G2 → Active.

9 Lockout G2 by entering:lockout op g2 ↵yes ↵Lockout asterisk on G2.

10 Put ESI G1 out of service and delete it by entering:eq esi g1 ↵chgstate oos ↵yes ↵G1 shows OOS.delete ↵yes ↵

11 Remove the ESI G1 card from the shelf. Wait 30s and then insert the new 2MHz ESI card in the G1 slot.G1 autoprovisions with a 2MHz ESI NTFW27AA circuit pack.G1 proceeds to Normal mode.


13 Remove G2 lockout by entering:dtlprot ↵lockout re g2 ↵yes ↵Asterisk clears from G1 lockout indicator.G2 stays active and G1 stays standby.

Procedure 7-2Converting a shelf which uses Line timing 7




7

Procedure 7-3Recovering from a failed 2 Mhz ESI upgrade 7-3

Use this procedure if the new 2 MHz circuit pack does not provision correctly. The procedure allows you to remove the new card and start the upgrade again. You should only use this recovery procedure if you are prompted to do so during either Procedure 7-1 (BITS timed) or Procedure 7-2 (Line timed).

Note: Do not use this procedure once the 2 MHz card has entered normal mode.

If you are carrying out a line timed upgrade, ignore any actions/responses in this procedure which refer to BITS

Action

Procedure 7-3Recovering from a failed 2 Mhz ESI upgrade 7


1 Put G2OUT out of service (OOS) by entering:fa esi g2out ↵chgstate oos ↵yes ↵G2 facility becomes OOS.

2 Put the ESI G2 card out of service and delete it by entering:eq esi g2 ↵chgstate oos ↵yes ↵delete ↵yes ↵

3 Remove the 2 MHz BITS signal (either 75 Ω or 120 Ω).Remove the 120 Ω terminator (if fitted).

4 Remove the 2 MHz ESI G2 card from the shelf. Wait 30 seconds and then insert the old 1.5 Mbit/s ESI card back into the G2 slot.

5 Reconnect the 1.5 Mbit/s BITS signal.

6 Put the ESI cards back to normal mode by entering:eq esi g1 ↵edittarg normal ↵yes ↵

7 Check that the 2 MHz BITS signal is valid, before repeating the upgrade procedure (either Procedure 7-1 or Procedure 7-2, as applicable).



End of chapter file

8 If the 2 MHz BITS signal is valid, and the upgrade fails repeated attempts, the 2 MHz card should be considered faulty and replaced.

—end—

Procedure 7-3Recovering from a failed 2 Mhz ESI upgrade 7



Test Result Sheet

0

Converting to the 2MHz ESI circuit pack

Comments

Network name : Station Name :

Shelf serial number :

NTFW27AA ESI card 1 serial number :

NTFW27AA ESI card 2 serial number :

Testers Name (s) : Date :

Preparations Tick

Converting a shelf which uses BITS timing

Procedure 7-1 Tick

Converting a shelf which uses Line timing

Procedure 7-2 Tick

End of chapter file

Acceptance form

The procedures detailed within this document have been carried out by representatives of Nortel Limited and have been found to be satisfactory for the acceptance of the equipment upgrade.

Nortel representative

Name:

Signature:

Date:

Customer representative

Company:

Name:

Signature:

Date:

8-1

Index 8

Numerics2MHz ESI converting 7-1

AAdd-drop multiplexer (ADM)

node, adding 4-6

CCommissioning Data Record form 3-27Control Network (CNet)

SDH DCC bridge, connecting 3-1

FForms

commissioning data 3-27

NNetwork element (NE)

adding to existing span-of-control 3-7moving to a new span-of-control 3-11software loads

determining 3-5

OOPC

moving to another shelf location 3-18software

loads, determining 3-5span-of-control

add/delete list 3-3

PProtection

protection loopnew shelf, connecting 6-5

RRegenerator

adding to ring 4-38Ring (MS SPRing)

ADM nodeadding 4-6removing 4-22

regeneratoradding 4-38removing 4-47

ring (MS SPRing) systems 4-1

SSDH DCC bridge

connecting systems 3-1STM-1 Electrical Tributary Unit

replacing 5-15STM-1 tributaries

adding or removing 5-1STM-1e/140M

tributariesconverting from STM-4o 5-26, 5-29

System expansion 4-1CNet and SDH DCC bridge 3-1converting to 2MHz ESI 7-1

shelf using BITS 7-3shelf using line timing 7-7

linear systems1+1 to 1:N 6-11:1 to 1:N 6-1adding channels to 1:N systems 6-1non-route diverse to route diverse 3-1working channel, adding 6-1

post-expansion verification 2-1pre-expansion verification 2-1span of control 3-1STM-1 tributaries, adding or removing 5-1


8-2 Index

TTesting

system expansionpre- and post-expansion verification

2-1Tributaries

converting from STM-4o to STM-1e/140M 5-26, 5-29

VVerification

pre- and post-expansion checks 2-1


Contacts Legal statements Trademarks

International Broadband Networks (Dept. 18600)Nortel LimitedOakleigh Road SouthLondon, N11 1HB

So far as Northern Telecom is aware the contents of this document are correct. However, such contents have been obtained from a variety of sources and Northern Telecom can give no warranty or undertaking and make no representation as to their accuracy. In particular, Northern Telecom hereby expressly excludes liability for any form of consequential, indirect or special loss, and for loss of data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein or any third party arising out of the contents of this document.

Family Product Manual Copyright Copyright statement NT confidetial DocNum DocIssue DocStatus Date Publishing statement

SDH Transmission

TN-16XSystem Expansion Procedures

Copyright 1994 - 1997 Northern Telecom

The copyright of this document is the property of Northern Telecom. Without the written consent of Northern Telecom, given by contract or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person whatsoever.

NORTHERN TELECOM CONFIDENTIAL: The information contained in this document is the property of Northern Telecom. Except as specifically authorized in writing by Northern Telecom, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation, and maintenance purposes only.

Document number: 323-1211-224Document issue: Release 4.2Document Status: StandardDate: March 1997Printed in England

nortel tn-16

Documents

property of northern

document number

document status

standard tn

preliminary release

rack24 release

northern telecomthe

standardproduct release