nlnt8f3_

NT0H65AENT0H65AE 323-1701-310

Nortel Networks

OPTera Metro 5200 Multiservice PlatformProvisioning and Operating Procedures:Chapters 54 to 59

What’s inside...Seating circuit packsUsing the System ManagerProvisioning circuit packs and managing trafficShelf management proceduresUpgrading OPTera Metro 5200 softwareAppendix—System Manager windows and fields

Standard Release 4.0 Issue 1 November 2001

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Nortel Networks, the Nortel Networks logo, the Globemark, How the World Shares Ideas, OPTera, and Unified Networks are trademarks of Nortel Networks.

HP and HP-UX are trademarks of Hewlett-Packard, Inc. Pentium is a trademark of Intel Corporation. Internet Explorer, Windows, and Windows NT are trademarks of Microsoft Corporation. Netscape Communicator is a trademark of Netscape Communications Corporation. Common Desktop Environment, Java, Solaris, and Ultra are trademarks of Sun Microsystems, Inc. UNIX is a trademark of X/Open Company Limited.

Printed in Canada and in the United Kingdom

Copyright 2000–2001 Nortel Networks, All Rights Reserved

Provisioning and Operating Procedures 323-1701-310 Rel 4.0 Issue 1 Standard Nov 2001

iii

Contents 0

Seating circuit packs 54-1Sequence for provisioning a new wavelength 54-3

Seating the SP and one OCM circuit pack 54-6

List of procedures54-2 Seating the circuit packs 54-8

Using the System Manager 55-1User levels and access privileges 55-2Access to the System Manager through IP addresses 55-2

List of procedures5S5-1 Logging in to the network 55-555-2 Changing the OPTera Metro 5200 password 55-655-3 Editing the naming, timing and basic communications settings 55-855-4 Viewing detailed event history 55-1455-5 Viewing the event console 55-1555-6 Saving event logs 55-1655-7 Printing event lists 55-1755-8 Clearing the event console 55-1855-9 Configuring telemetry alarms 55-2055-10 Saving the alarm list 55-2355-11 Printing the alarm list 55-2455-12 Acknowledging visual alarms 55-2555-13 Selecting shelves 55-2755-14 Sorting shelves 55-2955-15 Sorting information 55-3055-16 Saving information 55-3255-17 Printing information 55-3355-18 Adding, deleting, and getting details of information 55-3455-19 Querying the inventory list 55-3555-20 Querying facilities 55-3655-21 Querying channel assignments 55-3755-22 Changing the date and time on a shelf 55-3855-23 Provisioning Ethernet port alarms 55-4055-24 Provisioning Ethernet ports 1 and 2 55-4155-25 Defining or changing IP addressing and advanced communications settings

for the network 55-4255-26 Assigning IP addresses for Ethernet port 2 and serial ports 1 and 2 55-46

iv Contents

OPTera Metro 5200 Multiservice Platform 323-1701-310 Rel 4.0 Issue 1 Standard Nov 2001

55-27 Configuring shelf surveillance and external management 55-4855-28 Backing up shelf configuration data 55-4955-29 Restoring shelf configuration data 55-5255-30 Changing clock reference settings for a SONET/SDH SRM OCI 55-5555-31 Performing a health check 55-5755-32 Retrieving a health check report 55-5955-33 Viewing the Login User List 55-6055-34 Exiting the System Manager 55-61

Provisioning circuit packs and managing traffic 56-1Circuit pack and facility states 56-1

Facilities 56-1Changing the state of circuit packs and facilities 56-2

Requirements 56-3Procedure list 56-4

List of procedures56-1 Manually provisioning circuit packs 56-656-2 Making channel assignments 56-956-3 Deleting channel assignments 56-1756-4 Putting a circuit pack in-service 56-1956-5 Taking a circuit pack out-of-service 56-2056-6 Putting a circuit pack facility in-service 56-2156-7 Putting a WSC facility in-service 56-2256-8 Taking a circuit pack facility out-of-service 56-2456-9 Manually provisioning an ECT 56-2556-10 Removing traffic from an OCI circuit pack 56-2756-11 Adding traffic to an OCLD circuit pack 56-2856-12 Removing traffic from an OCLD circuit pack 56-2956-13 Adding traffic to an OTR circuit pack 56-3156-14 Removing traffic from an OTR circuit pack 56-3256-15 Adding path protection to an unprotected path 56-3456-16 Forcing traffic to one path on a protected channel 56-3656-17 Removing a forced path switch 56-3856-18 Creating two unprotected paths from one protected OCLD path 56-3956-19 Creating two unprotected paths from one protected OTR path 56-4156-20 Locking out a circuit pack 56-4356-21 Forced switching on OCM circuit packs 56-4456-22 Manual switching on protected channel assignments 56-4656-23 Manual switching on OCM circuit packs 56-4756-24 Creating a loopback using the System Manager 56-4956-25 Manual switching of clock references for a SONET/SDH SRM OCI 56-5056-26 Upgrading a shelf to 2.5 Gbit/s OCM circuit packs 56-52

Shelf management procedures 57-1Adding or removing OPTera Metro 5200 shelves from a network 57-1

List of procedures57-1 Decommissioning a shelf 57-457-2 Deleting a shelf 57-657-3 Restarting a shelf 57-7

Contents v


57-4 Adding a shelf to a path-protected network 57-857-5 Adding a shelf to an unprotected network 57-957-6 Adding a shelf to a linear OADM network 57-1057-7 Changing configuration information for a shelf 57-1157-8 Configuring shelf surveillance and external management 57-1357-9 Removing a shelf surveillance and external management entry 57-1557-10 Switching traffic off a span in a path-protected network 57-16

Upgrading OPTera Metro 5200 software 58-1

Appendix—System Manager windows and fields 59-1System Manager main window 59-1

Network shelf selector icons 59-1Commands and menu options 59-2Alarm banner colors 59-5Accessing information windows 59-6Refreshing System Manager windows 59-7

Fault window 59-7Fault—Active Alarms window 59-7Fault—Active Alarms—Alarm Details window 59-8Fault—Event Console window 59-10Fault—Event History window 59-11Fault—Event Console or Event History—Event Details window 59-12

Equipment window 59-13Equipment—Inventory window 59-13Equipment—Facilities window 59-16Equipment—Inventory or Facilities—Details window 59-18Equipment—Facilities—OPTera Metro 5200 Facility window 59-20Equipment—Telemetry window 59-22Equipment—Telemetry—Parallel Telemetry Input window 59-23Equipment—Telemetry—Parallel Telemetry Output window 59-24

Channel Assignments window 59-26Channel Assignments—OPTera Metro Channel Assignments window 59-27Channel Assignments—OPTera Metro Timing window 59-30

Configuration window 59-31Configuration—Shelf List window 59-31Configuration—Naming window 59-32Configuration—Communications window 59-33Configuration—Time window 59-34Configuration—Naming, Communications or Time— Shelf Configuration

window 59-34Configuration—surveillance tab 59-42

Admin—Software upgrade window 59-44Admin—Login User List window 59-45Performance Monitor window 59-45

Performance Monitor—Launch PM window 59-45Date and time notes 59-52Time stamp rules 59-53

Index

vi Contents



vii

About this document 0This document provides information about provisioning and operating the Nortel Networks OPTera Metro 5200 Multiservice Platform using the System Manager interface.

This document contains the following information:

• using the System Manager

• provisioning circuit packs and managing traffic

• shelf management procedures

• upgrading the software

• System Manager windows and fields

Audience for this documentThis document is intended for the following audience:

• strategic and current planners

• provisioners

• installers

• transmission standards engineers

• field maintenance engineers

• system line-up and testing (SLAT) personnel

• maintenance technicians

• network administrators

OPTera Metro 5200 libraryThe OPTera Metro 5200 library consists of the Nortel Networks OPTera Metro 5200 Multiservice Platform Technical Publications, NT0H65AE.

Technical PublicationsThe OPTera Metro 5200 Multiservice Platform Technical Publications (NTP) consist of descriptive information and procedures.

viii About this document


Descriptive informationThese NTPs provide detailed descriptive information about the OPTera Metro 5200 Multiservice Platform, including system, software, and hardware descriptions, technical specifications, ordering information, and TL1 user information.

ProceduresThese NTPs contain all procedures required to install, provision and maintain the OPTera Metro 5200 Multiservice Platform.

The following roadmap lists the documents in the OPTera Metro 5200 library.

OM0881t

Maintaining andTroubleshooting

a Network

Installing,Commissioning andTesting a Network

Managingand Provisioning

a Network

Provisioning andOperating

Procedures(323-1701-310)

Trouble Clearingand Alarm

Reference Guide(323-1701-542)

Maintenance andReplacement

(323-1701-546)

PerformanceMonitoring

(323-1701-520)

Planning aNetwork

About the NTPLibrary and

Master Index(323-1701-002)

Network Planningand Link Engineering

Guidelines(NT0H7104)

Software and UserInterface Description

(323-1701-101)

Hardware Description(323-1701-102)

TechnicalSpecifications

(323-1701-180)

TL1 Interface(323-1701-190)

Installing Shelvesand Components(323-1701-201)

Powering andCommissioning

Procedures(323-1701-220)

Test Procedures(323-1701-222)

About this document ix


Technical supportNortel Networks provides international technical support for the OPTera Metro 5200. Have your Express Routing Code and PIN (Personal Identification Number) ready before you call any of these numbers.

North America and the Caribbean

Carrier customers

For 24-hour emergency technical support for problems that affect service, call this toll-free number:

1-800-4-NORTEL (1-800-466-7834)(International 770-708-4985)

For 24-hour non-emergency technical support for problems that do not affect service, call this toll-free number:

1-800-ASK-TRAN (1-800-275-8726)(International 770-708-4981)

Enterprise customers

Call this toll-free number:

1-800-2LANWAN (1-800-251-6926)

Fax on demand

To obtain technical documentation for any optical networks products by Fax, call this toll-free number:

1-800-451-1685

International (United Kingdom and Europe)

If your installation is located in the United Kingdom or mainland Europe, or is normally supported from the United Kingdom, use one of the following numbers:

United KingdomFreephone: 0800 626 881

Telephone: 020 8361 4693

Fax: 020 8945 3456

EuropeTelephone: +44 20 8361 4693

Fax: +44 20 8945 3456

Other regionsContact your regional Nortel Networks customer service representative.

x About this document



54-1

Seating circuit packs 54-Use the procedure in this chapter to seat the circuit packs.

RequirementsTable 54-1 lists the tools and materials required to complete the procedure in this chapter.

Before you beginBefore you begin the procedure in this chapter:

• make sure that the circuit packs are inserted but not seated in the correct slots as described in “Inserting circuit packs” in the “Installing components in shelves and drawers” chapter of Installing Shelves and Components, 323-1701-201

• make sure that filler cards are completely installed in the shelf as described in “Inserting filler cards” on page 44-38 in the “Installing components in shelves and drawers” chapter of Installing Shelves and Components, 323-1701-201

• make sure that every site in your network has the correct equipment for your network plan as described in “Precautions” on page 10-1 of the “Site requirements” chapter in Network Planning and Link Engineering Guidelines, NT0H7104.

Table 54-1Tools and materials required for circuit pack seating procedures

Item Quantity Supplied

Antistatic wrist strap 1 no

Fiber-optic cleaning kit 1 no

54-2 Seating circuit packs

OPTera Metro 5200Multiservice Platform 323-1701-310 Rel 4.0 Issue 1 Standard Nov 2001

Figure 54-1 shows the slot numbers for circuit packs in a DWDM shelf.

Figure 54-1Slot numbers for circuit packs in a DWDM shelf

OM0794p

Figure 54-2 on page 54-3 shows the slot numbers for circuit packs in an OFA shelf.

OC

I/OC

LD/O

TR

OC

I/OC

LD

SP

OS

C

OC

I/OC

LD

OC

M

OC

M

OC

I/OC

LD/O

TR

OC

I/OC

LD/O

TR

OC

I/OC

LD/O

TR

OC

I/OC

LD/O

TR

OC

I/OC

LD/O

TR

OC

I/OC

LD/O

TR

OC

I/OC

LD/O

TR

OC

I/OC

LD/O

TR

OC

I/OC

LD/O

TR

OC

I/OC

LD/O

TR

OC

I/OC

LD/O

TR

OC

I/OC

LD/O

TR

OC

I/OC

LD/O

TR

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

west plane east plane

Seating circuit packs 54-3


Figure 54-2Slot numbers for circuit packs in an OFA shelf

OM0760p

Note: For both DWDM and OFA shelves, you must install optical channel manager (OCM) circuit packs in slots 9 and 10 and install a shelf processor (SP) circuit pack in slot 19. If required, you must install the optical supervisory channel (OSC) circuit pack in slot 20.

Sequence for provisioning a new wavelengthFollow this sequence to provision a new wavelength on the ring and minimize the number and severity of alarms generated. This sequence presumes that the shelves are commissioned and System Manager is installed. Proceed on a shelf-by-shelf basis, starting with the orginating or terminating shelf, and work your way in order around the ring to the opposite end of the path.

OFA

(C

-ban

d)

OC

M

OC

M

OFA

(C

-ban

d)

SP

OS

C

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

ECT (east)

ECT (west)

west plane east plane

OFA

(L-

band

)

OFA

(L-

band

)



OCLD/OCI connections• autoprovision the corresponding OCLDs (the inventory and facilities are

automatically brought in-service); see Procedure 54-1 on page 54-6 in this chapter.

• autoprovision the corresponding OCIs (the inventory is brought in-service and the facilities are out-of-service); see Procedure 54-1 on page 54-6 in this chapter.

• create the new channel assignment; see Procedure 56-2 on page 56-9 in the “Provisioning circuit packs and managing traffic” chapter of this book.

• connect the OCI to the traffic source; see Procedure 47-12 on page 47-44 in the “Connecting shelf components” chapter of Powering and Commissioning Procedures, 323-1701-220; make sure that you comply with the cabling requirements outlined in the “Connecting shelf components” chapter of Powering and Commissioning Procedures, 323-1701-220.

• place the OCI facilities in-service (Rx AIS alarms should clear); see Procedure 56-4 on page 56-19 in the “Provisioning circuit packs and managing traffic” chapter of this book.

• move to the next shelf in the ring, seat the OCLD, then the OCI circuit packs, create the channel assignment and place the OCI facilities in-service.

10 Gbit/s OTR connections• autoprovision the 10 Gbit/s OTR (the inventory is brought in-service, the

Line facility is in-service and the Client facility is out-of-service); see Procedure 54-1 on page 54-6 in this chapter.

• create the new channel assignment; see Procedure 56-2 on page 56-9 in the “Provisioning circuit packs and managing traffic” chapter of this book.

• connect the 10 Gbit/s OTR to the traffic source; for an unprotected connection, see Procedure 47-22 on page 47-83 in the “Connecting shelf components” chapter of Powering and Commissioning Procedures, 323-1701-220; for a protected connection, see Procedure 47-23 on page 47-86 in the “Connecting shelf components” chapter of Powering and Commissioning Procedures, 323-1701-220; for a pass-through connection see Procedure 46-10 on page 46-40 in the “Connecting shelf components” chapter of Powering and Commissioning Procedures, 323-1701-220.

• place the 10 Gbit/s OTR Client facility in-service; see Procedure 56-4 on page 56-19 in the “Provisioning circuit packs and managing traffic” chapter of this book.



• move to the next shelf in the ring, seat the 10 Gbit/s OTR circuit pack, create the channel assignment and place the Client facility in-service; for a pass-through connection, make sure that you comply with Procedure 47-10 on page 47-40 in the“Connecting shelf components” chapter of Powering and Commissioning Procedures, 323-1701-220.

Procedure listTable 54-2 lists the procedures in this chapter.

Table 54-2System Manager operation procedures

Procedure Page Comments

54-1 Seating the SP and one OCM circuit pack 54-6 Required.

54-2 Seating the circuit packs 54-8 Required.



Procedure 54-1Seating the SP and one OCM circuit pack

Follow this procedure to seat the SP and one OCM circuit pack, commission the shelf, and install release 4.0 software before seating the rest of the circuit packs in the shelf.

RequirementsDo not apply power to the shelf until the SP is seated in slot 19, and the OCM is seated in slot 9.

Expected resultsWhen you complete this procedure:

• the software load on the SP and the OCM match

• the shelf is commissioned

• the release 4.0 software is installed

Perform the next procedure in this chapter, titled Seating the circuit packs, to seat the rest of the circuit packs in the shelf.

Action

Step Action

1 Seat the SP circuit pack in slot 19, and seat an OCM circuit pack in slot 9.

2 Apply power to the shelf.

3 Wait for the green LED light to appear on the SP circuit pack.

a. When the LED is green, proceed to step 4.

b. If the green LED does not appear, repeat step 1 and step 3. If the green LED does not appear on the SP, then neither the SP or the OCM is of a release 4.0 software load. Use another SP and repeat step 1 and step 3. Contact Nortel Networks technical support if it still does not work.

4 Reseat the SP circuit pack.

5 Wait for the green LED light to appear on the SP circuit pack.

a. When the LED is green, proceed to step 6.

b. If the green LED does not appear, repeat step 4 and step 5. If the green LED does not appear on the SP, then neither the SP or the OCM is of a release 4.0 software load. Use another SP and repeat step 4 and step 5. Contact Nortel Networks technical support if it still does not work.

6 Use a straight-through Ethernet cable and connect your computer to the Ethernet 2 port on the shelf.

—continued—



Procedure 54-1 (continued)Seating the SP and one OCM circuit pack

7 Commission the shelf, following Procedure 51-1 through Procedure 51-6 in the “Commissioning shelves” chapter of Powering and Commissioning Procedures, 323-1701-220. The Commissioning Wizard restarts the shelf upon completion of Procedure 51-6, Reviewing the shelf data file.

8 Log in to System Manager as an Admin level user. View the alarms on the shelf. If you have a Shelf-Software Library Missing alarm, proceed to step 9. Otherwise, proceed to step 10.

9 Select the Admin tab. At the Software Upgrade tab, right-click on the shelf and select Transfer. In the dialog box that appears, select the file that you want to transfer to the shelf and click Open. Once the transfer is complete, right-click and select Cancel. In the dialog that appears, select Yes to confirm the cancel.

You have completed this procedure.

10 Complete the following procedures in the “Commissioning shelves” chapter of Powering and Commissioning Procedures, 323-1701-220. Specifically:

• Procedure 51-7, Downloading software to the commissioned shelves

• Procedure 51-8, Committing to an OPTera Metro 5200 software load

You have completed this procedure.

—end—



Procedure 54-2Seating the circuit packs

Follow this procedure to seat and autoprovision circuit packs in the commissioned shelf.

Precautions

RequirementsYou must have completed all the steps in Procedure 54-1, Seating the SP and one OCM circuit pack, before you begin to seat the remaining circuit packs in the shelf. Seat the OCM in slot 10 first.

—continued—

CAUTIONRisk of causing unnecessary alarmsDo not seat OCI circuit packs in an uncommissioned shelf. Commission the shelf before you seat OCI circuit packs.

CAUTIONRisk of provisioning failureAutoprovision the circuit packs one at a time. Insert a circuit pack and wait until it comes online, then insert the next circuit pack. If you seat several cards at once, autoprovisioning may not occur. Autoprovisioning takes between 15 to 75 seconds to complete.

CAUTIONRisk of seating OTR circuit pack incorrectlyThe 10 Gbit/s OTR is a double-slot circuit pack that consists of a mother board and a daughter board. The mother board on the left side of the circuit pack connects to the shelf, but the daughter board has no contact with the card guides or the backplane. The mother board can be placed in any slot except slots 8 and 18, 9 and 10 (OCM), 19 (SP), and 20 (OSC).



Procedure 54-2 (continued)Seating the SP and one OCM circuit pack

Expected resultsAfter successful autoprovisioning, seated circuit packs are listed in an in-service state in the Inventory window of System Manager. Circuit pack facilities are listed in the Facilities window in the following states:

• OCLD facilities are IS

• OCI/SRM facilities are OOS

• OTR Line facility is IS, and the Client facility is OOS

• OFA east and west facilities are IS

• OSC east and west facilities are IS, WSC east and west facilities are OOS

If the circuit packs do not display correctly in the System Manager, delete incorrect entries from the Facilities and Inventory windows (in that order). Place any incorrect in-service facilities and inventory out-of-service before you delete the entry. Remove and insert the circuit packs again, or manually provision the circuit packs, as outlined in Procedure 56-1 on page 56-6 of Provisioning and Operating Procedures, 323-1701-310.

When you complete this procedure

• follow Procedure 53-1 on page 53-7 to test the shelf lamp, and follow Procedure 53-2 on page 53-9 to test optical continuity. These procedures can be found in the “Test procedures” chapter in Test Procedures, 323-1701-222.

• continue with the procedures in the “Connecting shelf components” chapter in Powering and Commissioning Procedures, 323-1701-220.

Action

Step Action

1 Remove the shelf cover.

Note: Do not let go of the shelf cover when you open it. The door is not attached to the pivot pins on the shelf.

2 Lift the lock latches away from the circuit pack faceplate and slide the OCM circuit pack in slot 10 toward the back of the shelf until the circuit pack connector seats in the backplane connector.

Wait for the circuit pack to autoprovision. Autoprovisioning takes between 15 to 75 seconds to complete. Do not proceed to the next step until the circuit pack is online.

—continued—



Procedure 54-2 (continued)Seating circuit packs

Step Action

3 Push the ends of the lock latches against the faceplate of the circuit pack to lock the circuit pack in position, as shown in Figure 54-3 on page 54-10.

The top and bottom latches lock to the circuit pack cage.

4 Repeat step 2 and step 3 to seat all circuit packs in the shelf.

5 Make sure there are no empty slots in the circuit pack cage when you have finished locking all the circuit packs.

Figure 54-3Seating the circuit packs in the shelf

OM0144t

—end—


55-1

Using the System Manager 55-Use the procedures in this chapter to use the System Manager.

The System Manager is accessible from any shelf in the network through the 10Base-T 1X port on the maintenance panel.

Note: Refer to the “Appendix—System Manager windows and fields” chapter in this book for detailed information about System Manager windows.

Before you beginBefore you begin the procedures in this chapter, make sure you have

• read about the System Manager and its functions in the “OPTera Metro 5200 software” chapter of Network Planning and Link Engineering Guidelines, NT0H7104

• completed the installation of the System Manager and the Web browser using the procedures in the “Installing the System Manager” chapter in Powering and Commissioning Procedures, 323-1701-220

• correctly configured a remote connection between the System Manager computer and the OPTera Metro 5200 network, if required, according to the procedures in the “Configuring a remote connection to the System Manager” chapter in Powering and Commissioning Procedures, 323-1701-220

Note: For information on performance monitoring (PM) queries using System Manager, refer to the “Performance monitoring description” chapter in Performance Monitoring, 323-1701-520.

55-2 Using the System Manager


User levels and access privilegesThere are three different levels of user access and privilege. Table 55-1 lists descriptions of the different user privileges.

Note: Make sure to protect your passwords to the System Manager. If you do not remember your password, you must contact the Nortel Networks Technical support to access the shelves.

Access to the System Manager through IP addressesBy default, you access OPTera Metro 5200 shelves using uniform resource locator (URL) IP addresses. Your network administrator can configure your system to use shelf names or IP addresses, such as DNS entries that map user defined shelf names to their related IP address. If your network environment does not use DNS, your network administrator can create entries in the files listed below to map shelf names to IP addresses.

• (for Unix) /etc/hosts

• (for Windows NT) C:\WINNT\system32\drivers\etc\Hosts• (for Windows 95, Windows 98 and Windows 2000) C:\Windows\Hosts

Table 55-1System Manager user levels and privileges

User level Description

Admin The system administrator:

• has read and write access to all of the system

• can change passwords

• can commission and decommission shelves

Operator The typical user class:

• has read and write access to most of the system

• cannot change passwords

• cannot commission or decommission shelves

Observer This user has read-only access.

Using the System Manager 55-3



Table 55-2System Manager operation procedures


55-1 Logging in to the network 55-5 Required to perform most commissioning, provisioning, operating and test procedures.

55-2 Changing the OPTera Metro 5200 password

55-6 Optional. Make password changes on the primary shelf, and backup all affected shelves afterwards.

55-3 Editing the naming, timing and basic communications settings

55-8 Optional. Always perform a backup after editing shelf configurations.

55-4 Viewing detailed event history 55-14 Optional.

55-5 Viewing the event console 55-15 Optional.

55-6 Saving event logs 55-16 Perform this procedure before replacing an SP circuit pack.

55-7 Printing event lists 55-17 Optional.

55-8 Clearing the event console 55-18 Optional.

55-9 Configuring telemetry alarms 55-20 Optional.

55-10 Saving the alarm list 55-23 Optional.

55-11 Printing the alarm list 55-24 Optional.

55-12 Acknowledging visual alarms 55-25 Optional.

55-13 Selecting shelves 55-27 Optional.

55-14 Sorting shelves 55-29 Optional.

55-15 Sorting information 55-30 Optional.

55-16 Saving information 55-32 Optional.

55-17 Printing information 55-33 Optional.

55-18 Adding, deleting, and getting details of information

55-34 Optional.

55-19 Querying the inventory list 55-35 Optional.

55-20 Querying facilities 55-36 Optional.

55-21 Querying channel assignments 55-37 Optional.

—continued—



55-22 Changing the date and time on a shelf 55-38 Optional.

55-23 Provisioning Ethernet port alarms 55-40 Optional.

55-24 Provisioning Ethernet ports 1 and 2 55-41 Optional.

55-25 Defining or changing IP addressing and advanced communications settings for the network

55-42 Optional. Always perform a backup of the affected shelves after changing IP addresses and communication settings.

55-26 Assigning IP addresses for Ethernet port 2 and serial ports 1 and 2

55-46 Optional.

55-27 Configuring shelf surveillance and external management

55-48 Optional. Follow Procedure 57-8 in the “Shelf management procedures” chapter of Provisioning and Operating Procedures, 323-1701-310.

55-28 Backing up shelf configuration data 55-49 Strongly recommended after commissioning a new shelf, or changes to shelf configurations, shelf passwords or IP addresses.

55-29 Restoring shelf configuration data 55-52 Required in the event of shelf failure.

55-30 Changing clock reference settings for a SONET/SDH SRM OCI

55-55 Optional.

55-31 Performing a health check 55-57 Recommended for each shelf after a software upgrade to review the results.

55-32 Retrieving a health check report 55-59 Optional.

55-33 Viewing the Login User List 55-60 Optional.

55-34 Exiting the System Manager 55-61 Optional.

Table 55-2 (continued)System Manager operation procedures




Procedure 55-1Logging in to the network

Follow this procedure to log into the network with the System Manager.

Expected resultsWhen you complete this procedure, you are logged in to the network through the System Manager. If the login procedure fails three times, the System Manager automatically closes.

OM0864t

Note: The System Manager password is case sensitive.

Action

Step Action

1 Open the Web browser on the System Manager computer.

2 Enter the IP address of the OPTera Metro 5200 shelf in the address field of the Web browser.

3 Log in to the shelf using the user name and current password of the shelf.

4 Click OK.

—end—



Procedure 55-2Changing the OPTera Metro 5200 password

Follow this procedure to change the password for the OPTera Metro 5200 System Manager. System Manager sends all password changes to the primary shelf. The primary shelf updates and propogates passwords to the other shelves in the ring.

RequirementsYou must be an Admin level user to change passwords for the System Manager.

Precautions

Action

Step Action

1 Log in to the System Manager using the admin user name and current admin password. See Table 55-1.

2 From the Security menu, select Change Password.OM0578

—continued—

CAUTIONBackup all shelves affected by password changesOnce password changes are made at the primary shelf, backup all affected shelves. See Procedure 55-28 for details.



Procedure 55-2 (continued)Changing the OPTera Metro 5200 password

Step Action

OM0657t

The Change Password dialog box appears.

3 In the User field, select the user name for which you want to change the password.

4 Enter the current Admin password.

5 Enter the New password for the selected user level.

Note: The password is case sensitive and must be between eight and ten characters.

6 Re-enter the new password to confirm.

7 Click OK.

—end—



Procedure 55-3Editing the naming, timing and basic communications settings

Follow this procedure to edit the naming, timing, and basic communications settings. See Procedure 55-25 on page 55-42 for information on editing advanced communications settings and IP addressing.

RequirementsYou must be logged in as an Admin level user to edit configuration information.

The shelf automatically restarts after changes to specific naming data, and all basic communications data. Table 55-3 on page 55-11 and Table 55-4 on page 55-12 list the fields that initiate a shelf restart.

Precautions

—continued—

CAUTIONPossible loss of access to one or more shelvesIf you input incorrect information in the Configuration window, you can lose access to one or more shelves and impact intershelf communication.

CAUTIONBackup configuration changesBackup the shelf after configuration changes. Otherwise, the shelf could be restored from an out-of-date backup file in the event of shelf failure. See Procedure 55-28 for details.



Procedure 55-3 (continued)Editing the naming, timing and basic communications settings

Action

Step Action

1 Select the Configuration tab.

2 Select any one of the Naming, Communications, or Timing tabs and double-click.

OM0859t

The Shelf Configuration dialog displays.

—continued—




Step Action

3 Select the Naming tab to change name information. See Table 55-3.

4 Select the Communications tab to change basic communication information. See Table 55-4 on page 55-12. See Procedure 55-25 on page 55-42 if you need to edit advanced communications settings. See Procedure 55-23, Procedure 55-24, and Procedure 55-26 to edit port control settings, or IP addressing for Ethernet ports.

Note: Do not use brackets in a shelf name.OM0860t

5 Select the Time tab to change time information. See Table 55-5 on page 55-13.

6 Click the OK button to exit the dialog.

Note: If you edit any fields that initiate a shelf restart, System Manager displays a restart message.

—continued—




Step Action

7 Click Yes to launch the shelf restart and enable the new configuration data.OM0880t

.

—continued—

Table 55-3Editing name information

Field name Reboot required?

Result Result of incorrect value

Network Name N The field is changed. None

Site Name N The field is changed. None

Shelf Name N The field is changed. (See Note below.)

None

Shelf Description

N The field is changed. None

Site Identifier Y This field groups shelves together with the System Manager display.

Incorrect grouping in the System Manager shelf selector panel.

Shelf Identifier Y Shelf ID will be incorrect in the shelf list. Manually delete the shelf ID.

May need to do an Admin/Rediscover Network after the manual edit.

A duplicate value within the ring makes a shelf inaccessible.

Note: Do not use brackets in a shelf name.




—continued—

Table 55-4Editing communication information



Primary Shelf Address

Y This field changes the primary shelf IP address.

The shelf with the incorrect value will not appear in the System Manager.

Shelf Address Y This field changes the IP network address of the shelf.

An invalid value can make the shelf unreachable on the network.

Subnet Mask Y This field changes the range of IP addresses associated with the 10Base-T 1X interface.

May cause IP routing within the ring to become non-functional.

DHCP Address Y This field changes the IP address that will be assigned to the System Manager connected by way of 10Base-T 1X.

May cause a locally attached System Manager to be inoperative.

Default Gateway Address

Y This field changes the IP address of the router to which IP packets are forwarded for routing to the DCN.

May cause IP routing within the ring or to the DCN to become non-functional.

Shelf Type Y This field changes the type of shelf. Would cause provisioning mismatch alarms and loss of traffic.

Ethernet Hubbing Group

Y This field algorithmically changes the IP address used for ENET2 communications.

All shelves hubbed together by way of ENET2 must have the same Ethernet hubbing group value or they cannot communicate.




—end—

Table 55-5Editing time information



Time Fields N Editing on the primary shelf causes all shelves to be synchronized to the new time.

Editing on a non-primary will be overwritten after the time server on the Primary establishes communication with the shelf.

Events/alarms will have incorrect time stamps.



Procedure 55-4Viewing detailed event history

Follow this procedure to view up to 400 events in the event history from the shelf buffer.

For more information about event buffers, refer to “Event history review” on page 14-4 in the “OPTera Metro 5200 software” chapter of Software Description, 323-1701-101.

om0863p

Action

Step Action

1 Select the Fault tab.

2 Select the Event History tab.

3 Select the Refresh button.

The Event History window updates with information from the shelf-level buffer.

Note: To sort information in the Event History, see Procedure 55-15.

—end—



Procedure 55-5Viewing the event console

Follow this procedure to view events for all shelves in the network.

OM0862p

Action

Step Action


2 Select the Event Console tab.

The Event Console window displays information from the entire network.

Note: The System Manager may display an “Overhead Invalid Code” error in the Event Console. This error is monitored for diagnostic purposes and does not affect the performance of your system.

—end—



Procedure 55-6Saving event logs

Follow this procedure to save an event log.

The System Manager event buffer records up to 400 events from the shelves in the OPTera Metro 5200 network. When the System Manager event buffer has over 400 events, the System Manager overwrites the oldest events with the newer events. If you want to keep an event log you can save it to a file before the System Manager overwrites it. You can save events in the Event Console window and the Event History window.

Save your event log with a .csv (comma separated value) extension so you can open it easily in spreadsheet programs.

Action

Step Action


2 Select the Event Console or the Event History.

3 From the File menu, select Save As.

The Save As dialog box appears.

4 Name the event log file using the .csv extension and select a location for it.

—end—



Procedure 55-7Printing event lists

Follow this procedure to print events lists.

You can print both the Event Console and the Event History.

Action

Step Action


2 Select the Event Console or Event History.

3 From the File menu, select Print.

The Print dialog box appears.

4 Click OK in the Print File dialog box to confirm printing.

The file prints to your default printer.

—end—



Procedure 55-8Clearing the event console

Follow this procedure to clear the Event Console.

You can clear the events in the Event Console of a shelf. When you complete this procedure, the System Manager clears all the entries in the Event Console. Entries include events on shelves that you have not selected.

You cannot clear the shelf event buffer. For every shelf, the System Manager uses the information in this buffer to provide an event history. You can use the information for troubleshooting.

Note: Clearing the Event Console erases information for all shelves in the network including shelves that are not selected with the network shelf selector.

Action

Step Action


2 Select the Event Console tab.

3 From the Events menu, select the Clear event console option.OM0661t

The Confirm Clear Log dialog box appears.

4 Click Yes to clear the log.

The Confirm Save Log dialog box appears.

—continued—



Procedure 55-8 (continued)Clearing the event console

Step Action

5

6 Type the name of the event log file using a .csv extension and select a location.

—end—

If you Then

want to save a copy of the current log

click Yes in the Confirm Save Log dialog box, and proceed to step 6.

do not want to save a copy of the current log

click No in the Confirm Save Log dialog box



Procedure 55-9Configuring telemetry alarms

Follow this procedure to provision telemetry alarms.

The COTEL (central office telemetry) card in the maintenance panel allows you to connect external devices to control and respond to environmental conditions at the equipment site. For example, you can connect a water sensor to the input and a water pump to an output. When the sensor detects water at the equipment site, the System Manager displays an alarm. You can then manually activate the pump, and the alarm clears when the water level returns to normal. The System Manager allows you to indicate the severity of the alarm for every input and alarm text.

After you configure the severity and the text for the telemetry alarms, you can place the alarms in-service or out-of-service. When you place the alarm out-of-service, the alarm remains configured but is disabled. You cannot configure telemetry alarms if they are in-service.

There are four inputs and four outputs for telemetry equipment. The configuration for each input and output is the same, with one exception: Output Device 1 allows you to set the hardware to be normally open or normally closed. This option enables you to monitor your system for a power failure. If you set the hardware to normally closed, the relay is energized and a loss of power will trigger an alarm in the central office. The relay controls the alarm equipment in the central office.

The System Manager lists slot 27 as the location of telemetry alarms.

RequirementsYou must connect shelf alarms and telemetry equipment to the central office alarm system before you can configure COTEL alarms. For more information, refer to Procedure 45-3 “Connecting shelf alarms and telemetry equipment to the central office alarm system” in Installing Shelves and Components, 323-1701-201.

—continued—



Procedure 55-9 (continued)Configuring telemetry alarms

Action

Step Action

1 Select the Equipment tab.

2 Select the Telemetry tab.

The System Manager lists the shelves that have telemetry connections and their state.

Configuring the input port

3 Select the shelf for the input that you want to configure.

The information in the Parallel Telemetry window is specific to each shelf.

4 Double-click on a shelf to view input configuration information.

The Parallel Telemetry Input window appears. OM0237

5 Enter a description of the input port.

6 From the Alarm Severity menu, select an option to indicate the severity of the alarm.

—continued—



Procedure 55-9 (continued)Configuring telemetry alarms

Step Action

7 In the Alarm Text field, enter the text that you want the System Manager to display when it raises an alarm for this input port.

8 Place the input port in-service by clicking on the radio button.

9 Click OK.

Configuring the output port

10 Select the shelf for the output that you want to configure.

11 Enter a description of the output port.

Note: For Output Device 1, you can configure the hardware to be normally open or normally closed. This option is available for Output Device 1 only.

12 Place the output port in-service by clicking on the radio button.

13 Click Apply.

14 Click the radio button to place the device in a Released or Operated state.

Note: You must activate or deactivate an output device in response to an alarm by selecting Released or Operated. If the output port is powered on, choosing Operated activates the output port. Choosing Released deactivates the output port.

15 Click OK.

—end—



Procedure 55-10Saving the alarm list

Follow this procedure to save the alarm list.

You can save the information in the Active Alarms and the Event Log windows. Assign a .csv (comma separated value) extension so you can open it easily in spreadsheet programs.

Action

Step Action


2 Select the Active Alarms tab.

3 From the File menu, select Save as.


4 Name your file using a .csv extension and select a location for it.OM0578

—end—



Procedure 55-11Printing the alarm list

Follow this procedure to print the information in alarm and event lists.

Action

Step Action


2 Select the Active Alarms tab.


The Print File dialog box appears.

4 Click OK in the Print File dialog box to confirm printing.

The file prints to your default printer.

—end—



Procedure 55-12Acknowledging visual alarms

Follow this procedure to acknowledge visual alarms in the System Manager.

The alarm banner uses red, orange, and yellow to indicate alarms that are not acknowledged. When the alarm indicator is gray, there are no new alarms. Acknowledge alarms when you know the cause of the alarm. When you acknowledge an alarm, the alarm indicator turns gray again. Subsequent alarms change the color of the banner indicating new alarms.

Note: When you acknowledge an alarm, you are not clearing the alarm. You must remove the cause of an alarm to clear it from the System Manager.

Table 55-6 lists the color and the related status of alarm indicators. When the alarm banner is blue, the System Manager cannot poll the shelf for alarm status.

—continued—

Table 55-6Alarm indicator colors in the System Manager

Alarm or alert type

Color Meaning

Critical red There are unacknowledged critical alarms.

gray There are no unacknowledged critical alarms.

Major red There are unacknowledged major alarms.

gray There are no unacknowledged major alarms.

Minor yellow There are unacknowledged minor alarms.

gray There are no unacknowledged minor alarms.

Warning orange There are unacknowledged alerts.

gray There are no unacknowledged alerts.



Procedure 55-12 (continued)Acknowledging visual alarms

Action

Step Action

1 Make sure you know the active alarms.

2 Click on the highlighted alarm in the alarm banner to acknowledge the alarm count.

The alarm is acknowledged and the alarm indicator is no longer highlighted. The alarm is not removed.

—end—



Procedure 55-13Selecting shelves

Follow this procedure to select shelves.

When you select shelves, only information for the selected shelves appears in the information windows. The information displayed in the windows depends on the shelves you select with the network shelf selector. The bottom row of the alarm banner displays the alarm counts for the selected shelves. The top row of the alarm banner displays alarm counts for all the shelves in the network. For more information about the alarm banner, refer to the “System Manager main window” section of Software Description, 323-1701-101.

You can perform tasks on the entire information table, such as sorting, saving, or printing, or on a single row or cell within the table, such as adding, deleting, or retrieving details. You cannot sort the Event Console.

Table 55-7 lists the commands to select shelves. The list of selected shelves updates when you confirm your selection by clicking OK.

—continued—

Table 55-7Key controls for selecting shelves

Action Function

Left-click Resets the list of selected shelves to the shelf or group under the cursor. Used to select a single shelf or group of shelves.

Ctrl+Left-click Toggles the selection of the shelf or group of shelves under the cursor location on or off. Used to select multiple shelves in random order before committing the selection.

Shift+Left-click When you shift+left-click an item in a list, and then shift+left-click a second item, you select all items between the first and second items. Used to select multiple shelves in continuous order before committing the selection.

Double-click When you double-click on a shelf, the shelves are selected and applied.



Procedure 55-13 (continued)Selecting shelves

Action

Step Action

1 Click the Selected Shelves drop-list to display the network tree.

2 Select the network, sites, or shelves using the commands in Table 55-7.

3 Click OK to display the information about the shelves you selected.

4 Click Refresh List to refresh the connection with the OPTera Metro 5200 network.

OM0234p

—end—



Procedure 55-14Sorting shelves

Follow this procedure to sort your shelf list.

Action

Step Action

1 In the System Manager, select the Configuration tab.

The Configuration window appears.

2 Select the Shelf List tab.

3 Manually sort the shelf list into a clockwise ring order with the primary shelf as the top shelf in the list. Sort the remaining shelves descending in clockwise order as they exist in the ring, as shown in the following figure.

The shelves in the window appear as follows.OM0865p

—end—



Procedure 55-15Sorting information

Follow this procedure to sort information in the System Manager.

You can sort the data in the information windows in ascending or descending order. The type of information that you can sort depends on the information table you are using.

Note: For easy sorting, click the column headers on the main windows. When you click on a column header, you can toggle the contents of the column between ascending and descending order.

You can sort all the information windows except the Event Console window. The Event Console window displays information in chronological order.

Action

Step Action

1 Select the tab for the System Manager window that you want to sort.

2 From the View menu, select Sort Order.

The Table Sort Order dialog box appears.OM0375

—continued—



Procedure 55-15 (continued)Sorting information

Step Action

3 In the Columns area, select the headers that you want to use to sort the contents of the window.

4 In the Sort Order area, select Ascending, Descending, or None.

The information in the window appears in the sort that you selected.

5 Click OK.

Note: Click Reset to reset all columns and sort selections to None.

—end—



Procedure 55-16Saving information

Follow this procedure to save information in any table in the System Manager.

Nortel Networks recommends that you save the information to a file with a .csv (comma separated variable) extension. You can open comma separated variable files using spreadsheet applications.

Action

Step Action

1 Navigate to the window that contains the information that you want to save.

2 From the File menu, select Save As.


3 Select a name and location for the file.

4 Click Save.

—end—



Procedure 55-17Printing information

Follow this procedure to print information in any table in the System Manager.

Action

Step Action

1 Navigate to the window that you want to print information from.


The Print dialog box appears.

3 Click OK.

—end—



Procedure 55-18Adding, deleting, and getting details of information

Follow this procedure to

• add information in an editable field

• select shelves so that only information for the selected shelves appears in the information windows

Action

Step Action

1 Select the line that you want to delete, add information to, modify or view for PM information.

2 Right-click on the selected item.

A menu list appears.

3 Select one of these items from the menu list:

• Modify

• Add

• Delete

• Pm Info

Options that are not available for the line that you select are grayed out in the Edit menu.

4 Read the information window that appears and make any necessary changes.

5 Click OK.

—end—



Procedure 55-19Querying the inventory list

Follow this procedure to query the inventory list on the Equipment window.

The Inventory window displays information about the physical equipment installed in the shelf, as shown in Figure 55-1.

Query the inventory list when you want information about the state of circuit packs installed in the OPTera Metro 5200 shelf.

Figure 55-1System Manager window for querying inventory information

OM0229

Action

Step Action

1 Select the Equipment tab and then select the Inventory tab.

2 From the Refresh menu, select Current Window, or click the Refresh button.

The Inventory window appears with updated information from the shelf-level buffers of the shelves you select.

—end—



Procedure 55-20Querying facilities

Follow this procedure to query the facilities list on the Equipment window.

The Facilities window displays information about the operational status of the circuit packs in the shelf, as shown in Figure 55-2.

Query the facilities list when you want information about the operational status of the OCI, OCLD, OTR, and OFA circuit packs installed in the OPTera Metro 5200 shelf.

Figure 55-2System Manager window for querying facilities

OM0228

Action

Step Action

1 Select the Equipment tab and then select the Facilities tab.

2 From the Refresh menu, select Current Window, or click the Refresh button.

The Facilities window appears with updated information from the shelf-level buffers of the shelves you selected.

—end—



Procedure 55-21Querying channel assignments

Follow this procedure to query channel assignments.

The Channel Assignments window of the System Manager shows OPTera Metro 5200 channel assignment provisioning and status information, as shown in Figure 55-3.

Figure 55-3Channel assignments window

OM0878p

Action

Step Action

1 Select the Connections tab.

The Channel Assignments window appears.

2 Double-click the line that contains the channel assignment that you want to query.

The Channel Assignments details dialog box appears.

Note: Double-clicking on an “SRM aggregate” line displays information about the four SRM OCI port assignments.

3 Click OK to close the window.

—end—



Procedure 55-22Changing the date and time on a shelf

Follow this procedure to change the date and time for commissioned shelves.

The System Manager platform generates the time stamps for the event console in relation to the “Gained contact with shelf” and the “Lost contact with shelf” events. If you set a time on the System Manager platform that is different from the shelf, the time stamps of these events can appear incorrect relative to other events (for which the time stamp is generated by the shelf). Nortel Networks recommends that you set the System Manager platform and the shelf with the same time.

PrecautionsYou must change the date and time on the primary shelf in the network in order for the change to remain in effect. If you change the date and time on a secondary shelf, the change only lasts until the next time the shelf synchronizes its date and time with the primary shelf.

Action

Step Action


2 Select the Time tab.

3 Double-click on the shelf for which you want to change the date and time.

The Shelf Configuration window appears, as shown in Figure 55-4 on page 55-39.

4 Select the Time tab, if necessary.

5 Change the date and time.

6 Click OK to close the window.

—continued—



Procedure 55-22 (continued)Changing the date and time on a shelf

Figure 55-4Shelf Configuration window, Time tab

OM0376

—end—



Procedure 55-23Provisioning Ethernet port alarms

Follow this procedure to enable or disable the Ethernet Port 1 alarm and the Ethernet Port 2 alarm.

Both Ethernet port alarms are disabled upon commissioning.

Figure 55-5Port enabling/disabling window

OM0292t

Action

Step Action


2 Double-click on the appropriate shelf.

The Shelf Configuration window appears.

3 Select the Communication tab, if required.

4 Select the Port Control button.

The Port enabling/disabling window appears.

5 Select the appropriate setting for each port alarm.

6 Click OK.

—end—



Procedure 55-24Provisioning Ethernet ports 1 and 2

Follow this procedure to enable or disable Ethernet ports 1 and 2 after system commissioning.

Ethernet Port 1 is used to configure access to the shelf by way of a connection to the customer’s LAN, PC, or laptop. Ethernet Port 2 is used to bridge shelves through the Ethernet hub, or through a direct connection with a cross-connect cable.

The default values for Ethernet Ports 1 and Port 2 are enabled upon commissioning. Both default values can be altered during commissioning using the Commissioning Wizard.

If a shelf is decommissioned Port 1 defaults to enabled, while Port 2 defaults to disabled.

Action

Step Action


2 Double-click on the appropriate shelf.


3 Select the Communications tab, if required.

4 Select the Port Control button.

The Port enabling/disabling window appears.

5 Select the appropriate setting for each port.

Note 1: If the shelf configuration includes an Ethernet hub, and if 10Base-T 2X port on the host shelf is disabled, you can only monitor other shelves with the same bands as the host shelf. In order to see all shelves with all bands, you must enable 10Base-T 2X port on the host shelf.

Note 2: If all the ports on a shelf are disabled you cannot use the System Manager to access the shelf locally. You must access the shelf from another shelf in the network with the same bands to enable the ports.

Note 3: If all the ports on all the shelves in a network are disabled you must contact Nortel Networks Technical support to re-establish a network surveillance connection.

6 Click OK.

—end—



Procedure 55-25Defining or changing IP addressing and advanced communications settings for the network

Follow this procedure to change IP addressing or communications for the network. You can set your routing protocol to be None, OSPF or BGP. You can also apply the Inbound NAT and Assignable IP features.

For more information about BGP and Inbound NAT, refer to the “IP addressing in the OPTera Metro 5200 network” chapter of Network Planning and Link Engineering Guidelines, NT0H7104.

For more information about OSPF, BGP, and Inbound NAT settings fields, refer to Table 59-23 “ Configuration—Naming, Communications, or Time—Shelf Configuration window”, in “Appendix—System Manager windows and fields” chapter in this book

Precautions

Action

Step Action


2 Select the Communications tab.

3 Double-click on the shelf.


—continued—

CAUTIONBackup IP address or communication changesAlways backup affected network elements after performing IP address or communication changes. If you do not backup after making changes and the shelf fails, you must restore the shelves from out-of-date backup files. For more information about backing up shelf configuration data, refer to Procedure 55-28.

ATTENTIONIf you change the IP address of the primary shelf, all the other shelves in the network that communicate with the primary shelf must be modified. This results in every shelf going through a restart.



Procedure 55-25 (continued)Defining or changing IP addressing and advanced communications settings for the network

Step Action

4 Select the Communication tab in the Shelf Configuration window.

The Shelf Configuration—Communication tab appears.

5 To configure advanced communications settings for the network, click the Advanced... button.

The Advanced Communications settings window appears. See Figure 55-6.

Figure 55-6Advanced Communications Settings window

OM0737t

6 Select NONE, OSPF, or BGP from the Routing Protocol drop-down list.

7 If you want to change the default values of the selected protocol, click the Set button.

The OSPF Settings or BGP Settings window appears. See Figure 55-7 and Figure 55-8 on page 55-45.

8 Change the default values and click the OK button.

9 In the Advanced Communications settings window, select or deselect the Inbound NAT Enabled option to enable or disable the Inbound NAT feature.

The Inbound NAT Enabled option is selected by default.

10 If necessary, type a new value in the Inbound NAT Alias field to replace the default alias.

—continued—




Step Action

11 If you want to assign IP addresses to the Ethernet and Serial ports, click the Set Port IPs button.

The Set Port IPs window appears. See Figure 55-9 on page 55-45.

12 Change the default values and click the OK button.

Note: For more information about assigning IP addresses, refer to Procedure 55-26 on page 55-46.

13 Click the OK button on the Advanced Communications settings window.

14 Click the OK button on the Shelf Configuration window.

Figure 55-7OSPF settings window

OM0738t

—continued—




Figure 55-8BGP settings window

OM0739t

Figure 55-9Assignable IP Settings window

OM0740t

—end—



Procedure 55-26Assigning IP addresses for Ethernet port 2 and serial ports 1 and 2

If you are using a multiple IP address shelf configuration, you can manually assign the IP addresses for Ethernet port 2 and serial ports 1 and 2. If you do not assign an IP address, the system assigns the default address shown in Table 55-8.

Note 1: The 10.0.x.x (where x=0 to 255) IP addresses are for internal use in an OPTera Metro 5200 network. You cannot assign these reserved IP addresses in the network.

Note 2: You must assign unique IP addresses to avoid conflicts in the network.

Action

Step Action


2 Select the Communications tab.

3 Double-click on the shelf.

The Shelf Configuration—Communication tab appears.

4 Click the Advanced... button.

The Advanced Communications settings window appears.

5 Click the Set Port IPs... button.

The Assignable IP Settings window appears. See Figure 55-10.

6 Assign the IP addresses and click the OK button.

7 Click the OK button on the Advanced Communications settings window.

8 Click the OK button on the Shelf Configuration window.

—continued—



Procedure 55-26 (continued)Assigning IP addresses for Ethernet port 2 and serial ports 1 and 2

Step Action

Figure 55-10Assignable IP Settings window

OM0740t

—end—

Table 55-8Assignable IP Settings window

Field name Definition Value/range

Enet Port 2 IP IP address for 10BaseT 2X IP address. The default value is 10.2.hubbinggroup.shelfID.

Enet Port 2 Mask Broadcast address IP address. The default value is 10.2.hubbinggroup.255.

Enet Port 2 DHCP DHCP address for 10BaseT 2X IP address. The default value is 10.2.hubbinggroup.(shelfID + 128).

Serial Port1 Local IP DTE local IP address. The default value is 10.3.shelfID.1.

Serial Port1 Remote IP DTE remote IP address. The default value is 10.3.shelfID.2.

Serial Port2 Local IP DCE local IP address. The default value is 10.4.shelfID.1.

Serial Port2 Remote IP DCE remote IP address. The default value is 10.4.shelfID.2.



Procedure 55-27Configuring shelf surveillance and external management

To configure shelf surveillance and external management, follow Procedure 57-8 in the “Shelf management procedures” chapter of Provisioning and Operating Procedures, 323-1701-310.



Procedure 55-28Backing up shelf configuration data

Follow this procedure to back up the configuration data for a shelf. You must be logged in to System Manager as an Admin level user.

To perform a backup, the software load on the shelf must be in a committed state. The shelf must be commissioned and operational, with a 4.0 software load.

The network supports one instance of a backup operation for a particular shelf at any given time. You can perform multiple backups of different shelves in the network at the same time.

PrecautionsThis procedure will fail if provisioning changes or software upgrades are made to the shelf while the backup is in progress.

Note: During a backup operation, make sure you put both of the OCM circuit packs IS or remove one of them from the shelf. If you do not do this data can be lost after the backup operation.

Action

Step Action


2 Select the Naming tab.

3 Double-click on the shelf that you want to backup.


—continued—

ATTENTIONNortel Networks strongly recommends that you perform a backup each time you commission a new shelf or make changes to shelf configurations, shelf passwords or IP addresses.

CAUTIONRisk of file corruptionDo not make provisioning changes or start a software upgrade during a backup procedure, or the backup file can become corrupted.



Procedure 55-28 (continued)Backing up shelf configuration data

Step Action

4 Click Backup.OM0569

The Save Backup File As: window appears. System manager proposes a default directory on your PC (C:/NortelNetworks/OPTeraMetro/Backup/) to store the backup file. System manager also proposes a file naming convention: <shelf IP>_<version/load number>_<Date>_<military time>.dat.

5 If required, change the proposed file name and default directory. Click Save.OM0570

The Confirm Backup dialog appears.

6 Click Yes to confirm.

—continued—



Procedure 55-28 (continued)Backing up shelf configuration data

Step Action

OM0571

The Backup Status window appears. (It takes 3 to 5 seconds to complete the backup.) While the backup is in progress a “Backup In progress” message is displayed. When the backup is complete, the Backup Status dialog appears.

7 Read the status messages and click Close.

Note 1: If the backup procedure fails, an error message is displayed in the Backup Status dialog.

Note 2: Normally, System Manager does not backup the default target identifier (TID), the current active path for path switching, or the current active OCM for equipment switching. If the TID is not the default, or if the active path or the active OCM are forced switches, System Manager will backup and restore this data.

—end—



Procedure 55-29Restoring shelf configuration data

Follow this procedure to restore a commissioned shelf to service after a major failure. You must be logged in to System Manager as an Admin level user.

PrecautionsThe configuration restore file must be of the same release as the commissioned shelf. The network supports one instance of a restore operation for a particular shelf at any given time. You can restore different shelves in the network at the same time.

Note: During the restore operation, make sure to put both of the OCM circuit cards IS or to remove one of them from the shelf. Otherwise, data can be lost.

Action

Step Action



3 Double-click on the shelf that you want to restore.

The Shelf Configuration window displays.

—continued—

ATTENTIONThe restore operation overwrites all previous configuration information stored on the SP and OCM circuit packs at the target shelf. Once you commit the restore procedure as outlined in step 10, cancellation is not possible.

CAUTIONRisk of traffic lossNortel Networks recommends that you only restore shelf configuration data to an out-of-service shelf.



Procedure 55-29 (continued)Restoring shelf configuration data

Step Action

4 Click the Transfer button.OM0567

The Choose Restore File dialog displays.

5 Browse through the file system and select the correct file to restore the shelf. Click Open.

The Confirm Transfer dialog displays.

6 Click Yes to confirm the file transfer to the target shelf.

When the transfer is complete, the restore file resides on the SP circuit pack of the target shelf.

—continued—



Procedure 55-29 (continued)Restoring shelf configuration data

Step Action

7 In the Restore panel, select which aspects of the data file you want to load to the shelf. If you do not select any items, System Manager defaults to the basic shelf configuration. The following list describes the data associated with each selection item.

• User Profile–includes, but is not limited to user names, passwords and privileges

• Commissioning Data–shelf information which includes, but is not limited to network name, shelf site name, shelf name, shelf description, node type, shelf number, site identifier, shelf identifier, primary node address, hubbing group, IP address, subnet mask, DHCP address, gateway IP address

• TL1 Commissioning Data–includes but is not limited to TID, gateway flag, TCP port, Telnet port, maximum number of TCP sessions, maximum number of Telnet sessions, maximum number of sessions connected to other nodes (gateway sessions)

8 Click the Load button.

The Confirm Load dialog displays.

9 Click Yes to confirm the shelf load.

A message indicates the status of the shelf load.

10 Click the Commit button to commit the load to the shelf.

A message indicates the status of the restore process, which takes approximately 40 seconds. Once complete, the Restore Status dialog displays. If the load is successful, a shelf level restart is triggered, which shuts down System Manager.

11 Click Close. Restart your browser to restart the System Manager.

Note 1: Back out of the restore process by clicking No at step 6 or step 9. It is not possible to cancel the shelf restore process once the load is committed. If you do not want to commit the load, click Cancel at step 10.

Note 2: Normally, System Manager does not backup the default target identifier (TID), the current active path for path switching, or the current active OCM for equipment switching. If the TID is not the default, or if the active path or the active OCM are forced switches, System Manager will backup and restore this data.

—end—



Procedure 55-30Changing clock reference settings for a SONET/SDH SRM OCI

Follow this procedure to change clock reference settings for a SONET/SDH SRM OCI circuit pack.

Action

Step Action


2 Select the Channel Assignments tab.

3 Right-click on the SRM circuit pack that represents the appropriate SONET/SDH SRM OCI.

—continued—

ATTENTIONIf you use a SONET/SDH SRM OCI circuit pack, you must make sure that the four OC-12/STM-4 source signals come from a single SONET/SDH transport product that can be configured for either BITS synchronization or line timing. You cannot connect the OC-12/STM-4 signals to a SONET/SDH SRM OCI from a source that cannot function as a SONET/SDH transport product.

The four OC-12/STM-4 source traffic signals that are to be connected to the SONET/SDH SRM OCI must be frequency synchronous to a single internal clock source.



Procedure 55-30 (continued)Changing clock reference settings for a SONET/SDH SRM OCI

Step Action

4 From the menu that appears, select Timing Ref.

Note: The Timing Ref. menu item is available only when you select a SONET/SDH SRM OCI circuit pack. If it is not available, check that you have selected the correct type of SRM circuit pack.

The OPTera Metro Timing window appears.

5 In the Provisioning section of the window, use the drop-down menus to select one port to be the primary clock reference and one port to be the secondary clock reference. This action does not affect traffic.

Note: The change can take up to 10 seconds. The status updates when the change is complete. You can also click Refresh to update the status.

6 Click OK.

—end—



Procedure 55-31Performing a health check

Follow this procedure to check on the operating performance of any shelf in the network. Nortel Networks recommends that you perform a health check after a software upgrade to verify the successful completion of the upgrade on all the shelves in the network.

The target shelf must operate on a release 4.0 version of OPTera Metro 5200 software.

Action

Step Action

1 Select the Admin tab.

The Software Upgrade window displays.

2 Right-click on the target shelf.OM0574

A menu list displays.

3 Click the Healthcheck menu item.

The Confirm Health Check dialog displays.

4 Click Yes.

A progress bar indicates the percentage progress of the health check as it runs on the target shelf. When complete, the Health Check Status dialog prompts the user.

—continued—



Procedure 55-31 (continued)Performing a health check

Step Action

5 If the health check is successful, click Yes to save the report.

The Save Report File As: window displays. System manager proposes that you save the report to C:/NortelNetworks/OPTeraMetro/HealthCheck/ for WIndows, or to home/user/OPTeraMetro/HealthCheck for UNIX. The proposed file naming convention is: <shelf name>_<time>_<date> as in 47.180.99.30_1550_7Mar2001.

6 If required, change the proposed file name and default directory. Click Save.OM0573

The Confirm Save Report File dialog appears.

7 Click Yes to complete the process.

—end—



Procedure 55-32Retrieving a health check report

Follow this procedure to retrieve a health check report.

Action

Step Action


The Software Upgrade window displays.

2 Right-click on the target shelf.

A menu list displays.

3 Click the Report menu item.

The Report File Status dialog displays.

4 If a report exists, a file dialog displays the file name and default directory. If a report does not exist, a message advises you to perform a health check.

—end—



Procedure 55-33Viewing the Login User List

Follow this procedure to view the SNMP clients that are logged in through the System Manager.

System Manager lists reach through sessions from the Preside Manager for OPTera Metro, and direct System Manager user sessions.

TL1 clients are not shown at this time.

OM0879p

Step Action


The Login User List window appears.

The Shelf Name and Shelf IP are the name and IP address of the host shelf. The Machine IP is the user IP address where SNMP information is being sent. The Group.User ID column lists the user group and user ID for the session. The Trap Port indicates the communication port through which the session receives information. The Trap Type indicates whether the session is System Manager (SMI) or a Preside Manager for OPTera Metro (PMOM) reach through.

There is a limit of eight simultaneous System Manager sessions per ring.

—end—



Procedure 55-34Exiting the System Manager

Follow this procedure to exit the System Manager.

Action

Step Action

1 From the File menu, select Exit.

The Shut Down window appears. See Figure 55-11.

2 If you want to exit, click Yes. If you decide you do not want to exit, click No.

Figure 55-11Shut Down window

OM0236

Note: The Shut Down window does not appear when you click Cancel on the login prompt, or if the login procedure has failed three times. In these situations, the System Manager automatically closes.

—end—


56-1

Provisioning circuit packs and managing traffic 56-

Use the procedures in this chapter to assign channels, connect traffic, define path protection, and manage traffic.

Circuit pack and facility statesA provisioned circuit pack has two state types:

• administrative

• operational

Each state type can be either in-service (IS) or out-of-service (OOS). The administrative state of a provisioned circuit pack is IS if both the circuit pack and its related facilities (if any) are IS. Use the System Manager to place a circuit pack and any related facilities IS or OOS.

FacilitiesA facility is a provisioned configuration on a circuit pack that supports the data transport service. In the OPTera Metro 5200, only these circuit packs have facilities:

• OCI

• OCLD

• OFA

• OSC

• 10 Gbit/s OTR

An SRM OCI or SONET/SDH SRM OCI circuit pack has four facilities, one for each of its ports.

An OSC circuit has four facilities; two for the optical supervisory channel (OSC) and two for the wayside channel (WSC).

The 10 Gbit/s OTR has two facilities, one for the client and one for the DWDM line.

56-2 Provisioning circuit packs and managing traffic


Changing the state of circuit packs and facilitiesYou cannot control the operational state directly. The following factors determine the operational state of a circuit pack:

• the administrative state of the circuit pack

• the operational state of the network

If the administrative state of a circuit pack is IS and its network path can carry traffic, then the operational state is IS. All other combinations change the operational state to OOS. The operational state of circuit packs must be IS if they are to perform their assigned functions. When you use the System Manager to query the state of a circuit pack, the OPTera Metro 5200 shelf reports its operational state.

You must change the administrative state on a circuit pack to OOS before you perform any maintenance procedures on that circuit pack. When you change the administrative state to OOS, you force the operational state to OOS and the circuit pack cannot perform its provisioned function.

You can leave an OCM in-service before you switch traffic to the protecting OCM.

You must change the administrative state of an OCI, OCLD, OTR, or OFA circuit pack IS before you can put its related facility IS. In addition, you must change the state of an OCI, OCLD, OTR, or OFA facility to OOS before you can take its related circuit pack OOS. The software takes approximately 15 seconds to complete requests to change the state of facilities and circuit packs.

When you place the OSC circuit pack in service, the OSC facilities (east and west) are automatically in service. You must place the WSC facilities (east and west) in service if you require the wayside channel. The OSC circuit pack automatically defaults to an in service state when it is provisioned.

Note 1: An SRM OCI or SONET/SDH SRM OCI circuit pack must be IS before you can put any of its four facilities IS. All IS facilities of either type of SRM OCI circuit pack must be taken OOS before you can take the SRM OCI circuit pack OOS.

Note 2: A 10 Gbit/s OTR circuit pack must be IS before you can put any of its two facilities IS. When you take a 10 Gbit/s OTR circuit pack OOS, you must first put both of its facilities OOS.

Provisioning circuit packs and managing traffic 56-3


RequirementsTable 56-1 lists the tools and materials required to complete the procedures in this chapter.

Before you beginBefore you begin the procedures in this chapter, make sure that you have commissioned the network according to the “Commissioning shelves” chapter in Powering and Commissioning Procedures, 323-1701-220.

Log in to the System Manager as an Admin or Operator level user.

Precautions

Table 56-1Tools and materials required to complete circuit pack provisioning procedures

Item Quantity Supplied

Antistatic wrist strap 1 no

Optical fiber cleaning kit 1 no

Optical test set 1 no

Adapters (if necessary) 1 no

CAUTIONRisk of shelf malfunctionNortel Networks recommends that you do not use cellular phones at any OPTera Metro 5200 site. The use of cellular phones in proximity to OPTera Metro equipment can cause shelf malfunction.

CAUTIONRisk of file corruption or shelf failuresDo not make provisioning changes during a backup or restore procedure, because this can corrupt the backup file, or can cause shelf failures.

For more information about backup and procedures, refer to the procedures “Backing up shelf configuration data” on page 55-49 and “Restoring shelf configuration data” on page 55-52 in this book.




Table 56-2Procedures for provisioning the circuit packs


56-1 Manually provisioning circuit packs 56-6 Required.

56-2 Making channel assignments 56-9 Required.

56-3 Deleting channel assignments 56-17 Required.

56-4 Putting a circuit pack in-service 56-19 Required.

56-5 Taking a circuit pack out-of-service 56-20 Optional.

56-6 Putting a circuit pack facility in-service 56-21 Required.

56-7 Putting a WSC facility in-service 56-22 Optional.

56-8 Taking a circuit pack facility out-of-service 56-24 Optional.

56-9 Manually provisioning an ECT 56-25 Optional.

56-10 Removing traffic from an OCI circuit pack

56-27 Optional.

56-11 Adding traffic to an OCLD circuit pack 56-28 Required.

56-12 Removing traffic from an OCLD circuit pack

56-29 Optional.

56-13 Adding traffic to an OTR circuit pack 56-31

56-14 Removing traffic from an OTR circuit pack

56-32

56-15 Adding path protection to an unprotected path

56-34 Optional.

56-16 Forcing traffic to one path on a protected channel

56-36 Optional.

56-17 Removing a forced path switch 56-38 Optional.

56-18 Creating two unprotected paths from one protected OCLD path

56-39 Optional.

56-19 Creating two unprotected paths from one protected OTR path

56-41 Optional.

56-20 Locking out a circuit pack 56-43 Optional.

56-21 Forced switching on OCM circuit packs 56-44 Optional.

—continued—



56-22 Manual switching on protected channel assignments

56-46 Optional.

56-23 Manual switching on OCM circuit packs 56-47 Optional.

56-24 Creating a loopback using the System Manager

56-49 Optional.

56-25 Manual switching of clock references for a SONET/SDH SRM OCI

56-50 Optional.

56-26 Upgrading a shelf to 2.5 Gbit/s OCM circuit packs

56-52 You must use 2.5 Gbit/s OCM circuit packs in a shelf if you are provisioning SONET/SDH SRM OCI, OC-48/STM-16 OCI circuit packs, or if you are provisioning SONET/SDH OCI circuit packs for an OC-48/STM-16 signal.

Table 56-2 (continued)Procedures for provisioning the circuit packs




Procedure 56-1Manually provisioning circuit packs

Manually provision a circuit pack when autoprovisioning does not apply. For example, follow this procedure when you want to provision the circuit pack before it is actually inserted into the shelf, or when the circuit pack has been deleted from the inventory, and you want to add it without reseating the card.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to manually provision circuit packs.

Expected resultsWhen you complete this procedure, the Inventory window in the System Manager lists the manually provisioned circuit packs in an OOS state. The Facilities window in the System Manager lists the related facilities for the circuit pack(s) in an OOS state.

If the circuit packs do not display correctly in the Inventory, delete any incorrect entries from the Facilities and Inventory windows (in that order) and manually provision the circuit packs again.

Follow Procedure 56-2 to make channel assignments.

—continued—

ATTENTIONIf you are provisioning SONET/SDH SRM OCI or OC-48/STM-16 OCI circuit packs, or if you are planning to provision a SONET/SDH OCI circuit pack with an OC-48/STM-16 signal, you must have 2.5 Gbit/s OCM circuit packs installed in the shelf.

To upgrade 1.25 Gbit/s OCM circuit packs to 2.5 Gbit/s circuit packs, follow Procedure 56-26.

For more information, refer to “OCI compatibility” on page 17-3 of the “Circuit pack description” chapter in Hardware Description, 323-1701-102.



Procedure 56-1 (continued)Manually provisioning circuit packs

Action

Step Action

1 In the System Manager, select the Equipment tab.

2 Select the Inventory tab.

3 Double-click the empty slot that contains the circuit pack you want to provision.

The OPTera Metro 5200 Inventory—Add wizard window appears.OM0791t

4 From the Card Type drop-down list, select the type of circuit pack that you are provisioning. If you are provisioning a circuit pack in:

• slots 1 through 8, or 11 through 18, the Circuit Pack Type defaults to OCI, SRM, OCLD and OTR; do not attempt to provision an OTR in slots 8 or 18, or you will generate an Operation Error.

• slot 9 or 10, the Circuit Pack Type defaults to OCM.

• slot 20, the Circuit Pack Type defaults to OSC.

5 Click the Next button.

—continued—



Procedure 56-1 (continued)Manually provisioning circuit packs

Step Action

6 If you are provisioning an OCLD circuit pack, complete the following steps:a. Select a bit rate from the Max Bit Rate list.

b. Select a band from the Band drop-down list.

c. Select a channel from the Channel drop-down list.

d. Go to step 12.

7 If you are provisioning an OCI circuit pack, complete the following steps:

a. Select a bit rate from the Max Bit Rate list.

b. Select a wavelength from the Wavelength list.

c. Go to step 12.

8 If you are provisioning an SRM OCI or SONET/SDH SRM OCI circuit pack, select a bit rate from the Max Bit Rate list. Go to step 12.

9 If you are provisioning an OCM circuit pack, select a bit rate from the Max Bit Rate list. Go to step 12.

10 If you are provisioning an OSC circuit pack, go to step 12.

11 If you are provisioning an OTR, the circuit pack defaults to the 10 Gbit/s OTR. Complete the following steps:

a. Select a band from the Band list.

b. Select a channel from the Channel list.

c. Go to step 12.

12 Click the Finished button.

—end—



Procedure 56-2Making channel assignments

Follow this procedure to make channel assignments using the OPTera Metro 5200 System Manager. You can make unprotected, protected, or pass-through channel assignments.

If you configure the channel assignment as revertive, you can define the working path and WTR period. The WTR period is the amount of time traffic must wait before it reverts to the primary path after the fault on the primary path is cleared.

Before you beginSeat the circuit packs before making channel assignments. Make sure that you comply with all of the following guidelines:

• The OCI, OCLD, and OCM circuit packs must be compatible; that is, if the OCI and OCLD circuit packs support 2.5 Gbit/s service, the OCM must support 2.5 Gbit/s service.

• The OTR circuit pack is compatible with both the 1.25 Gbit/s and 2.5 Gbit/s OCM circuit packs.

• Seat the double-slot OTR circuit pack in slots 1 through 7 (west), or slots 11 through 17 (east).

• Seat OCI or OCLD circuit packs in slots 1 through 8 (west), or slots 11 through 18 (east).

• Assign a channel to one port at a time for SRM OCI and SONET/SDH SRM OCI circuit packs.

Equipping requirements for channel assignments• OCLD pass-through connections require two OCLD circuit packs; one for

the west (slots 1 through 8), and one for the east (slots 11 through 18).

• OCLD/OCI protected channels require one OCI circuit pack and two OCLD circuit packs; seat one OCLD in the west plane (slots 1 through 8), and seat one OCLD in the east plane (slots 11 through 18); seat the OCI in any of slots one through eight, or slots 11 through 18.

• OCLD/OCI unprotected channels require one OCI circuit pack and one OCLD circuit pack; seat the OCLD in the correct unprotected plane; for example, if the unprotected connection is east, seat the OCLD in any of slots 11 through 18.

Note: Equipping requirements for OCLD/SONET SDH SRM OCI or SRM OCI circuit packs are the same as the OCLD/OCI requirements.

—continued—



Procedure 56-2 (continued)Making channel assignments

• OTR protected channels require two OTR circuit packs and a transponder protection tray. One transponder protection tray can support a maximum of four OTR circuit pack pairs. Seat one double-slot OTR in the west plane (anywhere in slots 1 through 7), and one double-slot OTR in the east plane (anywhere in slots 11 through 17).

• OTR unprotected channels require one OTR circuit pack. Seat one double-slot OTR anywhere in slots 1 through 7 (west) or slots 11 through 17 (east).

Each channel assignment involves two to three facilities at each shelf in the path. Each facility has a status. The channel assignment status reflects the status of the sum of the two or three facilities. If any of the facilities are out-of-service, System Manager sets the status to out-of-service and the channel assignment cannot carry traffic. The only exceptions are:

• if the channel assignment is part of a protected channel and one OCLD is OOS, traffic can still be carried over the other OCLD.

• if the channel assignment is part of a protected channel for OTRs both the client-side and line-side facilities on the active path for the 10 Gbit/s signal must be in service; if they are out-of-service on the inactive path, there is no protection.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to make channel assignments.

System Manager provides a view of one ring. Before you begin to make channel assignments, sort the Shelf List clockwise to reflect the order of the ring. When you are done, the originating shelf is at the top of the Shelf List, followed by the passthrough shelves, in order. The terminating shelf is at the bottom. See Procedure 55-14 in the Using the System Manager chapter of this NTP for information on sorting shelves.

Know your network plan. Make your channel assignments on a band/shelf basis. Begin with the originating or terminal shelf for a particular band, and work your way through the pass through shelves to the opposite end of the ring. Use the Band Scope feature to view all the shelves that carry a particular band in the ring.

—continued—




Expected resultsWhen you complete this procedure, channel assignments are completed for the ring across an entire band.

• Proceed to the next band in the ring, and repeat this procedure until all bands are provisioned

• Nortel Networks recommends that you perform Procedure 53-6 in Test Procedures, 323-1701-222, to test far-end optical loopback before continuing with Procedure 56-4, to put the circuit pack in-service

Action

Step Action

1 Click on the Selected Shelves drop-list, and double-click on the shelf that terminates the traffic for the band of the channel assignments you intend to make.

System Manager updates the screen with data for the selected shelf.

2 Click on the Selected Shelves drop-list to return the screen to full view.


The Channel Assignments window displays.

4 Highlight a row containing the target band, channel, direction and circuit pack.

5 Select the Band Scope check box, and click Refresh.

System Manager lists all the shelves in the ring that carry that particular band.

—continued—

ATTENTIONBefore you make a channel assignment for a SONET/SDH SRM OCI circuit pack, you must make sure that the four OC-12/STM-4 source signals come from a single SONET/SDH transport product that can be configured for either BITS synchronization or line timing. You cannot connect the OC-12/STM-4 signals to a SONET/SDH SRM OCI from a source that cannot function as a SONET/SDH transport product.

The four OC-12/STM-4 source traffic signals that are to be connected to the SONET/SDH SRM OCI must be frequency synchronous to a single internal clock source.




6 Double-click on the correct line for the channel assignment that you want to make, or modify.

Note 1: If you select a line where SRM is listed in the End Point column, four more lines appear below the line you selected. These four lines list the four ports of the selected SRM OCI or SONET/SDH SRM OCI circuit pack. Double-click on the SRM port for which you intend to make or modify a channel assignment.

Note 2: If you are creating a channel assignment for a SONET/SDH SRM OCI circuit pack, the first port that you select for a channel assignment is automatically used as the primary clock reference for the SONET/SDH signal. The second port that you select for a channel assignment is automatically used as the secondary clock reference for the SONET/SDH signal. You can change the clock references at any time after making channel assignments.

The OPTera Metro 5200 Channel Assignments window appears.OM0875t

—continued—




7 Select a mode for the channel assignment from the Mode drop-down list. This is a mandatory field.

When the selected Mode is pass-through, System Manager automatically lists the east and west path facilities. When the selected Mode is unprotected, System Manager lists the facility in the east or west path, as appropriate, and enables the End point field. When the selected Mode is protected, the Protection tab is enabled after you apply the selection, and System Manager lists the facilities for the east and west paths, and enables the End point field.

8 If you defined a protected or unprotected channel assignment in the previous step, use the End point drop-list to select the originating facility for the signal at the current shelf. For a pass-through channel assignment or OTR facility, go directly to step 9.

The End point field remains blank for a pass-through channel assignment.

9 Select a protocol for the channel assignment from the Protocol drop-down list. This is a mandatory field.

Note: For an SRM OCI pass-through assignment select SRM 125. For a SONET/SDH SRM OCI pass-through assignment, select SRM 250. Both of these options are used only at pass-through sites.

10 Use the drop-list to define the PM Mode for the End point. (PM Mode is only applicable to the End point facility in this release).

Note: When you change the PM mode for the 10 Gbit/s OTR, a warning message about a possible traffic hit appears.

11 Enter a name for the channel assignment in CA Name. This is a mandatory field.

—continued—




Step Action

12 Enter a description of the channel assignment in CA Description. This is a mandatory field.

If you are creating a channel assignment for an SRM facility (an SRM OCI or a SONET/SDH SRM OCI circuit pack), enter a name for the port associated with the SRM facility in PA Name. Enter a description of the port associated with the SRM facility in PA Description.

13 Click OK.

The OPTera Metro Channel Assignments window closes after the channel assignment is created.

Defining parameters for protected channel assignments

14 Double-click on the line showing the channel assignment you just created.

The OPTera Metro Channel Assignments window appears.

15 Select the Protection tab.

—continued—

If the channel assignment is

Then

unprotected you have completed a channel assignment on this shelf; complete the remaining channel assignments for the same band at this shelf, then proceed to the next shelf carrying the same band; you must complete the channel assignment across the entire path.

pass-through you have completed a channel assignment on this shelf; complete the remaining channel assignments for the same band at this shelf, then proceed to the next shelf carrying the same band; you must complete the channel assignment across the entire path.

protected proceed to step 14 to make changes to the protection configuration.




Step Action

OM0876t

The Protection window displays.

The Status portion of the window is for display purposes. The Rx Reversion portion of the window shows the WTR and Working Path defaults, which remain greyed out and disabled until Reversion is enabled. The Rx Switch Request portion of the window lists the various switch options along with a To drop-list which you can use to define the target switch facility.

—continued—




Step Action

16

17 Click OK.

Note: The software takes approximately 15 seconds to update the channel assignment information.

18 Repeat this procedure until you assign all channels for the band at a particular shelf, then proceed to the next shelf carrying the same band and do the same.

—end—

If you intend to Then

enable reversion select the Enabled check box, and define the WTR period and the Working Path from the drop-lists provided.

disable reversion make sure that the Enabled check box is not selected.

make an Rx switch request

define the switch request by selecting the appropriate radio button, and use the drop-list to define the target facility for the request.



Procedure 56-3Deleting channel assignments

Follow this procedure to delete channel assignments.

RequirementsSystem Manager provides a view of one ring. Before you begin to delete channel assignments, sort the Shelf List clockwise to reflect the order of the ring. When you are done, the originating shelf is at the top of the Shelf List, followed by the passthrough shelves, in order. The terminating shelf is at the bottom.

Make channel deletions in order, from one end of the path to the opposite end. Begin with the originating or terminal shelf at one end, and work your way through the passthrough shelves to the opposite end of the ring.

You must be logged in to the System Manager as an Admin or Operator level user to delete channel assignments.

PrecautionsReroute and remove traffic from the channel before deleting the channel assignment. To reroute traffic refer to Procedure 56-15, Procedure 56-16 or Procedure 56-22. To remove traffic from an OCI circuit pack, follow Procedure 56-10. To remove traffic from an OCLD circuit pack, follow Procedure 56-12.

Expected resultsWhen you complete this procedure, follow Procedure 56-2 if you want to add new channel assignments.

—continued—

CAUTIONRisk of service interruptionIf you delete the channel assignment for a channel that is carrying traffic, the traffic will be interrupted.



Procedure 56-3 (continued)Deleting channel assignments

Action

Step Action

1 In the System Manager, select the Connections tab.

The Channel Assignments window displays.

2 Select the row containing the target band, channel, direction and circuit pack.

3 Select the Band Scope check box, and click Refresh.

System Manager lists all the shelves in the ring that carry that particular band, and all the associated channel assignments.

4 Begin at the terminating shelf for the channel assignment. Select the row for the channel assignment you want to delete.

Note: This step prepares you to delete the channel assignment. Deleting a channel assignment interrupts any traffic carried on that channel.

5 Right-click and select Delete.

The Confirm Channel Assignment Delete dialog box appears.

6 Click Yes.

Note 1: The software takes approximately 15 seconds to delete the channel assignment.

Note 2: If you delete a channel assignment connected to the port on a SONET/SDH SRM OCI circuit pack that was functioning as the clock reference source (primary or secondary), the next available provisioned port on that SONET/SDH SRM OCI will automatically become the clock reference source.

7 Repeat steps 3 through 6 for the pass-through channel assignments and the originating channel assignment for the path.

—end—



Procedure 56-4Putting a circuit pack in-service

Follow this procedure to put a circuit pack in-service (IS) after manual provisioning, or after the circuit pack has been placed out-of-service in the Inventory.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to put a circuit pack in-service.

Circuit pack equipment must be in-service before you place related circuit pack facilities in-service.

PrecautionsMake sure that the slot is equipped, or you will raise a Circuit Pack Missing alarm.

Expected resultsWhen you complete this procedure, follow Procedure 56-6 to put a circuit pack facility in-service.

Action

Step Action


The Equipment page appears.


3 Double-click the line that contains the circuit pack that you want to put IS.

The OPTera Metro 5200 Inventory dialog box appears.

4 In the State area of the OPTera Metro 5200 Inventory dialog box, select IS from the Administrative drop-down list.

5 Click OK to apply the selection and exit the window.

Note: The software takes approximately 15 seconds to put the circuit pack IS.

—end—

CAUTIONRisk of generating alarms on the networkMake sure the slot is equipped before you change the administrative state to IS or you will raise a Circuit Pack Missing alarm on the network.



Procedure 56-5Taking a circuit pack out-of-service

Follow this procedure to take a circuit pack out-of-service (OOS).

RequirementsBefore you take a traffic carrying circuit pack OOS, put all related circuit pack facilities OOS first. To put a circuit pack facility OOS, follow Procedure 56-8.

Note 1: When you take an SRM OCI or SONET/SDH SRM OCI circuit pack OOS, you must first put all four of its facilities OOS.

Note 2: When you take a 10 Gbit/s OTR circuit pack OOS, you must first put both of its facilities OOS.

You must be logged in to the System Manager as an Admin or Operator level user to take a circuit pack out-of-service.

Action

Step Action


The Equipment screen appears.


The Inventory window appears.

3 Select the row that lists the target circuit pack in the correct slot number.

4 Double-click on the selected row.


5 In the State area of the OPTera Metro 5200 Inventory dialog box, select OOS from the Administrative drop-down list.

6 Click OK to close the dialog box.

The Confirm Inventory OOS dialog box appears.

7 Click Yes to confirm the change.

Note: The software takes approximately 15 seconds to take the circuit pack OOS.

—end—



Procedure 56-6Putting a circuit pack facility in-service

Follow this procedure to put a circuit pack facility in-service (IS).

RequirementsBefore you can begin this procedure, the related circuit pack must be IS. Follow Procedure 56-4 if you need to put the circuit pack IS.

You must be logged in to the System Manager as an Admin or Operator level user to put a circuit pack facility in-service.

Expected resultsWhen you complete this procedure, follow Procedure 53-6 in Test Procedures, 323-1701-222, to test far-end optical loopback. You must test far-end optical loopback before adding traffic to a circuit pack.

Action

Step Action


2 Select the Facilities tab.

The Facilities window appears.

3 Select the row that lists the slot number, port number, and circuit pack facility that you want to place IS.



5 In the State area of the OPTera Metro 5200 Inventory dialog box select IS from the Administrative drop-down list.


The Confirm Inventory OOS dialog box appears.


Note: The software takes approximately 15 seconds to put the facility IS.

—end—



Procedure 56-7Putting a WSC facility in-service

Follow this procedure to put the east and west WSC facilities of an OSC circuit pack in-service (IS). The east and west OSC facilities are automatically in-service, as soon as the OSC circuit pack is placed in-service.

RequirementsBefore you can begin this procedure, the OSC circuit pack must be IS.

Make sure that the OSC circuit pack is connected to the OSC trays. Follow Procedure 47-16 to Procedure 47-20 in the “Connecting shelf components” chapter of Powering and Commissioning Procedures, 323-1701-220, to make the required connections.

Action

Step Action

1 In the System Manager, click on Selected Shelves.

2 Select the shelf that has the target OSC in its inventory and double-click.


The Equipment screen appears.


The Facilities window appears.

5 Select the row in slot 20 that lists the WSC facility that you want to place IS.


The OPTera Metro Facility dialog box appears.

7 Click on the drop-down list in the Mode field, and select Add-Drop or Pass Through to define WSC traffic at this shelf.

The selection that you make in this field applies to the east and west WSC facilities for this shelf.

—continued—



Procedure 56-7 (continued)Putting a WSC facility in-service

Step Action

8 In the State area of the dialog box, select IS from the Administrative drop-down list.

The selection that you make in this field applies to the east and west WSC facilities.


10 Go to the next shelf in the network, and repeat steps 3 to 8 until you have provisioned the WSC facilities at each shelf in the path.

—end—



Procedure 56-8Taking a circuit pack facility out-of-service

Follow this procedure to take a circuit pack facility out-of-service (OOS).

The circuit pack can remain in-service while the facility of the circuit pack is out-of-service.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to put a circuit pack facility out-of-service.

If you are taking an SRM OCI or SONET/SDH SRM OCI circuit pack OOS, you must first take all four of its facilities OOS.

If you are taking facilities carried by the OSC circuit pack OOS, do the east and west WSC facilities first, then do the east and west OSC facilities. The east and west facilities are independent of each other, so you must take each individual facility OOS.

Action

Step Action



3 Select the row that lists the facility you want to place OOS and double-click.


4 In the State area of the OPTera Metro 5200 Inventory dialog box select OOS from the Administrative drop-down list.


Note: The software takes approximately 15 seconds to take the facility OOS.

—end—



Procedure 56-9Manually provisioning an ECT

When power is applied to an OFA shelf, the OPTera Metro 5200 automatically provisions the ECTs that are installed in the shelf.

Follow this procedure to manually provision an ECT and put the ECT in-service.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to manually provision an ECT.

Expected resultsWhen you complete this procedure, the ECT is put in-service.

Action

Step Action


The Equipment window appears.


The Inventory window appears.OM0290

—continued—



Procedure 56-9 (continued)Manually provisioning an ECT

Step Action

3 In the Slot column, double-click the ECT that you want to put in-service.

The OPTera Metro Inventory window appears.OM0291

4 From the Filter Type drop-down list, select the type of ECT that you are provisioning.

5 From the Administrative drop-down list, select IS.

6 Click Apply to make the changes.

7 Click OK to exit the window.

—end—



Procedure 56-10Removing traffic from an OCI circuit pack

Follow this procedure to remove traffic from an OCI circuit pack.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to remove traffic from an OCI circuit pack.

When you remove traffic from a SONET/SDH SRM OCI circuit pack, leave the subtending equipment connected to the circuit pack.

Expected resultsWhen you complete this procedure, traffic is removed from the OCI circuit pack.

Action

Step Action

1 Identify the circuit pack from which you want to remove the traffic.



4 Double-click on the line for the circuit pack that carries the traffic you want to remove.

5 Take the OCI facility OOS. See Procedure 56-8 for further information.


7 Take the OCI circuit pack OOS. See Procedure 56-5 for further information.

—end—



Procedure 56-11Adding traffic to an OCLD circuit pack

Follow this procedure to add traffic to an OCLD circuit pack.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to add traffic to an OCLD circuit pack.

Seat the OCLD and OCI circuit packs before you begin this procedure. See the “Seating circuit packs” chapter in this NTP for further information.

Expected resultsWhen you complete this procedure the OCLD circuit pack is IS and ready to carry traffic.

Action

Step Action

1 Provision a channel assignment for the OCLD and OCI circuit packs in the connection. See Procedure 56-2 for further information.

2 Connect the corresponding OCI circuit pack to the traffic source. See Procedure 47-12 in the “Connecting shelf components” chapter of Powering and Commissioning Procedures, 323-1701-220.

3 Place the OCI facility IS. See Procedure 56-6 for further information.

—end—



Procedure 56-12Removing traffic from an OCLD circuit pack

Follow this procedure to remove traffic from an OCLD circuit pack.

You can remove traffic from an OCLD that is part of a protected channel assignment without losing traffic. In a protected channel assignment, an OCI circuit pack has two corresponding OCLD circuit packs. You can force all the traffic to one OCLD circuit pack at each end of the path before you take the corresponding OCLD circuit pack OOS.

If you remove traffic from an OCLD circuit pack that is part of an unprotected channel assignment, you will lose traffic.

RequirementsFollow Procedure 56-17 to force the traffic to a different path in both the Tx and Rx directions. To make sure there is no traffic loss, remove traffic from the OCLD circuit pack at both ends of the path.

You must be logged in to the System Manager as an Admin or Operator level user to remove traffic from an OCLD circuit pack.

Expected resultsWhen you complete this procedure, traffic is removed from the OCLD circuit pack.

Action

Step Action

1 Identify the OCLD circuit pack that carries the traffic that you want to remove.

2 In the System Manager, select the Channel Assignment tab.

3 Check to see if the OCLD circuit pack is part of a protected channel assignment. If the OCLD is protected, its Mode is listed as Active-path or Prot-path. If the OCLD is unprotected, its Mode is listed as Pass-through, Unprotected, or is blank.

4 If the OCLD is unprotected, right-click on the OCLD line and select Delete from the menu that appears. Go to step 9.

—continued—



Procedure 56-12 (continued)Removing traffic from an OCLD circuit pack

Step Action

5 If the channel assignment has path protection, double-click the line for the OCLD that you want to remove traffic from.

The OPTera Metro 5200 Channel Assignments dialog box appears.

6 Select the Protection tab. In the Request Switch area, select the Force radio button. In the To drop-down list, select the OCLD circuit pack that you want to force the traffic to.

7 Click OK.

8 Repeat step 2 to step 7 for the other end of the path to make sure that the traffic is forced from the Tx and the Rx of the OCLD circuit pack.

9 Take the OCLD facility OOS by following Procedure 56-8.

10 Take the OCLD circuit pack OOS using Procedure 56-5.

—end—



Procedure 56-13Adding traffic to an OTR circuit pack

Follow this procedure to add traffic to a 10 Gbit/s OTR circuit pack.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to add traffic to a 10 Gbit/s OTR.

Expected resultsWhen you complete this procedure the 10 Gbit/s OTR is in-service (IS) and ready to carry traffic.

Action

Step Action

1 Make sure that the 10 Gbit/s OTR is connected to the OMX (Standard) or OMX + Fiber Manager 4CH, as described in Procedure 47-8 “Connecting an OMX (Standard) tray to OTR circuit packs” on page 47-32 and Procedure 47-9 “Connecting an OMX + Fiber Manager 4CH to OTR circuit packs” on page 47-36.

2 Make sure that the 10 Gbit/s OTR is connected to the subtending equipment.

Note: For a protected network, make sure that the Transponder Protection Tray is installed and connected to the 10 Gbit/s OTR.

3 Provision a channel assignment for the 10 Gbit/s OTR using Procedure 56-2 on page 56-9.

4 Put the OTR IS using Procedure 56-4 “Putting a circuit pack in-service” on page 56-19.

5 Put the OTR LINE facility IS using Procedure 56-6 “Putting a circuit pack facility in-service” on page 56-21.

6 Put the OTR CLIENT facility IS using Procedure 56-6 “Putting a circuit pack facility in-service” on page 56-21.

—end—



Procedure 56-14Removing traffic from an OTR circuit pack

Follow this procedure to remove traffic from a 10 Gbit/s OTR circuit pack.

You can remove traffic from a 10 Gbit/s OTR that is part of a protected channel assignment without losing traffic. In a protected channel assignment, there are two OTRs, one for east traffic and one for west traffic. You can force all the traffic to one OTR at each end of the path before you take the corresponding OTR out-of-service (OOS).

If you remove traffic from an OTR that is part of an unprotected channel assignment, you will lose traffic.

RequirementsFollow Procedure 56-17 to force the traffic to a different path in both the Tx and Rx directions. To make sure there is no traffic loss, remove traffic from the 10 Gbit/s OTR at both ends of the path.

You must be logged in to the System Manager as an Admin or Operator level user to remove traffic from a 10 Gbit/s OTR.

Expected resultsWhen you complete this procedure, traffic is removed from the 10 Gbit/s OTR.

Action

Step Action

1 Identify the 10 Gbit/s OTR that carries the traffic that you want to remove.


3 Check to see if the 10 Gbit/s OTR is part of a protected channel assignment. If the OTR is protected, its Mode is listed as Active-path or Prot-path. If the OTR is unprotected, its Mode is listed as Unprotected or is blank.

4 If the OTR is unprotected, right-click on the OTR line and select Delete from the menu that appears. Go to step 9.

5 If the channel assignment has path protection, double-click the line for the OTR that you want to remove traffic from.


6 Select the Protection tab. In the Request Switch area, select the Force radio button. In the To drop-down list, select the OTR that you want to force the traffic to.

—continued—



Procedure 56-14 (continued)Removing traffic from an OTR circuit pack

Step Action

7 Click the OK button.

8 Repeat step 2 to step 7 for the other end of the path to make sure that the traffic is forced from the LINE Tx and the LINE Rx of the 10 Gbit/s OTR.

9 Take the OTR LINE facility OOS as described in Procedure 56-8.

10 Take the OTR CLIENT facility OOS as described in Procedure 56-8.

11 Take the OTR circuit pack OOS using Procedure 56-5.

—end—



Procedure 56-15Adding path protection to an unprotected path

Follow this procedure to add path protection to an unprotected path.

You can configure protected channel assignments as revertive or nonrevertive.

If you configure the channel assignment as revertive, you can configure the primary OCLD path and WTR period. The WTR period is the amount of time traffic must wait before it reverts to the primary path after the fault on the primary path is cleared.

For more information about protection schemes, refer to the “OPTera Metro 5200 protection schemes” chapter in Network Planning and Link Engineering Guidelines, NT0H7104.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to add path protection to an unprotected path.

You must install a Transponder Protection Tray before you can add path protection for 10 Gbit/s OTR circuit packs.

PrecautionsFor 10 Gbit/s OTR circuit packs, adding path protection is traffic-affecting if the Transponder Protection Tray is not already installed. In order to install the tray, the client signal has to be disrupted while the fiber between the Transponder Protection Tray and the 10 Gbit/s OTR is connected.

Expected resultsWhen you complete this procedure

• the path is protected

• follow Procedure 56-2 to assign two OCLD circuit packs to an OCI circuit pack and make the channel assignment

Action

Step Action

1 Make sure that the circuit packs required for path protection are inserted in the shelf.

2 Make sure that the circuit packs and facilities required for path protection are IS.

—continued—



Procedure 56-15 (continued)Adding path protection to an unprotected path

Step Action

3 In the System Manager, select the Connections tab.

4 Select the Channel Assignment tab.

5 Double-click on the line that contains the unprotected path that you want to protect.

The OPTera Metro 5200 Connections dialog box appears.

6 In the Channel Characteristics area, select Protected from the Mode drop-down list.

The OPTera Metro Channel Assignments dialog box closes.

7 Double-click on the line showing the channel assignment you just protected.

The OPTera Metro Channel Assignments dialog box appears.


9 Select revertive or nonrevertive from the path protection dialog box.

10 If you selected revertive protection switching in step 9, configure the primary OCLD path and WTR period.

a. Select the path you want to configure as the primary path from the path protection dialog box.

b. Select the WTR period from the WTR period drop-down menu in the path protection dialog box

Note: You can set the WTR period from between 5 to 12 minutes, in 1-minute intervals. The default is 5 minutes.

11 Click OK.

—end—



Procedure 56-16Forcing traffic to one path on a protected channel

Follow this procedure to force traffic to one path on a protected channel. This procedure is also called a forced switch.

In the Channel Assignment window, the Current Rx Selection indicates which side of the ring is receiving the signal. To determine on which side of the ring the signal is being transmitted, check the Current Rx Selection checkbox for the far end of the connection.

You cannot set a forced equipment switch if you lock out the channel assignment.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to force traffic to one path on a protected channel.

PrecautionsWhen you force traffic to one path on a protected channel, the single path operates like an unprotected path.


• traffic is forced to the OCLD or 10 Gbit/s OTR circuit pack that is specified in the Current Rx Selection area of the Protection panel

• the Force column displays an Active status for the OCLD line that you selected

—continued—

CAUTIONRisk of service interruptionWhen you change a protected path to an unprotected, you run the risk of losing traffic if there is a fiber cut or equipment failure on the active path.

Make sure that you are forcing traffic to an OCLD or 10 Gbit/s OTR that is IS. If you force traffic to an OCLD that is OOS, traffic is lost.



Procedure 56-16 (continued)Forcing traffic to one path on a protected channel

Action

Step Action



3 Double-click the line that contains the protected channel assignment that you want to force to one path. If a channel is protected, its Mode is listed as “Active-path” or “Prot-path”.

The Channel Assignments dialog box appears.


5 In the Switch Request area of the dialog box, select the Force radio button.

6 In the To drop-down list, make sure that the OCLD facility you want to force the traffic to is specified. The To field defaults to the corresponding OCLD circuit pack.

7 Click OK.

Wait until the forced switch is complete. This can take several seconds. The switch is complete when the Channel Assignments dialog box becomes active again.

8 Click Cancel to close the dialog box.

—end—



Procedure 56-17Removing a forced path switch

Follow this procedure to remove a forced path switch.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to remove a forced path switch.

Action

Step Action



3 Double-click the line that contains the channel assignment from which you want to remove the force.

The Channel Assignment dialog box appears.


5 In the Switch Request area of the dialog box, select the None radio button.

6 Click OK.

—end—



Procedure 56-18Creating two unprotected paths from one protected OCLD path

Follow this procedure to create two unprotected paths from one OCLD protected path by deleting the protected channel assignment and replacing it with two unprotected channel assignments.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to create two unprotected paths from one protected path.

PrecautionsWhen you create two unprotected paths from one protected path, you add another path to your network, but you lose protection for both paths. If there is an equipment or facility fault on either unprotected path, traffic will be lost.

Action

Step Action

1 Make sure that there is an another OCI circuit pack available in the shelf that goes with one of the OCLD circuit packs that was part of the protected channel assignment.

2 Check the System Manager to see if the OCLD path that you want to add traffic to is already in use. If it is, the Channel Assignment window displays the OCLD circuit packs in bold font. To add a new unprotected connection to a path that is already in use, follow the procedure “Manual switching on protected channel assignments” on page 56-46.

3 Make sure that the circuit packs and facilities required for the unprotected paths are in-service.


5 Double-click on the line that contains the protected path that you want to use to create the first of two unprotected paths.


6 From the Mode drop-down list, select Unprotected East or Unprotected West.

7 Click OK.

—continued—



Procedure 56-18 (continued)Creating two unprotected paths from one protected OCLD path

Step Action

8 To test each of the new connections, follow the procedure “Testing far-end optical loopback” on page 53-26 in Test Procedures, 323-1701-222.

9 Connect the OCI circuit packs to the subtending equipment using Procedure 47-12 in Powering and Commissioning Procedures, 323-1701-220.

10 Make a channel assignment for the remaining OCI circuit pack using Procedure 56-2.

—end—



Procedure 56-19Creating two unprotected paths from one protected OTR path

Follow this procedure to create two unprotected paths from one 10 Gbit/s OTR protected path by deleting the protected channel assignment and replacing it with two unprotected channel assignments.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to create two unprotected paths from one protected path.

PrecautionsWhen you create two unprotected paths from one protected path, you add another path to your network, but you lose protection for both paths. If there is an equipment or facility fault on either unprotected path, traffic will be lost.

A 10 Gbit/s OTR protected path requires two 10 Gbit/s OTR circuit packs, one is active and the other is standing by. Both of the OTR circuit packs are connected to the Transponder Protection Tray. You need to first physically remove the fiber that connects the Transponder Protection Tray and the standby OTR circuit pack before you can connect the OTR to the newly added subtending equipment.

Action

Step Action

1 Check the System Manager to see if the OTR path that you want to add traffic to is already in use. If it is, the Channel Assignment window displays the OTR circuit packs in bold font.

2 Manually switch traffic to the specified 10 Gbit/s OTR in the protection pair for both traffic directions by following the procedure “Manual switching on protected channel assignments” on page 56-46.


4 Double-click on the line that contains the Active protected path that you want to use to create the first of two unprotected paths.


5 From the Mode drop-down list, select Unprotected East or Unprotected West accordingly.

6 Click OK.

—continued—



Procedure 56-19 (continued)Creating two unprotected paths from one protected OTR path

Step Action

7 Physically remove the fiber that connects the Transponder Protection Tray and the standby 10 Gbit/s OTR.

Note: Laser from the client interface of the standby OTR is shut down when the connection is removed.

8 Connect the standby 10 Gbit/s OTR to the newly added subtending equipment.

9 Make a channel assignment for the standby 10 Gbit/s OTR by following the Procedure 56-2.

10 Follow Procedure 56-4 on page 56-19 to put the standby 10 Gbit/s OTR in-service.

11 Follow Procedure 56-6 on page 56-21 to put the standby 10 Gbit/s OTR facility in-service.

—end—



Procedure 56-20Locking out a circuit pack

Follow this procedure to set a lockout on protected channel assignments. A lockout freezes the protection on the selected channel assignment.

If you have selected revertive path protection switching on the channel assignment, the lockout request locks the traffic to the working path. If you have selected nonrevertive path-protection switching on the channel assignment, the traffic is locked to the current path, regardless of its condition.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to lock out a circuit pack.

Precautions


• there is a lockout on protected channel assignments

• no additional protection actions can occur until you remove the lockout

Action

Step Action



3 Double-click the line that contains the channel assignment that you want to lockout.



5 In the Switch Request area, select the Lockout radio button.

6 Click OK.

—end—

CAUTIONRisk of service interruptionWhen you set a lockout, OPTera Metro 5200 cannot do protection switching. Traffic is lost if there is a fiber cut or equipment failure on the active path.



Procedure 56-21Forced switching on OCM circuit packs

Follow this procedure to set a forced switch on OCM circuit packs.

Note: You cannot set a forced switch on one OCM in a shelf if the other OCM is out-of-service (OOS).

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to set a forced switch.

Precautions

Expected resultsWhen you complete this procedure, traffic is forced to the OCM circuit pack that is specified in the Current Rx Selection area of the Equipment Protection panel, regardless of the state of either of the OCM circuit packs.

Action

Step Action



3 Select the OCM that you want to force traffic from.

4 Right-click the highlighted OCM line and select Protection from the menu that appears, or select the Protection button.

The OPTera Metro OCM Protection dialog box appears.

5 In the Switch Request area of the OCM Protection dialog box, select the Force radio button.

6 In the To drop-down list, make sure that the OCM that you want to force the traffic to is selected.

—continued—

CAUTIONRisk of service interruptionWhen you force an equipment switch, make sure that you are forcing the traffic to an OCM circuit pack that can carry traffic. If you force traffic to an out-of-service card, the traffic is lost. However, 10 Gbit/s OTR traffic is not affected.



Procedure 56-21 (continued)Forced switching on OCM circuit packs

Step Action

7 Click OK.

Wait until the forced switch is complete. This can take several seconds. The switch is complete when the OCM Protection dialog box becomes active again.

—end—



Procedure 56-22Manual switching on protected channel assignments

Follow this procedure to set a manual switch on protected channel assignments. When you set a manual switch, traffic only switches to the specified channel assignment when the path is working.

You cannot set a manual equipment switch if you lock out or force the channel assignment.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to set a manual switch.


• traffic is switched to the other OCLD or 10 Gbit/s OTR in the pair, if doing so will not interrupt traffic

• when required, the manually switched channel assignment reverts to the other OCLD or 10 Gbit/s OTR circuit pack in the pair to avoid traffic loss

Action

Step Action



3 Double-click the line that contains the channel assignment for which you want to set the manual switch.



5 In the To drop-down list, select the OCLD or 10 Gbit/s OTR circuit pack to which you want to switch traffic.

6 In the Switch Request area, select the Manual radio button.

7 Click OK.

—end—



Procedure 56-23Manual switching on OCM circuit packs

Follow this procedure to set a manual switch on OCM circuit packs. When you set a manual switch, traffic only switches to the specified OCM when the path is working and the circuit pack in-service.

You cannot set a manual equipment switch if you force the OCM.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to set a manual switch.


• traffic is received from the selected OCM if it is possible

• the manually switched OCM reverts to its mate OCM circuit pack to avoid traffic loss

• manual switching on OCM circuit packs does not affect 10 Gbit/s OTR traffic

Action

Step Action



3 Select the OCM that you want to force traffic from.

—continued—



Procedure 56-23 (continued)Manual switching on OCM circuit packs

Step Action

4 Right-click the highlighted OCM line and select Protection from the menu that appears, or select the Protection button.

The OPTera Metro 5200 OCM Protection dialog box appears.OM0377

5 In the Switch Request area of the OCM Protection dialog box, select the Manual radio button.

6 In the To drop-down list, make sure that the OCM that you want to force the traffic to is specified.

7 Click OK.

Wait until the forced switch is complete. This can take several seconds. The switch is complete when the OCM Protection dialog box becomes active again.

—end—



Procedure 56-24Creating a loopback using the System Manager

Follow this procedure to set up facility or terminal loopbacks using the system manager. A facility loopback connects the Tx to the Rx of a single circuit pack. A terminal loopback sends a signal through a circuit pack and the backplane, and through the circuit pack again.

Note 1: You can only create loopbacks on OCI and OCLD circuit packs that are part of a channel assignment. If the circuit pack is not part of a channel assignment, you cannot create a loopback for it using software.

Note 2: You cannot create terminal loopbacks on OSC and 10 Gbit/s OTR circuit packs. You can only set up facility loopbacks.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to create a loopback using software.


• if you performed a facility loopback, the Tx and Rx of a circuit pack are connected

• if you performed a terminal loopback, the loopback sends a signal through the circuit pack and backplane, and through the circuit pack again

• a minor alarm is raised (this alarm is cleared when the loopback is removed)

Action

Step Action



3 Double-click the line with the circuit pack for which you want to create the loopback.

4 In the State area, select OS from the Administrative drop-down list.

5 In the Loop Back area, select the Terminal radio button or the Facility radio button, depending on the type of loopback that you want to create.

Note: For OSC and 10 Gbit/s OTR circuit packs, you can only select the None radio button or the Facility radio button.

6 Click the OK button.

—end—



Procedure 56-25Manual switching of clock references for a SONET/SDH SRM OCI

Follow this procedure to put the active clock reference timer on standby and to make the standby clock reference the active clock reference for a SONET/SDH SRM OCI circuit pack.

Action

Step Action



3 Right-click the line for the SONET/SDH SRM OCI circuit pack.

4 Select Timing Ref. from the menu.

The OPTera Metro Timing window appears.

5 In the Switch Request area, select the Manual Radio button.

—continued—



Procedure 56-25 (continued)Manual switching of clock references for a SONET/SDH SRM OCI

Step Action

6 In the To field, select the port that you would like to make the active clock reference timer, as shown below.

Note: There are only two ports listed in the To field. These two ports are always the ports of the specified clock reference timers.

OM0347

7 Click Apply.

The Status section of the OPTera Metro Timing window indicates the status of the clock reference timers. If the switch is successful, the previously active clock reference is listed as standby, and the previous standby clock reference is listed as active. The Clock Signal for the new active clock reference should be listed as good.

Note 1: The changes do not interrupt traffic.

Note 2: It can take up to 10 seconds for the changes to take place. When the change is complete, the Status updates in the Timing window. You can also click the Refresh button to update the status.

8 Click OK.

—end—



Procedure 56-26Upgrading a shelf to 2.5 Gbit/s OCM circuit packs

Follow this procedure to upgrade a shelf with one or two 1.25 Gbit/s OCM circuit packs to two 2.5 Gbit/s OCM circuit packs.

RequirementsYou must be logged in to the System Manager as an Admin or Operator level user to create a loopback using software.

Precautions

Action

Step Action

1 Start the System Manager and log in as an admin level user.

2 Check that equipment protection is available on the shelf. Equipment protection means that there are no alarms present and that there are two OCM circuit packs in the shelf.


The Equipment page opens and displays the Inventory, Facilities, and Telemetry tabs.


The Equipment page opens and displays the Inventory worksheet.

Upgrade the OCM circuit pack in slot 10 first.

5 Refer to the Slot column in the Inventory worksheet and select the line containing the slot number for the OCM circuit pack that you want to take out-of-service.

—continued—

CAUTIONRisk of service interruptionYou can disrupt service when you take the OCM circuit pack out-of-service. However, 10 Gbit/s OTR traffic is not affected.

CAUTIONElectrostatic dischargeObserve all antistatic precautions when handling the OCM circuit pack.



Procedure 56-26 (continued)Upgrading a shelf to 2.5 Gbit/s OCM circuit packs

Step Action

6 Double-click on the selected line to open the OPTera Metro 5200 Inventory dialog box.

The OPTera Metro 5200 Inventory dialog box (with the Inventory tab selected) appears on top of the Equipment page.

7 In the State area of the OPTera Metro 5200 Inventory dialog box, select OS from the Administrative drop down menu.

8 Click Apply to update the Admin state.

The Confirm Inventory OS dialog box appears.


10 If present, remove the 1.25G OCM circuit pack from the slot.

11 In the OPTera Metro 5200 Inventory window, select 2.5G from the Max Bit Rate list.

12 Seat the OC48 OCM circuit pack and wait two minutes. Two minutes allows the new OCM circuit pack to boot up, copy the new load from the SP circuit pack, and to synchronize configuration data with the active OCM circuit pack.

13 In the State area of the OPTera Metro 5200 Inventory dialog box, select IS from the Administrative drop list.

14 Click OK to apply the selection and exit the window.

Note 1: At the OPTera Metro 5200 shelf, the Active indicator lamp on the OCM circuit pack lights when the circuit pack comes online.

Note 2: In the System Manager Fault screen, the system displays an “OCM Pair Mismatch” alarm until there are two OCM circuit packs with the same Max Bit Rate in the shelf.

15

16 Check that the system retains the new configuration after you replace the OCM circuit packs.

—end—

If you have just upgraded the OCM circuit pack in

Then

slot 10 repeat step 5 through step 15 for the other OCM circuit pack

slot 9 go to step 16


57-1

Shelf management procedures 57-Use the procedures in this chapter to manage shelves in the network.

Adding or removing OPTera Metro 5200 shelves from a networkYou can have up to 8 shelves at an OPTera Metro 5200 site and up to 40 OADM and 24 OFA shelves in an OPTera Metro 5200 network. The minimum network size is two shelves: one shelf in each of two sites.

If the OPTera Metro 5200 network is path-protected, you can add shelves to the network without affecting the traffic flow. Traffic interruption occurs if you have an unprotected or linear optical add/drop multiplexer (OADM) system.

The shelves in OPTera Metro 5200 hubbed-ring and point-to-point configurations work in pairs. For every terminal shelf in a hubbed-ring configuration, there is a corresponding OADM shelf. For every terminal shelf in a point-to-point configuration there is a corresponding shelf in the other terminal site. When you add or remove a shelf from an OPTera Metro 5200 hubbed-ring or point-to-point configuration, the corresponding shelf cannot add or drop traffic. You must add or remove the corresponding shelf.

For the other OPTera Metro 5200 configurations, including dual-hubbed, linear OADM, and meshed ring, a shelf can add or drop traffic when you commission the shelf.

57-2 Shelf management procedures


PrecautionsAlways decommission a shelf before you physically remove it from an OPTera Metro 5200 network. If you do not decommission the shelf first, the System Manager continues to display the shelf in the network tree. A shelf cannot be deleted from the System Manager if it is not decommissioned before it is removed from the network.

Before you beginBefore you begin the procedures in this chapter, make sure that you have correctly provisioned the shelves in the OPTera Metro 5200 network.


CAUTIONRisk of shelf malfunctionNortel Networks recommends that you do not use cellular phones at any OPTera Metro 5200 site. The use of cellular phones in proximity to OPTera Metro equipment can cause shelf malfunction.

Table 57-1Shelf management procedures


57-1 Decommissioning a shelf 57-4 Optional. You must remove connections on the shelf before you can decommission it.

Note: If you are physically removing a shelf from an OPTera Metro 5200 network, this procedure is required.

57-2 Deleting a shelf 57-6 Optional. You must decommission a shelf before you can delete it.

57-3 Restarting a shelf 57-7 Optional. Use this procedure for maintenance purposes only.

57-4 Adding a shelf to a path-protected network

57-8 Optional.

57-5 Adding a shelf to an unprotected network 57-9 Optional.

57-6 Adding a shelf to a linear OADM network 57-10 Optional.

57-7 Changing configuration information for a shelf

57-11 Optional.

—continued—

Shelf management procedures 57-3


57-8 Configuring shelf surveillance and external management

57-13 Optional.

57-9 Removing a shelf surveillance and external management entry

57-15 Optional.

57-10 Switching traffic off a span in a path-protected network

57-16 Optional.

Table 57-1 (continued)Shelf management procedures




Procedure 57-1Decommissioning a shelf

Follow this procedure to decommission a shelf.

When you decommission a shelf, that shelf cannot carry traffic. Decommissioning a shelf removes all the information that you entered with the commissioning wizard. You must recommission the shelf before the shelf can carry traffic.

When you decommission a shelf, the System Manager deletes the IP address that you assigned during commissioning procedures and restores the shelf to the default IP address that was assigned at the factory.

If you are decommissioning a pair of shelves in a ring, you must decommission the OADM shelf before the corresponding terminal shelf.

Note 1: When you delete a shelf you do not decommission the shelf. If you delete a commissioned shelf, the System Manager adds the shelf to the shelf list the next time you refresh the list.

Note 2: When you decommission a shelf and restart it, it cannot carry traffic until you commission it again.

RequirementsYou must be logged into the System Manager as an Admin level user to decommission a shelf.

PrecautionsMake sure you delete all connections on the shelf before you decommission it. When you try to decommission a shelf that has provisioned connections, a dialog box prompts you to delete the connections. The system does not let you continue with the decommission until you delete the connections. To delete connections, follow Procedure 56-3 in the “Provisioning circuit packs and managing traffic” chapter in this book.

Expected resultsWhen you complete this procedure, follow Procedure 57-2 to delete the shelf.

—continued—



Procedure 57-1 (continued)Decommissioning a shelf

Action

Step Action

1 Make sure that the network is in contact with the primary shelf.

If the primary shelf is out of contact with the network when you decommission a shelf, you must follow Procedure 57-2 to delete the shelf from the network.



4 Select the row that contains the name of the shelf you want to decommission.

5 From the Admin menu, select Decommission Shelf.

The Confirm Shelf Decommission Delete dialog box appears.OM0374

6 In the Confirm Shelf Decommission Delete dialog box, click Yes to delete the commissioning information.

—end—



Procedure 57-2Deleting a shelf

Follow this procedure to delete a shelf from the System Manager.

RequirementsYou must decommission the shelf before you delete it. If you do not decommission the shelf first, the System Manager continues to display the shelf each time the network list is refreshed.

Make sure the shelf you want to decommission and delete is in contact with the primary shelf. If the shelf is not, you must repeat this process at the primary shelf.

Expected resultsWhen you complete this procedure the shelf is deleted from the System Manager.

Action

Step Action


2 Select the Shelf List tab.

3 Select the row that contains the name of the shelf you want to delete.

4 Click Delete.

—end—



Procedure 57-3Restarting a shelf

Follow this procedure to restart a shelf from the System Manager.

If you want to restart the primary or gateway shelf, or the host shelf for the System Manager interface, there will be significant impacts to the ring when you restart the shelf.

If you want to restart the shelf that is hosting the System Manager, you must restart the System Manager interface as well.

If you want to restart the only gateway shelf in the network, all System Manager interface sessions may encounter an LOC during the shelf restart. If there is a fast shelf restart, the LOC may not be reported until after the shelf is restarted.

Action

Step Action


2 Select Communications.

3 Right-click on the shelf that you want to restart.

4 Select Restart.

—end—

CAUTION

This procedure is for maintenance purposes only. Do not restart a shelf on a live network.



Procedure 57-4Adding a shelf to a path-protected network

Follow this procedure to add a shelf to a path-protected network without interrupting traffic.

RequirementsYou must be an Admin level user to add a shelf to a network.

Expected resultsWhen you complete this procedure you have added a shelf to a path-protected network.

Action

Step Action

1 Install the shelf in the rack using the procedures in the “Installing and grounding racks, shelves, and equipment” chapter of Installing Shelves and Components, 323-1701-201.

2 Install the west and east OMXs into the DWDM fiber path as described in Procedure 57-10 “Switching traffic off a span in a path-protected network” on page 57-16.

3 Connect the System Manager computer to the shelf through the 10Base-T 1X port.

4 Start the System Manager and log in as an Admin level user.

5 Run the commissioning wizard on the shelf according to your network configuration. For more information, refer to the “Commissioning shelves” chapter of Powering and Commissioning Procedures, 323-1701-220.

6 Restart the System Manager and log in.

7 Reorder the shelf list to correctly position the new shelf in order. Make channel assignments on the new shelf, as described in Procedure 56-2 in the “Provisioning circuit packs and managing traffic” chapter of this book.

—end—



Procedure 57-5Adding a shelf to an unprotected network

Follow this procedure to add a shelf to an unprotected network.

RequirementsIf you are adding shelves to a network with a hubbed-ring configuration, add the terminal shelf before the OADM shelf.

Precautions

Expected resultsWhen you complete this procedure, a new shelf is added to an unprotected network.

Action

Step Action

1 Install the shelf in the first site using the procedures in the “Installing and grounding racks, shelves, and equipment” chapter of Installing Shelves and Components, 323-1701-201.

2 Connect the OPTera Metro 5200 System Manager to the shelf through the 10Base-T 1X port.


4 Connect the OMXs of the new shelf to the network using the connection tables that correspond to the network type.

5 Reorder the shelf list to correctly position the new shelf in order.

Note: After you commission the new shelf, and test the shelves in the terminal and OADM sites, you can provision the shelves. Make sure you provision new shelves at the terminal site first.

—end—

CAUTIONTraffic lossWhen you add shelves to a network carrying traffic that does not have path protection, the network loses traffic.



Procedure 57-6Adding a shelf to a linear OADM network

Follow this procedure to add a shelf to a linear OADM network.

Precautions

Expected resultsWhen you complete this procedure a shelf is added to a linear OADM network.

Action

Step Action

1 Install the shelf using the procedures in the “Installing and grounding racks, shelves, and equipment” chapter of Installing Shelves and Components, 323-1701-201.

2 Connect the OPTera Metro 5200 System Manager to the shelf through the 10Base-T 1X port.


4 Connect the OMXs of the new shelf to the network using the connection tables that correspond to the network type.

5 Reorder the shelf list to correctly position the new shelf in order.

—end—

CAUTIONTraffic lossThe network loses traffic when you connect the new shelves in a linear OADM network.



Procedure 57-7Changing configuration information for a shelf

Follow this procedure to change the configuration information for a shelf. Any changes that you make must follow the name and IP address rules followed when the network was originally configured.

Note: The shelf reboots when you apply changes to the Shelf configuration window. Traffic is not affected.

RequirementsYou must be logged into the System Manager as an Admin level user to change configuration information for a shelf.

Action

Step Action



3 From the Edit menu in the System Manager, select Modify.

The Shelf Configuration window appears (see Figure 57-1 on page 57-12).

4 Select the Naming tab to change the way the System Manager displays shelf name information.

5 Select the Communication tab to

• change IP addressing information

• change the shelf type

• change the Ethernet hubbing group

• access the advanced settings by clicking Advanced...

• access the maintenance panel port control by clicking Port Control

Note 1: If the Port Control window indicates that all the ports on a shelf are disabled, you will not be able to use the System Manager to access the shelf locally. To enable the ports, access the shelf from another shelf in the network that has the same band.

Note 2: If all the ports on all the shelves in a network are disabled you must contact Nortel Networks Technical support to re-establish a network surveillance connection.

—continued—



Procedure 57-7 (continued)Changing configuration information for a shelf

Step Action

6 Select the Time tab to

• change the date and time on the shelf

• apply the date and time of the System Manager PC to the shelf

Figure 57-1Shelf configuration window communication panel

OM0227

—end—



Procedure 57-8Configuring shelf surveillance and external management

Follow this procedure to configure surveillance and external management for a shelf.

The Shelf Configuration—Surveillance window contains information about where an OPTera Metro 5200 shelf sends SNMP traps for surveillance purposes. Each shelf can send traps to a maximum of two external managers.

The SNMP external manager receives the SNMP trap messages that the OPTera Metro 5200 shelf generates. You can decode the traps using the management information base (MIB) after the external manager compiles it.

The MIB file for the OPTera Metro 5200 System Manager is a text file describing the SNMP agent that exists on an OPTera Metro 5200 shelf. You can order the MIB file from Nortel Networks (NT0H70FA). Use the external manager to compile the MIB file so the MIB file can decode the traps sent from an OPTera Metro 5200 shelf.

Action

Step Action


2 Select the Surveillance tab.

The External Manager window appears.

—continued—



Procedure 57-8 (continued)Configuring shelf surveillance and external management

Step Action

3 Right-click on one of the listed shelves, and select Modify from the menu that appears.

The External Manager Entry window appears.OM0288t

4 Enter the external Manager IP Address.

5 Enter the Trap port, if required.

Note: The default Trap port is 162. The Trap port must match the trap port set on the external manager.

6 Enter the Trap community, if required.

The default Trap community is public. The community string must match the community string set on the external manager or it will not receive the traps from OPTera Metro 5200 shelves.

7 From the Filter menu, select the items that will be reported to the external manager.

8 Click OK on the External Manager Entry window.

—end—



Procedure 57-9Removing a shelf surveillance and external management entry

Follow this procedure to remove a shelf surveillance and external management entry.

Action

Step Action


2 Select the Surveillance tab.

The External Manager window appears.

3 Right-click on one of the listed shelves and select Delete from the menu that appears.

A Confirm Delete dialog box appears.

4 Click Yes to delete the external management entry.

—end—



Procedure 57-10Switching traffic off a span in a path-protected network

Follow this procedure to switch traffic off a span in an OPTera Metro 5200 ring with minimal traffic disruption. You may need to use this procedure if you need to add a shelf at an existing site, add a new shelf and site to the ring, or add an optical component, such as an OSC, to a site.

Three scenarios are available in this procedure:

1 DWDM fiber spans between shelves

2 DWDM fiber spans within an OADM stack of shelves

3 DWDM fiber spans within an OADM stack of shelves at a site with C/L splitter/couplers

In scenario 1, all the east and west traffic of the span must be redirected away from the span. In scenario 2, disrupting the span will impact only bands on the OTS IN and OTS OUT side of the span. As shown in Figure 57-2 below, if you want to disrupt the fiber span between the Band 6 west OMX and the Band 8 west OMX, Bands 5 and 6 will not be affected. However, Band 8 west at this site and Bands 1 to 4 and Band 7 elsewhere on the ring will be affected. This scenario assumes that all bands are in use on the ring. In scenario 3, disrupting the span within an OMX stack will impact only bands within either the C band or L band, but not both. As shown in Figure 57-3 below, when you disrupt the fiber between the Band 2 west OMX and the Band 4 west OMX, only the Band 3 and Band 4 traffic will be affected. This scenario assumes that only Band 3 is in use on the ring.

RequirementsYou must have Admin level user privileges to carry out this procedure.

Expected resultsWhen you complete this procedure, you will have switched all traffic off the DWDM fiber span that you intend to disconnect. In some applications, this procedure must be used multiple times to complete an installation.

—continued—



Procedure 57-10 (continued)Switching traffic off a span in a path-protected network

ActionStep Action

1 A

Scenario 1

2 Moving east of the fiber span, at one OADM shelf for each band in the OPTera Metro 5200 ring, use the Manual Switch command to select traffic from the east path. This will be the path that does not use the span you plan to disrupt.

3 If the Manual Path Switch command is successful, use the Lockout Command to prevent the path selection from accidentally reverting to the original path.

Note: while in this Lockout state, protection switching due to path failures will be disabled.

4 Should the Manual Switch fail, determine the reason for the failure based on the active alarms at the shelf where the Manual Switch failed. Correct the fault before proceeding.

5 Repeat steps 2 to 4 once for each band in the OPTera Metro 5200 ring. Do not perform these steps for more than one OADM shelf in each band. Where Channel Mesh Shelves are provisioned, steps 2 to 4 must be performed once for each channel in each band.

6 Starting at the span where the disruption will occur, move west along the ring and repeat steps 2 to 4 to select all traffic from the West path.

Scenario 2

7 Moving East of the fiber span at this site. Use the Manual Switch command to select traffic from the East path for Band 8.


Note: While in this Lockout state, protection switching due to path failures will be disabled.

9 Continue moving east around the ring and at the first Band 1, 2,3,4, and 7 OADM shelves. Use the Manual Path Switch command to select the East traffic path. Then use the Lockout command to prevent reversion to the original path.

—continued—

If you are in Then go to

scenario 1 step 2 to step 6






Step Action

10 Starting at the site where the disruption will occur, move west around the ring and at the first Band 1, 2, 3, 4, and 7 OADM shelves. Use the Manual Path Switch command to select the West traffic path. Then use the Lockout command to prevent reversion to the original path.

11 Should the Manual Switch fail, determine the reason for the failure based on the active alarms at the shelf where the Manual Switch failed. Correct the fault before proceeding.

Scenario 3

12 Moving east of the fiber span at this site. Use the Manual Switch command to select traffic from the East path for Band 4.


Note: While in this Lockout state, protection switching due to path failures will be disabled.

14 Continue moving east around the ring and at the first Band 3 ADM shelf. Use the Manual Path Switch command to select the east traffic path. Then use the Lockout command to prevent reversion to the original path.

15 Starting at the site where the disruption will occur, move west around the ring and at the first Band 3 OADM shelf use the Manual Path Switch command to select the West traffic path. Then use the Lockout command to prevent reversion to the original path.

16 Should the Manual Switch request fail, resolve the problem and repeat the Manual Switch and Lockout before proceeding.

—continued—




Figure 57-2Switching traffic off of a DWDM fiber span within an OADM stack of shelves at a site

OM0665t

—continued—

Band 8East OMX

Band 5East OMX

Band 6East OMX

Band 8West OMX

Band 5West OMX

Band 6West OMX

West Path

East Path




Figure 57-3Switching traffic off a span within an OADM stack of shelves at a site with C/L splitter/couplers

OM0666p

—end—

East Path

C&LSplitter/Coupler

C&LSplitter/Coupler

West Path

Band 8East OMX

Band 5East OMX

Band 6East OMX

Band 8West OMX

Band 5West OMX

Band 6West OMX

Band 8East OMX

Band 5East OMX

Band 6East OMX

Band 8West OMX

Band 5West OMX

Band 6West OMX


58-1

Upgrading OPTera Metro 5200 software58-Refer to CAP OC 01-114 (NTY427AD) for software upgrade paths from releases 3.0 or 3.1 to 3.2. Refer to CAP OC 01-115 (NTY428AD) for the software upgrade path from release 2.1 to 4.0.

You must log in to the primary shelf of System Manager as an Admin level user to upgrade the software.

Note: Connections that existed before an upgrade to release 4.0 will not support UAS PMs. UAS PMs will be available for new connections only.

58-2 Upgrading OPTera Metro 5200 software



59-1

Appendix—System Manager windows and fields 59-In this chapter

• System Manager main window on page 59-1

• Fault window on page 59-7

• Equipment window on page 59-13

• Channel Assignments window on page 59-26

• Configuration window on page 59-31

• Admin—Software upgrade window on page 59-44

• Performance Monitor window on page 59-45

• Date and time notes on page 59-52

• Time stamp rules on page 59-53

System Manager main windowThis section describes how to use the different parts of the System Manager main window.

Network shelf selector iconsColored icons indicate the status of the shelves selected in the drop-down list. Table 59-1 lists icon colors and the shelf status that each represents. When multiple alarm types occur on a shelf, the color of the drop-down list icon represents the most severe alarm type.

Table 59-1Network shelf selector icons

Icon color Status

Green There are no alarms on the shelf.

Red There are critical alarms on the shelf.

Red There are major alarms on the shelf.

—continued—

59-2 Appendix—System Manager windows and fields


Commands and menu optionsTable 59-2 lists the System Manager commands and menu options.

Orange There are minor alarms on the shelf.

Yellow There are warnings on the shelf.

Blue The System Manager is out of contact with the shelf.

Table 59-2System manager command and menu options

Menu Menu option Description Value or range

File Save As This option saves the contents of the current information window to a file.

—

Print This option prints the contents of the current information window.

—

Exit This option exits and logs off the System Manager.

Yes or No

Edit Add This option adds an entry to the item at the selected location.

—

Modify This option enables modification to the selected item.

—

Delete This option removes an entry from the location of the selected item.

—

View Network Tree This option activates the network shelf selector.

—

Show Details This option opens a window with detailed information about the selected item.

—

Rediscover Network

This option reinitializes communications with the other shelves in the network.

—

Refresh Current Window

This option refreshes the currently selected main window.

—

—continued—

Table 59-1 (continued)Network shelf selector icons

Icon color Status

Appendix—System Manager windows and fields 59-3


View Sort Order This option changes the order in which network data is presented.

Column

Select an option, for example Shelf or Slot.

Sort

Select one of the following:

• None

• Ascending

• Descending

Fault Active Alarms This option opens a window that lists the active alarms.

—

Event Console This option displays the event log from the event log buffer of the System Manager.

—

Clear Event Console

This option clears the event log from the event log buffer of the System Manager.You can use Clear Event Console when you select Event Console.

—

Event History This option retrieves the logs stored in the shelves in the Event History window.

—

Config-uration

Shelf List This option lists the active shelves in the network. You can sort the shelves from this window.

—

Equipment This option enables the Equipment Inventory, Facility and Telemetry menu items.

Select one of the following:

• Inventory

• Facility

• Telemetry

Connections This option enables the Channel Assignments menu item.

—

Naming This option enables the Naming window. Use the Naming window to edit network, site and shelf name information.

—

Communications This option enables the Communications window. Use the Communications window to edit shelf addressing information.

—

—continued—

Table 59-2 (continued)System manager command and menu options




Config-uration

Time This option enables the Time window. Use the Time window to edit time information on the primary shelf and synchronize the shelves.

—

Surveillance This option enables the Surveillance window. Use the Surveillance window to configure or edit external manager information.

—

Network Date and Time

This option synchronizes the date and time on the shelf with the date and time on the System Manager computer or sets the date and time of the shelf manually.

—

Admin Software Upgrade This option enables the Software Upgrade window. Record data in the appropriate fields to perform an upgrade.

—

Decommission Shelf

This option deletes the commissioning information stored in the shelf.

—

Perform-ance

Performance Monitor

This option opens a window which you use to launch performance monitor information.

—

Security Password This option allows admin users to change a password.

User

Select a user level from the pull-down menu. The user levels include:

• Admin

• Operator

• Observer

Admin Password

Enter the Admin password. Password must be 8 to 10 characters with no control characters.

—continued—





Alarm banner colorsThe alarm banner has a top and a bottom row. The top row shows the alarm count for the whole network. The bottom row shows the alarm count for the shelves you selected with the network shelf selector.

Table 59-3 lists the different alarm colors and their indications.

Security Password This option allows admin users to change a password.

New Password

Enter the New password for the selected user level. Password must be 8 to 10 characters with no control characters.

Confirm Password

Confirm the new password. Password must be 8 to 10 characters with no control characters.

Help System Manager Help

This option displays the OPTera Metro 5200 technical documentation.

—

About System Manager

This option displays the name of the host shelf, the software version, the build date, the user name and user class.

—

Table 59-3Alarm banner colors

Color Indication

Red Critical alarm

Red Major alarm

Amber Minor alarm

Yellow Warning

Gray Acknowledged alarm counts and warnings

Note: If an alarm or warning is unacknowledged and clears automatically, its alarm banner color remains highlighted until you acknowledge the alarm or warning. This convention makes sure that the System Manager reports all alarm activity to you.

Blue The System Manager cannot poll a shelf for alarm status.





Accessing information windowsAccess the different information windows by clicking on the labelled tabs in the System Manager.

Windows in the System Manager belong to the following categories:

• Fault

• Equipment

• Connections

• Configuration

• Admin

• Performance Monitor

You can access more detailed information windows by clicking on the tabs displayed in each of these windows. Figure 59-1 shows the window hierarchy in the System Manager.

Figure 59-1Hierarchy of windows in the System Manager

OM0221p

Channel Assignments

AdminSoftware upgrade

Login User List

Surveillance

Shelf List

Naming

Time

CommunicationsConfiguration

Connections

Fault

Equipment Facilities

Inventory

Telemetry

Active alarms

Event console

Event history

PC

Systemmanager

Launch PMsPerformanceMonitor



Refreshing System Manager windowsThe System Manager automatically updates the Fault—Active Alarms window. To refresh all other windows select the View > Refresh Current Window option from the main menu, or select the Refresh button.

Fault windowUse the Fault window to

• display a list of system alarms and events

• review the current state of the selected shelves in the OPTera Metro 5200

• access the system history

The System Manager records alarm state changes, warning state changes, and user provisioning requests in the Fault window.

Double-click on any line in the Active Alarms window or the Event Console window to access the Alarm or Event Details window.

Fault—Active Alarms windowTable 59-4 describes the data fields in the Fault—Active Alarms window. System Manager defaults to automatically update the Fault—Active Alarms window. Deselect the Auto Refresh box at the top of the window to disable automatic updates. The Active Alarms window displays the number of alarms listed at the top of the window beside Entries.

Table 59-4Fault—Active Alarms window

Data field Description Value

Time This field indicates the time and date of the raised alarm in the time zone set in the System Manager computer.

The date and time, in the format 1999/12/05 20:18:23.

Shelf This field indicates the user-assigned name of the shelf.

A name, e.g., Head Office

Card This field indicates the type of circuit pack that the alarm is raised against.

• OCI (includes SRM OCI and SONET/SDH SRM OCI alarms)

• OCLD

• OTR

• OSC

• OFA

• OCM

• OMX

• SP

—continued—



Fault—Active Alarms—Alarm Details windowWhen you right-click and select Details on a highlighted line or double-click on a highlighted line in the Active Alarms window, the Alarm Details window appears. Table 59-5 describes the data fields.

Slot This field indicates the shelf or slot number of the circuit pack that the alarm is raised against.

• a number from 1 to 20

• OMX1e

• OMX1w

• OMX2e

• OMX2w

Port This field displays which port of the circuit pack the alarm is raised against.


Direction This field displays which direction of the port the alarm is raised against.

• Tx

• Rx

Severity This field indicates the severity of the alarm. • Critical

• Major

• Minor

• Warning

State This field indicates the state of the alarm. • Active

• Clear

• Intermittent

Service affecting (SA)

This field indicates whether the alarm is service affecting or non-service affecting.

• SA

• NSA

Description This field displays a description of the alarm or event.

Text string, such as Circuit Card Missing

Table 59-5Fault—Active Alarms—Alarm Details window


Location



—continued—

Table 59-4 (continued)Fault—Active Alarms window






• OMX1e

• OMX1w

• OMX2e

• OMX2w




• Tx

• Rx

Card Type This field indicates the type of circuit pack that the alarm is raised against.

• OCI (includes SRM OCI and SONET/SDH SRM OCI alarms)

• OCLD

• OTR

• OSC

• OFA

• OCM

• OMX

• SP

Alarm Details


The date and time, in the format 1999/12/05 20:18:23


• Major

• Minor

• Warning


• Clear

• Intermittent

Service affecting (SA)

This field indicates whether the alarm is service affecting or non-service affecting.

• SA

• NSA



Table 59-5 (continued)Fault—Active Alarms—Alarm Details window




Fault—Event Console windowThe Event Console window shows all the events in the network in the current System Manager session. The network shelf selector does not affect the Event Console window. The Event Console window shows all current events for all shelves in the network.

Table 59-6 describes the data fields in the Fault > Event Console window. To refresh this window, select the Refresh button.

Table 59-6Fault—Event Console window






Class This field indicates the class of the event. • Alarm

• Event

• Warning

• User Request



• OMX1e

• OMX1w

• OMX2e

• OMX2w

Alarm State This field indicates the state of the alarm. • Active

• Clear

• Intermittent

Alarm Severity This field indicates the severity of the alarm. • Critical

• Major

• Minor

• Warning





Fault—Event History windowThe Event History window shows history events from the shelves that you selected with the network shelf selector. The System Manager updates the Event History window when you select Retrieve event history.

Table 59-7 describes the data fields in the Fault—Event History window. To refresh this window, select the Refresh button.

Table 59-7Fault—Event History window







• Event

• Warning

• User Request



• OMX1e

• OMX1w

• OMX2e

• OMX2w




• Tx

• Rx

Alarm State This field indicates the state of the alarm. • Active

• Clear

• Intermittent


• Major

• Minor

• Warning





Fault—Event Console or Event History—Event Details windowWhen you right-click and select Details on a highlighted line or double-click on a highlighted line in the Event Console window or the Event History window, the Event Details window appears. Table 59-8 describes the data fields.

Table 59-8Fault—Event Console or Event History—Event Details window


Location





• OMX1e

• OMX1w

• OMX2e

• OMX2w


• A number from 1 to 4

Alarm Details




• Event

• Warning

• User Request


• Major

• Minor

• Warning


• Clear

• Intermittent


Text string, such as Circuit Card Missing.



Equipment windowUse the Equipment window to

• add or delete equipment and facility information to the network

• view and sort inventory and facility information by shelf, slot, and other attributes

• configure telemetry inputs and outputs

• view telemetry information

• configure OCM equipment protection

Double-click on any line in the Inventory or Facilities window to access the OPTera Metro 5200 Inventory window for the selected circuit pack. The OPTera Metro 5200 Inventory window provides detailed inventory and facilities information.

Equipment—Inventory windowTable 59-9 describes the data fields in the Equipment—Inventory window. To refresh this window select the Refresh button.

Table 59-9Equipment—Inventory window



A name, e.g., Head Office.

Slot This field indicates the slot number of a circuit pack.


• OMX1e

• OMX1w

• OMX2e

• OMX2w

—continued—



Prov This field indicates the type of circuit pack that you provisioned for a slot in the shelf.

• OCI

• SRM (either SRM OCI or SONET/SDH SRM OCI)

• OCLD

• OTR

• OSC

• OFA

• SP

• OCM

• OMX

• blank

Actual This field indicates the type of circuit pack inserted in the slot.

• OCI

• SRM (includes SRM OCI and SONET/SDH SRM OCI)

• OCLD

• OTR

• OSC

• OFA

• SP

• OCM

• OMX

• blank

Admin This field indicates the user-assigned administrative state of the circuit pack.

• IS

• OOS

Oper This field indicates the operational state of the circuit pack.

• IS-NR: In-service normal

• IS-ANR: In-service abnormal

• OOS-MA: Out-of-service maintenance

• OOS-AU: Out-of-service autonomous

• OOS-AUMA: Out-of-service autonomous, maintenance

• OOS-MAANR: Out-of-service maintenance abnormal

—continued—

Table 59-9 (continued)Equipment—Inventory window




Sec This field indicates the secondary state of the circuit pack.

• OS

• Unequipped

• Supporting-Entity-Failed

• Failed

• NIL

PEC This field indicates the product engineering code for the circuit pack.

e.g., NT0H01DD

Version This field indicates the hardware version of a circuit pack.

Character string, e.g., 7 or DA.

CLEI This field indicates the Common Language Equipment Identification.

Character string, e.g., LG8C20A.

Serial # This field indicates the serial number of the circuit pack in a slot.

Character string, e.g, SN123454.

Table 59-9 (continued)Equipment—Inventory window




Equipment—Facilities windowTable 59-10 describes the data fields in the Equipment > Facilities window. To refresh this window select the Refresh button.

Table 59-10Equipment—Facilities window






• OMX1e

• OMX1w

• OMX2e

• OMX2w

Port This field displays the port of the circuit pack that the alarm is raised against.


Name This field indicates the name of the facility. e.g., OCI Facility 5.

Card This field indicates the type of circuit pack installed in a slot.

• OCI

• OCLD

• OTR

• OSC

• OFA

• OCM

• OMX

• SP

Admin This field indicates the user-assigned administrative state of the circuit pack.

• IS

• OS

Oper This field indicates the operational state of the circuit pack.







—continued—



Sec This field indicates the secondary state of the circuit pack.

• IS

• OS

• Unequipped

• Supporting Entity Failed

• Failed

• Nil

Loop Back This field applies a facility or terminal loopback. The facility or terminal must be out-of-service to apply a loopback.

• None

• Facility

• Terminal

Channel Name This field indicates the name of the channel assignment.

• blank

• character string

Tx (dBm) (See Note:below.)

This field displays the output Tx power (dBm) from the OCLD, OCI and OFA circuit packs.

• blank or N/A

• decimal value, e.g., -3.5

Rx (dBm) (See Note:below.)

This field displays the input Rx power (dBm) to the OCLD/OCI and OFA circuit packs.

• blank or N/A

• decimal value, e.g., +3.5

Note: The System Manager does not automatically update the Equipment—Facilities window. Use the Refresh button to obtain accurate power level readings for the Tx (dBm) and Rx (dBm) data fields.

The System Manager obtains the values for the Tx (dBm) and Rx (dBm) data fields from the hardware on the circuit pack. If you independently measure the power meter levels on the hardware of the circuit pack, they may be different from the System Manager values.

The optical Transmit (Tx) and receive (Rx) power levels are not monitored for SRM circuit packs. As a result the Tx and Rx fields in the System Manager Facilities window remain blank.

Table 59-10 (continued)Equipment—Facilities window




Equipment—Inventory or Facilities—Details windowWhen you right-click and select Modify on a highlighted line or double-click on a highlighted line in the Inventory or Facilities window, the OPTera Metro 5200 Inventory window appears. Table 59-11 describes the data fields.

Table 59-11Equipment Inventory—OPTera Metro 5200 Inventory window


Location




• A number from 1 to 20.

• OMX1e

• OMX1w

• OMX2e

• OMX2w

Provisioning Data

Card Type This field indicates the type of circuit pack that you provisioned for a slot in the shelf.

• OCI


• OCLD

• OTR

• OSC

• OFA

• SP

• OCM

• OMX

• blank

Max Bit Rate This field indicates the maximum speed of the circuit pack.

• 2.5 GB - Transparent

• 1.25 GB - Transparent

• 622 Mbits - Transparent

Band This field indicates the band of the circuit pack.

A number from 1 to 8.

Channel This field indicates the number of the channel.

A number from 1 to 4 for circuit packs.

State

—continued—



Administrative This field indicates the user-assigned administrative state of the circuit pack.

• IS

• OOS

Operational This field indicates the operational state of the circuit pack.







Secondary This field indicates the secondary state of the circuit pack.

• IS

• OS

• Unequipped


• Failed

• NIL

Manufacturing Data

Card Type This field indicates the type of circuit pack installed in the slot.

• OCI


• OCLD

• OTR

• OSC

• OFA

• SP

• OCM

• OMX

• blank

Version This field indicates the hardware version of a circuit pack.

Character string, e.g., 7 or DA.

Serial # This field indicates the serial number of the circuit pack in a slot.

Character string, e.g, SN123454.

—continued—

Table 59-11 (continued)Equipment Inventory—OPTera Metro 5200 Inventory window




Equipment—Facilities—OPTera Metro 5200 Facility windowWhen you double-click on a highlighted line in the Facilities window, the OPTera Metro 5200 Facility window appears. Table 59-12 describes the data fields.

PEC This field indicates the Product Engineering Code for the circuit pack.

e.g., NT0H01DD

CLEI This field indicates the Common Language Equipment Identification.

Character string, e.g., LG8C20A.

Max Bit Rate This field indicates the maximum speed of the circuit pack.

• 10 Gbit/s

• 2.5 Gbit/s

• 1.25 Gbit/s

• 622 Mbit/s

Band This field indicates the band of the circuit pack.


Channel This field indicates the number of the channel.

• A number from 1 to 4 for circuit packs.

• A number from 1 to 4 for C-band on an OFA.

• A number from 5 to 8 for L-band on an OFA.

Wavelength This field indicates the type of wavelength. • 1310nm

• 850nm

Table 59-12Equipment—Facilities—OPTera Metro 5200 Facility window


Facilities Tab

Location



—continued—

Table 59-11 (continued)Equipment Inventory—OPTera Metro 5200 Inventory window






• OMX1e

• OMX1w

• OMX2e

• OMX2w

Port This field displays which port of the circuit pack is in-service.


Card This field indicates the type of circuit pack installed in the slot.

• OCI


• OCLD

• OTR

• OSC

• OFA

• SP

• OCM

• OMX

• blank

Facility

Name This field indicates the name of the facility.

e.g., OCI Facility 5

Channel This field indicates the name of the channel.

• Character string

• No channel assignments allowed (OFA)

Administrative This field indicates the user-assigned administrative state of the circuit pack.

• IS

• OOS

Operational This field indicates the operational state of the circuit pack.







—continued—

Table 59-12 (continued)Equipment—Facilities—OPTera Metro 5200 Facility window




Equipment—Telemetry windowTable 59-13 describes the data fields in the Equipment—Telemetry window. To refresh this window, select View > Refresh Current Window from the menu bar or click on the Refresh button.

Secondary This field indicates the secondary state of the circuit pack.

• IS

• OS

• Unequipped


• Failed

• NIL

PM mode

SONET This field indicates if SONET PM counts are enabled or disabled.

• Enabled

• Disabled

SDH This field indicates if SDH PM counts are enabled or disabled.

• Enabled

• Disabled

Loop Back

None This field indicates that there are no active loop backs.

• Enabled

• Disabled

Terminal This field indicates a terminal loop back. • Enabled

• Disabled

Facility This field indicates a facility loop back. • Enabled

• Disabled

Table 59-13Equipment—Telemetry window


Network This field indicates the name of the network.

Character string

Shelf This field indicates the name of the shelf. Character string

Type This field indicates the type of port. • In

• Out

—continued—

Table 59-12 (continued)Equipment—Facilities—OPTera Metro 5200 Facility window




Equipment—Telemetry—Parallel Telemetry Input windowWhen you double-click on the Input 1, Input 2, Input 3 or Input 4 data fields, the Parallel Telemetry Input window appears. Table 59-14 describes the data fields.

Id This field indicates the port number. A number from 1 to 4

Admin This field indicates the user-assigned administrative state of the port.

• OOS

• IS

State This field indicates the state of the port. • Inactive

• Released

Severity This field indicates the severity of the alarm.

• Critical

• Major

• Minor

• Warning

Description This field indicates the user-assigned text of the device

Character string, e.g., Input Device 1

Alarm Description This field displays the user-assigned text of the alarm.

Character string, e.g., Parallel Telemetry Scan Point 1

Table 59-14Equipment—Telemetry—Parallel Telemetry Input window


Input Port Status



Port This field indicates the port number. A number from 1 to 4

Service Status This field indicates the user-assigned state of the port.

• Out-of-service

• In-service

Alarm Status This field indicates the state of the alarm. • Active

• Inactive

Configuration Information

—continued—

Table 59-13 (continued)Equipment—Telemetry window




Equipment—Telemetry—Parallel Telemetry Output windowWhen you double-click on the Output 1, Output 2, Output 3, or Output 4 data fields, the Parallel Telemetry Output window appears. Table 59-15 describes the data fields.

Description This field displays the user-assigned text of the input device.

Text string, e.g., Input Device 1


• Major

• Minor

• Warning

Alarm Text This field displays the user-assigned text of the alarm.

Text string, e.g., Parallel Telemetry Scan Point 1

Service This field indicates the user-assigned state of the input device.

• In-service

• Out-of-service

Table 59-15Equipment—Telemetry—Parallel Telemetry Output window


Output Port Status



Port This field indicates the port number. A number from 1 to 4

Service Status This field indicates the user-assigned state of the output device.

• In-service

• Out-of-service

Control Status This field indicates the current status of the port.

• Released

• Operated

Configuration Information

Description This field displays the user-assigned text of the output device.

Text string, e.g., Output Device 1

Hardware Config

This field indicates if you can configure the output device.

• Normally Open

• Normally Closed

—continued—

Table 59-14 (continued)Equipment—Telemetry—Parallel Telemetry Input window




Service State This field indicates the status of the output device.

• In-service

• Out-of-service

Control

Set State This field indicates the status of the port. • Released

• Operated

Table 59-15 (continued)Equipment—Telemetry—Parallel Telemetry Output window




Channel Assignments windowUse the Channel Assignments window to provision and view channel assignments. Each line of information in the window has a status description, which indicates the state of the channel assignment. You can also use the Channel Assignments window to configure path protection.

Select the Connections tab to automatically display the Channel Assignments tab and the Channel Assignments window.

Table 59-16 describes the data fields in the Channel Assignments window. Select the Refresh button to refresh this window.

Table 59-16Channel Assignments window




Channel This field indicates the name of the assigned channel.

Character string

Channel ID This field indicates the band, channel and direction of the OCM circuit pack.

Character string, e.g., B3C4W

OCLD Name This field displays the OCLD facility name. For example, OCLD Facility 1

End Point This field indicates the name of the OCI facility name.

For example, OCI Facility 5

Mode This field displays the channel assignment type.

• Unprotected

• Active

• Protected

• Passthrough

Lockout This field applies a lockout to a protected channel assignment. The System Manager blocks all protection switches if you apply a lockout.

• Yes

• No

• blank

—continued—



Channel Assignments—OPTera Metro Channel Assignments windowWhen you right-click and select Modify on a highlighted line or double-click on a highlighted line in the Channel Assignments window, the OPTera Metro Channel Assignments window appears. Table 59-17 describes the data fields.

Force This field applies a forced protection switch from one facility to another. Force only applies to protected channel assignments.

• Active

• Inactive

• No

• blank

Revertive This field applies a revertive or non-revertive protection switch to a protected channel assignment. Configure the WTR period and the primary path for a revertive protection switch.

• Active

• Inactive

• No (for non-revertive)

• blank

Status This field indicates the status of the channel assignment.

• IS

• OOS

Table 59-17Channel Assignments—OPTera Metro Channel Assignments window


Channel Assignment tab

Selected Facility

Facility Name This field displays the facility name. e.g. OCLD Facility 1

Channel ID This field indicates the band, channel and direction.

Character string, for example, B3C4w

Channel Characteristics

Mode This field displays the channel assignment type.

• Unprotected

• Protected

• Passthrough

West path This field indicates which circuit pack and facility are on the west path.

e.g. OCLD Facility 2, orOTR Facility 2, port 2 line

—continued—

Table 59-16 (continued)Channel Assignments window




PM Mode This field indicates the PM Mode of the west path. The drop-list is context sensitive to the path protocol and facility. If PM Mode is not applicable to the west path, the field is grayed out.

• None

• SONET

• SDH

East path This field indicates which circuit pack and facility are on the east path, for a protected signal.

e.g. OCLD Facility 17

PM Mode This field indicates the PM Mode of the east path. The drop-list is context sensitive to the path protocol and facility. If PM Mode is not applicable to the east path, the field is grayed out.

• None

• SONET

• SDH

End point This field indicates the originating circuit pack and facility for the signal.

e.g. OCI Facility 8, orOTR Facility 2, port 1 client

PM Mode This field indicates the PM Mode of the end point. The drop-list is context sensitive to the path protocol and facility. If PM Mode is not applicable to the end point, the field is grayed out.

• None

• SONET

• SDH

Protocol This field indicates the protocol being used. The drop-list is context sensitive to the provisioned circuit pack.

—

CA Name This field indicates the user defined channel assignment name.

e.g. unprot OTR

CA Description This field indicates the user defined channel assignment description.

Character string

PA Name This field indicates the user-assigned name of the port of the SRM OCI associated with the facility. It only displays if an SRM facility is added, modified or selected.

Character string, for example, port 1

PA Description This field indicates the user-assigned description of the port. It only displays if an SRM facility is added, modified or selected.

Character string

Rx traffic path for band/channel/direction - shelf name

end point This field displays the originating facility for the signal.

—

—continued—

Table 59-17 (continued)Channel Assignments—OPTera Metro Channel Assignments window




west path This field displays the west path facility for the signal on the shelf.

—

east path This field displays the east path facility for the signal on the shelf. This field only displays if the signal is protected.

—

Protection tab (This tab only appears when the Mode field is protected.)

Status

End Point This field displays the originating facility for the protected signal.

—

Channel Name This field displays the name of the assigned channel.

—

Current Rx Selection

This field indicates the facility that is receiving traffic for the protected path in a channel assignment.

e.g. OCLD Facility 2

Rx Reversion

Enabled This field indicates whether reversion is enabled or disabled.

• selected

• not selected

WTR This field indicates the waiting period selected for wait to restore.

• anywhere from 5 to 12 minutes (options in one minute intervals)

Working path This field indicates which path of the protected facility is the working path.

• east path

• west path

Rx Switch Request

Current state This field displays the current state of the protected facility.

Proctection switch options

A series of radio buttons for the protection switching options available.

• Release

• Manual

• Forced

• Lockout

To This field indicates which path the switch is applied to.

• east path

• west path

Table 59-17 (continued)Channel Assignments—OPTera Metro Channel Assignments window




Channel Assignments—OPTera Metro Timing windowWhen you right-click and select Timing Ref. on a highlighted line for a SONET/SDH SRM OCI circuit pack in the Channel Assignments window, the OPTera Metro Timing window appears. Table 59-18 describes the data fields.

Table 59-18Channel Assignments—OPTera Metro Timing window


Status

Port This field displays the port number. Number between 1 and 4.

Provisioned This field indicates whether the port is provisioned as the primary or secondary clock reference timer.

• Primary

• Secondary

Status This field indicates the status of the clock reference timer.

• Good

• Failed

• Wait-to-restore

Clock Signal This field indicates the status of the signals on the two ports that are provisioned as clock reference timers.

• Active

• Standby

• Failed

Switch Request

None/Manual These radio buttons indicate if a switch is requested or in effect.

• None – there is no switch requested or in effect

• Manual – there is a switch requested

To This field allows you to select the port/clock reference timer that you would like to switch to.

The only port numbers that appear in the menu are ports that are already provisioned as clock reference timers. You can not switch to a port that is not provisioned as a clock reference timer.

Provisioning

Port This column lists the four ports of the SONET/SDH SRM OCI.

Number between 1 and 4.

Provisioned This column lists whether a port is selected to be the primary or secondary clock reference timer.

• Primary

• Secondary

• None

Note: You can only provision one port to be the primary clock and one port to be the secondary port.



Configuration windowUse the Configuration window to edit commissioning data for OPTera Metro 5200 shelves. You can view shelf names, communications, time, and a shelf list from the Configuration window.

Double-click on any line in the Naming window, Communications window, or the Time window to access the Shelf Configuration window. The Shelf Configuration window displays detailed name, communications and time information about the item you selected.

Configuration—Shelf List windowTable 59-19 describes the data fields in the Configuration—Shelf List window. Select the Refresh button to refresh this window.

Table 59-19Configuration—Shelf List window


Site Name This field indicates the name of the site. Character string.

Shelf Name This field indicates the user-assigned name of the shelf.

Character string.

Site ID This field groups shelves together in the System Manager.

A number from 1 to 64. Assign shelves at the seamed site to site number 1. Assign the other sites in the ring to the next available number.

Shelf ID This field indicates the user-assigned unique ID of the shelf.

Assign one number to one shelf only

A number from 1 to 64.Use shelf ID 1 to 8 for shelves at the seamed site. Use Shelf ID 9 to 64 for other shelves.

Shelf IP This field indicates the shelf IP address. IP address, e.g., 172.16.283.57



Configuration—Naming windowTable 59-20 describes the data fields in the Configuration—Naming window. Select the Refresh button to refresh this window.

Table 59-20Configuration—Naming window



Nortel Networks recommends that all shelves in a ring have the same network name.

A character string that can be any combination of letters and numbers, up to 32 characters.

Site Name This field indicates the user-assigned name of the site

Nortel Networks recommends that all shelves at a site have the same site name.


Site ID This field groups shelves together in the System Manager.


Assign shelves at the seamed site to site number 1. Assign the other sites in the ring to the next available number.


Nortel Networks recommends that each shelf in a ring have a different descriptive shelf name, such as Surveillance Site Band 3.


Note: Do not use brackets in the shelf name.

Shelf ID This field indicates the user-assigned unique ID of the shelf.


Use shelf ID 1 to 8 for shelves at the seamed site. Use Shelf ID 9 to 64 for other shelves.

Description This field displays a description of the shelf

Nortel Networks recommends that each shelf in a ring have a different shelf description.


Role This field displays the role of the selected shelf.

• PGH (primary gateway host)

• H (the System Manager host shelf that you are connected to)



Configuration—Communications windowTable 59-21 describes the data fields in the Configuration—Communications window. Select the Refresh button to refresh this window.

Table 59-21Configuration—Communications window


Site Name This field indicates the user-assigned name of the site.






Shelf IP This field indicates the IP address of the shelf. Each shelf in a network must have a unique IP address.

IP address mask, e.g., 172.16.283.57

Primary IP This field indicates the address of the primary node shelf in the network. The primary shelf distributes network-level information across all the shelves in a network.

IP address, e.g., 172.16.283.56

Subnet Mask This field indicates the network mask of the shelf. The shelf mask segments the shelf from other shelves in the network.


Shelf Type This field indicates the type of shelf. OADM, OFA, or terminal

DHCP This field indicates the DHCP address of the shelf.

IP address

Default Gateway

The default gateway address is an IP address that activates the Proxy Address Resolution Protocol (ARP) server when the open shortest path first (OSPF) backbone is not enabled.

IP address



Configuration—Time windowTable 59-22 describes the data fields in the Configuration—Time window. Select the Refresh button to refresh this window.

Configuration—Naming, Communications or Time— Shelf Configuration window

When you right-click and select Modify on a highlighted line or double-click on a highlighted line in the Configuration—Naming, Communications, or Time window, the Shelf Configuration window appears. Table 59-23 lists the data fields and their descriptions.

Table 59-22Configuration—Time window



Character string, e.g., Office 1.


Character string, e.g., Floor 1.


Character string.

Time This field indicates the time and date of the time zone set in the System Manager computer.

The date and time, in the format 1999/12/05 20:18:23.

Table 59-23Configuration—Naming, Communications, or Time—Shelf Configuration window


Naming tab

Network Name This field indicates the name of the network.

Nortel Networks recommends that all shelves in a ring have the same network name.





—continued—






Shelf Description

This field displays a description of the shelf.

Nortel Networks recommends that each shelf in a ring have a different shelf description.


Site Identifier This field groups shelves together in the System Manager.


Assign shelves at the seamed site to site number 1. Assign the other sites in the ring to the next available number.

Shelf Identifier This field indicates the user-assigned unique ID of the shelf.

Assign one number to one shelf only.


Use shelf ID 1 to 8 for shelves at the seamed site. Use Shelf ID 9 to 64 for other shelves.

Communication tab

Shelf Address This field indicates the IP address of the shelf. Each shelf in a network must have a unique IP address.


Primary Shelf Address

This field indicates the address of the primary node shelf in the network. The primary shelf distributes network-level information across all the shelves in a network.

You use the primary node to add and remove other shelves in the OPTera Metro 5200 network. Assign all shelves in the network the same primary node address.

IP address, e.g., 172.16.283.56

Subnet Mask This field indicates the network mask of the shelf. The net mask segments the shelf from other shelves in the network.


—continued—

Table 59-23 (continued)Configuration—Naming, Communications, or Time—Shelf Configuration window




DHCP Address This field indicates the DHCP address for Ethernet Port 1. The DHCP address is an IP address that allows you to connect a PC to the 10Base-T 1X port on the maintenance panel of the shelf.


Default: 0.0.0.0.

Default Gateway Address

This field indicates the default gateway address. The IP address of the GNE shelf must be on the same LAN segment as the router that connects the OPTera Metro 5200 network to the DCN.

The default gateway address activates Proxy ARP server when open shortest path first (OSPF) backbone is not enabled.

IP address, e.g., 172.16.283.56

Default: 0.0.0.0.

Shelf Type This field indicates the type of the shelf. • OADM

• OFA

• Terminal

Ethernet Hubbing Group

This field identifies which shelves connect to the same Ethernet hub.

A number from 1 to 16. Ethernet Hubbing Group number should correspond to the Site ID.

Advanced ... This field enables you to configure the Advanced Communications Settings, such as you can set OSPF routing control information.

Button. See “Advanced Communication settings” below, in this table.

Port control This field allows you to enable or disable the ports on the maintenance panel.

If you disable all the ports on a shelf you cannot use the System Manager to access the shelf locally. You must access the shelf from another shelf in the network with the same band to enable the ports.

If you disable all the ports on all the shelves in a network you must contact Nortel Networks Technical Support to reestablish a network surveillance connection.

Button. See “Port enabling/disabling” below, in this table.

—continued—





Advanced Communications settings

Internal OSPF Setting

This field defines the OSPF area used for internal OPTera Metro 5200 communication.

If you use 0.0.0.0, the OPTera Metro 5200 network uses the Area ID for the primary node address.

You must assign all shelves in the network the same Area ID.

Gateway Routing Protocol

This field allows you to select whether you want to use any gateway routing protocol or not, and if yes, which gateway routing protocol to use.

If you select None, no gateway routing protocol will be used.

Select OSPF if you want to use it as your gateway routing protocol.

Select BGP if you want to use it as your gateway routing protocol.

Drop-down list.

Set This field allows you to change the default values for the protocol that you selected from the Gateway Routing Protocol drop-down list. Clicking the button brings up the OSPF or BGP settings window.

Button. See “OSPF settings” and “BGP settings” below, in this table.

NAT Setting This field allows you to enable or disable the Inbound NAT feature and to set the Inbound NAT alias if Inbound NAT is in use.

Check box for Inbound NAT Enabled.

For Inbound NAT Alias, any number from 1 to 126.

See “NAT settings” below, in this table.

Assignable IP Setting

This field allows you to assign the IP addresses for Ethernet port 2 and serial ports 1 and 2.

Set Port IPs... Clicking the button opens the Assignable IP Settings window.

Button. See “Assignable IP settings” below, in this table.

—continued—





OSPF settings

External Area ID This field defines the OSPF area used for the customer DCN router interface. In this release, only OSPF backbone routers can be connected to the OPTera Metro 5200 GNEs.

This field is currently grayed out for future use.

Default: 0.0.0.0

Cost This field indicates the cost of sending a data packet on the interface.

A number from 0 to 200. The default is 10.

Password Enabled

This field indicates if there is a password assigned to the OSPF backbone. The password is for “simple password authentication”.

Check box.

If there is more than one GNE shelf in the network, you must choose Enabled in all GNE shelves.

Password This field allows the authentication procedure to generate (or check) the incoming and outgoing OSPF packets.

Character string up to eight characters.

If there is more than one GNE shelf in the network, you must assign the same password to all the GNE shelves.

Transmit Delay This field indicates the number of seconds to transmit a link state update packet over the 10Base-T 1X port.


Default: 1 second.

Retransmit Interval

This field indicates the number of seconds between link state advertisement retransmission.


Default: 5 seconds.

Hello Interval This field indicates the number of seconds between Hello packets that the router sends on the interface.


Default: 10 seconds.

Router Dead Interval

This field indicates the number of seconds before the router’s neighbors determine that it is out-of-service (when they stop receiving the Hello packet from the router).



—continued—





BGP settings

BGP Local AS Number

This field indicates the autonomous system (AS) number assigned to the OPTera Metro 5200 network element.


Default: 0.

Peer 1 IP Address

This field indicates the IP address of the peering router. The IP address has to be in the same subnet as the shelf IP address (Ethernet Port 1).

IP address.

Default: 0.0.0.0

Peer 1 AS Number

This field indicates the AS number assigned to the AS where the customer router locates.


Default: 0.

Peer 2 IP Address

This field indicates the IP address of the peering router. The IP address has to be in the same subnet as the shelf IP address (Ethernet Port 1).

IP address.

Default: 0.0.0.0

Peer 2 AS Number

This field indicates the AS number assigned to the AS where the customer router locates.


Default: 0.

Retry Interval This field indicates the retry interval for establishing a peer-to-peer session.


Default: 120.

Holddown Time This field indicates the amount of time that a peer will wait for either a keep-alive or update message before declaring the connection is down.



AS Weight This field indicates the AS weight assigned to an AS in a path. AS weights provide a way either to prefer or to avoid routes that pass through certain AS(s). The path with the smallest total weight is the preferred path.


Default: 10.

—continued—





NAT settings

Inbound NAT Enabled

This field indicates if the Inbound NAT feature is enabled.

The Inbound NAT feature is only applicable to GNEs in the OPTera Metro 5200 ring.

Check box.

Default: disabled.

Inbound NAT Alias

This field indicates the alias address provided by the user for Inbound NAT.

One OPTera Metro 5200 network supports only one Inbound NAT alias.

Any number from 1 to 126.

Default: 47.

Assignable IP settings

Enet Port 2 IP IP address for 10BaseT 2X IP address. Default: 10.2.hubbinggroup.shelfID.

Enet Port 2 Mask

Broadcast address IP address. Default: 10.2.hubbinggroup.255.

Enet Port 2 DHCP

DHCP address for 10BaseT 2X IP address. Default: 10.2.hubbinggroup.(shelfID + 128).

Serial Port1 Local IP

DTE local IP address. Default: 10.3.shelfID.1.

Serial Port1 Remote IP

DTE remote IP address. Default: 10.3.shelfID.2.

Serial Port2 Local IP

DCE local IP address. Default: 10.4.shelfID.1.

Serial Port2 Remote IP

DCE remote IP address. Default: 10.4.shelfID.2.

Port enabling/disabling

Ethernet Port 1 – 10BASE-T 1X

This field enables communications using the 10Base-T 1X port.

Use this field to prevent access to the shelf by way of a connection to the customer’s LAN.

• Enabled

• Disabled

—continued—





Ethernet Port 2 – 10BASE-T 2X

This field enables communications using the 10Base-T 2X port.

Use this field to prevent access to the shelf by way of a PC or laptop connected to the 10Base-T 2X port.

You impact network surveillance if Ethernet port 2 is disabled on a shelf at a site where shelves connect to an Ethernet hub by way of the 10Base-T 2X port. The System Manager can monitor only shelves with the same band as that of the host shelf (if the shelf is the same band as the shelf with the 10Base-T 2X port disabled) or all of the other bands in the network (if the shelf is a different band than the shelf with the 10Base-T 2X port disabled).

• Enabled

• Disabled

Serial Port 1 – RS232/V24 1 (DTE)

This field disables communications using the RS232/V24 1 (DTE) port.

Use this field to prevent access to the shelf by way of a dial-up modem.

• Enabled

• Disabled

Serial Port 2 – RS232/V24 2 (DCE)

This field disables communications using the RS232/V24 2 (DCE) port.

Use this field to prevent access to the shelf by way of a communication port on a PC or laptop.

• Enabled

• Disabled

Time tab

Date

Year This field indicates the year. 0000 to 9999

Month This field indicates the month. 01 to 12

Day This field indicates the day. 01 to 31

Time

Hour This field indicates the hour. 01 to 23

Minute This field indicates the minute. 01 to 59

Second This field indicates the second. 01 to 59

—continued—





Configuration—surveillance tabTable 59-24 describes the data fields in the Configuration—surveillance tab.

External Manager Entry

Location



SNMP Trap Forwarding

Manager IP Address

This field indicates the IP address of the external management application.

A valid IP address.

Trap port This field determines which port the traps are sent to at the IP address of the external manager.

e.g., 162

Trap community This field allows you to configure the community name in traps sent to the external manager.

e.g., public

Filter This field determines what traps are sent to the external manager.

• All (alarms/events/user requests)

• Alarms only

• Alarms/events Only

Table 59-24Configuration—surveillance tab


External Manager



IP Address This field indicates the IP address of the external management application.

A valid IP address.

Port This field determines which port the traps are sent to at the IP address of the external manager.

e.g., 162

Community This field allows you to configure the community name in traps sent to the external manager.

e.g., public

—continued—





Configuration—surveillance tab—external manager entryWhen you double-click on an entry or a line in the surveillance tab of the Configuration window, the External Manager Entry dialog appears. Table 59-25 describes the data fields.

You can add an address for Simple Network Management Protocol (SNMP) trap forwarding using the External Manager entry window.



• Alarms only


Audible Alarm

Two radio buttons that indicate whether the audible alarm is enabled or disabled.

• Enabled

• Disabled

Actions

Button with an alarm icon that represents the state of the alarm cut-off.

• Crossed out, if Alarm cut off disabled

• Not crossed out, if Alarm cut off enabled.

Alarm cut off This field allows you to enable or disable the Alarm cut off.

• Selected

• Not selected

Lamp test Button for activating a lamp test. • Selected

• Not selected

Table 59-25Configuration—Surveillance—External Manager Entry window


Location



SNMP Trap Forwarding

Manager IP Address

This field indicates the IP address of the external management application.

A valid IP address.

—continued—

Table 59-24 (continued)Configuration—surveillance tab




Admin—Software upgrade windowTable 59-26 describes the data fields in the Admin—Software Upgrade window. To refresh this window, select the Refresh button.

Trap Port This field determines which port the traps are sent to at the IP address of the external manager.

e.g., 162

Trap Community

This field allows you to configure the community name in traps sent to the external manager.

e.g., public



• Alarms only


Table 59-26Admin—Software Upgrade window


Site name This field indicates the name of the site where the shelf you are upgrading is located.

Character string.

Shelf name This field indicates the name of the shelf whose software you need to upgrade. Select a shelf name by clicking up and down arrows.

Character string.

Shelf ID This field indicates the unique user-assigned ID of the shelf.

Assign one number to one shelf only.

A number from 1 to 64.Use shelf ID 1 to 8 for shelves at the seamed site. Use Shelf ID 9 to 64 for other shelves.

Version This field indicates the current version of OPTera Metro 5200 software.

• Release n.n

• Unknown

State This field indicates the current state of the OPTera Metro 5200 software.

• Uncommitted

• Committed

• Unknown

• Retrieving

Table 59-25 (continued)Configuration—Surveillance—External Manager Entry window




Admin—Login User List windowTable 59-26 describes the data fields in the Admin—Login User List window. To refresh this window, select the Refresh button.

Performance Monitor windowUse the performance monitor window to view, set, or modify performance parameter values and enable or disable TCA reporting.

Performance Monitor—Launch PM windowTable 59-28 on page 59-46 describes the data fields in the Performance Monitor—Launch PM window. Select the Performance Monitor tab to view this window.

Table 59-27Admin—Login User List window


Shelf Name This field indicates the name of the host shelf where the user logged in to System Manager.

Character string.

Shelf IP This field indicates the IP address of the host shelf.

A valid IP address.

Machine IP This field indicates the user IP address where SNMP information is sent.

A valid IP address.

Group.UserID This field indicates the user group and user ID for the session.

e.g. Admin.TedSmith

Trap Port This field indicates which communications port at the user shelf is receiving information.

e.g. 1196

Trap Type This field indicates the type of System Manager session.

• SMI session

• PMOM

• TL1



Table 59-29 describes the command and menu options for the Performance Monitor window.

Table 59-28Performance Monitor—Launch PM window


Launch This field launches the Performance Monitor portion of System Manager.

• Selected

• Not selected

Auto Launch This field automatically launches the Performance Monitor portion of System Manager each time the Performance Monitor tab is selected for the remainder of the System Manager session.

• Selected

• Not selected

Table 59-29Performance monitor command and menu options


File Save As This option saves the contents of the query results display.

—

Print This option prints the contents of the query results display.

—

Exit This option exits the performance monitor portion of System Manager.

Yes or No

Edit Shelf Level Parameters

This option displays the Shelf Level PM portion of the screen. Select to perform shelf level operations.

—

View Details/Modify Attributes

This option opens the Details for Shelf portion of the screen. Select to view historical counts, or to modify threshold or current count attributes.

—

Remove from List This option removes the selected rows from the display.

—

Refresh Selected Row

This option refreshes the currently selected row.

—

Refresh All Rows This option refreshes all rows for the selected performance parameters.

—

—continued—



Table 59-30 describes the data fields in the Performance Monitor window.

Query New This option clears the query results portion of the screen for a new query.

—

Refresh Shelf List This option updates the current shelf list. —

Retrieve This option retrieves the PM data for the parameters and location specified in the query panel.

—

Table 59-30Performance Monitor window


Location

NE This field indicates the name of the shelf for which you want to view PMs. Click the arrow to display the list of shelves available in the same ring.

Alphanumeric string.

Direction This field indicates the direction of the circuit pack for which you want to display PMs.

• Rx

• Tx

Slot This field indicates the slot number of the circuit pack for which you want to view PMs. Click the arrow to choose from the list of possible slot numbers.

An integer value from 1 to 20.

Port This field indicates the port for which you want to view PMs. Click the arrow to choose from the list of possible ports.

• 1 optical

• 2 optical

• 3 optical

• 4 optical

• 1 backplane

Performance Parameters

Select All Use this field to select all performance parameters displayed in the Performance Parameter display window.

• Selected

• Unselected

—continued—

Table 59-29 (continued)Performance monitor command and menu options




Unselect All Use this field to unselect all previously selected performance parameters in the display.

• Selected

• Unselected

Performance Parameter display

This field displays all performance parameters associated with the selected shelf, slot, port and direction. You can select each parameter individually.

Character strings representing applicable performance parameters, each with a selection box.

Output Options

Create New List Select this option to display the specified PM data on a fresh list.

• Selected

• Unselected

Append to Current List

Select this option to append the specified PM data to an existing list.

• Selected

• Unselected

Retrieve button This button retrieves the PM data for the parameters and location specified in the query panel.

—

Equipment PM

Shelf This field indicates the name of the selected shelf.


Slot This field indicates the slot number of the circuit pack for the particular row.


Port This field indicates the port of the circuit pack that is associated with the performance parameter for the row.

• 1 optical

• 2 optical

• 3 optical

• 4 optical

• 1 backplane

Direction This field indicates the direction associated with the performance parameter for the row.

• Rx

• Tx

Parameter This field indicates the equipment performance parameter reported on for a particular row.

• RxPowerHigh

• RxPowerLow

• TxPowerHigh

• TxPowerLow

—continued—

Table 59-30 (continued)Performance Monitor window




Current Reading

This field indicates the current value of the performance parameter for the row.

An integer value.

Degrade Threshold

This field displays the current value of the performance parameter only if it falls within the degrade range. Otherwise, this field displays a not available message.

An integer value, or not available.

Degrade TCA This field indicates the specific alarm or warning raised when the degrade TCA is crossed.

High optical power warning, or low optical power warning.

Fail Threshold This field displays the current value of the performance parameter only if it falls within the fail range. Otherwise, this field displays a not available message.

An integer value, or not available.

Fail TCA This field indicates the specific alarm or warning raised when the fail TCA is crossed.

High optical power, or loss of signal.

Facility PM

Shelf This field indicates the name of the selected shelf.


Slot This field indicates the slot number of the circuit pack for the particular row.


Port This field indicates the port of the circuit pack that is associated with the performance parameter for the row.

• 1 optical

• 2 optical

• 3 optical

• 4 optical

• 1 backplane

Direction This field indicates the direction associated with the performance parameter for the row.

• Rx

• Tx

Parameter This field indicates the facility performance parameter reported on for a particular row.

Character strings representing applicable facility performance parameters. See the “Facility PMs” section in Performance Monitoring, 323-1701-520.

—continued—





Interval This field indicates the time interval of the PM count for a particular row.

• 15 Min

• 1 Day

• Untimed

Current Count This field indicates the current count of the performance parameter for the selected row.

An integer value.

IDF This field displays a period (.) to indicate that the current count for a particular row is valid, or it displays a question mark (?) to indicate that the validity of the count is questionable.

• .

• ?

Threshold This field indicates the threshold value that, once crossed, raises an warning or alarm. If the interval is untimed, a not applicable message is displayed.

An integer value or not applicable.

Time Stamp This field indicates the time and date of the count for a particular row.

e.g. 06:15:00 2001/05/18

Shelf level PM

Reset all counts This field, if selected, resets all current and historical facility counts on the shelf to zero.

• Selected

• Unselected

Set all 15 Min thresholds to default

This field, if selected, sets all 15 Min thresholds on the shelf to the factory default values.

• Selected

• Unselected

Set all 1 Day thresholds to default

This field, if selected, sets all 1 Day thresholds on the shelf to the factory default values.

• Selected

• Unselected

TCA for all 15 Min counts

Select the appropriate field to enable, disable or retain the current TCA settings for all 15 Min counts on the shelf.

• Keep current settings

• Enable

• Disable

TCA for all 1 Day counts

Select the appropriate field to enable, disable or retain the current TCA settings for all 1 Day counts on the shelf.

• Keep current settings

• Enable

• Disable

—continued—





Details for shelf

Current Count tab

Reset all counts This field, if selected, resets the current and historical counts for the performance parameter to zero.

• Selected

• Unselected

Reset current count

This field, if selected, resets the current count of the performance parameter to zero.

• Selected

• Unselected

Cancel button This button exits the bottom Details for Shelf portion of the screen.

• Selected

• Unselected

Apply button This button applies selections made in the Current Count portion of the screen.

• Selected

• Unselected

Historical Counts tab

Time Stamp This field displays the time and date of the count for a particular interval.

e.g. 06:15:00 2001/05/18

IDF This field displays a period (.) to indicate that the count is valid, or it displays a question mark (?) to indicate that the validity of the count is questionable.

• .

• ?

Count This field indicates the count of the performance parameter for the interval.

An integer value.


• Selected

• Unselected

Threshold tab

Current Threshold

This field displays the current threshold value for the selected performance parameter.

An integer value.

Set to default threshold

This field, if selected, sets the threshold value for the selected performance parameter to the factory default.

• Selected

• Unselected

TCA enabled for current

This field, if selected, raises the appropriate TCA alarm when the value displayed in the Current Threshold field is crossed.

• Selected

• Unselected

—continued—





Date and time notesBecause the System Manager was developed using the C programming language, the available date range is 1970 and 2038.

The program stores the date and time for the System Manager as a 32-bit number offset in seconds from midnight, January 1, 1970. The field will run out of space on January 19, 2038 at 3:14:07 AM GMT. When the next second ticks by, the number field will overflow.

For OPTera Metro 5200, when the date and time passes January 19, 2038 3:14:07 AM GMT, the OPTera Metro 5200 System Manager will display the year 1901. No error message is displayed.

If you enter a date and time after January 19, 2038 at 3:17 PM in the OPTera Metro 5200 System Manager, the System Manager will not accept the date. No error message is displayed.

TCA A display field that shows the selected performance parameter and interval.

A character string.

TCA port/direction operations

1st drop list Select an option to enable or disable all TCA reporting on all facility performance parameters associated with a specified interval, port or direction.

• Enable TCA for all counts

• Disable TCA for all counts

• Unselected

2nd drop list Select an option to define the interval for which you intend enable or disable TCA reporting. You must make a selection from the 1st drop-list to enable the 2nd drop-list.

• For both intervals

• For 15 Min

• For 1 Day

3rd drop list Select an option to define the direction for which you intend enable or disable TCA reporting. You must make a selection from the 2nd drop-list to enable the 3rd drop-list.

Note: Select both directions by selecting the At current port item.

• At current direction

• At current port


• Selected

• Unselected

Apply button This button applies selections made in the Threshold portion of the screen.

• Selected

• Unselected





Time stamp rulesThe System Manager observes the following time stamp rules.

• Each shelf in the ring has a Time of Day (TOD) clock. When you perform the system lineup and testing (SLAT) procedure during a shelf installation, the TOD clock is initialized. Each TOD clock

— uses absolute time, or Greenwich Mean Time (GMT)

— provides a calendar date and time in the following format:

YYYY/MM/DD hh:mm:ss

— survives events, such as power failures

• For every ring, one shelf is designated as the primary shelf. The other shelves in the ring periodically synchronize their TOD clocks with the primary shelf using the Simple Network Time Protocol (SNTP). The SNTP operates on per wavelength overhead channels. The SNTP keeps the shelves in the ring synchronized within one second of the primary shelf and with each other.

• When events occur on a shelf, the event is time stamped using the TOD clock of the shelf. Events can include alarm raise or clear, protection switching, and user login or logout. The shelf uses the time stamp internally and for communications with the System Manager. When the System Manager displays events to the user, the time stamp is converted to local time. The local time is adjusted for daylight saving time (DST) and the time zone. The local time is adjusted using the setup of the users PC or Workstation, such as the date and time control panel in a WinNT environment or the time zone related environment variables on a UNIX station.

As a result of the time stamp rules, multiple shelf events on multiple rings are correlated in time. You do not need to remember which shelf is in which time zone, and you do not need to convert times for different shelves. OPTera Metro 5200 monitors a network which spans multiple time zones over many rings. You view your time zone and DST settings. Users that are located in different time zones can view events using their local time. OPTera Metro 5200 allows multiple users in multiple time zones, such as remote support roles to monitor the network.


Index 78-10 Gbit/s OTR circuit pack

PEC 12-1510Base-T ports

pinouts 27-5019-inch rack 42-22, 42-24, 42-37

installing Ethernet hub in 20-4installing mounting brackets 42-15installing patch panel in 23-3installing shelves in 42-1

23-inch rackinstalling Ethernet hub in 20-4installing mounting brackets 42-15installing patch panel in 23-3installing shelves in 42-1

535-mm cabinetinstalling shelves in 42-1

535-mm rackinstalling Ethernet hub in 20-4installing patch panel in 23-3installing shelves in 42-1

AACT 29-2Active Alarms window 59-7ACT-USER, TL1 security and administration

commands 29-2adapter housing, cleaning 77-19adding

shelf to linear OADM network 57-10shelf to path-protected network 57-8shelf to unprotected network 57-9

adding trafficto an OCLD circuit pack 56-28

additional equipment, ordering 12-18adjusting facility PP threshold value,

PM procedures 61-12

administrative state 56-1Agile SRM PM alarms, clearing 72-9air filter, replacing 75-3Alarm Details window 59-8alarm, event and external control commands

TL1 interface 37-1alarms

acknowledging 55-25administration procedures 14-11and shelf restarts 64-2audible 64-2banner 59-5classifications 64-3clearing OSC 73-1clearing procedures 64-1counts for shelves 55-27ECT 69-1ECT Auto-Provisioning Mismatch 69-3ECT Circuit Pack Mismatch 69-3ECT Circuit Pack Missing 69-2external power for rectifier 43-18Fault window 59-7indicators 64-2locating with System Manager 64-2OCI alarms 65-1 to 65-34OCI Autoprovisioning Mismatch 65-4OCI Backplane Invalid Signal (9 or

10) 65-6OCI Circuit Pack Failed 65-7OCI Circuit Pack Mismatch 65-4OCI Circuit Pack Missing 65-8OCI Facility Loopback 65-9OCI Forced Switch to East Path

Active 65-10OCI Forced Switch to West Path

Active 65-10

Index


OCI High Optical Power Warning 65-11OCI Inter-card Communication

Failure 65-12OCI Laser Output Degrade 65-13OCI Loss of Activity (9 or 10) 65-14OCI Loss Primary Clock Source

Warning 65-16OCI Loss Secondary Clock Source

Warning 65-17OCI Low Optical Power Warning 65-18OCI Path Lockout Active 65-19OCI Port Alarm Indication Signal 65-20OCI Port Mapping Fault 65-22OCI Rx High Optical Power 65-23OCI Rx Loss of Clock 65-24OCI Rx Loss of Frame 65-25OCI Rx Loss of Lock 65-27OCI Rx Loss of Signal 65-29OCI Terminal Loopback 65-9OCI Tx Loss of Frame 65-31OCI Unequipped or OOS Remote SRM

Port 65-34OCI Unknown Circuit Pack 65-33OCLD 67-1OCLD Alarm Indication Signal 67-3OCLD alarms 67-3 to 67-33OCLD Backplane Invalid Signal (9 or

10) 67-6OCLD Bit Disparity 67-8OCLD Circuit Pack Failed 67-9OCLD Circuit Pack Missing 67-11OCLD Facility Loopback 67-13OCLD High Optical Power Warning 67-14OCLD Inter-card Communication

Failure 67-16OCLD Laser Output Degrade 67-18OCLD Loss of Activity 67-19OCLD Loss of Overhead

Synchronization 67-21OCLD Low Optical Power Warning 67-24OCLD Overhead Link Failure 67-21OCLD Rx High Optical Power 67-27OCLD Rx Invalid Signal 67-29OCLD RX Loss of Signal 67-31OCLD Supporting OMX not

Provisioned 67-26OCLD Terminal Loopback 67-13

OCLD Unknown Circuit Pack 67-33OCM 66-1OCM Auto-Provisioning Mismatch 66-3OCM Autoswitch to Protection Path

active 66-4OCM Circuit Pack Failed 66-5OCM Circuit Pack Mismatch 66-3OCM Circuit Pack Missing 66-6OCM Forced Switch to OCM 9 (or 10)

active 66-7OCM Inter-card Communication

Failure 66-8OCM Loss of Activity 66-9OCM Manual Switch to West (or East) path

active 66-11OCM Pair Mismatch 66-12OCM Unknown Circuit Pack 66-13OFA 70-1OFA Auto-Provisioning Mismatch 70-3OFA Circuit Pack Failed 70-4OFA Circuit Pack Mismatch 70-3OFA Circuit Pack Missing 70-6OFA Inter-card Communication

Failure 70-13OFA Rx High Optical Power 70-7OFA Rx Loss of Signal 70-8OFA Supporting ECT not

Provisioned 70-12OFA Temperature Out of Range 70-10OMX alarms 68-1 to 68-5OMX Auto-Provisioning Mismatch 68-3OMX Band Input Failure 68-4OMX Band Signal Degrade 68-4OMX Circuit Pack Mismatch 68-3OMX Circuit Pack Missing, OMX

alarms 68-2OMX Mismatch 68-3OMX Missing 68-2OSC

Circuit Pack Failed 73-4Circuit Pack Missing 73-19East or West Overhead Link

Failure 73-11East or West Remote Overhead Link

Failure 73-13East/West Fiber Mismatch 73-14Invalid Data 73-6

Index


Invalid Signal 73-9Loss of Frame 73-10Loss of Link 73-5Loss of Signal 73-7Remote Invalid Signal 73-15Remote Loss of Frame 73-16Remote Loss of Signal 73-17Shelf Input Failure 73-18Unequipped Remote Port 73-12Wayside Alarm Indication Signal 73-3

printing 55-17, 55-24printing alarm lists 55-24processing sequence 64-1related commands in TL1 37-1saving 55-23saving alarm lists 55-23shelf alarms 71-1 to 71-8shelf, Breaker A Tripped 71-3shelf, Breaker B Tripped 71-3shelf, Brownout 71-4shelf, Cooling Unit Failed/Missing 71-5shelf, Data Recovery Failure 71-6shelf, Parallel Telemetry Scan Point

(1-4) 71-9shelf, Power Feed A Low/Missing 71-10shelf, SBUS Failure 71-11shelf, Software Library Missing 71-12shelf, Software Upgrade in Progress 71-13shelf, Temperature Out of Range 71-14shelf, VAC Failed/Missing 71-15SP 71-1SP Circuit Pack Failed 71-16types 64-2visual 64-2

alertsand shelf restarts 64-2locating with System Manager 64-2types 64-2

alignment sleeve, cleaning 77-19ALW-MSG-ALL, TL1 alarm and event

commands 37-3ALW-MSG-NETWORK, TL1 alarm and

event commands 37-4ALW-PMREPT-ALL, TL1 performance

monitoring commands 36-2

ALW-PMREPT-NETWORK, TL1 performance monitoring commands 36-3

amplification 3-51amplified networks

accounting for fiber loss 7-18accounting for OMX losses 7-18accounting for OSC losses 7-18checking for receiver overload 7-18comparing transmit power to receiver

sensitivity 7-18determining receiver sensitivity 7-16determining transmit power 7-17

amplifier band restrictions 6-3amplifier receive power 6-3amplifiers, adding 7-5ARP server

IP addressing in the commissioning wizard 51-11

attenuator, installing in OMX 47-20, 47-23autonomous messages

TL1 interface 38-1

Bbackbone, connecting to remote site 48-23,

48-27backplane, continuity test 53-12backup, shelf

TL1 procedure 40-2Band and channel allocation worksheet 8-4band meshing 1-4, 3-8bands

linear configuration 4-3ring configuration 4-3

bin countshistorical counts 60-3intervals 60-3

blank filler cards 44-38brackets

Ethernet hub 20-4vertical optical fiber 16-16

buffer See event buffersbuilding a network

commissioning shelves 41-19downloading System Manager

software 41-10

Index


general process 41-1installing and connecting shelves and

components 41-15interconnecting and testing shelves 41-20provisioning and testing the system 41-21

Ccable assembly, routing to ECT 44-24cable, pinouts 27-51Call 64-20CANC-PROV, TL1 security and

administration commands 29-3CANC-USER, TL1 security and

administration commands 29-3capacity, system 1-4card cage door See shelf covercascaded amplifiers 6-4C-band channels 6-3C-band spectrum 1-2C-band traffic, ECT 42-58CD-ROM

contents 49-1downloading software from (Solaris) 49-7downloading software from (Windows 95,

98 or NT) 49-5central office alarms See COTEL interfacecentralized equalization 3-51changing

configuration information for shelf 57-11channel assignments 56-9

creating in TL1 33-1deleting 56-17manual switch 56-46pass-through 56-9protected 56-9querying 55-37unprotected 56-9viewing 59-26

Channel Assignments window 59-26channel meshing 1-4, 3-8checklists

circuit pack and equipment requirements for shelf 10-20

equipment for hubbed-ring network 10-9equipment for meshed-ring network 10-10equipment for point-to-point network 10-9

equipment for unprotected linear ADM chain 10-10

equipment rack requirements 10-2equipment requirements 10-15Ethernet network address 10-4facility environment requirements 10-3IP address 10-4optical fiber access requirements 10-4power and grounding requirements 10-4rack proximity requirements 10-3room and space requirements 10-2site readiness 10-1

CHK-HLTH, TL1 security and administration commands 29-5

CHK-HLTH-REPT, TL1 security and administration commands 29-6

circuit packschanging state 56-2facility 56-1filler cards 44-33inserting in shelf 44-33locking out 56-43lockout 56-43making channel assignments 56-9OCI 1-5OCLD 5-4OCM 16-5power consumption 27-4provisioning 56-6putting in-service 56-19replacing an SP 76-20seating 54-8shelf requirements 10-21specifications 27-9states 56-1taking out-of-service 56-20

cleaningadapter housing 77-19alignment sleeve 77-19assessing cleanliness of fiber end 77-22connectors with kit 77-16duplex connectors 77-8duplex FDDI and SC connectors 77-8fiber-optic connectors 77-16internal connectors on OCLD and OMX

circuit packs 77-25MT-RJ connectors 77-10

Index


receptacle devices 77-13single SC, FC, and ST connectors 77-5zones 77-1

clearing alarmsOCI alarms 65-1 to 65-34OCM alarms 66-1 to 66-4OFA alarms 70-1 to 70-12OMX alarms 68-1 to 68-5procedures 64-1shelf alarms 71-1 to 71-16

client signals, interfacing 1-5clock reference

manual switching for SONET/SDH SRM OCI 56-50

CMMT-PROV, TL1 security and administration commands 29-4

CO alarm system See COTEL interfacecommissioning

DHCP address 51-9commissioning wizard

about 14-11external management 51-12naming shelves 51-5OSPF routing control 14-5setting shelf date and time 51-16shelf surveillance 51-12

common equipment, ordering 12-4communications settings

setting with the commissioning wizard 51-8

setting with the system manager 55-42Communications window 59-33component handling precautions 53-4, 62-6configuration

backing up data 55-49changing for shelf 57-11restoring data 55-52TL1 interface 28-6

Configuration window 59-31Communications window 59-33Surveillance window

External manager entry window 59-43configuring System Manager See System

Managerconnecting

intershelf communications 45-5maintenance panel to OMXs 44-18

OMX (Standard) to OCLD circuit packs 47-26

OMX (Standard) trays to OCLD circuit packs 47-32

power leads to a shelf 43-7remote site to backbone 48-23, 48-27shelf alarms to the CO alarm system 45-11to network 14-6to the Ethernet hub 45-5, 45-16unused OMX pigtails 47-41

connecting power to a shelf 43-7, 43-15Connections window

Channel Assignments window 59-26OPTera Metro Channel Assignments

window 59-27OPTera Metro Timing window 59-30

connectorOTR circuit pack 17-29

connectors10Base-T 27-49assessing cleanliness of fiber end 77-22cleaning 77-8cleaning internal on OCLD and OMX

circuit packs 77-25cleaning MT-RJ connectors 77-10cleaning optical fiber 77-2cleaning with kit 77-16cleaning zones 77-1COTEL 27-53DTE 27-49Ethernet hub 20-1filler cards 27-45OCI circuit pack 17-10OCLD circuit pack 17-17, 27-25OCM circuit pack 17-34OFA circuit pack 27-33OMX 27-31OSC circuit pack 17-39rectifier 27-57

continuity testbackplane 53-12OMX module 53-15

cooling unitabout 16-10air filter 16-10connectors 16-11fan speeds 16-10

Index


features 27-7grill 16-17indicator lamps 16-11location 16-11product engineering code 16-11replacing 75-5

COTEL connectors 27-53COTEL interface

about 16-14, 45-11, 45-13, 55-20connectors 27-53, 45-11

cross-connect commandsTL1 interface 33-1

crossover, Ethernet cable 45-16cross-talk 6-6

Ddata communications network 45-16date

setting 55-38DCN See data communications networkdecommissioning, shelf 57-4default error codes, TL1 interface 39-8default gateway address, description

gateway network elementdefault 51-10

deletingchannel assignments 56-17shelf 57-6

detailed event history, viewing 55-14Details window 59-18DHCP address, commissioning 51-9dimensions, shelf 27-3dispersion 5-17, 6-11distributed equalization 3-51DLT-CRS-ALL, TL1 cross-connect

commands 33-3DLT-EQPT, TL1 equipment commands 31-3DLT-OCI, TL1 facility commands 32-4DLT-OCLD, TL1 facility commands 32-4DLT-OFA, TL1 facility commands 32-5DLT-OSC, TL1 facility commands 32-6,

32-7DLT-SRM, TL1 facility commands 32-7DLT-WSC, TL1 facility commands 32-8downloading software See softwareDTE connector 27-49

dual hubbed-ring configuration 3-6 to 3-7, 7-7

duplex devices, cleaning receptacle 77-13DWDM shelf. See OPTera Metro 5200

DWDM shelf

EECT

about 18-7alarms, clearing 69-1C-band traffic 42-58centralized equalization 3-51connecting to maintnance panel 44-24connecting to OFA circuit pack 47-58installing 42-58L-band traffic 42-58losses 7-15, 7-17, 7-18miniature VOA 42-58OTS input and output adapters 42-58putting in-service 56-25routing optical fiber from 48-15

ECT alarms, Circuit Pack Missing 69-2ECT modules

losses according to type of ECT 5-14optical tap 5-13PBE 5-13specifications 5-14types 5-12VOA 5-13

ED-CRS-ALL, TL1 cross-connect commands 33-15

ED-CRS-OC12, TL1 cross-connect commands 33-7



ED-CRS-OC48, TL1 cross-connect commands 33-11, 33-13

ED-DAT, TL1 security and administration commands 29-6

ED-EQPT, TL1 equipment commands 31-4ED-IP, TL1 system commands 30-2ED-IP-OSPF, TL1 system commands 30-6ED-NE-CFG, TL1 system commands 30-9

Index


ED-NE-NAME, TL1 system commands 30-11

ED-OCI, TL1 facility commands 32-8ED-OCLD, TL1 facility commands 32-9ED-OFA, TL1 facility commands 32-10ED-OSC, TL1 facility commands 32-10,

32-11ED-PID, TL1 security and administration

commands 29-7ED-SECU-PID, TL1 security and

administration commands 29-8ED-SRM, TL1 facility commands 32-11ED-TCA-OCI, TL1 alarm and event

commands 36-4, 36-5ED-TCA-SRM, TL1 alarm and event

commands 36-6ED-WSC, TL1 facility commands 32-12empty sites. See glass-through sitesenabling or disabling facility TCA notification

PM procedure 61-9ENT-CRS-ALL, TL1 cross-connect

commands 33-28ENT-CRS-OC12, TL1 cross-connect




commands 33-24ENT-EQPT, TL1 equipment commands 31-4ENT-NE-CFG, TL1 system

commands 30-12ENT-OCI, TL1 facility commands 32-13ENT-OCLD, TL1 facility commands 32-13ENT-OFA,TL1 facility commands 32-14ENT-OSC, TL1 facility commands 32-15,

32-16ENT-SRM, TL1 facility commands 32-16ENT-WSC, TL1 facility commands 32-17environment

humidity 27-8specifications 27-8

equalizationcentralized equalization 3-51distributed equalization 3-51

equalizer coupler tray. See ECT

equipmentconnecting subtending, to OCI circuit

packs 47-44lineup for point-to-point application 10-9performance parameters 60-11positions in rack or cabinet 42-11protection 2-4, 14-4redundancy 2-4

equipment access identifiers, TL1 equipment commands 31-1

equipment cabinet, mounting brackets 15-7equipment commands, TL1 interface 31-1equipment protection

forced switch 56-44manual switch 56-46

equipment rackdetermining site requirements 10-15installing 15-5mounting brackets 15-6number at site 10-15peripheral space requirements 11-3positioning and securing 42-9

equipment rack requirements, terminal and OADM sites 10-5

Equipment window 59-13Facilities window 59-16

Details window 59-18OPTera Metro 5200 Facility

window 59-20Inventory window 59-13

Details window 59-18Telemetry window 59-22

Parallel Telemetry Input window 59-23Parallel Telemetry Output

window 59-24error codes, TL1 interface 39-1, 39-2error messages

internal 64-12 to 64-19operational 64-7 to 64-12

ESD grounding lug 16-12ESD protection 42-40establishing a connection, TL1

interface 28-14, 28-16Ethernet

cable requirements for OPTera Metro 45-2configuring System Manager (Windows

95) 49-9

Index


configuring System Manager (Windows NT) 49-11

port on maintenance panel 16-15port pinouts 27-50

Ethernet cablecrossover 45-16maximum length 27-51product engineering code 21-2types 21-2types for OPTera Metro 45-2

Ethernet cables 10-8Ethernet hub 10-6

bracket sizes 20-4connections 45-5connectors 20-1in point-to-point network 42-45in ring network 42-45indicator lamps 20-2installing 42-45, 46-6installing in 19-inch rack 20-4installing in 23-inch rack 20-4installing in 535-mm rack 20-4intershelf messaging 45-8location 20-2mounting 20-4power requirements 20-1product engineering code 20-4requirements 20-1, 45-1specifications 27-56

eventFault window 64-2

event buffersclearing 55-18System Manager 14-5system manager 14-5

Event Console window 59-10Event Details window 59-12Event History window 59-11event lists

about 55-17, 55-24administration procedures 14-11printing 55-17, 55-24saving 55-23

event log 64-6event logs, saving the System Manager 55-16events

clearing 55-18

printing event logs 55-17related commands in TL1 37-1saving event log files 55-16shelf restarts 64-2System Manager 64-2types 64-2viewing history 55-14

external controlrelated commands in TL1 37-1

external managementconfiguring in the commissioning

wizard 51-12configuring in the System Manager 57-13

External Manager Entry window 59-43External manager entry window 59-43external surveillance

configuring for a shelf 57-13

FFacilities window 59-16facility

changing state 56-2, 56-21, 56-22circuit packs 56-1configuration 14-3in-service 56-21, 56-22out-of-service 56-24protection 14-4querying 55-36section counts 60-3SRM OCI or SONET/SDH SRM OCI

circuit pack 56-1states 56-1

facility access identifiers, TL1 facility commands 32-1

facility commandsTL1 interface 32-1

facility information, viewing 59-13facility loopback commands

TL1 interface 34-1fan See cooling unitFar-End Optical Loopback Test 53-26fault isolation

with alarms present 64-1with no alarms present 62-4

Fault window 59-7Active Alarms window 59-7

Index


Alarm Details window 59-8Event Console window 59-10

Event Details window 59-12Event History window 59-11

Event Details window 59-12FC connector, cleaning simplex 77-5, 77-10FDDI connector, cleaning duplex 77-8feature

OTR circuit pack 17-27fiber loss 5-19, 7-15fiber management trough 16-16Fiber Manager 26-1

installing 42-76product engineering code 26-3

fiber, optical patch cords, ordering 12-18fiber-optic patch cord, product engineering

code 21-3field descriptions 59-1filler cards

about 17-45connecting OMX pigtails 47-41connectors 17-45for unused slots 44-38inserting in shelf 44-38location 17-46product engineering code 17-46rules for using 44-40types 17-45

filler cards, types 27-45filters

channel 18-2replacing air 75-3wavelength band 18-2

forced path switching, on OCM circuit packs 56-44

forced switch 56-36forced traffic, removing a path switch 56-38forcing, equipment switch 56-44four-fiber systems. See ring topologiesfront-mounting with vertical fiber

brackets 42-24front-mounting without vertical fiber

brackets 42-22, 42-24, 42-37front-mounting, holes on a shelf 42-15function

OTR circuit pack 17-25

Ggateway network element

commissioning 51-10Communications window 59-33using in TL1 28-17

glass-through sites 3-9grounding

ESD jack 16-12shelf 42-40

Hhelp, calling for 64-20historical counts, bin counts 60-3hub site

installing the Ethernet hub at a 42-45, 46-6making intershelf connections 48-6

hubbed-ringequipment 10-9with Ethernet hub 42-45

hubbed-ring configuration 3-4 to 3-6, 7-7humidity, operating environment 27-8

IIDF See invalid data flagindicator lamp

10Base-T connections 16-16alarms 16-14communications failure 17-41cooling unit 16-11during the system lamp test 53-8Ethernet connections 16-16Ethernet hub 20-2maintenance panel 16-14OCI circuit pack 17-9OCLD circuit pack 17-16OCM circuit pack 17-34OSC circuit pack 17-38OTR circuit pack 17-29power 16-13SP circuit pack 17-42status lamp 17-41testing on shelf 53-7

information windows, System Manager 14-10

INH-MSG-ALL, TL1 alarm and event commands 37-4

Index


INH-PMREPT-ALL, TL1 performance monitoring commands 36-9

INIT-REG-OCI,TL1 performance monitoring commands 36-10

INIT-REG-SRM,TL1 performance monitoring commands 36-13

INIT-WARM, TL1 administration commands 29-9

insertingcircuit packs 44-33filler cards 44-38

in-service, circuit packs 56-19installation kit 15-8installing

components 44-1ECT 42-58equipment racks 15-5Ethernet hub 42-45, 46-6ETSI mounting brackets on a shelf 42-32NEBS shelf extension 42-34OMX (Standard) 44-4OMX tray 44-4patch panel 42-49plug housing on a power feed 43-12rectifier 43-20shelf components 46-1shelves 42-1

interconnect cablesabout 21-1Ethernet 21-2fiber optic patch cords 21-2

interfacing client signals 1-5internal error messages

connection details 64-13general errors 64-15network discovery 64-16passwords 64-17protocols 64-17provisioning details 64-17 to 64-19shelf 64-19

Internet Explorer, configuring 49-13intershelf communications, setting up 45-5intershelf connections

double density point-to-point 3-17interconnecting shelves with patch

cords 48-2OFA site 48-3

OMX modules 44-4remote site 3-19stacked 3-14

intershelf messaging, Ethernet hub 45-8intershelf OMX connections

about 48-1intervals, bin counts 60-3intrashelf OMX connections

about 48-1invalid data flaginventory

querying list 55-35inventory information, viewing 59-13Inventory window 59-13IP address

access to the System Manager 55-2ARP servers 51-11setting with the commissioning

wizard 51-8setting with the system manager 55-42shelf address 51-19, 55-5System Manager 51-9, 59-33, 59-35system manager 59-33

IP addressesexamples 9-13 to 9-23

ITU grid compliance 16-4

Jjitter 6-10

Kkit

cleaning connectors 77-16installation 15-8

Llaser radiation tag 44-5laser safety notices 62-5L-band channels 6-3L-band spectrum 1-2L-band traffic, ECT 42-58linear ADM chain, equipment 10-10linear configuration, allocation of bands 4-3linear OADM configuration 3-3, 7-7linear topologies

linear OADM 3-3

Index


point-to-point 3-1link budgets 8-8 to 8-24link engineering

amplified networks 7-18components

ECT modules 5-12 to 5-14OCLD circuit packs 5-4 to 5-5, 5-7OFA circuit packs 5-8 to 5-10OMX modules 5-10 to 5-11OPTera Metro 5200 DWDM shelf 5-1 OPTera Metro 5200 OFA shelf 5-3OSC module 5-15 to 5-16

introduction 4-1purpose 7-1rules for OPTera Metro 5200 networks

rule 1, network size limitations 6-2rule 2, OCLD power level 6-3rule 3, OMX pass-through losses 6-3rule 4, amplifier band restrictions 6-3rule 5, amplifier receive power 6-3rule 6, cascaded amplifiers 6-4rule 7, OSNR 6-4rule 8, coherent cross-talk 6-6rule 9, optical seams 6-8rule 11, jitter penalty 6-10rule 12, dispersion 6-11rule 13, OSC link engineering 6-14

unamplified networks using 1.25 Gbit/s or 2.5 Gbit/s OCLDs 7-16

work flow 7-3 to 7-6lists

printing alarm or event 55-17, 55-24saving alarm or event 55-23

locking out circuit pack 56-43lockout 56-43logging on to the system 55-5loopback

creating a facility or terminal loopback with the system manager 56-49

test, far-end optical 53-26TL1 interface commands 34-1

Mmaintenance panel

about 16-11alarm cut-off 16-13

connecting to ECT 44-24connecting to the OMX tray 44-18connector fields 16-11cover 16-12electrical breakers 16-11ESD grounding lug 16-12fault indicators 16-11grounding lug 16-12, 42-40location 16-11telemetry card 16-14, 55-20

making a PM query, PM procedures 61-3management

external, configuring for a shelf 57-13external, removing an entry 57-15horizontal fiber 16-16information base 51-12

management information base 57-13managing shelves 57-1mandatory

circuit packs 10-21filler cards 10-21

mandatory regulationsCanada 27-64Europe 27-67general requirements 27-63Norway 27-70Sweden 27-70Switzerland 27-70United Kingdom 27-70United States 27-66

manual equipment switch 56-47manual switching

on OCM circuit packs 56-47on protected channel assignments 56-46

marginsamplified networks 7-6

menu barPerformance Monitor 59-46

menu bar, System Manager 59-2meshed-ring

equipment 10-10with Ethernet hub 42-45

meshed-ring configuration 7-7meshing

band 1-4, 3-8channel 1-4, 3-8

message headers, TL1 interface 28-12

Index


message notation, TL1 interface 28-8messages See error messagesmessages, TL1 interface 28-10metropolitan optical network, description 1-1MIB file 51-12, 57-13

compiling 57-13mid-mounting, holes on a shelf 42-15miniature VOA, ECT 42-58modem, configuring external 50-5mounting brackets

19/23 cross-section 42-16patch panel 42-49

mounting optionsfront-mounting 42-21mid-mounting 42-21

multiplexer, replacing 75-7

NNaming window 59-32NEBS shelf extension

description 16-17installation 42-34product engineering code 16-17

Netscape Communicatorconfiguring 49-14configuring Java plug-in (Solaris) 49-17setting environment variables (Solaris

2.6) 49-15network element identification, TL1

interface 28-6network layout, description 4-2network shelf selector icons

System Manager 59-1network size limitations 6-2network topologies

linear 3-1 to 3-4ring 3-4 to 3-8

network, logging on to the 55-5Null Pointer Exception 49-17

OOADM shelves 5-2OADM site 1-8OADM sites

wiringsingle-shelf 3-19

OADM, shelf 57-1OCI 1.25 Gbit/s 1310 nm circuit pack

features 17-4OCI 1.25 Gbit/s 850 nm circuit pack

features 17-4OCI 622 Mbit/s 1310 nm circuit pack

features 17-4OCI alarms

Autoprovisioning Mismatch 65-4Backplane Invalid Signal (9 or 10) 65-6Circuit Pack Failed 65-7Circuit Pack Mismatch 65-4Circuit Pack Missing 65-8Facility Loopback 65-9Forced Switch to East Path Active 65-10Forced Switch to West Path Active 65-10High Optical Power Warning 65-11Inter-card Communication Failure 65-12Laser Output Degrade 65-13Loss of Activity (9 or 10) 65-14Low Optical Power Warning 65-18OCI Loss Primary Clock Source

Warning 65-16OCI Loss Secondary Clock Source

Warning 65-17OCI Rx Loss of Clock 65-24Path Lockout Active 65-19Port Alarm Indication Signal 65-20Port Mapping Fault 65-22Rx High Optical Power 65-23Rx Loss of Frame 65-25Rx Loss of Lock 65-27Rx Loss of Signal 65-29Terminal Loopback 65-9Tx Loss of Frame 65-31Unequipped or OOS Remote SRM

Port 65-34Unknown Circuit Pack 65-33

OCI circuit packabout 17-1alarms, clearing 65-1attenuation requirements 47-44, 47-48,

47-55client signal interfacing 1-5compatibility with OCMs and

OCLDs 17-3connecting to subtending equipment 47-44

Index


connectors 17-10features 17-4function 17-3indicator lamps 17-9location 17-13ordering 12-15removing traffic 56-27replacing 76-5signal flow 17-7SONET 47-44specifications 27-9types 17-2

OCI ISC 1310 nm circuit packfeatures 17-5

OCI OC-48/STM-16 1310 nm circuit packfeatures 17-4

OCLDpower level 6-3receiver sensitivity 7-8, 7-15transmit power 7-8

OCLD alarmsAlarm Indication Signal 67-3Backplane Invalid Signal (9 or 10) 67-6Bit Disparity 67-8Circuit Pack Failed 67-9Circuit Pack Missing 67-11Facility Loopback 67-13High Optical Power Warning 67-14Inter-card Communication Failure 67-16Laser Output Degrade 67-18Loss of Activity 67-19Loss of Overhead Synchronization 67-21Low Optical Power Warning 67-24Overhead Link Failure 67-21Rx High Optical Power 67-27Rx Invalid Signal 67-29Rx Loss of Signal 67-31Supporting OMX not Provisioned 67-26Terminal Loopback 67-13Unknown Circuit Pack 67-8, 67-33

OCLD circuit packabout 17-14adding traffic 56-28alarms, clearing 67-1cleaning internal connectors 77-25connecting OMX to 47-26, 47-32connectors 17-17

filler card, connecting pigtails to 47-41indicator lamps 17-16location 17-17optical service channel 17-16ordering 12-9primary path 56-9product engineering code 17-18removing traffic 56-29replacing 76-9, 76-12specifications 27-25testing indicator lamps 53-9

OCLD circuit packsspecifications 5-4

OCLD filler cardsabout 44-38connectors on faceplate 44-38

OCM alarmsAuto-Provisioning Mismatch 66-3Autoswitch to Protection Path active 66-4Circuit Pack Failed 66-5Circuit Pack Mismatch 66-3Circuit Pack Missing 66-6Forced Switch to OCM 9 (or 10)

active 66-7Inter-card Communication Failure 66-8Loss of Activity 66-9Manual Switch to West (or East) path

active 66-11OCM Pair Mismatch 66-12Unknown Circuit Pack 66-4, 66-7, 66-11,

66-13OCM circuit pack 16-5

about 17-32alarms, clearing 66-1connectors 17-34forced switching 56-44indicator lamps 17-34location 17-34manual switch 56-47manual switching 56-47ordering 12-4product engineering code 17-34replacing 76-15specifications 27-30types 17-32upgrading to OC48 56-52

OFA 6-3

Index


OFA alarmsCircuit Pack Failed 70-4Circuit Pack Missing 70-6Rx High Optical Power 70-7Rx Loss of Signal 70-8Supporting ECT not Provisioned 70-12Temperature Out of Range 70-10

OFA circuit packalarms, clearing 70-1connecting ECT to 47-58specifications 27-33

OFA filler cards 44-38connectors on faceplate 44-38slots to install in 44-38

OFA shelfabout 1-6filler cards 44-38installing ECT 42-58

OFA shelf. See OPTera Metro 5200 OFA shelfOFA site, about 1-8OMC See Optical Management ChannelOMX

band filter 18-2cable, connecting and routing 44-9connecting to the maintenance panel 44-20connectors 18-4continuity test 53-15function 47-10labels on pigtail connectors 47-28pigtails connected to filler cards 44-38routing fiber-optic pigtails from 44-12shelf requirements 10-20specifications 27-30

OMX (Standard) drawerproduct engineering code

18-5OMX (Standard) tray

replacement procedures 75-7OMX (Standard) trays

product engineering code 18-4OMX alarms

Auto-Provisioning Mismatch 68-3Band Input Failure 68-4Band Signal Degrade 68-4Circuit Pack Mismatch 68-3Circuit Pack Missing 68-2OMX Mismatch 68-3

OMX cableconnecting to the maintenance panel 44-20labeling 44-20

OMX cable assembly, product engineering code 18-6

OMX cablesrequired in a terminal site 10-8required in an OADM site 10-7

OMX circuit pack, cleaning internal connectors 77-25

OMX connection methodsconsideration in calculating OMX losses

OMX connectionsmultishelf OADM site 3-19terminal site 3-12

OMX lossescalculating for multishelf OADM site 7-9

to 7-13calculating for stacked terminal site 7-13

to 7-14pass-through losses 6-3

OMX moduleabout 18-1color coding on pigtail connectors 47-28connecting pigtails to filler cards 47-41connecting to OCLD circuit packs 47-26,

47-32crossover connection in remote

shelves 48-14installing attenuator 47-20, 47-23layout of crossover connections 47-14location 18-4removing cover 75-10removing the cover 44-14replacing cover 48-26, 75-11replacing the cover 44-16specifications 27-30

OMX patch cords, product engineering code 18-6

OMX trayconnecting to the maintenance panel 44-18flexible fiber guide 44-8, 44-15, 75-10installing 44-4locking tabs 44-6

operational error messagesadministrative 64-8commissioning 64-9 to 64-11

Index


loopback 64-11OCI card 64-8OCLD card 64-8OCM card 64-9OMX 64-9password 64-11provisioning 64-12

operational state 56-1OPR-ACO-COM, TL1 alarm and event

commands 37-5OPR-EXT-CONT, TL1 alarm and event

commands 37-6OPR-LPBK-OCI, TL1 facility loopback

commands 34-1OPR-LPBK-OCLD, TL1 facility loopback

commands 34-2OPR-LPBK-SRM, TL1 facility loopback

commands 34-2, 34-5OPR-PROTNSW-EQPT, TL1 protection

switching commands 35-1OPR-PROTNSW-OCLD, TL1 protection

switching commands 35-2OPR-SYNCNSW-SRM, TL1 protection

switching commands 35-4OPTera Metro 3500 Multiservice

Platform 5-20OPTera Metro 5200 DWDM shelf

description 5-1OADM shelves 5-2terminal shelves 5-2

OPTera Metro 5200 Facility window 59-20OPTera Metro 5200 networks

equipmentequipment racks 10-5Ethernet cables 10-8Ethernet hub 10-6optical patch cords 10-6rectifiers 10-6sparing requirements 10-11 to 10-14

OPTera Metro 5200 OFA shelfdescription 5-3

OPTera Metro 5200 shipmentchecking contents 42-8checking for damage 42-6

OPTera Metro 5200 SONET section 60-3OPTera Metro Channel Assignments

window 59-27

OPTera Metro Timing window 59-30optical continuity test 53-9optical fiber

cleaning connectors 77-16patch cords 21-3plant, return loss from 27-45single-mode, operating wavelengths

for 27-46optical fiber characteristics

dispersion 5-17fiber loss 5-19

optical fiber, NDSF used in OPTera Metro 5200 networks 4-4

Optical Management Channel 17-37optical multiplexer See OMX moduleoptical patch cords 1-5, 10-6optical patch cords See fiber optic patch cordsoptical seams 6-8optical service channel, OCLD circuit

pack 17-16optical signal-to-noise ratio. See OSNRoptical tap 5-13Optical Trunk Switch

about 25-1back panel 25-6closing a TL1 session 52-9commands 52-2communicating with 52-6configuring telemetry alarms 46-11events 64-6front panel 25-3installing 46-4making alarm connections 46-9making optical connections 46-6making power connections 46-8menu commands 52-3networking configuration 52-1opening a TL1 session 52-7operation modes 25-2product engineering codes 25-8specifications 27-43TL1 commands 52-2

optical-channel interface circuit pack See OCI circuit pack

optical-channel laser and detector circuit pack See OCLD circuit pack

Index


optical-channel manager circuit pack See OCM circuit pack

optical-fiber amplifier circuit pack See OFA circuit pack

optical-fiber amplifier. See OFAordering

additional equipment 12-18common equipment 12-4equipment bay 12-18Ethernet cables 12-18Ethernet hub 12-18OCI circuit pack 12-15OCLD circuit pack 12-9OCM circuit pack 12-4optical patch cords 12-18patch panel 12-20power supplies 12-18software upgrade kits 12-3SP circuit pack 12-4SRM OCI (MT-RJ to SC) patch

cords 12-19OSC

deployment 3-25fault sectionalization

scenarios 63-3link engineering 6-14losses 7-15

OSC alarmsCircuit Pack Failed 73-4Circuit Pack Missing 73-19clearing 73-1East or West Overhead Link Failure 73-11East or West Remote Overhead Link

Failure 73-13East/West Fiber Mismatch 73-14Invalid Data 73-6Invalid Signal 73-9Loss of Frame 73-10Loss of Link 73-5Loss of Signal 73-7Remote Invalid Signal 73-15Remote Loss of Frame 73-16Remote Loss of Signal 73-17Shelf Input Failure 73-18Unequipped Remote Port 73-12Wayside Alarm Indication Signal 73-3

OSC circuit pack

about 17-34connectors 17-39faceplate 17-35function 17-36functions 17-36indicator lamps 17-38location 17-39signal flow 17-35specifications 27-35

OSC modulespecifications 5-16

OSC trayspecifications 27-37

OSNR 6-4OSPF routing control, commissioning

wizard 14-5OTR circuit pack 17-31

about 17-24connector 17-29feature 17-27function 17-25indicator lamp 17-29product engineering code 17-31protection 17-30provision rule 17-30signal flow 17-28

OTS input and output adapters, ECT 42-58out-of-service, circuit packs 56-20

Pparallel telemetry

interface specifications 27-53related commands in TL1 37-1

Parallel Telemetry Input window 59-23Parallel Telemetry Output window 59-24pass-through, channel assignments 56-9password

changing for the System Manager 55-6patch cords

intershelf connections 3-19optical fiber 21-3ordering 12-18routing in hub site 48-9routing in multishelf site 48-13SRM OCI (MT-RJ to SC) 47-51

Index


SRM OCI (MT-RJ to SC), routing through patch panel 47-48

patch panelbrackets 23-3, 24-4, 26-2installing 42-49installing in 19-inch rack 23-3installing in 23-inch rack 23-3installing in 535-mm rack 23-3location 23-1, 24-4maximum per shelf 42-49mounting brackets 42-49ordering 12-20product engineering code 23-3, 24-5purpose 23-1

pathcreating two unprotected 56-39protection 2-1

path protectionadding protection to an unprotected

path 56-34manual switching 56-46manual switching on OCM circuit

packs 56-47PBE 5-13per band equalizer. See PBEperformance management 17-16Performance Monitor

command and menu options 59-46Launch PM window 59-45

Performance Monitor window 59-45field descriptions 59-47

performance monitoringabout 60-1mode default on SONET/SDH circuit

packs 60-3TCA (threshold crossing alert) 60-9

performance monitoring commandsTL1 interface 36-1

performance monitoring, procedures 61-1performance parameters

equipment 60-11SDH 60-6

performing global shelf operationsabout 61-15PM procedures 61-15

physical connectivity 8-2pigtails See OMX

pigtails See OMX (Standard) traypinouts

10Base-T 1X port 27-5010Base-T 2X port 27-50communications cables 27-51COTEL interface 27-53Ethernet ports 27-50RS232 V24 1 (DTE) port 27-49RS232 V24 2 (DCE) port 27-49telemetry port 27-53

planning an OPTera Metro 5200 networkallocating bands 8-4 to 8-7engineering for optimal link budgets 8-8 to

8-24equipment required 1-5, 10-4 establishing physical connectivity 8-2 to

8-3understanding traffic demands 8-1 to 8-2

platform requirements, System Manager 27-47

PM alarmsAgile SRM PM alarms 72-9clearing 72-1

PM procedures 61-15adjusting facility PP threshold

values 61-12enabling or disabling facility TCA

notification 61-9making a PM query 61-3resetting facility counts to zero 61-7resetting facility PP thresholds to default

values 61-14viewing facility history counts 61-6

point-to-pointequipment 10-9with Ethernet hub 42-45

point-to-point configuration 3-1, 7-7port control

setting with the commissioning wizard 51-8

poweralarm 43-18card, inserting 43-15connections 43-7, 43-15consumption 27-4leads 43-15rectifier 43-22

Index


power connections, testing 43-23power leads, connecting to the shelf 43-15power loss 4-1power margins 4-4power requirements

Ethernet hub 20-1rectifiers 22-1

power sourcesground 42-40testing the connections 43-23

primary 59-33primary shelf

about 51-9, 59-35identifying during commissioning 51-16

printingabout 55-17, 55-24alarm lists 55-24event lists 55-17information from the System

Manager 55-33problem reporting 64-20procedures

performance monitoring 61-1product engineering code 17-31

Ethernet cable 21-2Ethernet hub 16-17, 20-4fiber-optic patch cord 21-3filler card 17-46NEBS shelf extension 16-17OCI circuit pack 17-13, 17-40OCLD circuit pack 17-18OCM circuit pack 17-34OMX cable assembly 18-6OMX module 18-4rectifier 22-2SP circuit pack 17-43

protected path, creating two unprotected paths from 56-39

protected, channel assignments 56-9protection

about 2-1equipment 2-4, 14-4facility 14-4OTR circuit pack 17-30path 2-1

protection switch, time required 2-4, 27-61protection switching commands

TL1 interface 35-1protocol handling

ATM 1-4attenuator requirements 47-44Gigabit Ethernet 1-4OC-12 1-4OC-3 1-4SONET 1-4, 47-44

provision ruleOTR circuit pack 17-30

provisioningcircuit packs 56-6system 56-1

provisioning rules, SONET/SDH 60-2

Qquerying

connections 55-37facilities 55-36inventory list 55-35

Rreceptacle devices, cleaning 77-13rectifier

about 22-1audible noise 27-59connecting alternating current

power 43-22connecting an external power alarm 43-18connecting the direct current outputs 43-4connectors 22-2dimensions 27-57dual-unit chassis 22-1installing 43-20installing the chassis 42-42location 22-2power requirements 22-1specifications 27-57weight 27-57

rectifiers 10-6redundancy, equipment 2-4, 17-34reflection, maximum discrete 27-45regulations, mandatory 27-63remote access 14-6, 50-3remote site

connecting to backbone 48-23, 48-27

Index


making intershelf connections 48-10patch cord routing 48-8, 48-12

removinga shelf surveillance and external

management entry 57-15removing traffic

from an OCI circuit pack 56-27from an OCLD circuit pack 56-29

replacingair filter 75-3cooling unit 75-5OCI circuit pack 76-5OCLD circuit pack 76-9, 76-12OCM circuit pack 76-15OMX modules 75-7SP circuit pack 76-20

REPT ALM COM, TL1 autonomous messages 38-3

REPT ALM ENV, TL1 autonomous messages 38-11

REPT ALM EQPT, TL1 autonomous messages 38-13

REPT ALM OCI, TL1 autonomous messages 38-15

REPT ALM OCLD, TL1 autonomous messages 38-16

REPT ALM OFA, TL1 autonomous messages 38-17

REPT ALM OHCHN, TL1 autonomous messages 38-19

REPT ALM OMX, TL1 autonomous messages 38-20

REPT ALM SRM, TL1 autonomous messages 38-23

REPT COND COM, TL1 autonomous messages 38-26

REPT COND EQPT, TL1 autonomous messages 38-27

REPT COND OCI, TL1 autonomous messages 38-29

REPT COND OCLD, TL1 autonomous messages 38-31

REPT COND OFA, TL1 autonomous messages 38-32

REPT COND OHCHN, TL1 autonomous messages 38-34

REPT COND OMX, TL1 autonomous messages 38-35

REPT COND SRM, TL1 autonomous messages 38-40

REPT DBCHG, TL1 autonomous messages 38-43

REPT EVT, TL1 autonomous messages 38-44

REPT NETWORK EVENT, TL1 autonomous messages 38-61

REPT PM EQPT, TL1 autonomous messages 38-62

REPT PM OCI, TL1 autonomous messages 38-64

REPT PM SRM, TL1 autonomous messages 38-67

resetting facility counts to zero, PM procedures 61-7

resetting facility PP thresholds to default values, PM procedures 61-14

response format, TL1 interface 28-10restarting a shelf 57-7restore, shelf

TL1 procedure 40-4ring configuration, allocation of bands 4-3ring topologies

dual hubbed-ring 3-6 to 3-7hubbed-ring 3-4 to 3-6meshed-ring 3-7 to 3-8

RLS-EXT-CONT, TL1 alarm and event commands 37-7

RLS-LPBK-OCI, TL1 facility loopback commands 34-7

RLS-LPBK-OCLD, TL1 facility loopback commands 34-8

RLS-LPBK-SRM, TL1 facility loopback commands 34-12

RLS-PROTNSW-EQPT, TL1 protection switching commands 33-31

RLS-PROTNSW-OCLD, TL1 protection switching commands 33-31

RMV-EQPT, TL1 equipment commands 31-6

RMV-OCI, TL1 facility commands 32-18RMV-OCLD, TL1 facility commands 32-19RMV-OFA, TL1 facility commands 32-19RMV-OSC, TL1 facility commands 32-20

Index


RMV-SRM, TL1 facility commands 32-20RMV-WSC, TL1 facility commands 32-21RST-EQPT, TL1 equipment commands 31-7RST-OCI, TL1 facility commands 32-22RST-OCLD, TL1 facility commands 32-23RST-OFA, TL1 facility commands 32-23RST-OSC, TL1 facility commands 32-24RST-PROV, TL1 security and administration

commands 29-10RST-SRM, TL1 facility commands 32-25RST-WSC, TL1 facility commands 32-25RTRV-ACO-COM, TL1 alarm and event

commands 37-8RTRV-ALM-ALL, TL1 alarm and event

commands 37-9RTRV-ALM-COM, TL1 alarm and event

commands 37-24RTRV-ALM-ENV, TL1 alarm and event

commands 37-26RTRV-ALM-EQPT, TL1 alarm and event

commands 37-29RTRV-ALM-OCI, TL1 alarm and event

commands 37-32RTRV-ALM-OCLD, TL1 alarm and event

commands 37-35RTRV-ALM-OFA, TL1 alarm and event

commands 37-37RTRV-ALM-OHCHN, TL1 alarm and event

commands 37-39RTRV-ALM-OMX, TL1 alarm and event

commands 37-41RTRV-ALM-OSC, TL1 alarm and event

commands 37-43RTRV-ALM-SRM, TL1 alarm and event

commands 37-47RTRV-ALM-WSC, TL1 alarm and event

commands 37-49RTRV-ATTR-CONT, TL1 alarm and event

commands 37-51RTRV-ATTR-ENV, TL1 alarm and event

commands 37-53RTRV-CFG-CONT, TL1 alarm and event

commands 37-55RTRV-COND-ALL, TL1 alarm and event

commands 37-56RTRV-COND-COM, TL1 alarm and event

commands 37-59

RTRV-COND-EQPT, TL1 alarm and event commands 37-61

RTRV-COND-OCI, TL1 alarm and event commands 37-64

RTRV-COND-OCLD, TL1 alarm and event commands 37-66

RTRV-COND-OFA, TL1 alarm and event commands 37-68

RTRV-COND-OHCHN, TL1 alarm and event commands 37-70

RTRV-COND-OMX, TL1 alarm and event commands 37-73

RTRV-COND-OSC, TL1 alarm and event commands 37-75

RTRV-COND-SRM, TL1 alarm and event commands 37-79

RTRV-COND-WSC, TL1 alarm and event commands 37-81

RTRV-CRS-ALL, TL1 cross-connect commands 33-33

RTRV-EQPT, TL1 equipment commands 31-8

RTRV-EXT-CONT, TL1 alarm and event commands 37-83

RTRV-HDR, TL1 security and administration commands 29-11

RTRV-INVENTORY, TL1 equipment commands 31-12

RTRV-IP, TL1 system commands 30-15RTRV-IP-OSPF, TL1 system

commands 30-19RTRV-MONTYPE-EQPT, TL1 performance

monitoring commands 36-14RTRV-MONTYPE-OCI, TL1 performance

monitoring commands 36-16, 36-18RTRV-MONTYPE-SRM, TL1 performance

monitoring commands 36-20RTRV-NE-CFG, TL1 system

commands 30-20RTRV-NE-CX, TL1 cross-connect

commands 33-38RTRV-NE-LIST, TL1 system

commands 30-22RTRV-NE-NAME, TL1 system

commands 30-23RTRV-NETYPE, TL1 system

commands 30-24

Index


RTRV-OCI, TL1 facility commands 32-26RTRV-OCLD, TL1 facility commands 32-28RTRV-OFA, TL1 facility commands 32-30RTRV-OSC, TL1 facility commands 32-32,

32-33RTRV-PM-EQPT, TL1 performance

monitoring commands 36-22RTRV-PMMODE-OCI,TL1 performance

monitoring commands 36-37RTRV-PMMODE-SRM,TL1 performance

monitoring commands 36-39RTRV-PM-NETWORK, TL1 performance

monitoring commands 36-24RTRV-PM-OCI, TL1 performance monitoring

commands 36-28RTRV-PM-SRM, TL1 performance

monitoring commands 36-35RTRV-SRM, TL1 facility commands 32-35RTRV-STATUS, TL1 system

commands 30-25RTRV-SW-VER, TL1 system

commands 30-26RTRV-SYNCNSW-SRM, TL1 protection

switching commands 35-5RTRV-TH, TL1 performance monitoring

commands 36-41, 36-45RTRV-WSC, TL1 facility commands 32-37Rx Loss of Clock 65-24Rx Loss of Frame 65-25Rx Loss of Lock 65-27Rx Loss of Signal 65-29

Ssafety standards 27-62, 75-3saving

alarm or event lists 55-23event log 55-16information from the System

Manager 55-32SAV-PROV, TL1 security and administration

commands 29-12, 29-14SC connector

cleaning duplex 77-8cleaning simplex 77-5, 77-10

SDH, performance parameters 60-6seating circuit packs 54-6

sectionfacility 60-3OPTera Metro 5200 SONET section 60-3

security and access permissions, TL1 interface 28-4

security and administration commandsTL1 interface 29-1

security certificate, installingSolaris 49-24

SET-ACO-COM, TL1 alarm and event commands 37-84

SET-ATTR-CONT, TL1 alarm and event commands 37-85

SET-ATTR-ENV, TL1 alarm and event commands 37-86

SET-CFG-CONT, TL1 alarm and event commands 37-88

SET-NETYPE, TL1 system commands 30-27

SET-PMMODE-OCI, TL1 performance monitoring commands 36-47

SET-PMMODE-SRM, TL1 performance monitoring commands 36-48

SET-SID, TL1 security and administration commands 29-13

SET-TH-OCI, TL1 performance monitoring commands 36-49

SET-TH-SRM, TL1 performance monitoring commands 36-52

shelf 16-17adding to a network 57-1adding to linear OADM network 57-10adding to path-protected network 57-8adding to unprotected network 57-9alarms, clearing 71-1backing up configuration data 55-49changing configuration information 57-11configuring external management 57-13configuring shelf surveillance 57-13date and time for primary 14-2decommissioning 57-4deleting 57-6dimensions 27-3installing ETSI mounting brackets 42-32lamp test 53-7management 57-1maximum per network 57-1

Index


maximum per site 57-1minimum network size 57-1naming with the commissioning

wizard 51-5OADM 57-1power consumption 27-4removing from a network 57-1restarting 57-7restarting and alarms 64-2restarting and alerts 64-2restarting and events 64-2restoring configuration data 55-52seating circuit packs 54-8selecting 55-27setting up external management 51-12troubleshooting alarms at 64-1weight 27-3

shelf alarmsBreaker A Tripped 71-3Breaker B Tripped 71-3Brownout 71-4Cooling Unit Failed/Missing 71-5Data Recovery Failure 71-6Parallel Telemetry Scan Point (1-4) 71-9Power Feed A Low/Missing alarm 71-10Power Feed B Low/Missing alarm 71-10SBUS Failure 71-11Software Library Missing 71-12Software Upgrade in Progress 71-13Temperature Out of Range 71-14VAC Failed/Missing 71-15

shelf cover 16-17, 48-30removing 44-36

shelf extensionfor NEBS compliance 16-17product engineering code 16-17

shelf names instead of IP addresses 55-2shelf positions

measuring the equipment rack 42-11shelf processor circuit pack See SP circuit packshelf surveillance

configuring in the commissioning wizard 51-12

configuring in the System Manager 57-13shelf, cover 44-36shelf, terminal 57-1signal amplification

equalization 3-51signal flow

OTR circuit pack 17-28signal flow, OCI circuit pack 17-7simplex

cleaning connectors 77-10simplex, cleaning connectors 77-5site readiness See checklistssites

glass-through 3-9OADM 3-19 to 3-24parallel configuration

with amplification 3-11with no amplification 3-10

serial configurationwith amplification 3-11with no amplification 3-10

types in OPTera Metro 5200 networks 3-8SNMP traps 51-12, 57-13software

downloading (Solaris) 49-7downloading (Windows 95, 98 or

NT) 49-5upgrading SP circuit pack 76-22

software loadcommitting new 51-21testing new 51-21

software upgrade kitsordering 12-3

Software Upgrade window 59-44, 59-45, 59-46

Solaris, troubleshooting, environment variables 62-2

SONET 60-2about 60-5section layer PMs 60-5

SONET, with OCI circuit pack 47-44SONET/SDH

OCI circuit pack 17-5provisioning rules 60-2

SONET/SDH SRM OCImanual switching of clock

references 56-50SONET/SDH SRM OCI circuit pack

changing clock reference settings 55-55connecting to subtending equipment 47-48facilities 56-1

Index


features 17-6specifications 27-24

sorting information 55-30SP alarms, Circuit Pack Failed 71-16SP circuit pack

about 17-40alarms, clearing 71-1changing to a higher or lower software

load 76-22connectors 17-43indicator lamps 17-42location 17-43ordering 12-4product engineering code 17-43replacing 76-20specifications 27-33

sparing requirements in an OPTera Metro 5200 network

two shelves 10-1232 shelves 10-12130 shelves 10-14

sparing rules 10-11specifications

cable pinouts 27-51circuit packs 27-9discrete reflection, optical return

loss 27-45environmental 27-8Ethernet hub 27-56OCI circuit pack 27-9OCLD circuit pack 27-25OCM circuit pack 27-29OFA circuit pack 27-33OMX module 27-30optical return loss from fiber plant 27-45Optical Trunk Switch 27-43rectifier 27-57shelf dimensions 27-3SP circuit pack 27-33SRM OCI circuit pack 27-24System Manager 27-46weight 27-3

SRM OCI (MT-RJ to SC) patch cordsordering 12-19product engineering codes 23-3

SRM OCI circuit packchanging clock reference settings 55-55

connecting to subtending equipment 47-48facilities 56-1specifications 27-24

SRM OCI circuit pack, features 17-5STA-LAMP-TST, TL1 alarm and event

commands 37-88standards

safety 27-62TL1 interface, compliance 28-3

stateadministrative 56-1facility, changing 56-21, 56-22operational 56-1

statusshelves selected in the System

Manager 59-1subtending equipment

connecting OCI circuit packs to 47-44connecting SRM circuit packs to 47-48speed considerations 47-44

surveillanceexternal, configuring for a shelf 57-13

Surveillance windowExternal manager entry window 59-43

systemabout 1-3capacity 1-4forcing traffic to one path on

path-protected 56-36logging on 55-5provisioning 56-1

System Managerabout 1-9, 14-3access privileges 55-2access through IP address 55-2accessibility 14-6, 55-1accessing information windows 59-6Active Alarms window 59-7alarm banner 14-8, 14-9Alarm Details window 59-8applet 14-6changing password 55-6Channel Assignments window 59-26commands and menu options 59-2Configuration window 59-31configuring for Ethernet connection

(Windows 95) 49-9

Index


configuring for Ethernet connection (Windows NT) 49-11

downloading software to (Solaris) 49-7event buffers 14-5event log 55-16exiting 55-61external management 57-13information windows 14-8, 14-10installing 49-1locating alarms with 64-2main window 14-7menu bar 14-9, 59-2minimum platform requirements 27-47network connections 14-6network shelf selector 14-8network shelf selector icons 59-1network tree 14-8Null Pointer Exception 49-17printing information 55-33protection management 14-4requirements 14-7saving information 55-32security 14-5selecting shelves 14-8shelf surveillance 57-13sorting data 14-10sorting information 55-30specifications 27-46TCP/IP settings (Windows 95) 49-9TCP/IP settings (Windows NT) 49-11user administration 14-5user levels 55-2window hierarchy 14-10

system managercommunications settings 55-42Communications window 59-33creating facility loopback 56-49creating terminal loopback 56-49date and time 59-52Details window 59-18downloading software to (Windows 95, 98

or NT) 49-5Equipment window 59-13Event Console window 59-10Event Details window 59-12Event History window 59-11External Manager Entry window 59-43

Facilities window 59-16Fault window 59-7Inventory window 59-13Naming window 59-32OPTera Metro 5200 Facility

window 59-20OPTera Metro Channel Assignments

window 59-27OPTera Metro Timing window 59-30Parallel Telemetry Input window 59-23Parallel Telemetry Output window 59-24Performance Monitor window 59-45refreshing windows 59-7setting up IP addressing 55-42Software Upgrade window 59-44, 59-45,

59-46Surveillance window 59-43Telemetry window 59-22time stamp rules 59-53time stamps 59-53user interface 59-1viewing facility information 59-13viewing inventory information 59-13window hierarchy 14-10, 59-6

System Manager, system requirements 14-7system requirements

System Manager 14-7

TTCA

performance monitoring 60-9TCP/IP, configuring System Manager

for 49-9, 49-11telemetry alarms, configuring 55-20telemetry interface. See COTEL interfaceTelemetry window 59-22Telnet

accessing 28-6Telntet

connecting to 28-14temperature, operating environment 27-8terminal

shelf 57-1terminal shelves 5-2terminal site, about 1-8tests

Index


backplane continuity 53-12graduated loopback test 53-29new software load 51-21OMX continuity 53-15optical continuity 53-9power connections 43-23shelf lamps 53-7

threshold crossing alert (TCA)performance monitoring 60-9

timesetting 55-38

time stampssystem manager 59-53

timestampsTL1 interface 28-10

TL1 administration commandsINIT-WARM 29-9

TL1 alarm and event commandsALW-MSG-ALL 37-3ALW-MSG-NETWORK 37-4ED-TCA-OCI 36-4, 36-5ED-TCA-SRM 36-6INH-MSG-ALL 37-4OPR-ACO-COM 37-5OPR-EXT-CONT 37-6RLS-EXT-CONT 37-7RTRV-ACO-COM 37-8RTRV-ALM-ALL 37-9RTRV-ALM-COM 37-24RTRV-ALM-ENV 37-26RTRV-ALM-EQPT 37-29RTRV-ALM-OCI 37-32RTRV-ALM-OCLD 37-35RTRV-ALM-OFA 37-37RTRV-ALM-OHCHN 37-39RTRV-ALM-OMX 37-41RTRV-ALM-OSC 37-43RTRV-ALM-SRM 37-47RTRV-ALM-WSC 37-49RTRV-ATTR-CONT 37-51RTRV-ATTR-ENV 37-53RTRV-CFG-CONT 37-55RTRV-COND-ALL 37-56RTRV-COND-COM 37-59RTRV-COND-EQPT 37-61RTRV-COND-OCI 37-64RTRV-COND-OCLD 37-66

RTRV-COND-OFA 37-68RTRV-COND-OHCHN 37-70RTRV-COND-OMX 37-73RTRV-COND-OSC 37-75RTRV-COND-SRM 37-79RTRV-COND-WSC 37-81RTRV-EXT-CONT 37-83SET-ACO-COM 37-84SET-ATTR-CONT 37-85SET-ATTR-ENV 37-86SET-CFG-CONT 37-88STA-LAMP-TST 37-88

TL1 autonomous messagesREPT ALM COM 38-3REPT ALM ENV 38-11REPT ALM EQPT 38-13REPT ALM OCI 38-15REPT ALM OCLD 38-16REPT ALM OFA 38-17REPT ALM OHCHN 38-19REPT ALM OMX 38-20REPT ALM SRM 38-23REPT COND COM 38-26REPT COND EQPT 38-27REPT COND OCI 38-29REPT COND OCLD 38-31REPT COND OFA 38-32REPT COND OHCHN 38-34REPT COND OMX 38-35REPT COND SRM 38-40REPT DBCHG 38-43REPT EVT 38-44REPT NETWORK EVENT 38-61REPT PM EQPT 38-62REPT PM OCI 38-64REPT PM SRM 38-67

TL1 cross-connect commandsDLT-CRS-ALL 33-3ED-CRS-ALL 33-15ED-CRS-OC12 33-7ED-CRS-OC24 33-9ED-CRS-OC3 33-5ED-CRS-OC48 33-11, 33-13ENT-CRS-ALL 33-28ENT-CRS-OC12 33-20ENT-CRS-OC24 33-22ENT-CRS-OC3 33-18

Index


ENT-CRS-OC48 33-24RTRV-CRS-ALL 33-33RTRV-NE-CX 33-38

TL1 equipment commandsDLT-EQPT 31-3ED-EQPT 31-4ENT-EQPT 31-4equipment access identifiers 31-1RMV-EQPT 31-6RST-EQPT 31-7RTRV-EQPT 31-8RTRV-INVENTORY 31-12

TL1 facility commandsDLT-OCI 32-4DLT-OCLD 32-4DLT-OFA 32-5DLT-OSC 32-6, 32-7DLT-SRM 32-7DLT-WSCI 32-8ED-OCI 32-8ED-OCLD 32-9ED-OFA 32-10ED-OSCI 32-10, 32-11ED-SRM 32-11ED-WSC 32-12ENT-OCI 32-13ENT-OCLD 32-13ENT-OFA 32-14ENT-OSC 32-15, 32-16ENT-SRM 32-16ENT-WSC 32-17facility access identifiers 32-1RMV-OCI 32-18RMV-OCLD 32-19RMV-OFA 32-19RMV-OSC 32-20RMV-SRM 32-20RMV-WSC 32-21RST-OCI 32-22RST-OCLD 32-23RST-OFA 32-23RST-OSC 32-24RST-SRM 32-25RST-WSC 32-25RTRV-OCI 32-26RTRV-OCLD 32-28RTRV-OFA 32-30

RTRV-OSC 32-32, 32-33RTRV-SRM 32-35RTRV-WSC 32-37

TL1 facility loopback commandsOPR-LPBK-OCI 34-1OPR-LPBK-OCLD 34-2OPR-LPBK-SRM 34-2, 34-5RLS-LPBK-OCI 34-7RLS-LPBK-OCLD 34-8RLS-LPBK-SRM 34-12

TL1 interfacealarm commands 37-1alarm, event, and external control

commands 37-1automatic reports 38-1autonomous messages 38-1backing up shelf configuration data 40-2backup and restore related commands 29-1configuration 28-6creating channel assignments 33-1cross-connect commands 33-1default error codes 39-8equipment commands 31-1error codes 39-1, 39-2establishing a connection 28-14, 28-16event commands 37-1external control commands 37-1facility commands 32-1facility loopback commands 34-1message headers 28-12message notation 28-8messages 28-10network element identification 28-6performance monitoring commands 36-1protection switching commands 35-1response format 28-10restoring shelf configuration data 40-4security and access permissions 28-4security and administration

commands 29-1standards compliance 28-3timestamps 28-10troubleshooting backup failure 40-7troubleshooting restore failure 40-9using the OPTera Metro gateway network

element 28-17TL1 performance monitoring commands

Index


ALW-PMREPT-ALL 36-2ALW-PMREPT-NETWORK 36-3INH-PMREPT-ALL 36-9INIT-REG-OCI 36-10INIT-REG-SRM 36-13RTRV-MONTYPE-EQPT 36-14RTRV-MONTYPE-OCI 36-16, 36-18RTRV-MONTYPE-SRM 36-20RTRV-PM-EQPT 36-22RTRV-PMMODE-OCI 36-37RTRV-PMMODE-SRM 36-39RTRV-PM-NETWORK 36-24RTRV-PM-OCI 36-28RTRV-PM-SRM 36-35RTRV-TH 36-41, 36-45SET-PMMODE-OCI 36-47SET-PMMODE-SRM 36-48SET-TH-OCI 36-49SET-TH-SRM 36-52

TL1 protection switching commandsOPR-PROTNSW-EQPT 35-1OPR-PROTNSW-OCLD 35-2OPR-SYNCNSW-SRM 35-4RLS-PROTNSW-EQPT 33-31RLS-PROTNSW-OCLD 33-31RTRV-SYNCNSW-SRM 35-5

TL1 security and administration commandsACT-USER 29-2CANC-PROV 29-3CANC-USER 29-3CHK-HLTH 29-5CHK-HLTH-REPT 29-6CMMT-PROV 29-4ED-DAT 29-6ED-PID 29-7ED-SECU-PID 29-8RST-PROV 29-10RTRV-HDR 29-11SAV-PROV 29-12, 29-14SET-SID 29-13

TL1 system commandsED-IP 30-2ED-IP-OSPF 30-6ED-NE-CFG 30-9ED-NE-NAME 30-11ENT-NE-CFG 30-12RTRV-IP 30-15

RTRV-IP-OSPF 30-19RTRV-NE-CFG 30-20RTRV-NE-LIST 30-22RTRV-NE-NAME 30-23RTRV-NETYPE 30-24RTRV-STATUS 30-25RTRV-SW-VER 30-26SET-NETYPE 30-27

trafficadding to an OCLD circuit pack 56-28creating two unprotected paths from one

protected path 56-39forcing to one path on path-protected

system 56-36removing a forced path switch 56-38removing from an OCI circuit pack 56-27removing from an OCLD circuit

pack 56-29traffic demands 8-1Transponder Protection Tray 24-1

installing 42-71product engineering code 24-5replacing 75-16tributary-side protection 24-1

troubleshootingisolating faults with no alarms 62-4Solaris environment variables 62-2TL1 backup failure 40-7TL1 restore failure 40-9Web browser 62-2

two-fiber systems. See linear topologiesTx Loss of Frame 65-31

Uunamplified networks

accounting for ECT losses 7-15, 7-17, 7-18

accounting for fiber loss 7-15accounting for OSC losses 7-15checking for OCLD receiver overload 7-16comparing transmit power to OCLD

receiver sensitivity 7-15determining OCLD receiver sensitivity 7-8determining OCLD transmit power 7-8prerequisite information for link

engineering 7-1

Index


unprotected channel assignments 56-9unprotected path

adding path protection 56-34upgrading

1.25 Gbit/s OCM to OC48 OCM 56-52SP circuit pack to higher software

load 76-22user interface 59-1user provisioning requests

Fault window 59-7using the OPTera Metro gateway network

elementTL1 interface 28-17

Vvariable optical attenuator. See VOAvertical fiber brackets

attachment procedure on a 19-inch front-mounted shelf 42-26

attachment procedure on a 23-inch front-mounted shelf 42-27

attachment procedure on ETSI mounting brackets 42-30

location 15-3on a mid-mounted shelf 42-29purpose 15-1

viewing facility history counts, PM procedures 61-6

VOA 5-13

Wwarnings, Fault window 59-7wavelength

bands 17-18, 17-19 to 17-33bands, OMX + Fiber Manager 4CH 18-5

to ??bands, OMX module 18-2, 18-2bands, OMX(Standard) trays 18-4 to ??single-mode fiber 27-46

wavelength grid 1-2Wayside Channel

definition 17-37Web browser

configuring Internet Explorer 49-13configuring Netscape

Communicator 49-14

Web browser, troubleshooting 62-2weight

rectifier 27-57weight, shelf 27-3Windows 95, configuring dial-up

connection 50-11Windows 95/98, downloading software from

CD-ROM 49-5Windows NT

configuring dial-up connection 50-12downloading software from

CD-ROM 49-5windows, accessing information 14-10wiring methods

consideration in calculating OMX lossesmultishelf OADM site 7-9 to 7-13stacked terminal site 7-13 to 7-14

signal flow 3-23worksheets

Band and channel allocation 8-4WSC See Wayside ChannelWTR period 56-9, 56-34

Index


Copyright 2000–2001 Nortel Networks, All Rights Reserved

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Nortel Networks

OPTera Metro 5200 Multiservice PlatformProvisioning and Operating Procedures

323-1701-310Standard Release 4.0 Issue 1 November 2001Printed in Canada and in the United Kingdom

Nortel Networks, the Nortel Networks logo, the Globemark, How the World Shares Ideas, OPTera, and Unified Networks are trademarks of Nortel Networks.HP and HP-UX are trademarks of Hewlett-Packard, Inc. Pentium is a trademark of Intel Corporation. Internet Explorer, Windows, and Windows NT are trademarks of Microsoft Corporation. Netscape Communicator is a trademark of Netscape Communications Corporation. Common Desktop Environment, Java, Solaris, and Ultra are trademarks of Sun Microsystems, Inc. UNIX is a trademark of X/Open Company Limited.

nlnt8f3_

Documents