Oamp Guide 6-2 Stand 01

Operations, Administration,
Maintenance & Provisioning Guide
BTI Systems
50 Northside Road
Ottawa, ON K2H 5Z6
(613) 248-9154
www.btisystems.com
Product Release 6.2

Document Version 01
January 2008
Part Number BP1A74FB
STANDARD
Copyright 2003-2008 BTI Systems All rights reserved.

The information contained herein is the property of BTI Systems and is strictly confidential. Except as expressly authorized in
writing by BTI Systems, 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 BTI Systems, the holder is granted no rights to use the information contained herein.
Contents
Preface
xiii
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
New features and upcoming product enhancements . . . . . . . . . . . . . . . . . . . . . . . . . .xxxii
Organization of the Netstender documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxv
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii
Obtaining documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix
World Wide Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix
Product documentation CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix
Ordering documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix
Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix
Obtaining technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix
1.0 Netstender overview
1-1
1.1 Netstender features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Netstender design values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Netstender technology features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1 Optical amplification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2 Optical multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.3 Optical signal conditioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.4 Optical Supervisory Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.5 Wavelength conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.6 Muxponder modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.7 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2
1-4
1-5
1-5
1-6
1-7
1-7
1-8
1-8
1-9
2.0 Netstender state management
2-1
2.1 Entity management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.2 Telcordia state model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Product Release 6.2 STANDARD iii
Contents
2.3 Telcordia state attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 PST and PSTQ values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1.1 IS In service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1.2 OOS Out of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1.3 NR Normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1.4 ANR Abnormal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1.5 AU Autonomous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1.6 MA Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1.7 MAANR Management and abnormal . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1.8 AUMA Autonomous and management . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2 SST values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2.1 AINS Automatic in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2.2 COMM Communication error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2.3 FLT Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2.4 FRCD Forced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2.5 LKDO Locked out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2.6 LPBK Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2.7 MEA Mismatch of equipment and attributes. . . . . . . . . . . . . . . . . . . .
2.3.2.8 MT Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2.9 SGEO Supporting entity outage . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2.10 STDBY Standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2.11 SWDL Software download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2.12 UEQ Unequipped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2.13 WRK Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Equipment state management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 Amplifier entity state management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6 Wavelength conversion transceiver port state management. . . . . . . . . . . . . . . . .
2.7 State management behavior interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.8 State management provisioning interactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.9 State change reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.10 Supporting and supported physical entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11 Fault reporting interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.0 Operating the Netstender
2-17
2-17
2-17
2-18
2-18
2-18
2-18
2-19
2-19
2-20
2-20
2-20
2-21
2-21
2-21
2-21
2-21
2-21
2-21
2-21
2-22
2-22
2-22
2-22
2-23
2-24
2-24
2-25
2-25
2-25
2-26
2-26
3-1
3.1 Starting up the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

3.1.1 Communication ports on the Netstender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2 Establishing a TL1 session using Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.2.1 Method One: Connecting through the management LAN . . . . . . . . . . . . . . . . 3-5
3.2.2 Method Two: Connecting through the craft LAN port . . . . . . . . . . . . . . . . . . . . 3-6
3.2.3 Changing the IP address and mask from the default . . . . . . . . . . . . . . . . . . . . 3-8
3.2.4 Changing the default gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.3 Establishing a TL1 session using RS-232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.3.1 RS-232 serial communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
3.4 Establishing a TL1 session using a Hayes modem . . . . . . . . . . . . . . . . . . . . . . . . 3-14
3.5 Connecting management systems to Netstender ports. . . . . . . . . . . . . . . . . . . . . 3-16
3.5.1 Netstender SNMP support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
iv Netstender OAM&P Guide Document Version 01
Contents
3.5.2 Modes of TL1 operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.6 Establishing an expansion shelf interface CLI session . . . . . . . . . . . . . . . . . . . . .
3.6.1 Connecting through the craft LAN port on an ESI circuit pack . . . . . . . . . . . .
3.6.2 Connecting through the craft serial port on an ESI circuit pack . . . . . . . . . . .
3.7 Understanding the audible and visual indications . . . . . . . . . . . . . . . . . . . . . . . . .
3.7.1 Location of Netstender 2060 main shelf and system alarms . . . . . . . . . . . . .
3.7.2 Location of Netstender 2060 expansion shelf alarms . . . . . . . . . . . . . . . . . .
3.7.3 Location of Netstender 1030 shelf and system alarms . . . . . . . . . . . . . . . . .
3.7.4 Netstender system alarm LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7.5 Audible alarms and office alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7.6 Shelf and circuit pack LED behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7.6.1 Netstender 2060 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7.6.2 Netstender 1030 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7.7 Alarm cutoff and lamp test button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7.8 Alarm masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.8 TL1 identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.8.1 Network element SID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.8.2 Subordinate elements AID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.9 Events, conditions and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.9.1 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.9.2 Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.9.3 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.10 Circuit pack detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.10.1 System responses for common equipment circuit packs . . . . . . . . . . . . . . .
3.10.2 System responses for various circuit packs . . . . . . . . . . . . . . . . . . . . . . . . .
3.11 In-service shelf reconfiguration of a Netstender 2060 . . . . . . . . . . . . . . . . . . . . .
3.12 Shutting down the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.0 Installing optional Netstender circuit packs
3-17
3-18
3-19
3-20
3-21
3-21
3-21
3-22
3-22
3-23
3-23
3-23
3-24
3-24
3-24
3-25
3-25
3-25
3-29
3-29
3-29
3-29
3-30
3-31
3-32
3-34
3-37
4-1
4.1 Installing optical amplifier circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

4.2 Installing optical supervisory channel circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.3 Installing wavelength conversion circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.3.1 Installing SFP transceivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.3.2 Installing 10G Wavelength Regenerator XFP transceivers . . . . . . . . . . . . . . 4-15
4.4 Installing Muxponder circuit packs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
4.5 Installing optical add-drop module circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.6 Installing optical component tray circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
4.7 Installing multiplexer/demultiplexer circuit packs. . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
4.8 Installing DWDM bi-directional coupler/splitter circuit packs . . . . . . . . . . . . . . . . . 4-31
4.9 Installing dispersion compensation module circuit packs . . . . . . . . . . . . . . . . . . . 4-33
4.10 Installing filler circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
5.0 Connecting circuit packs
5-1
5.1 Amplifier configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Product Release 6.2 STANDARD
Contents
5.1.1 Connecting fibers between an OLAM and a DCM . . . . . . . . . . . . . . . . . . . . . .

5.2 OADM configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1 Basic cascading of OADMs to provide mux/demux functionality . . . . . . . . . . .
5.2.2 OADM survivability of upstream and downstream traffic . . . . . . . . . . . . . . . . .
5.2.3 Cascading OADMs for survivability and future growth . . . . . . . . . . . . . . . . . . .
5-2
5-3
5-3
5-4
5-6
6.0 Connecting expansion shelves
6-1
6.1 Netstender 2060 expansion shelves overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

6.2 Connecting local expansion shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6.3 Connecting remote expansion shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
7.0 Provisioning the Netstender
7-1
7.1 How Netstender provisioning works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

7.1.1 Auto provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.1.1.1 Controlling auto provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.1.1.2 Amplifier circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.1.1.3 OSC circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.1.1.4 Active mux/demux circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.1.1.5 Passive circuit packs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
7.1.1.6 Wavelength conversion circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
7.1.1.7 Wavelength manager ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
7.1.1.8 Muxponder circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
7.1.1.9 Muxponder circuit pack ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
7.1.1.10 Expansion shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
7.1.2 Auto de-provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
7.1.2.1 Controlling auto de-provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
7.1.2.2 Expansion shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
7.1.3 Pre-provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
7.1.4 Automatic in service secondary state. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
7.1.4.1 ENT commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
7.1.4.2 Forcing a transition from the AINS state to the IS state . . . . . . . . . . . . . . 7-9
7.1.4.3 Viewing AINS timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
7.1.4.4 MSCP or MSI restart or replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
7.1.4.5 Retrieving the faults against equipment in the AINS state . . . . . . . . . . . . 7-9
7.2 Hierarchical organization of Netstender components . . . . . . . . . . . . . . . . . . . . . . 7-10
7.2.1 Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
7.2.2 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
7.2.3 Equipmentshelves and circuit packs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
7.2.3.1 Shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
7.2.3.2 Common equipment circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
7.2.3.3 Provisionable slots for application circuit packs . . . . . . . . . . . . . . . . . . . 7-12
7.2.4 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
7.2.5 Supporting and supported relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
7.3 Designating names and IDs to system components . . . . . . . . . . . . . . . . . . . . . . . 7-14
7.4 System provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
7.4.1 Network element, site, time zone, and system identification code . . . . . . . . . 7-15
7.4.1.1 Editing the network element, site, and time zone . . . . . . . . . . . . . . . . . . 7-15
vi Netstender OAM&P Guide Document Version 01
Contents
7.4.1.2 Setting the system identification code. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

7.4.1.3 Retrieving the network element, site, time zone, and uptime . . . . . . . . . 7-17
7.4.1.4 Retrieving the vendor, model, NE type and software version . . . . . . . . . 7-17
7.4.2 Date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
7.4.2.1 Editing the date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
7.4.2.2 Editing the date and time during a daylight-saving-time transition . . . . . 7-19
7.4.2.3 Retrieving the system identifier, date, and time . . . . . . . . . . . . . . . . . . . 7-20
7.4.3 IP address parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
7.4.3.1 Editing the IP address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
7.4.3.2 Retrieving the IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
7.4.4 Craft serial interface parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
7.4.4.1 Editing the craft serial port information . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
7.4.4.2 Retrieving the craft serial port information . . . . . . . . . . . . . . . . . . . . . . . 7-24
7.5 Expansion shelf provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
7.5.1 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
7.5.1.1 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
7.5.2 Expansion shelf provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
7.5.2.1 Basic provisioning tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
7.5.2.2 Auto creation of expansion shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
7.5.2.3 Expansion shelf LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
7.5.2.4 Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
7.5.3 Reconfiguring expansion shelves. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
7.5.4 Re-purposing expansion shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
7.5.5 Expansion shelf command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
7.6 Equipment provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
7.6.1 Entering new equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
7.6.2 Editing equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
7.6.3 Removing equipment from service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
7.6.4 Restoring equipment to service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
7.6.5 Retrieving equipment attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
7.6.6 Retrieving an equipment inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
7.6.7 Deleting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
7.7 Optical amplifier provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
7.7.1 Provisioning an optical amplifier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
7.7.2 Modifying the definable parameters of an optical amplifier . . . . . . . . . . . . . . 7-45
7.7.3 Removing an optical amplifier from service . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47
7.7.4 Restoring an optical amplifier to service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50
7.7.4.1 Using the OPR-OBR-HTSO command . . . . . . . . . . . . . . . . . . . . . . . . . . 7-53
7.7.5 Retrieving optical amplifier settings and status . . . . . . . . . . . . . . . . . . . . . . . 7-54
7.7.6 Deleting an optical amplifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-63
7.8 OSC provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66
7.9 Wavelength conversion provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67
7.9.1 Provisioning wavelength conversion circuit pack equipment . . . . . . . . . . . . . 7-68
7.9.2 Provisioning transceiver ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-70
7.9.2.1 Retrieving a manufacturers SFP/XFP transceiver inventory information 7-71
7.9.2.2 Provisioning transceiver ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-75
7.9.2.3 Implementing advanced provisioning features . . . . . . . . . . . . . . . . . . . . 7-81
vii
Contents
7.9.2.4 Modifying the definable parameters of a transceiver port . . . . . . . . . . . . 7-83

7.9.2.5 Removing a transceiver port from service . . . . . . . . . . . . . . . . . . . . . . . 7-85
7.9.2.6 Restoring a transceiver to service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-87
7.9.2.7 Retrieving transceiver attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-88
7.9.2.8 Deleting a transceiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-92
7.9.3 Provisioning cross-connects on a Wavelength Conversion circuit pack. . . . . 7-93
7.9.3.1 Provisioning cross-connects on a Wavelength Conversion circuit pack . 7-93
7.9.3.2 Retrieving cross-connect port information from a Wavelength Conversion
circuit pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-97
7.9.3.3 Deleting a cross-connect on a Wavelength Conversion circuit pack . . . 7-98
7.9.4 Provisioning protection groups on a Wavelength Conversion circuit pack . . . 7-99
7.9.4.1 How protection switching works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-100
7.9.4.2 Provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-100
7.9.4.3 Example scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-101
7.9.4.4 Provisioning a protection group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-103
7.9.4.5 Modifying the definable parameters of a protection group . . . . . . . . . . 7-104
7.9.4.6 Retrieving protection group parameters . . . . . . . . . . . . . . . . . . . . . . . . 7-104
7.9.4.7 Deleting a protection group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-105
7.10 2-Port GE Muxponder provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-106
7.10.1 Provisioning 2-Port GE Muxponder circuit pack equipment . . . . . . . . . . . . 7-107
7.10.2 Provisioning synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-108
7.10.2.1 Provisioning the timing mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-109
7.10.2.2 Retrieving timing-mode information . . . . . . . . . . . . . . . . . . . . . . . . . . 7-110
7.10.2.3 Provisioning the timing reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-111
7.10.2.4 Retrieving timing-reference information . . . . . . . . . . . . . . . . . . . . . . . 7-113
7.10.3 Provisioning Fast Ethernet client side ports . . . . . . . . . . . . . . . . . . . . . . . . 7-114
7.10.3.1 Provisioning an FE client side port . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-114
7.10.3.2 Modifying the provisionable parameters of an FE client side port. . . . 7-116
7.10.3.3 Retrieving FE client side port attributes . . . . . . . . . . . . . . . . . . . . . . . 7-117
7.10.3.4 Deleting an FE client side port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-119
7.10.4 Retrieving a manufacturers SFP transceiver inventory . . . . . . . . . . . . . . . 7-120
7.10.5 Provisioning gigabit Ethernet client side ports . . . . . . . . . . . . . . . . . . . . . . 7-123
7.10.5.1 Provisioning a GE client side port . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-124
7.10.5.2 Implementing advanced provisioning features . . . . . . . . . . . . . . . . . . 7-126
7.10.5.3 Modifying the provisionable parameters of a GE client side port . . . . 7-128
7.10.5.4 Removing a GE client side port from service . . . . . . . . . . . . . . . . . . . 7-129
7.10.5.5 Restoring a GE client side port to service . . . . . . . . . . . . . . . . . . . . . . 7-130
7.10.5.6 Retrieving GE client side port attributes . . . . . . . . . . . . . . . . . . . . . . . 7-131
7.10.5.7 Deleting a GE client side port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-134
7.10.6 Provisioning OC-48 line side ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-135
7.10.6.1 Provisioning an OC-48 line side port . . . . . . . . . . . . . . . . . . . . . . . . . 7-135
7.10.6.2 Enabling threshold crossing alarms on OC-48 line side ports . . . . . . 7-139
7.10.6.3 Modifying the provisionable parameters of an OC-48 line side port . . 7-139
7.10.6.4 Removing an OC-48 line side port from service . . . . . . . . . . . . . . . . . 7-141
7.10.6.5 Restoring an OC-48 line side port to service . . . . . . . . . . . . . . . . . . . 7-142
7.10.6.6 Retrieving OC-48 line side port attributes . . . . . . . . . . . . . . . . . . . . . . 7-143
7.10.6.7 Deleting an OC-48 line side port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-146
7.10.7 Provisioning STM-16 line side ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-148
7.10.7.1 Provisioning an STM-16 line side port . . . . . . . . . . . . . . . . . . . . . . . . 7-148
viii Netstender OAM&P Guide Document Version 01
Contents
7.10.7.2 Enabling threshold crossing alarms on STM-16 line side ports . . . . . 7-151
7.10.7.3 Modifying the provisionable parameters of an STM-16 line side port . 7-152
7.10.7.4 Removing an STM-16 line side port from service . . . . . . . . . . . . . . . . 7-153
7.10.7.5 Restoring an STM-16 line side port to service . . . . . . . . . . . . . . . . . . 7-154
7.10.7.6 Retrieving STM-16 line side port attributes . . . . . . . . . . . . . . . . . . . . . 7-156
7.10.7.7 Deleting an STM-16 line side port. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-159
7.10.8 Retrieving Virtual Concatenation Group attributes . . . . . . . . . . . . . . . . . . . 7-161
7.10.9 Provisioning cross-connections on a Muxponder circuit pack . . . . . . . . . . 7-165
7.10.9.1 Provisioning a cross-connection on a Muxponder circuit pack . . . . . . 7-166
7.10.9.2 Retrieving cross-connection information from a Muxponder circuit pack . 7170
7.10.9.3 Deleting a cross-connection on a Muxponder circuit pack . . . . . . . . . 7-172
7.10.10 Provisioning protection switching on a Muxponder circuit pack . . . . . . . . 7-173
7.10.10.1 How protection switching works . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-173
7.10.10.2 Protection switching rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-174
7.10.10.3 Operating a protection switch using an STS1 path facility object . . . 7-174
7.10.10.4 Releasing an STS1 path facility object protection switch . . . . . . . . . 7-175
7.10.10.5 Operating a protection switch using a VC4 path facility object . . . . . 7-175
7.10.10.6 Releasing a VC4 path facility object protection switch . . . . . . . . . . . 7-176
7.11 Provisioning active mux/demux ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-177
7.12 Provisioning non-powered circuit pack ports . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-178
7.12.1 Modifying the parameters of a port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-179
7.12.2 Retrieving the parameters of a port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-182
8.0 Netstender performance monitoring
8-1
8.1 Understanding performance monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

8.1.1 PM parameter history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
8.1.2 PM parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
8.1.2.1 Optical amplifier modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
8.1.2.2 Optical Supervisory Channel modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
8.1.2.3 Transceiver ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
8.1.2.4 2.5G Wavlength Manager modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
8.1.2.5 10G Wavelength Regenerator modules . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
8.1.2.6 2-Port GE Muxponder modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
8.1.2.7 DWDM active multiplexer/demultiplexer modules. . . . . . . . . . . . . . . . . . 8-19
8.1.3 Bin validity qualifiers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
8.1.4 Threshold crossing alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
8.2 Retrieving performance monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
8.2.1 PM retrieval command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
8.2.1.1 Other PM retrieval commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
8.2.2 Retrieving current PM bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
8.2.2.1 Example one . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
8.2.2.2 Example two . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
8.2.3 Retrieving historical PM bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
8.2.3.1 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
9.0 Administering the Netstender
9-1
ix
Contents
9.1 Security management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

9.1.1 Security user profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
9.1.2 Security authorization levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
9.1.3 Security default userid and password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
9.1.4 Security commands and authorization level required. . . . . . . . . . . . . . . . . . . . 9-3
9.1.5 Security commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
9.1.5.1 Creating a userid, password and privilege for a user . . . . . . . . . . . . . . . . 9-9
9.1.5.2 Modifying passwords and privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
9.1.5.3 Deleting a userid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
9.1.5.4 Inhibiting a userid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
9.1.5.5 Allowing a userid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
9.1.5.6 Retrieving a list of active users and cancelling a users TL1 session . . . 9-14
9.1.6 Common user commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
9.1.6.1 Logging in to a TL1 session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
9.1.6.2 Cancelling a TL1 session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
9.1.6.3 Editing a users own password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
9.1.6.4 Retrieving a users own security credentials. . . . . . . . . . . . . . . . . . . . . . 9-18
9.2 Log management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
9.2.1 Log management history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
9.2.2 About logs on the Netstender. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
9.2.3 Standard log commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
9.2.3.1 Retrieving logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
9.2.3.2 Stopping logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
9.2.3.3 Starting logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
9.2.3.4 Initializing logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
9.2.3.5 Retrieving log attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
9.2.4 Security log commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
9.2.4.1 Retrieving security log attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
9.2.4.2 Setting security log attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30
9.3 Protection switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31
9.3.1 Protection switching severity levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31
9.3.2 User-invoked protection switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
9.4 Software load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34
9.5 Database backup and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-35
9.5.1 Database backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-35
9.5.2 Database restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
9.6 Restarting a circuit pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-45
9.7 Performing a loopback test through an SFP, XFP or MSA transceiver on a Wavelength
Conversion circuit pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-47
9.7.1 How to tell when an SFP, XFP or MSA transceiver port on a Wavelength
Conversion circuit pack is in loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49
9.7.1.1 RTRV-XCVR command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49
9.7.1.2 RTRV-COND-ALL command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49
9.8 Performing a loopback test through a port on a Muxponder circuit pack . . . . . . . 9-50
9.8.2 How to tell when a port on a Muxponder circuit pack is in loopback . . . . . . . 9-53
9.8.2.1 RTRV-GE, RTRV-OC48, or RTRV-STM16 command . . . . . . . . . . . . . . . 9-53
9.8.2.2 RTRV-COND-ALL command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-53
x Netstender OAM&P Guide Document Version 01
Contents
9.9 Configuration profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.9.1 Creating configuration profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.9.1.1 Creating a profile online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.9.1.2 Creating a profile offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.9.2 Importing profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.9.3 Applying profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.9.4 Edit, view or delete profiles online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-54
9-55
9-55
9-56
9-57
9-58
9-59
10.0 Replacing circuit packs
10-1
10.1 Common equipment circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

10.1.1 Netstender 2060 common equipment circuit packs . . . . . . . . . . . . . . . . . . . 10-2
10.1.1.1 Netstender 2060 common equipment circuit pack locations. . . . . . . . . 10-2
10.1.1.2 Netstender 2060 Cooling Unit circuit pack . . . . . . . . . . . . . . . . . . . . . . 10-3
10.1.1.3 Netstender 2060 Main Shelf Interface circuit pack . . . . . . . . . . . . . . . . 10-6
10.1.1.4 Netstender 2060 Expansion Shelf Interface circuit pack. . . . . . . . . . . . 10-8
10.1.1.5 Netstender 2060 Multiport System Control Processor circuit pack . . . 10-10
10.1.2 Netstender 1030 common equipment circuit packs . . . . . . . . . . . . . . . . . . 10-14
10.1.2.1 Netstender 1030 common equipment circuit pack locations. . . . . . . . 10-14
10.1.2.2 Netstender 1030 Cooling Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
10.1.2.3 Netstender 1030 System Control Processor circuit pack . . . . . . . . . . 10-17
10.2 Optical supervisory channel circuit pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
10.2.1 OSC Coupler/Splitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
10.3 Wavelength conversion circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
10.3.1 SFP transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
10.3.2 10G Wavelength Regenerator XFP transceivers . . . . . . . . . . . . . . . . . . . . 10-33
10.4 Muxponder circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37
10.5 Optical amplifier circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-40
10.6 Dispersion compensating module circuit packs. . . . . . . . . . . . . . . . . . . . . . . . . 10-45
10.7 Filler circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-48
10.8 Multiplex/demultiplex module circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-50
10.9 Optical add-drop module circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-54
10.10 DWDM bi-directional coupler/splitter circuit packs . . . . . . . . . . . . . . . . . . . . . 10-57
Appendix A: Optical back reflection safety feature
A-1
A.1 Principle of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

A.1.1 Next generation OBA and SBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
A.2 Querying back-reflection photo-detector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Appendix B: Working with the configuration database
B-1
B.1 Configuration database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

B.1.1 Database backup precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
B.2 Automatic backup process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
B.3 Impact of circuit pack replacement on the database. . . . . . . . . . . . . . . . . . . . . . . . B-4
B.3.1 Recommendations when replacing circuit packs . . . . . . . . . . . . . . . . . . . . . . . B-4
B.4 Automatic restore process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
xi
Contents
B.4.1 System running current software, replace MSCP with a unit loaded with the
current software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
B.4.2 System running current software, replace MSCP with a unit loaded with an earlier
or later software load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
B.4.3 System running current software, cycle power . . . . . . . . . . . . . . . . . . . . . . . . B-5
B.5 Manual backup process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
B.6 Manual restore process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
B.7 Pre-provisioning circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
B.8 Preconfigured MSCP scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
B.9 Replacing a failed MSCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9
B.10 Replacing failed circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9
B.11 Clearing the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9
Appendix C: Universal connectors
C-1
C.1 About universal connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

C.2 Cleaning universal connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Appendix D: ESI command line interface
D-1
D.1 Expansion shelf interface access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

D.2 ESI main menu display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
D.3 ESI shelf configuration display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
D.4 ESI SFP inventory display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5
D.5 ESI SFP alarm status display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
D.6 ESI SFP digital diagnostics data display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-8
Appendix E: Contacting BTI support
E-1
E.1 Before you contact BTI support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

E.2 How to collect required information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
E.2.1 Obtaining information locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
E.2.2 Obtaining information remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3
E.2.2.1 Netstender product release number . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3
E.2.2.2 Circuit pack information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4
E.2.2.3 SFP and XFP transceiver information . . . . . . . . . . . . . . . . . . . . . . . . . . E-6
E.2.2.4 Detailed description of the problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-8
E.3 How to contact BTI support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-9
xii Netstender OAM&P Guide Document Version 01
Preface
This section explains who should read the OAM&P Guide, how the document is
organized, related documentation, document conventions, how to obtain order
documentation and how to obtain technical support.
Audience
This guide is primarily intended for technicians and network operation center
(NOC) staff. For product description, planning, commissioning, installation, alarm
clearing, troubleshooting or Transaction Language 1 (TL1) information see
Organization of the Netstender documentation.
Product Release 6.2 STANDARD xiii
Preface
Revision History
The following table tracks the revision history for each product release
modification to this document.
Document Revision History
Release
Date
Modifications
1.0
1.1
March 2003
August 2003
This document is released.

Added the Revision History to the Preface of this document.
Added the following power monitor tap circuit packs: PMT1 and
PMT2.
Added the SMF 40 km dispersion compensating fiber module circuit
pack.
Added section 4.11, Installing power monitor taps.
Added the following new equipment AIDs: PMT1, PMT2, and
SMF40.
Added section 4.8, Power monitor tap provisioning.
Added the PM Parameter History to the Netstender performance
monitoring chapter in this document.
Added the operator interrupt q to the RTRV-LOG command.
Added the LASERSTATUS parameter in the RTRV-OA message.
Added section section 10.10, Power monitor tap circuit packs.
Added Appendix E: Contacting BTI support.
Updated the circuit pack state transition diagram.
Updated Figure 3-11, Netstender 2060 LED behavior.
Updated the content for sections 7.1, How Netstender provisioning
works, 7.2, Hierarchical organization of Netstender components,
7.3, Designating names and IDs to system components, and 7.7,
Optical amplifier provisioning.
Updated section 9.1.4, Security commands and authorization level
required.
Removed the INVK-SCP-LOAD command that is now replaced by
the INVK-SCP-RELNUM command.
Removed the LASERMDE parameter from the following commands:
ED-OA, ENT-OA, and RTRV-OA.
xiv Netstender OAM&P Guide Document Version 01
Preface

Release
Date
Modifications
2.1
March 2004
The former Optical Link System (OLS) is rebranded as the

Netstender. In general, former occurrences of OLS are replaced by
the term NETSTENDER.
Added the following equipment to all applicable descriptions and
procedures:
- 1-, 2- and 4-Channel DWDM OADMs
- 4- and 32-Channel DWDM Multiplexer/Demultiplexers
- 1-Channel CWDM OADMs
- 8-Channel CWDM Multiplexer/Demultiplexer
- CWDM and DWDM Splitter/Combiner
- Blue, Red and Wideband CWDM Line Amplifiers
- Optical Supervisory Channel
- Single-channel Pre-Amplifier
Added the following shelf configuration (SHCONF) values for the
message syntax of the RTRV-INV command: 4-SLOT and 5-SLOT.
Added additional state transitions to the Circuit Pack State Transition
Diagram in Chapter 2.
Added the GATEWAY parameter to the ED-SYS and RTRV-SYS
commands.
Added the following LAN AIDs: IP-NMS and IP-CRAFT.
Added D1ADM, D2ADM, D4ADM, D32MD, C1ADM, C8MD, CDSC,
CLAB, CLAR, CLAW, OSC and SPA as valid equipment to all
applicable descriptions and procedures.
Added replacement procedures for the Multiplex/Demultiplex circuit
packs.
Add CWDM Line Amplifier Blue, CWDM Line Amplifier Red, CWDM
Line Amplifier Wideband and DWDM Single Channel Pre-Amplifier
as valid amplifier types for the optical amplifier circuit pack
replacement procedure.
The following PM parameters are added:
EFFGAIN_B
EFFGAIN_R
OPR_B
OPR_R
OPT_B
OPT_R
INNONUNICAST
INUNICAST
IPFWDDATA
IPINRX
IPOUTREQ
OUTNONUNICAST
OUTINICAST
The following PM parameters are changed:
PL1TEMP changes to L1TEMP
PL2TEMP changes to L2TEMP
PL1CUR changes to L1CUR
PL2CUR changes to L2CUR
PL1PWR changes to L1PWR
PL2PWR changes to L2PWR
Product Release 6.2 STANDARD xv
Preface

Release
Date
Modifications
2.1
March 2004
2.1
2.1
April 2004
May 2004
2.2
August 2004
2.2
Sept. 2004
Changed the name Graphical Craft Interface (GCI) to Netstender

Node Controller (NNC).
Changed ED-DAT command so that either the date or time
parameters can now be edited separately without the need to specify
both parameters.
Changed the date field for all TL1 headers from YYYY-MM-DD to
YY-MM-DD (for example, 2004-12-15 becomes 04-12-15).
Removed the GATEWAY parameter from the ED-IP and RTRV-IP
commands.
Removed the SHCONF parameter from the following commands:
ED-EQPT, ENT-EQPT and RTRV-EQPT.
Removed the following log commands: ALW-LOG-SECU,
INH-LOG-SECU, and INIT-LOG-SECU.
Note: For some special customer loads, refer to the included
addendum for specific TL1 modifications to the REPTÂLM and
REPTÊVT message formats.
Minor corrections and updates are incorporated to the document.
Added a description of the effects the INIT-SYS command has on an
SCP circuit pack.
Added the Optical Component Tray (OCT) circuit pack installation
procedure.
Added the Optical Component Tray (OCT) circuit pack replacement
procedure.
"<aid>,<state>"
procedures:
- Single-channel/Sub-band Booster Amplifier
Added the following commands: DLT-ARP-PROXY,
ENT-ARP-PROXY, OPR-OBR-HTSO, RTRV-ARP-ALL, and
RTRV-ARP-PROXY TL1 commands.
Added a section called Using the OPR-OBR-HTSO command.
Increased to number of concurrent TL1 sessions to 24 and the
number of unique userids to 50.
Restricted the number of active TL1 sessions per userid to one.
Modified the REPT^RMV and REPT^RST commands by changing
the format of <aid>,<state> to <aid>:<state>.
Updated the Telcordia state model information in Chapter 2.
Updated the In-service shelf reconfiguration procedure.
xvi Netstender OAM&P Guide Document Version 01
Preface

Release
Date
Modifications
2.3
Dec. 2004
3.0
Dec. 2004
3.1
April 2005

procedures:
- Dispersion Compensating Fiber Module 30 km
- 2-Port Connectorized Power Monitor Tap 1%
- Single ASE Noise Filter
- SMF Single Channel DCM 40 km
- System Control Processor (with 1 Expansion Shelf Connector)
Added Appendix A: Universal connectors.
Modified the restrictions of a userid and password from being the
same string. For example, the userid george cannot have a
password of george.
procedures:
- Netstender 1030 Shelf
- Netstender 1030 System Control Processor
- Netstender 1030 Cooling Unit
Added a prerequisite to the Database Restore procedure in
Chapter 6.
Modified the use of the CTAG in all TL1 commands. The CTAG is
now optional.
Added LPBK as a valid secondary state.
Added a procedure for installing wavelength conversion circuit
packs.
Added provisioning information for the following:
- wavelength conversion circuit packs
- SFP transceiver ports
- Cross-connects
Added the following new performance monitoring (PM) parameters:
- LBC
- SUPPLY
- TEMP
Product Release 6.2 STANDARD xvii
Preface

Release
Date
Modifications
3.1 contd
April 2005
3.1
May 2005
3.1
June 2005
3.1.1
July 2005
Added the following new TL1 commands to the table in Chapter 9.0,
Administering the Netstender:
- DLT-CRS-XCVR
- DLT-XCVR
- ED-XCVR
- ENT-CRS-XCVR
- ENT-XCVR
- OPR-LPBK-TST
- RLS-LPBK-TST
- RMV-XCVR
- RST-XCVR
- RTRV-ALM-XCVR
- RTRV-COND-XCVR
- RTRV-CRS-XCVR
- RTRV-PM-XCVR
- RTRV-XCVR
Added the following replacement procedures:
- Wavelength translator/regenerator circuit packs
- SFP transceivers
Removed the BP1A26AA and BP1A26BA Power Monitor Tap circuit
packs as their manufacture is discontinued.
Added a restriction to the procedure for installing wavelength
translator/regenerator circuit packs.
Added the Optical Line Amplifier (OLA) and Optical Line Amplifier
with Mid-stage access (OLAM) as being supported by the
OPR-OBR-HTSO command.
Updated the PROTOCOL parameter for the ED-XCVR, ENT-XCVR
and RTRV-XCVR commands to include the following values: STM1,
STM4 and STM16.
xviii Netstender OAM&P Guide Document Version 01
Preface

Release
Date
Modifications
4.1
May 2006
5.1
Dec. 2006
Added the following chapters:

- 5.0, Connecting circuit packs
- 6.0, Connecting expansion shelves
Added the following appendices:
- Appendix A: Optical back reflection safety feature
- Appendix B: Working with the configuration database
- Appendix D: ESI command line interface
Added the following sections:
- 3.6, Establishing an expansion shelf interface CLI session
- 9.9, Configuration profiles
Added a default backup file name to the INVK-DB-BKUP command
in Chapter 9.0, Administering the Netstender.
Added the following commands to section 9.1.4, Security
commands and authorization level required:
- CMMT-ES
- DLT-FFP-XCVR
- ED-AMD
- ED-FFP-XCVR
- ENT-FFP-XCVR
- INIT-REG-XCVR
- OPR-PROTNSW-XCVR
- RLS-PROTNSW-XCVR
- RMV-AMD
- RST-AMD
- RTRV-ALM-AMD
- RTRV-AMD
- RTRV-AUTOD
- RTRV-COND-AMD
- RTRV-FFP-XCVR
- RTRV-PM-AMD
- RTRV-TH-XCVR
- SET-TH-XCVR
Divided Chapter 3 into two separate chapters:
- 3.0, Operating the Netstender
- 4.0, Installing optional Netstender circuit packs
Updated the authorization required to ALL for the following
commands: RTRV-ALM-SECU and RTRV-COND-SECU.
Updated the hardware illustrations to reflect the latest design
improvements to the circuit packs.
- the section on Compliance in the Preface
- 7.1.1.7, Wavelength manager ports
- Appendix E: Transport overhead bytes for wavelength manager
Updated the following sections:
- 1.3.5, Wavelength conversion
- 2.4, Equipment state management
- 2.6, Wavelength conversion transceiver port state management
- 3.7.5, Audible alarms and office alarms
- 3.8.2, Subordinate elements AID
- 4.3, Installing wavelength conversion circuit packs
- 4.3.1, Installing SFP transceivers
Product Release 6.2 STANDARD xix
Preface

Release
Date
Modifications
5.1
(contd)
Dec. 2006
- 7.1.1.6, Wavelength conversion circuit packs

- 7.9.1, Provisioning wavelength conversion circuit pack equipment
- 7.9.2, Provisioning transceiver ports
- 7.9.2.1, Retrieving a manufacturers SFP/XFP transceiver
inventory information
- 7.9.2.2, Provisioning transceiver ports
- 7.9.2.3, Implementing advanced provisioning features
- 7.9.2.4, Modifying the definable parameters of a transceiver port
- 7.9.2.5, Removing a transceiver port from service
- 7.9.2.6, Restoring a transceiver to service
- 7.9.2.7, Retrieving transceiver attributes
- 7.9.2.8, Deleting a transceiver
- 7.9.3.1, Provisioning cross-connects on a Wavelength Conversion
circuit pack
- 7.9.3.3, Deleting a cross-connect on a Wavelength Conversion
circuit pack
- 7.9.4.2, Provisioning rules
- 7.9.4.3, Example scenarios
- 8.1.1, PM parameter history
- 8.1.2, PM parameters
- 8.1.3, Bin validity qualifiers
- 8.1.4, Threshold crossing alerts
- 8.2.1, PM retrieval command
- 8.2.2.1, Example one
- 9.5.1, Database backup
- 9.6, Restarting a circuit pack
- 9.7, Performing a loopback test through an SFP, XFP or MSA
transceiver on a Wavelength Conversion circuit pack
- 9.7.1, How to tell when an SFP, XFP or MSA transceiver port on a
Wavelength Conversion circuit pack is in loopback
- 10.1.1.2, Netstender 2060 Cooling Unit circuit pack
- 10.3, Wavelength conversion circuit packs
- 10.3.1, SFP transceivers
xx Netstender OAM&P Guide Document Version 01
Preface

Release
Date
Modifications
5.2
June 2007
Added a note to section 7.1.1.1, Controlling auto provisioning.

Added a note to section 7.4.1.1, Editing the network element, site,
and time zone regarding the new North American daylight saving
time rules activation.
Added a note about OSC IP interfaces to 7.6.7, Deleting
equipment.
Added new performance metrics for the GE, STM-16, OC-3, and
OC-12 optical transceivers.
Updated the command syntax of the ENT-XCVR command in
section 7.9.2.2, Provisioning transceiver ports.
Updated the parameters PROTOCOL, LASERSTATUS, OPTLT,
OPTHT, OPRLT, and OPRHT in Table 7-16, Transceiver port
parameters.
Added a note to the parameter FPSD in Table 7-16, Transceiver
port parameters and in Table 7-19, Transceiver parameters.
Removed the footnote at Table 7-16, Transceiver port parameters
and at Table 7-19, Transceiver parameters.
Updated the parameters PROTOCOL, LASERSTATUS, OPTLT,
OPTHT, OPRLT, and OPRHT in Table 7-19, Transceiver
parameters.
Modified the rules for FPSD settings and laser status in
7.9.2.3, Implementing advanced provisioning features.
Modified the note about the PHYPMMON parameter in 7.9.2.3,
Implementing advanced provisioning features.
Updated the note in 7.9.2.4, Modifying the definable parameters of
a transceiver port.
Updated Release 5.2 in Table 8-1, PM parameter history.
Added the following parameters to Table 8-2, PM parameters:
- CV
- RS-BBE
- RS-EB
- RS-ES
- RS-OFS
- RS-SES
- SEFS
Product Release 6.2 STANDARD xxi
Preface

Release
Date
Modifications
5.2
(contd)
June 2007
Updated the following parameters in Table 8-2, PM parameters:

- CVS
- ES
- ESS
- OPR
- OPT
- SEFS-S
- SES
- SESS
Removed the parameters FRC, FRER, and TFRC from Table 8-2,
PM parameters.
Added DWDM Bi-Directional Coupler/Splitter to 1.3.2, Optical
multiplexing, 2.4, Equipment state management, and Table 3-1,
Netstender Access Identifier Structure.
Added 4 Channel DWDM OADM Channels 53, 55, 57, 59 to 1.3.2,
Optical multiplexing and 4.5, Installing optical add-drop module
circuit packs.
Updated the note about cooling-unit support for the 2-port 10G
Wavelength Regenerator in 4.3, Installing wavelength conversion
circuit packs.
Added the topic 4.8, Installing DWDM bi-directional coupler/splitter
circuit packs.
Updated 9.6, Restarting a circuit pack to include the 2-Port 10G
Wavelength Regenerator, and updated a note.
Updated 10.1.1.2, Netstender 2060 Cooling Unit circuit pack to
include BP1A52CA.
Updated 10.3, Wavelength conversion circuit packs to include the
2-Port 10G Wavelength Regenerator, and deleted a note.
Added notes to step 6 in the procedure Replacing an SFP or XFP
transceiver in 10.3.1, SFP transceivers.
Added the topic DWDM bi-directional coupler/splitter circuit packs
to chapter 10.0, Replacing circuit packs.
Removed the topic Optical Component Tray circuit packs from
chapter 10.0, Replacing circuit packs.
Updated image of 32 Channel DWDM Mux/Demux circuit pack in
10.8, Multiplex/demultiplex module circuit packs.
Changed management LAN to craft LAN in step 3 of the
procedure in 3.2.2, Method Two: Connecting through the craft LAN
port.
Removed SMF Single-Channel DCMs 40 km/60 km/80 km from the
list in 4.9, Installing dispersion compensation module circuit packs.
Added DWDM Bi-Directional Coupler/Splitter (CS) to Table 7-2,
Application circuit packs.
Removed Power Monitor Taps 2% (PMT2) from Table 7-2,
Application circuit packs.
xxii Netstender OAM&P Guide Document Version 01
Preface

Release
Date
Modifications
5.2
(contd)
June 2007
Added DWDM Bi-Directional Coupler/Splitter to the list in 7.12,

Provisioning non-powered circuit pack ports.
Removed SMF Single-Channel DCMs from the list in 7.12,
Removed PMT2 from the entry for Power Monitor Taps in 7.12,
Added the AID CS-(1,11,21,31)-(1-6)-(1-2) to step 1 of the procedure
in 7.12.1, Modifying the parameters of a port.
Removed the AID PMT2-(1,11,21,31)-(1-6)-(1-4) from step 1of the
procedure in 7.12.1, Modifying the parameters of a port.
Added the AID CS-(1,11,21,31)-(1-6)-(1-2) to step 1 of the procedure
in 7.12.2, Retrieving the parameters of a port.
Removed the AID PMT2-(1,11,21,31)-(1-6)-(1-4) from step 1 of the
procedure in 7.12.2, Retrieving the parameters of a port.
Added a note about the 10G Wavelength Regenerator to 9.7.1.1,
RTRV-XCVR command.
Changed the number of types of 4 Channel DWDM OADM from 8 to
9 in 10.9, Optical add-drop module circuit packs.
Added the following to the list in 10.2.1, OSC Coupler/Splitters:
- OSC Double Coupler/Splitter 1510 nm
- OSC Double Coupler/Splitter 1510 nm/1610 nm
- OSC Double Coupler/Splitter 1610 nm
- OSC Single Coupler/Splitter 1510 nm
- OSC Single Coupler/Splitter 1610 nm
Updated the authorization-level requirements for the commands
RTRV-ALM-SECU and RTRV-COND-SECU in Table 9-2, Security
commands and authorization level required.
Product Release 6.2 STANDARD xxiii
Preface

Release
Date
Modifications
6.1
September
2007
Added the following to 1.3.2, Optical multiplexing and 2.4,

Equipment state management:
- 2-Port GE Muxponder - SONET
- 2-Port GE Muxponder - SDH
- 4-Channel CWDM Mux/Demux
- 2-Channel CWDM OADM
- Double 1-Channel OADM
- Double DWDM Red/Blue Coupler/Splitter
- Single 50/50 3dB Coupler Splitter
- 32-Channel DWDM Active Mux/Demux Modules 2 to 4
Removed the following from 1.3.2, Optical multiplexing, 2.4,
Equipment state management, and Table 7-2, Application circuit
packs:
- 8-Channel CWDM Mux/Demux (C8MD1, C8MD2)
- 1-Channel CWDM OADM (C1ADM)
Added information about the 10G Wavelength Regenerator to 1.3.5,
Wavelength conversion.
Added 2-Port GE Muxponder - SONET and 2-Port GE Muxponder SDH to 2.7, State management behavior interactions.
Added the following to Table 3-1, Netstender Access Identifier
Structure:
- 2-Port GE Muxponder
- Double DWDM Red/Blue Coupler Splitter
Removed AIDs for C8MD1, C8MD2, and PMT2 from Table 3-1,
Netstender Access Identifier Structure.
Updated the note about installation requirements for the cooling unit
and the 10G Wavelength Regenerator in 4.3, Installing wavelength
conversion circuit packs.
Added the section 4.4, Installing Muxponder circuit packs.
Added 2-Channel N+1 CWDM OADM and Double 1-Channel OADM
to 4.5, Installing optical add-drop module circuit packs.
Added the following to 4.7, Installing multiplexer/demultiplexer
circuit packs:
Removed 8-Channel CWDM Mux/Demux (C8MD1, C8MD2) from
4.7, Installing multiplexer/demultiplexer circuit packs.
Updated a note about the width of the 8-Channel CWDM Mux/
Demux and the 32-Channel DWDM Mux/Demux in 4.7, Installing
multiplexer/demultiplexer circuit packs.
Added Wavelength Manager to the heading For SDH customers
only in 7.1.1.1, Controlling auto provisioning.
xxiv Netstender OAM&P Guide Document Version 01
Preface

Release
6.1
(contd)
Date
Modifications
Added the topics 7.1.1.8, Muxponder circuit packs and 7.1.1.9,
Muxponder circuit pack ports to 7.1.1, Auto provisioning.
Updated Table 7-15, Manufacturers SFP and XFP transceiver
parameters as follows:
- Updated the range of values for the CONNTYPE parameter.
- Corrected the XFP AID in the range of values for the AID
parameter.
Added the following to Table 7-2, Application circuit packs:
- Muxponder Modules
- 32 Channel DWDM Active Mux/Demux Modules 2 to 4
Updated Table 7-16, Transceiver port parameters as follows:
- Added 10GELANFEC, OC192FEC, and STM64FEC to the range of
the PROTOCOL parameter.
- Updated a note about the range of protocols the 10G Wavelength
Regenerator supports for the PROTOCOL parameter.
- Added a cross-reference to Table 7-17, Protocols supported on
10G Wavelength Regenerator ports to the description of the
PROTOCOL parameter.
- Added ODU2-AIS to the range of the LASERSTATUS parameter,
and a note about the protocols this value applies to.
-Removed the parameter CMDMDE.
Updated 7.9.2.2, Provisioning transceiver ports as follows:
- Changed heading SFP parameters to Transceiver parameters
- Added Table 7-17, Protocols supported on 10G Wavelength
Regenerator ports.
- Removed the parameter CMDMDE from the command syntax for
ENT-XCVR.
Added a rule for FPSD and the protocols 10GELANFEC,
OC192FEC, and STM64FEC to FPSD and laser status in
7.9.2.3, Implementing advanced provisioning features.
Added 10GELANFEC, OC192FEC, and STM64FEC to the protocol
parameter in 7.9.2.4, Modifying the definable parameters of a
transceiver port.
Updated Table 7-19, Transceiver parameters as follows:
- Added 10GELANFEC, OC192FEC, and STM64FEC to the range of
the PROTOCOL parameter.
- Updated a note about the range of protocols the 10G Wavelength
Regenerator supports for the PROTOCOL parameter.
- Added a cross-reference to Table 7-17, Protocols supported on
10G Wavelength Regenerator ports to the description of the
PROTOCOL parameter.
- Added ODU2-AIS to the range of the LASERSTATUS parameter,
and a note about the protocols this value applies to.
Product Release 6.2 STANDARD xxv
Preface

Release
6.1
(contd)
Date
Modifications
Added 10GELANFEC, OC192FEC, and STM64FEC to the range of
the PROTOCOL parameter in 7.9.2.4, Modifying the definable
parameters of a transceiver port.
Added section 7.10, 2-Port GE Muxponder provisioning.
Added the following to 7.12, Provisioning non-powered circuit pack
ports:
Removed the following from 7.12, Provisioning non-powered circuit
pack ports:
- CWDM Mux/Demux (C8MD1, C8MD2)
- CWDM OADM (C1ADM)
Updated the range of values for the AID parameter in 7.12.1,
Modifying the parameters of a port and in 7.12.2, Retrieving the
parameters of a port.
Updated the range of values for the WAVELENGTH parameter in
7.12.2, Retrieving the parameters of a port.
Updated Table 8-1, PM parameter history.
Updated Table 8-2, PM parameters as follows:
- Updated the following parameters: CVS, ES, ESS, SEFS, SEFS-S,
SES, and SES-S.
- Added the following parameters: CV-P, ES-P, FC-P, FCSE-RX,
FRDR, HP-BBE, HP-EB, HP-ES, HP-UAS, HP-SES, NUMBITSCR,
NUMBYTESCR, SES-P, TFRC-RX, TRFC-TX, UAS-P, and
UNCRCDWRD.
Updated Table 8-10, Threshold crossing alerts and their associated
protocols as follows:
- Added the protocols 10GELANFEC, OC192FEC, and STM64FEC.
- Added FCSE-RX and FRDR to the GE protocol.
- Updated the range of values for the protocol STM-64.
Removed a note about the parameter SES-S and threshold crossing
alerts from 8.1.4, Threshold crossing alerts.
Added Muxponder-related commands to 8.2.1.1, Other PM retrieval
commands.
Removed a note referring to warm and cold restarts of the WR10G
circuit pack from 9.6, Restarting a circuit pack.
Added all Muxponder-related commands to Table 9-2, Security
commands and authorization level required.
Removed a note about cold and warm restarts of the 10G
Wavelength Regenerator from 9.6, Restarting a circuit pack.
Added section 9.8, Performing a loopback test through a port on a
Muxponder circuit pack.
Updated the procedure for replacing an XFP transceiver in
10.3.2, 10G Wavelength Regenerator XFP transceivers.
Added section 10.4, Muxponder circuit packs.
xxvi Netstender OAM&P Guide Document Version 01
Preface

Release
Date
6.1
(contd)
6.2
January 2008
Modifications
Added two steps (2 and 9) to the procedure for replacing XFPs in
10.3.2, 10G Wavelength Regenerator XFP transceivers.
Added the following to 10.8, Multiplex/demultiplex module circuit
packs:
Added 2-Channel N+1 CWDM OADM and Double 1-Channel OADM
to 10.9, Optical add-drop module circuit packs.
Added a rule for provisioning protection switching on a 2.5G
Wavelength Regenerator to 7.9.4.2, Provisioning rules.
Added information about Extended Temperature Operation to
Compliance.
Removed Optical Booster Amplifier (OBA) and Optical Pre-Amplifier
(OPA) from 1.3.1, Optical amplification.
Removed 8-Channel CWDM Multiplexer/Demultiplexer (C8MD),
Double DWDM Red/Blue Coupler/Splitter (CS), and 50/50 3dB
Coupler/Splitter (CS) from 1.3.2, Optical multiplexing.
Removed reference to Single ASE Noise Filter from 1.3.3, Optical
signal conditioning.
Updated 1.3.5, Wavelength conversion as follows:
- Updated the description of the 10G Wavelength Regenerator.
- Modified the reference to the availability of Wavelength
Regenerator modules with protection.
Added information about support for pass-through crossconnections to 1.3.6, Muxponder modules.
Removed the following from 2.4, Equipment state management:
- DWDM Optical Booster Amplifier
- DWDM Optical Pre-Amplifier
- Double DWDM Red/Blue Coupler Splitter (CS)
- 4-Port 1G Wavelength Regenerator with Protection
- 4-Port 2.5G Wavelength Regenerator with Protection
- Power Monitor Tap
- Dispersion Compensating Fiber Modules SMF5, SMF10, SMF15,
SMF30
Removed Optical Booster Amplifier (OBA) and Optical Pre-Amplifier
(OPA) from 2.5, Amplifier entity state management.
Removed 4-Port 1G Wavelength Regenerator with Protection and
4-Port 2.5G Wavelength Regenerator with Protection from 2.6,
Wavelength conversion transceiver port state management.
Updated Table 3-1, Netstender Access Identifier Structure as
follows:
- Removed AIDs for 8-Channel CWDM Mux/Demux (C8MD); Single
ASE Noise Filter (NF); Power Monitor Tap (PMT1); Dispersion
Compensating Fiber Modules SMF5, SMF10, SMF15, and SMF30;
Double DWDM Red/Blue Coupler/Splitter (CS); and Single 50/50
3dB Coupler Splitter (CS).
Product Release 6.2 STANDARD xxvii
Preface

Release
6.2
Date
Modifications
Removed DWDM Optical Booster Amplifier and DWDM Optical PreAmplifier from 4.1, Installing optical amplifier circuit packs.
Updated 4.3, Installing wavelength conversion circuit packs as
follows:
- Added BP1A47BB to all WR10G PEC references.
- Removed 4-Port 1G Wavelength Regenerator with Protection and
4-Port 2.5G Wavelength Regenerator with Protection, and added
corresponding PEC to 4-Port 1G Wavelength Regenerator and 4Port 2.5G Wavelength Regenerator.
- Removed section on cross-connections.
Removed 8-Channel CWDM Mux/Demux, Double DWDM Red/Blue
Coupler/Splitter, and 50/50 3dB Coupler/Splitter from 4.7, Installing
multiplexer/demultiplexer circuit packs.
Removed the following topics from 4.0, Installing optional
Netstender circuit packs:
- Installing noise filter circuit packs
- Installing power monitor tap circuit packs
Removed the topic Connecting fiber between an amplifier and a
PMT from 5.0, Connecting circuit packs.
Removed the following from Table 7-2, Application circuit packs:
- Optical Booster Amplifier
- Optical Pre-Amplifier
- Double DWDM Red/Blue Coupler/Splitter
- Single 50/50 3dB Coupler/Splitter
- Dispersion Compensating Fiber modules SMF5, SMF10, SMF15,
and SFM30
- Power Monitor Tap
Removed the following from Table 7-4, Required optical amplifier
circuit pack information:
- DWDM Optical Pre-Amplifier (BP1A01AA)
- DWDM Optical Booster Amplifier (BP1A02AA)
- Single Channel Pre-Amplifier (BP1A05PA)
- Single Channel Booster Amplifier (BP1A05BA)
Removed the following PECs from 7.7.1, Provisioning an optical
amplifier and 7.7.6, Deleting an optical amplifier: BP1A01AA,
BP1A02AA, BP1A05BA, and BP1A05PA.
Removed the following PECs from Table 7-6, Operation
parameters, Table 7-7, Alarm thresholds, Table 7-9, Operation
parameters, and Table 7-10, Alarm thresholds: BP1A01AA,
BP1A02AA, BP1A05BA, and BP1A05PA.
Added BP1A47BB to the range of values for the TYPE parameter in
7.9.1, Provisioning wavelength conversion circuit pack equipment.
Updated Table 7-16, Transceiver port parameters and Table 7-19,
Transceiver parameters as follows:
- Added a note to the WAVELENGTH parameter.
- Added a note to the PHYPMMON parameter.
xxviii Netstender OAM&P Guide Document Version 01
Preface

Release
6.2 contd
Date
Modifications
Added Table 7-18, BTI-supported wavelengths for a tunable 10G
Wavelength Regenerator.
Updated the section Transceiver parameters in Provisioning
transceiver ports.
Updated the section Purpose in Modifying the definable
parameters of a transceiver port.
Added information about pass-through cross-connections on a
Muxponder circuit pack to the following sections:
- 7.10.9.1, Provisioning a cross-connection on a Muxponder circuit
pack
- 7.10.9.2, Retrieving cross-connection information from a
Muxponder circuit pack
7.10.9.3, Deleting a cross-connection on a Muxponder circuit pack
Updated VCG index values in the following sections:
- 7.10.6, Provisioning OC-48 line side ports
- 7.10.7, Provisioning STM-16 line side ports
- 7.10.8, Retrieving Virtual Concatenation Group attributes
Removed the following from 7.12, Provisioning non-powered circuit
pack ports:
- 8-Channel CWDM Mux/Demux (C8MD)
- Double DWDM Red/Blue Coupler/Splitter (CS)
- Single 50/50 3dB Coupler/Splitter (CS)
- Power Monitor Tap (PMT1)
- Dispersion Compensating Fiber Modules SMF5, SMF10, SMF15,
and SMF30
Removed AIDs for the following circuit packs from 7.12.1, Modifying
the parameters of a port and 7.12.2, Retrieving the parameters of a
port:
- 8-Channel CWDM Mux/Demux (C8MD)
- Double DWDM Red/Blue Coupler/Splitter (CS)
- Single 50/50 3dB Coupler/Splitter (CS)
- Power Monitor Tap (PMT1)
- Dispersion Compensating Fiber Modules SMF5, SMF10, and
SMF15, SMF30
Replaced table 8-2 PM parameters with the following tables:
- Table 8-2, PM Montypes: optical amplifier modules
- Table 8-3, PM Montypes: OSC modules
- Table 8-4, PM Montypes: IP Interface on OSC modules
- Table 8-5, PM Montypes: transceiver ports on WT, WM, and WR
modules
- Table 8-6, PM Montypes: 2.5G Wavelength Manager modules
- Table 8-7, PM Montypes: 10G Wavelength Regenerator modules
- Table 8-8, PM Montypes: 2-Port GE Muxponder modules
- Table 8-9, PM Montypes: DWDM active mux/demux modules
Product Release 6.2 STANDARD xxix
Preface

Release
6.2 contd
Date
Modifications
Added the following PMs to Table 8-7, PM Montypes: 10G
Wavelength Regenerator and Tunable 10G Wavelength
Regenerator modules: BCST, FRDR, FRGT, JABR, MCST,
TBYC-RX, OSIZE, OVER1518, PKTS, SESS, SIZE64, SIZE65-127,
SIZE128-255, SIZE256-511, SIZE512-1023, SIZE1024-1518,
USIZE.
Added a description to the HP-UAS parameter in 8.1.2.6, 2-Port GE
Muxponder modules.
Updated the TCAs for the protocols 10GELAN, 10GELANFEC,
OC192FEC, STM64FEC, and OC-192 in Table 8-10, Threshold
crossing alerts and their associated protocols.
Added the following commands to Table 9-1, Authorization levels:
DLT-NGBR, ED-NGBR, ENT-NGBR, and RTRV-NGBR.
Added a note to step 2 in the procedure in 9.7, Performing a
loopback test through an SFP, XFP or MSA transceiver on a
Wavelength Conversion circuit pack.
Removed DWDM Optical Booster Amplifier and DWDM Optical PreAmplifier from 10.5, Optical amplifier circuit packs.
Removed Dispersion Compensating Fiber Modules SMF5, SMF10,
SMF15, and SMF30 from 10.6, Dispersion compensating module
circuit packs.
Removed Double DWDM Red/Blue Coupler/Splitter (CS) and Single
50/50 3dB Coupler/Splitter from 10.8, Multiplex/demultiplex module
circuit packs.
Removed OSC Single Coupler/Splitter 1610nm from 10.2.1, OSC
Coupler/Splitters.
Removed the topics Power monitor tap circuit packs and Noise
filter circuit packs from 10.0, Replacing circuit packs.
Removed Power Monitor Tap circuit packs and ASE Noise Filter
circuit packs from list of circuit packs in 7.1.3, Pre-provisioning.
Added 1-Channel CWDM OADM (C1ADM) to the following sections:
- 1.3.2, Optical multiplexing
- 2.4, Equipment state management
- Table 3-1, Netstender Access Identifier Structure
- 4.5, Installing optical add-drop module circuit packs
- Table 7-2, Application circuit packs
- 7.12, Provisioning non-powered circuit pack ports
- 10.5, Optical amplifier circuit packs
Changed all occurrences of Dual GbE Muxponder to 2-Port GE
Muxponder.
Removed the topic Protection switching on 2-Port GE Muxponder
circuit packs from Chapter 2.0, Netstender state management.
xxx Netstender OAM&P Guide Document Version 01
Preface
Compliance
FDA
This equipment is classified by the FDA under IEC 60825, parts 1 and 2, as a Class
1 laser product with a Class 1 hazard rating.
FCC
This equipment complies with Part 15 of the FCC rules. Operation is subject to the
following two conditions: (1) This device may not cause harmful interference, and
(2) This device must accept any interference received, including interference that
may cause undesired operation.
Industry Canada
This Class A digital apparatus complies with Canadian ICES-003.

Extended Temperature Operation
The following BTI modules have been tested and are compliant with the industrial
temperature limit requirements (-20C to +65C) specified in GR-3108 (Generic
Requirements for Network Equipment in the Outside Plant (OSP):
2060 Main Shelf Interface
2060 Multiport System Control Processor
Cooling unit BP1A52CA
1G Wavelength Translator (WT1G)
1G Wavelength Regenerator (WR1G)
2.5G Wavelength Regenerator (WR2.5G)
2.5G Wavelength Manager (WM2.5G)
2-Port GE Muxponder (MXP2.5G)
1-Channel CWDM OADM (C1ADM)
Double 1-Channel OADM (C1ADM)
4-Channel CWDM Multiplexer/Demultiplexer (C4DM)
CWDM and DWDM Splitter Combiner (CDSC)
DWDM Multiplexer/Demultiplexer (D32MD1-4)
DWDM OADM (D1ADM, D2ADM, D4ADM)
Product Release 6.2 STANDARD xxxi
Preface
New features and upcoming product enhancements

With Release 6.2, BTI continues to focus on being the leading Optical Edge
System for delivery of Gigabit services, including 10 Gbps and Gigabit Ethernet.
In addition to the new Tunable 10 G Wavelength Regenerator module and
enhanced software features for new and upgraded modules, this release makes
available extended temperature operation for a large portion of the entire
Netstender product family.
New 10G Wavelength Regenerator module features
Tunable 10G Wavelength Regenerator module

Ethernet Layer 2 performance monitoring
As part of BTIs Transponder portfolio, the 10G Wavelength Regenerator module
is a full-featured transponder for 10GbE LAN PHY, OC-192, STM-64, and
OTU2/G.709 traffic protocols. Supporting the latest in pluggable optics
technology on the client side, the 10G Wavelength Regenerator is now offered
with a tunable MSA on the line side to support operability in DWDM applications.
The tunable line interface of the Tunable 10G Wavelength Regenerator module
provides customers with inventory and planning benefits.
With performance monitoring capabilities that now include Ethernet Layer 2, BTI
has expanded the current and historical performance metrics that operators can
retrieve from 10G Wavelength Regenerator modules to assess system performance
and network health.
New 2-Port GE Muxponder module feature
Pass-through cross-connection support on 2-Port GE Muxponder SONET

and SDH modules
BTIs 2-Port GE Muxponder module increases the fill on wavelengths and enables
flexible interconnect options with GFP to facilitate transparent interconnection
with any third-party SONET/SDH devices at a 2.5G line rate, providing a versatile
way to deliver Gigabit Ethernet on both new and existing networks.
The standards-based 2-Port GE Muxponder module, which provides GbE transport
and service delivery over SONET or SDH networks, now supports pass-through
cross-connections to selectively drop or pass through traffic in a ring
configuration. The path facilities in a pass-through cross-connection provide alarm
detection in both traffic directions.
New extended temperature operation
Release 6.2 marks the availability of a range modules tested for Outside Plant
cabinets. Compliant with the industrial temperature limit requirements (-20C to
+65C) specified in GR-3108 (Generic Requirements for Network Equipment in
xxxii Netstender OAM&P Guide Document Version 01
Preface
the Outside Plant (OSP)), the following modules extend Gigabit services and
microWDM further into the network, facilitating innovative 1U and 2U solutions
in Outside Plant operations:
2060 Main Shelf Interface
2060 Multiport System Control Processor
Cooling unit BP1A52CA
1G Wavelength Translator (WT1G)
1G Wavelength Regenerator (WR1G)
2.5G Wavelength Regenerator (WR2.5G)
2.5G Wavelength Manager (WM2.5G)
2-Port GE Muxponder (MXP2.5G)
4-Channel CWDM Multiplexer/Demultiplexer (C4DM)
CWDM and DWDM Splitter Combiner (CDSC)
DWDM Multiplexer/Demultiplexer (D32MD1-4)
DWDM OADM (D1ADM, D2ADM, D4ADM)
New software features
End-to-end system management via SNMP

BTI Node Controller (NNC) backward compatibility
BTI now provides broadened SNMP capabilities to include system upgrade,
database backup and restore, and SONET synchronization configuration
operations, in addition to more provisioning, performance monitoring, and fault
management operations.
Release 6.2 of the Node Controller software is backward compatible to support
NNC operations and upgrades for software releases 4.1, 5.1, 5.2., and 6.1
Later releases will introduce the following new modules:
10-port 10G Multi-Protocol Muxponder

Dual 10G Transponder
packetVX Ethernet Aggregation Modules
microROADM module
Product Release 6.2 STANDARD xxxiii
Preface
Organization of the Netstender documentation

The Netstender customer documentation suite includes a complete range of
installation, OAM&P and reference guides. The following diagram shows how the
Netstender documentation suite is organized:
Available customer documentation for the Netstender
Netstender Document
Description
OAM&P Guide, 6.2
This document describes the Netstender in an

overview format. It provides readers with
information about how the Netstender works,
the hardware and software components, as well
as detailed system specifications.
This document provides step-by-step
procedures about how to install and
commission a Netstender. Details about
hardware and software installation are
included, as well as how to validate particular
system configuration.
Installation and Commissioning Guide, 6.2
xxxiv Netstender OAM&P Guide Document Version 01
Preface
Netstender Document
Description
Operations, Administration, Maintenance and

Provisioning Guide, 6.2
This document explains how to operate and

administer the Netstender. Procedures are
provided to explain how to use the TL1
interface, what security issues need to be
considered and how to monitor the
performance of the system.
This document explains how to clear
Netstender alarms, replace circuit packs and
troubleshoot faults that can occur.
This card is a useful job aid to assist
experienced users in troubleshooting alarms.
This document describes the proper use of TL1
commands and how to use them. Many
examples are provided to illustrate the
versatility of the TL1 interface.
This document describes OSC network
topologies and configuration examples for
standard OSC applications.
This document provides instructions on how to
install, provision and manage the OSC using
the Netstender GUI.
This document details the Netstender SNMP
implementation.
This document describes new features and lists
known product limitations contained in this
release.
Alarm and Troubleshooting Guide, 6.2
Alarm Troubleshooting Reference Card, 6.2

TL1 Reference Guide, 6.2
OSC Networking Guide, 6.2
OSC Operations, Administration, Maintenance

and Provisioning Guide, 6.2
SNMP Reference Guide, 6.2
Release Notes, 6.2
Organization of this guide

Chapter
Description
Chapter 1, Netstender overview
Chapter 1 provides an introduction to the

operations, administration, maintenance and
provisioning aspects of the Netstender 2060.
Chapter 2 discusses various aspects of state
management as it relates to the Netstender
Chapter 3 discusses the operational aspects of
the Netstender.
Chapter 4 explains how to install optional
Netstender circuit packs.
Chapter 2, Netstender state management

Chapter 3, Operating the Netstender
Chapter 4, Installing optional Netstender circuit
packs
Chapter 5, Connecting circuit packs
Chapter 6,Connecting expansion shelves
Chapter 7, Provisioning the Netstender
Chapter 5 explains how to connect various

circuit packs together.
Chapter 6 explains how to connect expansion
shelves to a Netstender system.
Chapter 7 explains how to provision the
Netstender and how to perform provisioning
related activities.
Product Release 6.2 STANDARD xxxv
Preface
Organization of this guide (Continued)

Chapter
Description
Chapter 8, Netstender performance

monitoring
Chapter 8 discusses performance monitoring

and how to start and stop monitoring, how to
retrieve data and how to transfer performance
monitoring statistics.
Chapter 9 explains how to understand and
manage security issues, manage logs, manage
software, and perform backups, restores and
system upgrades.
Chapter 10 provides the procedures to use in
replacing circuit packs.
Appendix A explains the optical back reflection
safety feature.
Appendix B explains how to work with the
configuration database.
Appendix C explains how to clean the optical
surfaces of removable connector assemblies.
Appendix D explains the ESI command line
interface.
Appendix E explains what information to collect
before contacting BTI support.
Chapter 9, Administering the Netstender
Chapter 10, Replacing circuit packs

Appendix A: Optical back reflection safety
feature
Appendix B: Working with the configuration
database
xxxvi Netstender OAM&P Guide Document Version 01
Preface
Conventions
Note
Means reader take note. Notes contain helpful suggestions or background

information.
Means reader be careful. Equipment damage or loss of data can result from
your actions.
Caution
Means reader be careful. Harm to yourself or others can result from your
actions.
Warning
Laser Warning
Invisible laser radiation can be emitted from the aperture ports of amplifier
circuit packs when no fiber cable is connected. Avoid exposure and do not
stare into open apertures to avoid permanent eye damage.
Product Release 6.2 STANDARD xxxvii
Preface
Obtaining documentation
The following sections provide sources for obtaining documentation on the .
World Wide Web

The support portal on the btiphotonics.com web site provides access to technical
documentation and product information to registered users. Contact your account
manager for more information or for access to the support portal.
Product documentation CD-ROM

documentation is available on the documentation CD-ROM.
Ordering documentation
Customers can order documentation through their local account representative by
calling BTI headquarters at (613) 248-9154 or by emailing sales@btisystems.com.
Documentation feedback
You can email your comments to docfeedback@btisystems.com.
Obtaining technical support

For technical support, email support@btisystemss.com or call 1-866-431-4967. If
a licensed BTI reseller supplied your Netstender equipment, please call your
resellers support line.
If you are a registered customer, you can also access support services through the
BTI customer portal at www.btisystems.com.
xxxviii Netstender OAM&P Guide Document Version 01
H A P T E R
1.0 Netstender overview

This chapter provides an introduction to the Netstender. The following sections
provide an overview of the Netstender:
1.1, Netstender features
1.2, Netstender design values
1.3, Netstender technology features
Product Release 6.2 STANDARD 1-1
Netstender overview
1.1 Netstender features

The Netstender system combines amplification, signal conditioning, optical
multiplexing, and performance monitoring in a network-ready managed element.
Available in a 1U or 2U platform, the Netstender can accommodate a variety of
network configurations as shown in the following figures.
Figure 1-1 shows the Netstender 1030, which is 1U in height and holds up to three
circuit packs.
Figure 1-1 Netstender 1030
SER
In p ut
Mo nitor
A
view directly with optical

instruments.
Class 1 LASER PRODUCT
CLASS 3B Hazard Rating
Outp ut
Fail
REL 01
ACO
Fail
Active
Craft
Fan Critical Major Minor
Mgmnt
SCP
Craft
Figure 1-2 shows the Netstender 2060, which is 2U in height and holds up to six
single-width circuit packs.
Figure 1-2 Netstender 2060
Mon Line I n
D32MDE2
Out
In
Mon Line Out
In
S/N: BTIM01D1BJ25D
Fail
ESD
2
In
E
WR
WR
SER
4
Fail
S/N: BTIM01D1BJ25D
Fail Fa
Shelf 2
S/N: BTIM01D1BJ25D
Craft
Fail
Fail Fa
Shelf 3
Shelf 4
Shelf 5
Fail Fa
S/N: BTIM01D1BJ25D
Shelf 6
SCP
OSC 1
Drop
Eth 1
OSC 2
Drop
Fail
2
CAUTION: I nvisible
laser radiation. Do not
view directly with
optical instruments.
Class 1 LASER
PRODUCT
OSC
6
Tray
Figure 1-3 shows how to extend the capabilities of a basic Netstender 2060 system
with expansion shelves.
The example shows how one Netstender 2060 main shelf supports three expansion
shelves.
The first expansion shelf, labelled ES-11, is collocated with the Netstender 2060
main shelf.
The second and third expansion shelves, labelled ES-21 and ES-31 respectively,
are located remote to the Netstender 2060 main shelf and connected to it through
an optical communications link using the 100FX protocol.
1-2 Netstender OAM&P Guide Document Version 01
Netstender overview
Figure 1-3 Netstender 2060 with Expansion Shelves1

Mon Line I n
D32MDE2
Out
ESD
2
In
Mon Line Out
S/N: BTIM01D1BJ25D
Fail
WR
WR
SER
4
F il
S/N: BTIM01D1BJ25D
MSCP
Shelf 2
S/N: BTIM01D1BJ25D
Electrical
Cable
2
ESI
Shelf 3
Fail
F il
Shelf 4
F il
S/N: BTIM01D1BJ25D
Shelf 5
Shelf 6
SCP
OSC 1
Drop
Eth 1
Craft
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
Fail
2
PEC
BP1A04AA
03
CAUTION: I nvisible
CAUTION: I nvisible

view directly with
Class 1 LASER
PRODUCT
est
S/N: BTIM01D1BJ25D
Fail
Input
Output
Input
Output
Fail
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
OSC
6
OSC
Tray
SBA

view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
SMF60
Input
Output
Input
Output
PEC
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
SER
S/N: BTIM01D1BJ25D
Main
shelf
Fail Fa
OSC 2
Filler
ESD
ES11
SMF60
Local
expansion shelf
Filler
SER
6
S/N: BTIM01D1BJ25D
Fiber Cable
Pairs Between
Locations
Trouble
Power
S/N: BTIM01D1BJ25D
PEC
BP1A04AA
PEC
03
BP1A04AA
WR
03
ESD
ES21
est
S/N: BTIM01D1BJ25D
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
Fail Fa
S/N: BTIM01D1BJ25D
Input
SBA
PEC
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
SER
S/N: BTIM01D1BJ25D
Output
Filler
Input
OSC 1
Drop
Eth 1
OSC 2
Drop
CAUTION: I nvisible

view directly with
Class 1 LASER
PRODUCT
Dro
Fail
S/N: BTIM01D1BJ25D
SPA
4
Output
OSC
6
Tray
Remote
expansion shelf
Trouble
Power
PEC
BP1A04AA
PEC
03
BP1A04AA
WR
03
ESD
2
est
S/N: BTIM01D1BJ25D
S/N: BTIM01D1BJ25D
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
Input
SBA
Fail Fa
Fail Fa
PEC
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
SER
S/N: BTIM01D1BJ25D
Output
Filler
Input
CAUTION: I nvisible

view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
Input
ES31
Output
PEC
SER
S/N: BTIM01D1BJ25D
SPA
OPA
6
Output
Note: Altough the expansion shelf fiber cables are shown on the left side of the shelves,
the fiber cables should be run to the right side of the shelves.
1.Slot 5 in an expansion shelf is available for provisioning with a circuit pack other than a
Multiport System Control Processor (MSCP).
1-3
Netstender overview
1.2 Netstender design values

The Netstender is designed to interoperate with line terminating equipment from
multiple vendors and it meets performance requirements to deliver an optical layer
solution for evolving optical networks. Characteristics of the Netstender design
are:
carrier-grade platform
end-to-end system management
industry-standard management interfaces
compact footprint
modular design
open interfaces
Netstender overview
1.3 Netstender technology features

The Netstender manages the optical layer between terminal equipment, using
advanced optical amplification, optical multiplexing, wavelength conversion and
intelligent monitoring.
1.3.1 Optical amplification

The Netstender system supports two categories of optical amplifiers:
Single-channel amplifiers
DWDM amplifiers
Single-channel amplifiers
In this release a Single-channel/Sub-band Booster Amplifier (SBA) and a Singlechannel/Sub-band Pre-Amplifier (SPA) are supported for use in single-channel
networks or in low-channel networks.
These amplifiers are available either with or without built-in power monitors. The
power monitors allow one percent of the signal to be redirected for monitoring
purposes.
DWDM amplifiers
The Netstender offers several types of DWDM circuit packs for link extension:
Optical Line Amplifier (OLA)
Optical Line Amplifier with Mid-Stage Access (OLAM)
C-band Booster Amplifier (OBA)
C-band Pre-Amplifier (OPA)
These amplifiers have built-in power monitor ports. The power monitor ports
allow one percent of the signal to be redirected for monitoring purposes.
For more information about the DWDM amplifiers, see the Product Description.
1-5
Netstender overview
1.3.2 Optical multiplexing
Important
The Netstender offers flexible multiplexing configurations with DWDM and

CWDM Mux/Demuxes and Optical Add/Drop modules.
All Mux/Demuxes come with fiber optic terminators in the output ports. Do not
clean the terminators. Cleaning destroys the optical effectiveness of the devices. It
is recommended to install new terminators when decommissioning a port. Spare
LC terminators are orderable as part number BP1A5036.
CWDM multiplexers:
1 Channel CWDM OADM (C!ADM)

Double 1 Channel CWDM OADM (C1ADM)
2 Channel N+1 CWDM OADM (C2ADM)
4 Channel CWDM Mux/Demux (C4MD)-Channels 1-4
Note
CWDM & DWDM Splitter/Combiner (CDSC)

The Netstender CWDM multiplexer circuit packs are available in Class 2
equipment suitable for installation in Outside Plant (OSP) facilities.
DWDM multiplexers:
32 Channel DWDM Active Mux/Demux Module 1 (D32AMD1)-Channels 1-8

32 Channel DWDM Active Mux/Demux Module 2 (D32AMD2)-Channels 9-16
32 Channel DWDM Active Mux/Demux Module 3 (D32AMD3)Channels 17-24
32 Channel DWDM Active Mux/Demux Module 4 (D32AMD4)Channels 25-32
32 Channel DWDM Mux/Demux Module 1 (D32MD1)-Channels 1-8
32 Channel DWDM Bi-Directional Mux/Demux Module 24 (D32BMD24)
1 Channel DWDM OADM (D1ADM)
Netstender overview
2 Channel N+1 DWDM OADM (D2ADM)

4 Channel N+1, 2, 3 DWDM OADM (D4ADM)
4 Channel DWDM OADM (D4ADM)-Channels 53, 55, 57, 59
DWDM Bi-Directional Coupler/Splitter (CS)
For more information about the Netstender multiplexing equipment, see the
Product Description.
1.3.3 Optical signal conditioning

The Netstender supports SMF Dispersion Compensating Fiber Modules (DCMs)
for different compensation levels to correct for the amount of chromatic dispersion
in a specific fiber span (or link) and slope matched to the fiber type.
For more information, see the Product Description.
1.3.4 Optical Supervisory Channel

The Optical Supervisory Channel (OSC) circuit packs provide remote
management of a Netstender Network Element. The OSC circuit pack can use the
OSPF routing protocol to support network topology discovery and link failure.
The OSC coupler/splitter tray provides in-service splitting and coupling of the
OSC from live, traffic-carrying fibers. The coupler/splitter tray is separated from
the electronic components of the OSC circuit pack. As a result, failure of the
electronic components on the OSC circuit pack will not impact service on the
traffic-carrying fibers.
As of release 4.1, OSC capabilities are added to the Multiport System Control
Processor (MSCP) circuit pack.
For more information on the OSC, see the OSC Operations, Administration,
Maintenance and Provisioning Guide.
1-7
Netstender overview
1.3.5 Wavelength conversion

BTIs wavelength conversion solution translates any optical interface (850nm,
1310nm, CWDM, DWDM) to any wavelength on the ITU grid (CWDM, DWDM)
with optional 3R regeneration. Providing multi-rate, multi-protocol and loopback
capability, the SFP-based and XFP-based wavelength conversion circuit packs
translate optical signals between a variety of client-side interfaces. Four types of
wavelength conversion circuit packs are available:
The Wavelength Translator (WT) circuit pack provides 2R translation (reamplify and re-shape) of any optical wavelength to any other optical
wavelength.
The Wavelength Regenerator (WR) circuit pack provides translation of any
optical wavelength to any other or the same optical wavelength using 3R
regeneration (re-amplify, re-shape, and re-time). Protection switching is
supported.
The 10G Wavelength Regenerator (WR10G) circuit pack provides regeneration
of any optical wavelength to any other or the same optical wavelength using 4R
regeneration (re-amplify, re-frame, re-shape, and re-time). The two-port
WR10G, which uses an XFP port and a 300-pin MSA transponder port (line side
port), also provides for Forward Error Correction (FEC), using industrystandard RS (225,239) on both the client and line side ports.
The WR10G is available with a tunable line side port (BP1A47AB) or without a
tunable line side port (BP1A47BB).
The Wavelength Manager (WM2.5G) circuit pack provides translation of any
optical wavelength to any other or the same optical wavelength using 4R
regeneration (re-amplify, re-frame, re-shape, and re-time).
For more information about the Netstender wavelength conversion equipment, see
the Product Description.
1.3.6 Muxponder modules

The 2-Port GE Muxponder modules provide a dense, flexible interface for GbE
transport and service delivery over SONET or SDH networks. Ideally suited for
diverse backhaul of dual GbE connections from IP-DSLAM, OLT, WiMAX or
other broadband access devices, the 2-Port GE Muxponder maps two GbE signals
at full rate into a protected OC-48 or STM-16 connection. The following
functionality is provided:
2 GbE client side ports
2 OC-48 or STM-16 line side ports
All ports pluggable SFP transceivers: 850nm, 1310nm, 1550nm, CWDM, and
DWDM
Netstender overview
Full rate GbE transport of client signals into OC-48 or STM-16

UPSR and SNCP line protection
Performance monitoring on SONET or SDH line and GbE client signals:
15-minutes and 24-hour bins
Client and line side loopback
2 100BaseT (Fast Ethernet) ports for in-band management communication or
transport of additional client signals
Support for pass-through cross-connections to selectively drop or pass through
traffic in a ring configuration. The path facilities in a pass-through crossconnection provide alarm detection in both traffic directions.
1.3.7 Management
The Netstender is designed to be managed using a TL1 Command Line Interface
or the Java-based Netstender Node Controller (NNC). Netstender management is
easily integrated into existing element management systems (EMS) and network
management systems (NMS) using TL1 and SNMP. In addition, the NNC is
designed to simplify configuration and management of the Netstender and requires
minimal training to use (see the following figure).
The NNC connects to the Netstender through either the craft or management LAN
ports only. RS-232 serial communication supports TL1 access only.
Configuration management, fault management and performance monitoring of the
optical circuit packs in the Netstender system are handled by the System Control
Processor (SCP).
The SCP provides communication interfaces for local craft and management
system access.
Figure 1-4 Netstender Node Controller
1-9
Netstender overview
For more information about the craft and management interfaces used by the NNC,
see Chapter 3.0, Operating the Netstender in this document.
H A P T E R
2.0 Netstender state management

This chapter provides an introduction to Netstender state management. The
following sections provide an overview of this topic:
2.1, Entity management
2.2, Telcordia state model
2.3, Telcordia state attributes
2.4, Equipment state management
2.5, Amplifier entity state management
2.6, Wavelength conversion transceiver port state management
2.7, State management behavior interactions
2.8, State management provisioning interactions
2.9, State change reporting
2.10, Supporting and supported physical entities
2.11, Fault reporting interactions
Netstender state management
2.1 Entity management

The state of a managed entity represents the current condition of availability of the
resource or service in the network element. It is important for the Netstender to
manage and report on the state of various system components.
The purpose of a state model is to indicate the availability of an entity in providing
its functions, and if an entity is not available, to indicate the cause of the
unavailability and what kind of activity can be taken by the operator to make the
entity available.
For example the operator can choose to take an optical amplifier out of service. In
this case, the optical amplifier reports that it is in the out-of-service state due to a
maintenance action. In other cases, the amplifier might be out of service due to a
fault.
2.2 Telcordia state model

The Telcordia state model is used for network element state management when
TL1 is used as a management interface. The Netstender employs the Telcordia
state model as defined in GR-1093-CORE Generic State Requirements for
Network Elements, to provide a simple mapping.
The following figure shows the expansion shelf state transition diagram.
Expansion shelf state diagram
ENT:IS
Null,
No E xpansion
Shelf P resent
ENT:OOS
ED:OOS
Insert I nvalid
Expansion S helf
OOS-AU,
UEQ&AINS
Insert
Faulty
Expansion
Shelf
Insert
Valid
Expansion
Shelf
OOS-AU,
MEA
OOS-AUMA,
MT&MEA
ED:IS
Unplug
Expansion
Shelf
ED:
SHCONF
DLT
Insert
Invalid
Expansion
Shelf
ENT:IS
with I nvalid
Expansion S helf
OOS-AU,
UEQ
ENT:IS
with V alid
Expansion S helf
Insert
Valid
Expansion
Shelf
Unplug
Expansion
Shelf
DLT
Insert I nvalid
Expansion S helf
ED:OOS
Null,
Expansion S helf
Present
Unplug
Ext. S helf
OOS-AUMA,
MT&UEQ
Insert
Valid
Ext. S helf
Insert
Faulty
Expansion
Shelf
ENT:OOS
with I nvalid
Expansion S helf
ENT:OOS
with V alid
Expansion S helf
ED:
SHCONF
DLT
ED:OOS
OOS-MA,
MT
IS-NR
ED:IS
Unplug E xpansion S helf

Failed
Failed
ED:OOS
ED:IS
Recover
OOS-AU,
FLT
Recover
ED:OOS
OOS-AUMA,
FLT
ED:IS
The figure above indicates the resulting reports and events that occur from
expansion shelf state transitions.
2-3
The following figure shows the equipment state transition diagram.

Equipment state transition diagram
ENT:IS
Null,
Empty S lot
ENT:OOS
ED:OOS
Insert F iller
ENT:IS
OOS-AU,
MEA&AINS
Unplug
Filler
Null,
Filler P resent
ED:OOS
OOS-AU,
UEQ&AINS
Insert
Invalid
CP
ED:IS
OOS-AU,
MEA
Insert
FaultyCP
ENT:IS with
Invalid CP
Insert
Invalid CP
or F iller
Insert
Valid CP
OOS-AUMA,
MT&MEA
ENT:IS
Insert
Valid CP
Unplug CP
Unplug CP
OOS-AUMA,
MT&UEQ
Insert
Invalid CP
DLT
ED:IS
ENT:OOS with
Valid CP
Unplug
Faulty CP
Insert
Valid CP
OOS-MA,
MT
ED:OOS
Insert
Faulty CP
Failed
Failed
Unplug CP
DLT
IS-NR
Recover
DLT
ED:IS
ENT:OOS with
Invalid CP
Null,
CP P resent
OOS-AU,
UEQ
Insert
Faulty CP
ENT:OOS
ED:OOS
Unplug
CP
ED:OOS
DLT
ED:IS
Recover
OOS-AUMA,
MT&FLT
OOS-AU,
FLT
ED:OOS
Unplug
Faulty CP
DLT
ENT:IS
ENT:OOS
Null, F aulty
CP P resent
Tables 2-1 and 2-2 indicate the resulting reports and events that occur from
equipment state transitions.
Null, Empty
Slot
Null, CP
Present
Null, CP
Present
n/a
OOS-AU,UEQ
REPT RMV
REPT DBCHG
(cmd)
n/a
n/a
n/a
n/a
n/a
Insert Valid
CP
Insert Invalid
CP
Unplug CP
ENT:IS
ED:OOS
Equipment
Fails
Equipment
Recovers
Invoke
Upgrade
Upgrade
Completed
n/a
n/a
n/c
n/c
n/a
IS-NR
REPT DBCHG
(state)
REPT DBCHG
(cmd)
Null, Empty
Slot
n/a
n/a
Null, CP
Present
OOS-AU,
MEA&AINS
Null, Empty
Slot
n/a
n/a
Null, Filler
Present
Null, Empty
Slot
n/a
n/a
Null, Faulty
CP Present
n/a
OOS-AU,
SWDL
n/a
OOS-AU, FLT
REPT RMV
REPT ALM
REPT DBCHG
(state)
OOS-MA, MT
REPT RMV
REPT DBCHG
(cmd)
n/a
OOS-AU,
UEQ
REPT EVT
REPT RMV
REPT ALM)
n/a
n/a
IS-NR
n/a
n/a
n/a
n/a
OOS-AUMA,
MT&MEA
REPT DBCHG
(state)
REPT DBCHG
(cmd)
n/a
n/a
OOS_AU,
MEA
REPT EVT
REPT ALM
REPT DBCHG
(state)
IS-NR
REPT EVT
REPT ALM
REPT RST
UEQ
Equipment State Transitions with Reports and Events
Event
Table 2-1
MEA
n/a
n/a
n/a
n/a
OOS-AUMA,
MT&MEA
REPT ALM
REPT DBCHG
(state)
REPT DBCHG
(cmd)
n/a
OOS-AU,
UEQ
REPT EVT
REPT ALM
REPT DBCHG
(state)
n/a
n/a
n/a
n/a
IS-NR
REPT ALM
REPT DBCHG
(state)
REPT RST
n/a
OOS-AUMA,
MT&FLT
REPT ALM
REPT DBCHG
(state)
REPT DBCHG
(cmd)
n/a
OOS-AU,
UEQ
REPT EVT
REPT ALM
REPT DBCHG
(state)
n/a
n/a
FLT
OOS-AU
COMM
n/a
n/a
IS-NR
REPT ALM
REPT DBCHG
(state)
REPT RST
n/a
OOS-AUMA,
MT&COMM
REPT ALM
REPT DBCHG
(state)
REPT DBCHG
(cmd)
n/a
OOS-AU,
UEQ
REPT EVT
REPT ALM
REPT DBCHG
(state)
n/a
n/a
SWDL
IS-NR
n/a
n/a
n/a
n/a
n/a
OOS-AU,
UEQ
REPT EVT
REPT ALM
REPT DBCHG
(state)
n/a
n/a
2-5
IS-NR
REPT EVT
REPT ALM
REPT RST
OOS_AU, MEA
REPT EVT
REPT ALM
REPT DBCHG
(state)
n/a
n/a
OOS-AUMA,
MT&UEQ
REPT ALM
REPT DBCHG
(state)
REPT DBCHG
(cmd)
n/a
n/a
Insert Invalid CP
Unplug CP
ED:IS
ED:OOS
Equipment Fails
Equipment
Recovers
UEQ

n/a
n/a
OOS-AUMA,
MT&MEA
REPT ALM
REPT DBCHG
(state)
REPT DBCHG
(cmd)
n/a
OOS-AU, UEQ
REPT EVT
REPT ALM
REPT DBCHG
(state)
n/a
n/a
MEA
OOS-AU
IS-NR
REPT ALM
REPT RST
REPT DBCHG
(state)
n/a
OOS-AUMA,
MT&FLT
REPT ALM
REPT DBCHG
(state)
REPT DBCHG
(cmd)
n/a
OOS-AU, UEQ
REPT EVT
REPT ALM
REPT DBCHG
(state)
n/a
n/a
FLT
n/a
OOS-AU, FLT
REPT RMV
REPT ALM
REPT DBCHG
(state)
OOS-MA, MT
REPT RMV
REPT DBCHG
(cmd)
n/a
OOS-AU, UEQ
REPT EVT
REPT ALM
REPT RMV
n/a
n/a
IS-NR
UEQ
n/a
n/a
n/a
OOS-AU, UEQ
REPT DBCHG
(state)
REPT DBCHG
(cmd)
n/a
OOS-AUMA,
MT&MEA
REPT EVT
REPT ALM
REPT DBCGHG
(state)
OOS-AUMA, MT
REPT EVT
REPT ALM
REPT DBCGHG
(state)
Equipment State Transitions with Reports and Events
Insert Valid CP
Event
Table 2-2
n/a
n/a
n/a
OOS-AU, MEA
REPT DBCHG
(state)
REPT DBCHG
(cmd)
OOS-AUMA,
MT&UEQ
REPT EVT
REPT ALM
REPT DBCGHG
(state)
n/a
n/a
MEA
OOS-AUMA
MT
OOS-AUMA, MT
REPT ALM
REPT DBCHG
(state)
n/a
n/a
OOS-AU, FLT
REPT DBCHG
(state)
REPT DBCHG
(cmd)
OOS-AUMA,
MT&UEQ
REPT EVT
REPT ALM
REPT DBCGHG
(state)
n/a
n/a
FLT
n/a
OOS-AUMA,
MT&FLT
REPT ALM
REPT DBCHG
(state)
n/a
IS-NR
REPT RST
REPT DBCHG
(state)
OOS-AUMA,
MT&UEQ
REPT EVT
REPT ALM
REPT DBCGHG
(state)
n/a
n/a
OOS-MA
MT
The following figure shows the optical amplifier state transition diagram.
Optical amplifier state transition diagram
ENT:IS with AINS and
Equipment F ault
ED:OOS
OOS-AU, UEQ&
AINS&SGEO
OOS-AUMA,
MT&UEQ&SGEO
ED:IS
Equipment
Fault Clears
ED:OOS
OOS-AU,
UEQ&SGEO
Equipment
Fault P resent
Equipment
Fault P resent
Equipment
Fault P resent
Equipment
Fault
ENT:IS with Normal

Running E quipment
Equipment
Fault P resent
Equipment
Fault Clears
Equipment
Fault Clears
ED:OOS
OOS-MA,
MT
IS-NR
ED:IS
Amplifier
Component
Fault
Optical Metrics
Not Met
ENT:OOS with Normal

Running E quipment
Amplifier
Component
Fault Clears
Amplifier
Component
Fault Clears
OOS-AU,
FLT
Optical Metrics
Met
Equipment
Fault P resent
Amplifier
Component
Fault
ED:OOS
ED:IS
OOS-AUMA,
MT&FLT
Optical Metrics
Not Met
Optical Metrics
Met
ED:OOS
IS-ANR
ED:IS
OOS-MA,
ANR
Tables 2-3 indicates the resulting reports and events that occur from optical
amplifier state transitions.
2-7
IS-NR
REPT RST
n/a
n/a
OOS-AUMA,
MT&UEQ&
SGEO
REPT DBCHG
(state)
REPT DBCHG
(cmd)
n/a
n/a
n/a
n/a
Equipment Fault
Present
ED:IS
ED:OOS
Amplifier
Component Fault
Amplifier
Component Fault
Clears
Optical Metric
Met
Optical Metric
Not Met
OOS-AU
UEQ&AIN&
SGEO

n/a
n/a
n/a
n/a
OOS-AUMA,
MT&UEQ&
SGEO
REPT DBCHG
(state)
REPT DBCHG
(cmd)
n/a
n/a
IS-NR
REPT RST
OOS-AU
UEQ&SGEO
n/a
n/a
IS-NR
REPT ALM
REPT RST
n/a
OOS-AUMA,
MT&FLT
REPT ALM
REPT DBCHG
(state)
REPT DBCHG
(cmd)
n/a
OOS-AU, UEQ
&SGEO
REPT DBCHG
(state)
n/a
OOS-AU
FLT
n/a
IS-NR
REPT ALM
REPT DBCHG
(state)
n/a
n/a
OOS-MA, MT
&ANR
REPT RMV
REPT DBCHG
(cmd)
n/a
OOS-AU
UEQ&SGEO
REPT RMV
REPT DBCHG
(state)
n/a
IS-ANR
IS-ANR
REPT DBCHG
(state)
n/a
n/a
OOS-AU, FLT
REPT ALM
REPT RMV
OOS-MA, MT
REPT RMV
REPT DBCHG
(cmd)
n/a
OOS-AU
UEQ&SGEO
REPT RMV
REPT DBCHG
(state)
n/a
IS-NR
n/a
n/a
n/a
n/a
n/a
OOS-AU,
UEQ&SGEO
REPT DBCHG
(state)
REPT DBCHG
(cmd)
n/a
OOS-MA, MT
REPT DBCHG
(state)
OOS-AUMA
MT&UEQ&
SGEO
Optical Amplifier State Transitions with Reports and Events
Equipment Fault
Clears
Event
Table 2-3
OOS-MA<
MT&ANR
REPT DBCHG
(state)
n/a
n/a
OOS-AUMA,
MT&FLT
REPT DBCHG
(state)
n/a
IS-NR
REPT RST
REPT DBCHG
(cmd)
OOS-AUMA,
MT&UEQ&
SGEO
REPT DBCHG
(state)
n/a
OOS-MA
MT
n/a
n/a
OOS-MA, MT
REPT DBCHG
(state)
n/a
n/a
OOS-AU, FLT
REPT ALM
REPT DBCHG
(state)
REPT DBCHG
(cmd)
OOS-AUMA,
MT&UEQ&
SGEO
REPT DBCHG
(state)
n/a
OOS-AUMA
MT&FLT
n/a
OOS-MA, MT
REPT DBCHG
(state)
n/a
n/a
n/a
IS-ANR
REPT RST
REPT ALM
REPT DBCHG
(cmd)
OOS-AUMA,
MT&UEQ&
SGEO
REPT DBCHG
(state)
n/a
OOS-MA
MT&ANR
The following figure shows the automatic in-service (AINS) state transition
diagram.
Automatic In-Service (AINS) state transition diagram
ENT:IS,AINS
with F aulty
Equipment
OOS-AUMA,
MT&SGEO
ED:OOS
ED:IS
OOS-AU,
SGEO
OOS-AU,
AINS&SGEO
ED:AINS
Equipment
Problem
Clears with
Invalid S ignal
Equipment
Problem
Present
Equipment
Problem
Clears with
Valid S ignal
Timer E xpired
ED:IS
Valid S ignal
OOS-AU,
AINS
IS,NR
Equipment
Problem
Present
ENT:IS,AINS
with I nvalid
Signal
OOS-AU,
AINS&FLT
Invalid S ignal
ED:AINS
ED:OOS
ED:OOS
ED:IS
OOS-MA,
MT
OOS-AUMA,
MT&FLT
OOS-AU,FLT
ED:AINS
The following figure shows a portion of the wavelength conversion transceiver

port out-of-service state transitions diagram. The wavelength conversion
transceiver port in-service state transitions diagram appears in the illustration that
follows this one.
2-9
Unplug SFP
OOS-AUMA
MT&MEA&SGEO&LPBK
Equipment IS
SFP
Failure
Raise
Equipment
OOS
RLS-LPBK
Unplug SFP
OOS-AUMA
MT&MEA&SGEO&FLT&LPBK
Equipment
IS
SFP
Mismatch Clear
SFP
Failure
Clear
OPR-LPBK
OPR-LPBK
Unplug
SFP
DLT-XCVR
Unplug SFP
SFP F ailure Clear
SFP Mismatch Clear

SFP F ailure Raise
OOS-AUMA
MT&MEA&SGEO
SFP
Mismatch
Raise
Equipment IS
OPR-LPBK
DLT-XCVR
RLS-LPBK
OOS-AUMA
MT&FLT
OPR-LPBK
RLS-LPBK
SFP Mismatch Clear
Equipment IS
SFP Mismatch Raise
Unplug SFP
OPR-LPBK
SFP
Failure
Clear
Equipment IS
Insert
SFP
Unplug SFP
DLT-XCVR
OOS-AUMA
MT&UEQ&SGEO
SFP
Mismatch Raise
OOS-AUMA
MT&SGEO
SFP
Failure
Raise
OOS-AUMA
MT&SGEO&FLT
RLS-LPBK
DLT-XCVR
RLS-LPBK
OPR-LPBK
Insert
SFP
SFP
Mismatch
Raise
OOS-AUMA
MT&UEQ&SGEO&LPBK
OPR-LPBK
RLS-LPBK
SFP
Failure Clear
OOS-AUMA
MT&SGEO&LPBK
Equipment IS
Equipment OOS
Equipment OOS
OOS-MA
MT&LPBK
Insert
SFP
OOS-AUMA
MT&UEQ&LPBK
RLSLPBK
SFP
Failure Raise
Unplug SFP
OOS-AUMA
MT&SGEO&FLT&LPBK
Null,
No SFP P resent
DLT-XCVR
RLS-LPBK
OPR-LPBK
Equipment OOS
OOS-AUMA
MT&UEQ
SFP
Mismatch Raise
SFP Mismatch Raise
OOS-AUMA
MT&MEA&SGEO&FLT
Equipment OOS
RMV-XCVR
SFP
Unplug
SFP
SFP Failure
Equipment OOS
Mismatch Clear
Raise
OOS-AUMA
MT&FLT&LPBK
DLT-XCVR
SFP
Failure
Raise
SFP
Mismatch
Clear
Unplug SFP
Equipment OOS
OOS-MA
MT
SFP
Mismatch Raise
SFP Mismatch Raise
SFP
Failure
Clear
SFP
Mismatch
Clear
Equipment
OOS
OOS-AUMA
MT&MEA&FLT&LPBK
DLT-XCVR
SFP
Failure
Clear
Null,
SFP P resent
Unplug
SFP
SFP F ailure Raise
Equipment
OOS
OOS-AUMA
MT&MEA&FLT
OPR-LPBK
DLT-XCVR
SFP Mismatch Clear
SFP
Failure
Clear
Unplug SFP
RLS-LPBK
SFP
Failure
Raise
RLS-LPBK
Unplug SFP
OOS-AUMA
MT&MEA
Equipment IS
OPR-LPBK
Equipment IS
Insert SFP
Unplug SFP
Unplug SFP
Unplug SFP
SFP F ailure Raise
OOS-AUMA
MT&MEA&LPBK
Unplug SFP

Equipment IS
Equipment OOS
Wavelength conversion transceiver port OOS state transitions diagram
OOS-AUMA
MT&SGEO
REPT-DBCHG
(state)
n/a
Equipment OOS
Equipment IS
Null, SFP
Present
REPT-DBCHG
(cmd)
n/a
SFP or XFP
Failure Clears
n/a
OOS-AUMA
MT&FLT
REPT-DBCHG
(state)
SFP or XFP
Failure Raised
DLT-XCVR
n/a
ED:OOS
ENT-XCVR
IS-NR
REPT-RST
(state)
REPT-DBCHG
(cmd)
ED:IS
n/a
n/a
SFP or XFP
Mismatch
Cleared
RLS-LPBK
OOS-AUMA
MT&MEA
REPT-DBCHG
(state)
SFP or XFP
Mismatch
Raised
OOS-MA
MT&LPBK
OOS-AUMA
MT&UEQ
REPT-DBCHG
(state)
Unplug SFP or
XFP
OPR-LPBK
n/a
OOS-MA
MT
Insert SFP or
XFP
Event
n/a
n/a
OOS-MA
MT
REPT-DBCHG
(state)
REPT-DBCHG
(cmd)
n/a
n/a
OOS-AUMA
MT&SGEO&LPB
K
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&FLT&LPBK
REPT-DBCHG
(state)
n/a
n/a
n/a
OOS-AUMA
MT&MEA&LPBK
REPT-DBCHG
(state)
OOS-AUMA
MT&UEQ&LPBK
REPT-CBCHG
(state)
n/a
OOS-MA
MT&LPBK
n/a
n/a
OOS-AUMA
MT&FLT
REPT-DBCHG
(state)
n/a
n/a
OOS-AUMA
MT&SGEO&FLT&
LPBK
REPT-DBCHG
(state)
OOS-MA
MT&LPBK
n/a
n/a
n/a
n/a
OOS-AUMA
MT&MEA&FLT&LP
BK
REPT-DBCHG
(state)
OOS-AUMA
MT&UEQ&LPBK
REPT-CBCHG
(state)
n/a
OOS-AUMA
MT&FLT&LPBK
Null, No SFP or
XFP Present
REPT-DBCHG
(cmd)
n/a
n/a
OOS-AUMA
MT&UEQ&LPBK
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&UEQ&SGE
O
REPT-DBCHG
(state)
n/a
n/a
n/a
OOS-AU
UEQ
REPT-DBCHG
(state)
REPT-DBCHG
(cmd)
n/a
n/a
n/a
OOS-MA
MT
REPT-DBCHG
(state)
UEQ
Null, SFP or XFP

Present
REPT-DBCHG
(cmd)
n/a
n/a
OOS-AUMA
MT&MEA&LPBK
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&MEA&SGE
O
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&MEA&FLT
REPT-DBCHG
(state)
n/a
OOS-AU
MEA
REPT-DBCHG
(state)
REPT-DBCHG
(cmd)
OOS-MA
MT
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&UEQ
REPT-DBCHG
(state)
n/a
MEA
Null, SFP or XFP

Present
REPT-DBCHG
(cmd)
n/a
n/a
OOS-AUMA
MT&SGEO&
LPBK
REPT-DBCHG
(state)
OOS-MA
MT
REPT-DBCHG
(state)
n/a
n/a
OOS-AUMA
MT&SGEO&FLT
REPT-DBCHG
(state)
n/a
OOS-AU
SGEO
REPT-DBCHG
(state)
REPT-DBCHG
(cmd)
n/a
OOS-AUMA
MT&MEA&
SGEO
REPT-DBCHG
(state)
OOS-AUMA
MT&UEQ&
SGEO
REPT-DBCHG
(state)
n/a
SGEO
OOS-AUMA
MT
SFP and XFP State Transitions with Reports and Events
State
Table 2-4
Null, SFP or XFP

Present
REPT-DBCHG
(cmd)
n/a
n/a
OOS-AUMA
MT&FLT&LPBK
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&SGEO&FLT
REPT-DBCHG
(state)
OOS-MA
MT
REPT-DBCHG
(state)
n/a
n/a
OOS-AU
FLT
REPT-DBCHG
(state)
REPT-DBCHG
(cmd)
n/a
OOS-AUMA
MT&MEA&FLT
REPT-DBCHG
(state)
OOS-AUMA
MT&UEQ
REPT-DBCHG
(state)
n/a
FLT
Null, No SFP or
XFP Present
REPT-DBCHG
(cmd)
n/a
n/a
OOS-AUMA
MT&UEQ&SGE
O&LPBK
REPT-DBCHG
(state)
OOS-AUMA
MT&UEQ
REPT-DBCHG
(state)
n/a
n/a
n/a
n/a
OOS-AU
UEQ&SGEO
REPT-DBCHG
(state)
REPT-DBCHG
(cmd)
n/a
n/a
n/a
OOS-AUMA
MT&SGEO
REPT-DBCHG
(state)
SGEO
n/a
n/a
OOS-AUMA
MT&UEQ
REPT-DBCHG
(state)
n/a
n/a
OOS-AUMA
MT&UEQ&
SGEO&LPBK
REPT-DBCHG
(state)
n/a
n/a
n/a
n/a
n/a
n/a
n/a
OOS-MA
MT&LPBK
REPT-DBCHG
(state)
LPBK
OOS-AUMA
MT&UEQ
n/a
n/a
OOS-AUMA
MT&UEQ&SGE
O
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&UEQ&LPBK
REPT-DBCHG
(state)
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
OOS-AUMA
MT&SGEO&
LPBK
REPT-DBCHG
(state)
SGEO&LPB
K
Tables 2-4, 2-5 and 2-6 indicate the resulting reports and events that occur from
wavelength conversion transceiver port state transitions.
2-11
n/a
OOS-AUMA
MT&UEQ&
SGEO
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&SGEO
REPT-DBCHG
(state)
OOS-AU
MEA&SGEO
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&MEA&
SGEO&FLT
REPT-DBCHG
(state)
n/a
n/a
OOS-AUMA
MT&MEA
REPT-DBCHG
(state)
OOS-AUMA
MT&MEA&
SGEO&LPBK
REPT-DBCHG
(state)
n/a
n/a
Null, SFP
Present
REPT-DBCHG
(cmd)
Unplug SFP
SFP Mismatch
Raised
SFP Mismatch
Cleared
ED:IS
ED:OOS
SFP Failure
Raised
SFP Failure
Clears
Equipment OOS
Equipment IS
OPR-LPBK
RLS-LPBK
ENT-XCVR
DLT-XCVR
SGEO
Insert SFP
Event

Null, SFP
Present
REPT-DBCHG
(cmd)
n/a
n/a
OOS-AUMA
MT&MEA&FLT&
LPBK
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&MEA&
SGEO&FLT
REPT-DBCHG
(state)
OOS-AUMA
MT&MEA
REPT-DBCHG
(state)
n/a
n/a
OOS-AU
MEA&FLT
REPT-DBCHG
(state)
REPT-DBCHG
(cmd)
OOS-AUMA
MT&FLT
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&UEQ
REPT-DBCHG
(state)
n/a
FLT
n/a
n/a
OOS-AUMA
MT&MEA
REPT-DBCHG
(state)
n/a
n/a
OOS-AUMA
MT&MEA&
SGEO&LPBK
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&MEA&FLT&
LPBK
REPT-DBCHG
(state)
n/a
n/a
OOS-AUMA
MT&LPBK
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&UEQ&LPBK
REPT-DBCHG
(state)
n/a
LPBK
Null, SFP
Present
REPT-DBCHG
(cmd)
n/a
n/a
OOS-AUMA
MT&MEA&
SGEO&FLT&LP
BK
REPT-DBCHG
(state)
OOS-AUMA
MT&MEA&FLT
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&MEA&
SGEO
REPT-DBCHG
(state)
n/a
n/a
OOS-AU
UEQ&SGEO&
FLT
REPT-DBCHG
(state)
REPT-DBCHG
(cmd)
OOS-AUMA
MT&SGEO&FLT
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&UEQ&
SGEO
REPT-DBCHG
(state)
n/a
SGEO&FLT
OOS-AUMA
MT&MEA
n/a
n/a
OOS-AUMA
MT&MEA&FLT
REPT-DBCHG
(state)
n/a
n/a
OOS-AUMA
MT&MEA&
SGEO&FLT&LP
BK
REPT-DBCHG
(state)
OOS-AUMA
MT&MEA&LPBK
REPT-DBCHG
(state)
n/a
n/a
n/a
OOS-AUMA
MT&FLT&LPBK
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&UEQ&LPBK
REPT-DBCHG
(state)
n/a
FLT&LPBK
n/a
n/a
OOS-AUMA
MT&MEA&SGEO
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&MEA&LPBK
REPT-DBCHG
(state)
n/a
n/a
OOS-AUMA
MT&MEA&SGEO
&FLT&LPBK
REPT-DBCHG
(state)
n/a
n/a
OOS-AUMA
MT&SGEO&
LPBK
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&UEQ&SGEO
&LPBK
REPT-DBCHG
(state)
n/a
SGEO&LPBK
State
Table 2-5
n/a
n/a
OOS-AUMA
MT&MEA&
SGEO&FLT
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&MEA&FLT&
LPBK
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&MEA&
SGEO&LPBK
REPT-DBCHG
(state)
n/a
n/a
n/a
OOS-AUMA
MT&SGEO&FLT
&LPBK
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&UEQ&
SGEO&LPBK
REPT-DBCHG
(state)
n/a
SGEO&FLT&
LPBK
FLT
Null, SFP
Present
REPT-DBCHG
(cmd)
n/a
n/a
OOS-AUMA
MT&SGEO&FLT
&LPBK
REPT-DBCHG
(state)
OOS-AUMA
MT&FLT
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&SGEO
REPT-DBCHG
(state)
n/a
n/a
OOS-AU
SGEO&FLT
REPT-DBCHG
(state)
REPT-DBCHG
(cmd)
n/a
OOS-AUMA
MT&MEA&
SGEO&FLT
REPT-DBCHG
(state)
OOS-AUMA
MT&UEQ&
SGEO
REPT-DBCHG
(state)
n/a
LPBK
n/a
n/a
OOS-AUMA
MT&SGEO
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&LPBK
REPT-DBCHG
(state)
n/a
n/a
OOS-AUMA
MT&SGEO&FLT
&LPBK
REPT-DBCHG
(state)
n/a
n/a
n/a
OOS-AUMA
MT&MEA&
SGEO&LPBK
REPT-DBCHG
(state)
OOS-AUMA
MT&UEQ&
SGEO&LPBK
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&SGEO
FLT&LPBK
n/a
n/a
OOS-AUMA
MT&SGEO&FLT
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&FLT&LPBK
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&SGEO&
LPBK
REPT-DBCHG
(state)
n/a
n/a
n/a
n/a
OOS-AUMA
MT&MEA&
SGEO&FLT&
LPBK
REPT-DBCHG
(state)
OOS-AUMA
MT&UEQ&
SGEO&LPBK
REPT-DBCHG
(state)
n/a
The following figure shows the wavelength conversion transceiver port in-service
state transitions diagram.
Wavelength conversion transceiver port IS state transitions diagram
SFP
Failure
Raised
Unplug SFP
SFP F ailure Raised
Equipment OOS
OOS-AU
MEA&SGEO
OOS-AU
MEA
Equipment IS
Unplug SFP
SFP
Mismatch
Raised
Unplug SFP
SFP
Mismatch
Raised
Equipment OOS
OOS-AU
SGEO
SFP
Failure
Cleared
OOS-AU
MEA&FLT
Unplug
SFP
Equipment
OOS
Insert
SFP
Equipment OOS
SFP
Mismatch
Raised
Unplug SFP
OOS-AU
FLT
Equipment IS
SFP
Mismatch
Raised
OOS-AU
UEQ
Equipment
OOS
Unplug SFP
Equipment
IS
OOS-AU
MEA&SGEO&FLT
Equipment
IS
Note
Null, SFP
Present
Unplug
SFP
SFP
Failure
Raised
SFP
Mismatch
Raised
OOS-AU
SGEO&FLT
SFP
Failure
Cleared
ENT-XCVR
IS-NR
Equipment IS
SFP
Failure
Cleared
Unplug SFP
OOS-AU
UEQ&SGEO
ENT-XCVR
Null, No SFP
Present
Insert
SFP
Where SFP is indicated, the action is also applicable to an XFP.
2-13
OOS-AU
UEQ
REPT-RMV
(state)
OOS-AU
MEA
REPT-RMV
(state)
n/a
n/a
OOS-MA
MT
REPT-RMV
(state)
REPTDBCHG
(cmd)
OOS-AU
FLT
REPT-RMV
(state)
n/a
OOS-AU
SGEO
REPT-RMV
(state)
n/a
n/a
n/a
n/a
n/a
Unplug SFP or
XFP
SFPor XFP
Mismatch
Raised
SFP or XFP
Mismatch
Cleared
ED:IS
ED:OOS
SFP or XFP
Failure Raised
SFP or XFP
Failure Clears
Equipment OOS
Equipment IS
OPR-LPBK
RLS-LPBK
ENT-XCVR
DLT-XCVR
IS-NR
n/a
State

n/a
n/a
n/a
n/a
n/a
OOS-AU
UEQ&SGEO
REPTDBCHG
(state)
n/a
n/a
OOS-AUMA
MT&UEQ
REPTDBCHG
(state)
REPTDBCHG
(cmd)
n/a
n/a
n/a
n/a
IS-NR
REPT-RST
(state)
UEQ
n/a
n/a
n/a
n/a
n/a
OOS-AU
MEA&SGEO
n/a
OOS-AU
MEA&FLT
REPT
DBCHG
(state)
OOS-AUMA
MT&MEA
REPTDBCHG
(state)
REPTDBCHG
(cmd)
n/a
n/a
n/a
OOS-AU
UEQ
REPTDBCHG
(state)
n/a
MEA
n/a
n/a
n/a
n/a
IS-NR
REPT-RST
(state)
n/a
n/a
OOS-AU
SGEO&FLT
REPTDBCHG
(state)
OOS-AUMA
MT&SGEO
REPTDBCHG
(state)
REPTDBCHG
(cmd)
n/a
n/a
OOS-AU
MEA&SGEO
REPTDBCHG
(state)
OOS-AU
UEQ&SGEO
REPTDBCHG
(state)
n/a
SGEO
n/a
n/a
n/a
n/a
n/a
OOS-AU
SGEO&FLT
REPTDBCHG
(state)
IS-NR
REPT-RST
(state)
n/a
OOS-AUMA
MT&FLT
REPTDBCHG
(state)
REPTDBCHG
(cmd)
n/a
n/a
OOS-AU
MEA&FLT
REPTDBCHG
(state)
OOS-AU
UEQ
REPTDBCHG
(state)
n/a
FLT
n/a
n/a
n/a
n/a
OOS-AU
UEQ
REPT-DBCHG
(state)
n/a
n/a
n/a
OOS-AUMA
MT&UEQ&SGE
O
REPT-DBCHG
(state)
n/a
n/a
n/a
n/a
OOS-AU
SGEO
REPT-DBCHG
(state)
UEQ&SGEO
n/a
n/a
n/a
n/a
OOS-AU
MEA
REPT-DBCHG
(state)
n/a
n/a
n/a
OOS-AUMA
MT&MEA&SGE
O
REPT-DBCHG
(state)
REPT-DBCHG
(cmd)
n/a
n/a
n/a
OOS-AU
UEQ&SGEO
REPT-DBCHG
(state)
n/a
MEA&SGEO
OOS-AU
Insert SFP or
XFP
Event
Table 2-6
MEA&FLT
n/a
n/a
n/a
n/a
n/a
OOS-AU
MEA&SGEO&FL
T
REPT-DBCHG
(state)
OOS-AU
MEA
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&MEA&FLT
REPT-DBCHG
(state)
REPT-DBCHG
(cmd)
n/a
n/a
n/a
OOS-AU
UEQ
REPT-DBCHG
(state)
n/a
SGEO&FLT
n/a
n/a
n/a
n/a
OOS-AU
FLT
REPT-DBCHG
(state)
n/a
OOS-AU
SGEO
REPT-DBCHG
(state)
n/a
OOS-AUMA
MT&SGEO&FLT
REPT-DBCHG
(state)
REPT-DBCHG
(cmd)
n/a
n/a
OOS-AU
MEA&SGEO&FL
T
REPT-DBCHG
(state)
OOS-AU
UEQ&SGEO
REPT-DBCHG
(state)
n/a
MEA&SGEO&FLT
n/a
n/a
n/a
n/a
OOS-AU
MEA&FLT
REPT-DBCHG (state)
n/a
OOS-AU
MEA&SGEO
REPT-DBCHG (state)
n/a
OOS-AUMA
MT&MEA&SGEO&FLT
REPT-DBCHG (state)
REPT-DBCHG (cmd)
n/a
n/a
n/a
OOS-AU
UEQ&SGEO
REPT-DBCHG (state)
n/a
Protection Switching Group Transition Table
The protection switching state transition table is based on the assumption that there
are two SFP transceiver ports A and B, where B is protecting A. The following
command is assumed to have provisioned the protection switching group:
ENT-FFP-XCVR:NETSTENDER:WR-1-2-1,WR-1-2-3:::;
Table 2-7 describes the state transitions of both A and B due to various events. In
each state row, the top state is for A whereas the bottom state is for B. The event
columns indicate the following:
Table 2-7
Protection Switching State Transitions
Event Title
Indicates
SD:A1
Signal Degrade on A
Signal Degrade on B
Signal Failure on A
Signal Failure on B
OPR-PROTNSW-XCVR::A::MAN;
OPR-PROTNSW-XCVR::B::MAN;
OPR-PROTNSW-XCVR::A::FRCD;
OPR-PROTNSW-XCVR::B::FRCD;
OPR-PROTNSW-XCVR::A::LKDO;
OPR-PROTNSW-XCVR::B::LKDO;
RLS-PROTNSW-XCVR::A;
RLS-PROTNSW-XCVR::B;
RMV-XCVR::A; (same as SF:A)
RMV-XCVR::B; (same as SF:B)
RST-XCVR::A; (represents any transition from OOS to IS)
RST-XCVR::B; (represents any transition from OOS to IS)
SD:B1
SF:A1
SF:B1
A:MAN2
B:MAN2
A:FRCD2
B:FRCD2
A:LKDO2
B:LKDO2
RLS:A2b
RLS:B2
RMV:A
RMV:B
RST:A
RST:B
1. Currently not supported.

2. Applies only to wavelength regenerators with protection switching.
2-15

44
43
42
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
Event #
1
State
IS,WRK
IS,STBY
IS,WRK
IS-ANR,STDBY
IS,WRK
IS-ANR,STDBY,FRCD
IS,WRK
IS-ANR,STDBY,LKDO
IS,WRK
IS,STDBY,FRCD
IS,WRK
IS,STDBY,LKDO
IS,WRK
OOS,STDBY
IS,WRK
OOS,STDBY,FRCD
IS,WRK
OOS,STDBY,LKDO
IS-ANR,WRK
IS-ANR,STDBY
IS-ANR,WRK
IS-ANR,STDBY,FRCD
IS-ANR,WRK
IS-ANR,STDBY,LKDO
IS-ANR,WRK
OOS,STDBY
IS-ANR,WRK
OOS,STDBY,FRCD
IS-ANR,WRK
OOS-STDBY,LKDO
OOS,WRK
IS,STDBY,LKDO
OOS,WRK
OOS,STDBY
OOS,WRK
OOS,STDBY,FRCD
OOS,WRK
OOS,STDBY,LKDO
IS,STBY
IS,WRK
IS-ANR,STDBY
IS,WRK
IS-ANR,STDBY,FRCD
IS,WRK
IS-ANR,STDBY,LKDO
IS,WRK
IS,STDBY,FRCD
IS,WRK
IS,STDBY,LKDO
IS,WRK
OOS,STDBY
IS,WRK
OOS,STDBY,FRCD
IS,WRK
OOS,STDBY,LKDO
IS,WRK
IS-ANR,STDBY
IS-ANR,WRK
IS-ANR,STDBY,FRCD
IS-ANR,WRK
IS-ANR,STDBY,LKDO
IS-ANR,WRK
OOS,STDBY
IS-ANR,WRK
OOS,STDBY,FRCD
IS-ANR,WRK
OOS-STDBY,LKDO
IS-ANR,WRK
IS,STDBY,LKDO
OOS,WRK
OOS,STDBY
OOS,WRK
OOS,STDBY,FRCD
OOS,WRK
OOS,STDBY,LKDO
OOS,WRK
IS-ANR,WRK
IS,STDBY,FRCD
IS-ANR,WRK
IS,STDBY,LKDO
IS,STDBY,FRCD
IS-ANR,WRK
IS,STDBY,LKDO
IS-ANR,WRK
OOS,WRK
IS-ANR,STDBY,LKDO
IS-ANR,STDBY,LKDO
OOS,WRK
SD:A
44
43
31
30
40
39
38
37
36
44
34
33
32
31
30
29
28
27
26
23
22
23
22
21
21
19
18
17
16
15
14
13
12
11
10
15
14
13
40
39
12
11
10
21
44
43
42
41
12
11
38
37
36
35
34
33
32
31
30
29
34
41
32
42
41
31
30
29
19
18
17
43
15
14
13
12
11
10
NA
NA
NA
SD:B
2
38
43
34
33
16
26
38
37
36
38
34
33
32
34
33
32
28
27
26
28
27
28
27
26
26
19
18
17
16
19
18
17
43
32
32
19
18
17
16
26
43
32
32
SF:A
26
44
19
35
15
14
38
37
36
35
38
37
36
44
13
13
38
37
36
35
44
14
13
19
18
17
19
15
14
13
15
14
13
SF:B
7
error
error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
29
Error
Error
Error
Error
Error
Error
Error
Error
A:MAN
20
error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
10
Error
Error
Error
Error
Error
Error
Error
Error
Error
error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
error
Error
error
error
B:MAN
error
Table 2-8 Protection Switching Group Transitions
error
error
error
error
error
22
error
error
37
error
error
error
33
error
error
30
error
error
27
error
error
error
error
22
24
error
error
error
error
error
error
error
error
30
30
error
error
error
error
24
error
41
41
A:FRCD
24
error
error
error
error
error
error
error
error
error
error
error
error
error
11
11
error
error
error
error
error
39
39
error
error
18
error
error
error
14
error
error
11
error
error
error
error
error
error
B:FRCD
5
error
error
error
42
error
28
error
38
38
error
error
34
34
error
31
31
error
28
28
error
25
error
23
23
25
error
38
38
error
error
44
44
error
31
31
error
35
35
error
25
error
42
42
A:LKDO
25
error
error
error
error
40
error
19
19
error
error
43
43
error
12
12
error
16
19
error
error
40
40
error
19
19
error
error
15
15
error
12
12
error
error
error
B:LKDO
6
13
Error
Error
Error
36
36
error
32
32
error
29
29
error
26
26
error
20
20
21
21
error
error
Error
error
error
error
error
error
error
error
error
Error
error
error
error
error
error
error
error
error
RLS:A
Error
Error
32
Error
Error
21
21
Error
Error
Error
Error
Error
Error
Error
Error
Error
error
error
error
error
Error
error
Error
error
error
error
17
17
error
26
13
13
error
10
10
error
error
error
RLS:B
Error
43
32
32
RMV:A
26
RMV:B
7
error
Error
Error
Error
Error
35
Error
42
41
error
Error
Error
25
24
20
Error
Error
Error
Error
Error
error
Error
Error
Error
Error
Error
Error
Error
Error
Error
Error
error
error
error
Error
RST:A
Error
23
Error
Error
Error
Error
Error
28
27
26
25
Error
Error
Error
error
Error
Error
Error
Error
Error
error
Error
Error
Error
Error
Error
16
26
26
error
40
39
21
Error
Error
Error
Error
error
Error
error
Error
RST:B
Error
2.3 Telcordia state attributes

The Telcordia state model is based on the concept of the service condition of an
entity. In the model, the state information of an entity is represented by the
following attributes:
Primary State (PST)This attribute indicates the overall service condition of the
entity. The service condition can be either in service (IS) or out of service (OOS).
Primary State Qualifier (PSTQ)This attribute qualifies the PST. If the entity is
in service, the PSTQ indicates whether it is totally or partially in service. If the
entity is out of service, the PSTQ indicates whether this is due to an external
management command or is determined by the network element based on an
internal event or situation.
Secondary State (SST)This parameter provides additional information
pertaining to the PST and PSTQ.
2.3.1 PST and PSTQ values

The following table lists the PST and PSTQ values that the system can use.
Primary state and primary state qualifier values
Value
Description
IS-NR
IS-ANR
OOS-AU
OOS-MA
OOS-MAANR
OOS-AUMA
In service, normal
In service, abnormal
Out of service, autonomous
Out of service, management
Out of service, management and abnormal
Out of service, autonomous and management
2.3.1.1 IS In service
The entity is available for providing its provisioned functions. That is, the entity is
operationally capable and at the same time administratively allowed to provide its
provisioned functions.
If the entity is partially available for providing its provisioned functions, whether
partially capable, partially allowed, or both, it is still considered to be in service.
However, the fact that it is partially available is qualified by a value of the PSTQ
parameter.
For a usage-sensitive entity, as long as the entity is available for providing its
provisioned functions, whether it is currently in use or not, it is still considered in
service.
2-17
2.3.1.2 OOS Out of service

The entity is not available for providing any of its provisioned functions. The
PSTQ parameter will qualify the unavailability of the entity. That is, whether it is
operationally incapable or administratively inhibited from providing its
provisioned functions, or both.
2.3.1.3 NR Normal
This value implies that the entity is normally in service. That is, it is capable and
allowed to provide all of its provisioned functions.
While the entity is in this state, updates of provisioning data and maintenance
activity that affect service are not permitted. Physical actions (such as, unplugging
a circuit pack) performed in this state can generate alarms. Fault detection
continues in this state.
2.3.1.4 ANR Abnormal

The entity is allowed to perform all of its provisioned functions, but it is capable of
performing only part of (but not none of) these functions, or of performing these
functions at a degraded level.
activities that affect service are not permitted. Physical actions (such as
unplugging a circuit pack) performed in this state can generate alarms. Fault
detection is continued to determine if the operational problem has been corrected.
Before a maintenance activity to cure the operational problem can be performed,
the entity must be explicitly removed from service by using the REMOVE or
EDIT commands (the entity transitions into the MAANR state that is discussed
later). Otherwise, the maintenance activity can trigger unnecessary notifications.
2.3.1.5 AU Autonomous
The entity is incapable of performing any of its provisioned functions, and there is
no external administrative restriction inhibiting the entity from performing these
functions.
In general, the cause of incapability is an unsolicited event occurrence on the NE
or in the associated network. Examples of such events include, but are not limited
to, a defect developed in the entity, or its supporting entity is OOS. The transition
between PST=IS and PST=OOS, PSTQ=AU is determined by the NE, based
on the event that occurred in the entity (or in the entitys supporting entity). Such a
transition should not be achieved by simply applying a state change command to
the entity.
activities are not permitted. Physical actions (such as unplugging a circuit pack)
performed in this state can generate an alarm. Fault detection continues to
determine if the operational problem has been corrected or whether additional
operational problems have occurred. Before maintenance activities to cure the

operational problem can be performed, the entity should be explicitly removed
from service by using the REMOVE or EDIT commands (the entity transitions
into the AUMA state that is discussed later). Otherwise, the maintenance activity
can trigger unnecessary notifications.
2.3.1.6 MA Management
The entity is intentionally suspended by the external management command from
performing all of its provisioned functions. In this state, the entity itself is still
operationally capable of, even though it is currently being suspended from performing its provisioned functions. Such suspension is temporary in nature. Otherwise, the permanent suspended functions should be excluded from the domain of
the entitys provisioned functions.
It should be noted that if some functions are not included in the provisioned functions of the entity, then any change of operational capability of the non-provisioned functions should be outside the scope of the state of the entity. For example,
if a bidirectional termination point is provisioned for receiving only, then any
change to its operational capability regarding transmit should not be reflected in
the state of this termination point. That is, the termination point behaves like a
receive-only termination point and shows the state information that is relevant to
receive only.
The PST=OOS, PSTQ=MA state is also called Manual Out-Of-Service. In
other words, the transition between PST=IS and PST=OOS, PSTQ=MA is
caused by a management command external to the NE (for example, by a command from an OS or a craft directed to the entity). Examples of such a command
are the TL1 commands REMOVE, RESTORE, and EDIT.
When equipment is put into the OOS&MA state, alarms against the equipment are
not raised.
2.3.1.7 MAANR Management and abnormal

The entity is operationally capable of performing only part of its provisioned
functions or at a degraded level, and at the same time is intentionally suspended
from performing all of its provisioned functions.
To transition from PST=OOS, PSTQ=MAANR to the in-service state, the cause
of being intentionally suspended is released completely (that is, it transitions to
PST=IS, PSTQ=ANR). The transition from PST=OOS, PSTQ=MAANR to
PST=IS, PSTQ=ANR is done by editing the service from OOS to IS.
When equipment is put into the OOS&MAANR state, alarms against the
equipment are not raised.
2-19
2.3.1.8 AUMA Autonomous and management

The entity is incapable of performing any of its provisioned functions, and at the
same time has been intentionally suspended from performing all of its provisioned
functions.
To transition from PST=OOS, PSTQ=AUMA to the in-service state, both the
causes of being operationally incapable and of being intentionally suspended
must be corrected (either completely or partially).
activities are permitted. Physical actions (such as unplugging a circuit pack)
performed in this state do not generate alarms. Fault detection continues to
determine if an operational problem has been corrected or an additional
operational problem has occurred.
2.3.2 SST values

This parameter provides additional information, called secondary state (SST)
values, pertaining to the PST and PSTQ. For example, it can indicate the type and/
or reason of the external command, or the event that occurred in the NE. Multiple
SST values can be applied to an entity at any given moment.
The following table lists the SST values that the system can use.
Secondary state values
Value
Description
AINS
COMM
FLT
FRCD
LKDO
LPBK
MEA
MT
PWR
SGEO
STDBY
SWDL
UEQ
WRK
Automatic in service
Communication error
Fault
Forced
Locked out
Loopback
Mismatch of equipment and attributes
Maintenance
Loss of shelf power
Supporting entity outage
Standby
Software download
Unequipped
Working
2.3.2.1 AINS Automatic in service

The entity is in a delay transition (to IS) state. The transition to IS is pending on the
correction of off-normal conditions on the entity (such as, UEQ for equipment).
Alarms and threshold crossing alerts (TCA) are not generated for the entity if
AINS is present. Once the off-normal conditions clear, the entity transitions to IS
according to the autonomous rules of the OOS-AU state.
When the ENT command is used to provision an entity, if the requested state in the
command is IS and the required resource is not present (such as circuit pack is not
present for the equipment, or valid signal is not present for the termination point),
then the entity enters the OOS-AU,AINS state and alarms are not generated.
2.3.2.2 COMM Communication error

The entity is OOS because the SCP cannot communicate with the affected circuit
pack, SFP, or XFP.
2.3.2.3 FLT Fault

The entity is OOS because of a hardware fault.
2.3.2.4 FRCD Forced

The entity is FRCD because a user-invoked FRCD protection switch was applied
to the entity.
2.3.2.5 LKDO Locked out

The entity is LKDO because a user-invoked LKDO protection switch was applied
to the entity.
2.3.2.6 LPBK Loopback

The entity is LPBK because the equipment is in the loopback test mode.
2.3.2.7 MEA Mismatch of equipment and attributes

The equipment provisioned is different from the equipment that is inserted. The
system compares the provisioned product equipment code (PEC) to the inserted
equipment PEC.
For SFP and XFP transceivers, the system checks the provisioned protocol bit rate
and the provisioned wavelength against the actual SFP transceiver that is inserted
into the circuit pack.
2.3.2.8 MT Maintenance
The entity has been manually removed from service for maintenance activity. This
value must be accompanied with the PSTQ value MA or AUMA.
2.3.2.9 SGEO Supporting entity outage

The associated facility is in an outage state because its supporting entity is in an
out-of-service state due to equipment missing, an equipment mismatch, or an
equipment failure. The SGEO value is for qualifying the OOS-AU state of an
entity when its supporting entity is OOS-AU, OOS-MA, or OOS-AUMA.
2-21
2.3.2.10 STDBY Standby

The entity is in standby because it backs up another entity and it is synchronized
with the backed up entity. An entity in STDBY can immediately take over the role
of the backed up entity without the need for initialization activity. This is
conditional on the absence of other faults and the current switching state
associated with the entity. This state is only applicable when protection switching
is provisioned.
2.3.2.11 SWDL Software download

The associated entity is in a software download process.
2.3.2.12 UEQ Unequipped

The equipment entity is not equipped with the necessary hardware. This value is
used for clarifying the PSTQ value AU.
2.3.2.13 WRK Working

The entity is working because it is currently the active entity in a redundant object
pair. This state is only applicable when protection switching is provisioned.
2.4 Equipment state management

The following circuit packs support the state attributes discussed in 2.3, Telcordia
state attributes:
Double 1-Channel CWDM OADM (C1ADM)
CWDM and DWDM Splitter/Combiner (CDSC)
1-Channel DWDM OADM (D1ADM)
32-Channel DWDM Active Multiplexer/Demultiplexer Modules
(D32AMD1-4)
32-Channel DWDM Multiplexer/Demultiplexer Module (D32MD1-4)
32-channel DWDM Bi-Directional Multiplexer/Demultiplexer Modules
(D32BMD24 and 42)
DWDM C-band Optical Booster Amplifier (OBA)
DWDM C-band Optical Line Amplifier (OLA)
DWDM C-band Optical Line Amplifier with Mid-stage Access (OLAM)
DWDM C-band Optical Pre-amplifier (OPA)
DWDM Optical Line Amplifier (OLA)
DWDM Optical Line Amplifier with Mid-stage Access (OLAM)
Optical Supervisory Channel (OSC)
Single Optical Supervisory Channel (OSC)
Dispersion Compensating Fiber Modules (SMF20, SMF40, SMF60 and
SMF80)
Single Mode Fiber (SMF) ITU-T DCMs (SMF40, SMF60 and SMF80)
Shelf entities (ES, MS and SH)
Single-channel/Sub-band Booster Amplifier (SBA)
Single-channel/Sub-band Pre-Amplifier (SPA)
Multiport System Control Processor (MSCP)
2-Port 10G Wavelength Regenerator (WR10G)
2-23
4-Port 2.5G Wavelength Regenerator (WR2.5G)

4-Port 2.5G Wavelength Manager SONET-SDH & Data (WM2.5G)
4-Port 1G Wavelength Translator (WT1G)
2-Port GE Muxponder - SONET (MXP2.5G)
2-Port GE Muxponder - SDH (MXP2.5G)
2.5 Amplifier entity state management

The following amplifier entities support the state attributes discussed in 2.3,
Telcordia state attributes:
DWDM C-band Optical Booster Amplifier (OBA)
DWDM C-band Optical Pre-amplifier (OPA)
DWDM Optical Line Amplifier with Mid-stage Access (OLAM)
2.6 Wavelength conversion transceiver port state management

The following wavelength conversion transceiver ports support the state attributes
discussed in 2.3, Telcordia state attributes:
2.7 State management behavior interactions

When equipment is taken out of service, any subordinate entities must be in the
out-of-service state as a prerequisite. Any state change attempted by the operator
when this prerequisite is not satisfied will result in a command failure.
The following Muxponder transceiver ports support the state attributes discussed
in 2.3, Telcordia state attributes:
2.8 State management provisioning interactions

Certain provisioning operations can cause an interruption in service. For example,
the ability to turn off the laser in an amplifier is an important safety feature.
However, if performed by mistake, this operation potentially places terabits of data
at risk of an outage.
If potential service-affecting changes are attempted while the affected component
is providing service, then the provisioning request is rejected with an error.
For further information, see 2.2, Telcordia state model in this document.
2.9 State change reporting

Whenever the state of an entity changes, the change is reported autonomously
through all active management interfaces. Some state changes are initiated by the
operator, while others are caused by system faults or network conditions.
Example
NETSTENDER 02-07-04 23:43:16
A
90 REPT DBCHG
"TIME=23-43-16,DATE=02-07-04,SOURCE=100,LINKID=2-12,
USERID=NETSTENDER,DBCHGSEQ=12:RMV-OA:OLA-1-1-1"
;
2-25
2.10 Supporting and supported physical entities

Netstender circuit packs have a supporting/supported relationship with the devices
that reside on them. In this relationship, the supported entitys operational
capability is affected by the service availability of the supporting entity. That is,
the state of the supported entity is affected by the state of the supporting entity.
However, the state of the supporting entity is not affected by the state of the
supported entity.
An example of this relationship is an optical amplifier and its supporting
equipment. If the supporting equipment is out of service, the supported optical
amplifier is out of service autonomously. In this case, the secondary state of the
optical amplifier indicates supporting entity outage (that is, SST=SGEO).
As a result, if a Netstender circuit pack goes out of service, all devices present on it
autonomously transition to the out-of-service state with the SGEO secondary state
qualifier.
For more information about the Telcordia state model, see 2.2, Telcordia state
model.
2.11 Fault reporting interactions

When an entity is placed in the OOS-MA state, updates of provisioning data and
maintenance activities are permitted. Fault detection continues in this state but
does not generate any alarms.
An alarm is generated if the system is in service. Otherwise, faults are reported as
conditions that can be retrieved.
The primary state of the entity determines, in part, the alarm forwarding
characteristics when conditions are raised against the entity. If the entity is in
service, then a condition might be raised as an alarm. If the entity is in service and
goes out of service, then any active alarms are cleared. If the entity is out of service
and goes in service, then any active conditions are raised as alarms.
Example
NETSTENDER 02-08-26 20:37:13
M
100 COMPLD
"OLA-1-1-1,OA:MJ,T-CTEMP-HT,NSA,02-08-26,02-26-14,NEND,,NA:\"Case
temperature threshold exceeded.\",,,,,"
;
H A P T E R
3.0 Operating the Netstender

This chapter discusses the operational aspects of the Netstender that include:
3.1, Starting up the system
3.2, Establishing a TL1 session using Ethernet
3.3, Establishing a TL1 session using RS-232
3.4, Establishing a TL1 session using a Hayes modem
3.5, Connecting management systems to Netstender ports
3.6, Establishing an expansion shelf interface CLI session
3.7, Understanding the audible and visual indications
3.8, TL1 identifiers
3.9, Events, conditions and alarms
3.10, Circuit pack detection
3.11, In-service shelf reconfiguration of a Netstender 2060
3.12, Shutting down the system
Operating the Netstender
3.1 Starting up the system

The Netstender performs a system initialization when power is switched on.
The Multiport System Control Processor (MSCP) performs a self-test, memory
check and other diagnostic checks.
3.1.1 Communication ports on the Netstender

The Netstender supports the following three communications ports:
Management LAN port
Craft LAN port
RS-232 craft serial port
Figure 3-1 show the location of the three communication ports on the Netstender
1030 shelf.
Figure 3-1 Netstender 1030 communication ports
Optical Circuit Packs
SER
Input
Monitor
A
Cooling Unit
Craft
Fail Active Fan Critical Major Minor
ACO
Mgmnt
-48VDC Feeds
view directly with optical

instruments.
Class 1 LASER PRODUCT
CLASS 3B Hazard Rating
Output
Fail
REL 01
SCP
Craft
System Control Processor
Figure 3-2 shows the location of the three communication ports on the main shelf
of the Netstender 2060.
Figure 3-2 Netstender 2060 main shelf communication ports
Main Shelf Interface
Mon Line I n
D32MDE2
Out
In
Mon Line Out
In
Fail
ESD
2
In
S/N: BTIM01D1BJ25D
WR
WR
SER
4
Fail
S/N: BTIM01D1BJ25D
Fail Fa
Shelf 2
S/N: BTIM01D1BJ25D
-48 VDC
Feeds
Cooling Unit
Notes
Craft
Fail
Fail Fa
Shelf 3
Shelf 4
Shelf 5
Fail Fa
S/N: BTIM01D1BJ25D
Shelf 6
SCP
OSC 1
Drop
Eth 1
OSC 2
Drop
Fail
2
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
OSC
6
Tray
Multiport System Control Processor
For the Netstender 2060 only: A crossover Ethernet cable is required if a direct
connection is made between a PC or laptop to the management LAN port of the
Netstender 2060. A straight-through Ethernet cable is required for a direct
connection from a PC or laptop to the craft LAN port of the Netstender 2060.
For the Netstender 1030 only: The type of Ethernet cable is not a restriction. The
Ethernet transceiver automatically determines the signaling requirements.
The Netstender Ethernet ports are set to Auto-Negotiate. To ensure optimum

communication between the Netstender and connected equipment, we recommend
that you set the equipment to Auto-Negotiate, as well.
3.2 Establishing a TL1 session using Ethernet
Note
Use 3.2.1, Method One: Connecting through the management LAN, or 3.2.2,
Method Two: Connecting through the craft LAN port, to establish an Ethernet
connection to the Netstender.
The same functions are available through the craft LAN and the management LAN
interfaces.
The following table lists the IP addresses for the Netstender LAN communication
ports.
IP Addresses
Communications Port Default IP Address Default IP Mask Default IP Gateway
Default IP Addresses:
Management LAN Port
Craft LAN Port
For a PC Connected To:1
Management LAN Port
Craft LAN Port
10.0.0.1
192.168.17.1
255.0.0.0
255.255.255.0
10.x.y.z2
192.168.17.z3
255.0.0.0
255.255.255.0
0.0.0.0
0.0.0.0
1. You do not need to configure a default gateway on the PC.

2. Where x and y are 0 to 255, and 2 z 254
3. Where 2 z 254
Note
The Netstender Ethernet ports are set to Auto-Negotiate. To ensure optimum

communication between the Netstender and connected equipment, we recommend
that you set the equipment to Auto-Negotiate as well.
Figure 3-3 shows the two methods for establishing a TL1 session using Ethernet
with the Netstender 2060.
Figure 3-3 Establishing a TL1 session with a Netstender 2060 using Ethernet
Management
Network
Hub or
Switch
Management
LAN Port 10.0.0.1
Craft
LAN Port
192.168.17.1
Method 1
Method 2
PC
IP Address: 10.0.0.X
Mask: 250.0.0.0
telnet 10.0.0.1 3083
PC
IP Address: 192.168.17.x
Mask: 255.255.255.0
telnet 192.168.17.1 3083
Figure 3-4 shows the two methods for establishing a TL1 session using Ethernet
with the Netstender 1030.
Figure 3-4 Establishing a TL1 session with a Netstender 1030 using Ethernet
Management
Network
Hub or
Switch
Management
LAN Port
10.0.0.1
Craft
LAN Port
192.168.17.1
Method 1
PC
IP Address: 10.0.0.X
Mask: 250.0.0.0
telnet 10.0.0.1 3083
Method 2
PC
IP Address: 192.168.17.x
Mask: 255.255.255.0
telnet 192.168.17.1 3083
3.2.1 Method One: Connecting through the management LAN

Authorization required
Superuser
Note
Provisioning
Maintenance
Surveillance
Use this procedure to connect a PC, or router, to the Netstender through a hub or
switch that is connected to the management LAN port.
For the Netstender 2060 only, you require a CAT 5 shielded, grounded Ethernet
straight-through cable of sufficient length with RJ-45 male connectors to
connect an Ethernet hub or switch to the management LAN port of the Netstender.
To connect a PC directly to the management LAN port on the Netstender 2060,
you require a CAT 5 shielded, grounded Ethernet crossover cable of sufficient
length with RJ-45 male connectors.
The Netstender 1030 Ethernet LAN ports automatically determine what device is
attached and they automatically configure the input and output signals for the
Ethernet cable used. As a result. either straight-through or crossover Ethernet
cables can be used.
Connecting through the management LAN
Step
Action
Provision the IP Address

If not yet configured, provision the Netstender with the IP address of your intended
management Ethernet LAN. See the procedure Changing the default IP address and
mask in this document.
Connect the Netstender Ethernet Cables
a) Insert one end of a shielded and grounded Ethernet cable in the management LAN
port.
b) Insert the other end of the shielded and grounded Ethernet cable in the RJ-45
female Ethernet LAN connector on your hub or switch.
Connect the Computer Ethernet Cables
a) Insert one end of a shielded and grounded Ethernet cable in the RJ-45 female
Ethernet LAN connector on your PC.
female connector of your management LAN.
Connecting through the management LAN

Step
Action
Establish a TL1 Session

From a command prompt window, establish an Ethernet session to the management
LAN port by typing the following at the command line prompt:
telnet 10.0.0.1 30831
Response
A telnet session is established and the system responds with the Netstender prompt.
Log on to Netstender
Enter the following syntax at the Netstender prompt:
ACT-USER:[TID]:<uid>:<CTAG>::<pid>;
where
TID
uid
CTAG
pid
is the target identifier (NETSTENDER is the default target identifier)

is the user identifier (admin is the default system administrator uid)
is the correlation tag (100 is the default correlation tag)
is the password identifier (admin is the default system administrator pid)
Example
ACT-USER:NETSTENDER:admin:100::*****;
Response
The Netstender sends back a COMPLD message to indicate a successful log on.
You have successfully completed this procedure.
1. See 3.5.2, Modes of TL1 operation for details about the selectable port numbers in an IP
address.
3.2.2 Method Two: Connecting through the craft LAN port

Superuser
Note
Provisioning
Maintenance
Surveillance
Use this procedure to connect a PC to the Netstender through the craft LAN port.
For the Netstender 2060 only, you require a CAT 5 shielded, grounded straightthrough Ethernet cable of sufficient length with RJ-45 male connectors to
connect a PC to the craft LAN port of the Netstender.
The Netstender 1030 Ethernet LAN ports automatically determine what device is
attached and they automatically configure the input and output signals for the
Ethernet cable used. As a result, either straight-through or crossover Ethernet
cables can be used.
Connecting through the craft LAN port

Step
Action
Provision the IP Address

If not yet configured, provision the Netstender with the IP address of your intended craft
Ethernet LAN. See the procedure Changing the default IP address and mask in this
document.
Connect the Ethernet Cable
a) Insert one end of the shielded and grounded Ethernet cable in the craft LAN port.
female Ethernet LAN connector on your PC or laptop.
From a command prompt window, establish an Ethernet session to the craft LAN port
by typing the following at the command line prompt:
telnet 192.168.17.1 30831
Response
A telnet session is established and the system responds with the Netstender prompt.
Log on to the Netstender
Enter the following syntax at the Netstender prompt:
where
TID
uid
CTAG
pid

Example
Response
address.
3.2.3 Changing the IP address and mask from the default

Superuser
Note
Provisioning
Maintenance
Surveillance
Using the ED-IP command can result in temporary loss of contact with the
network element connection.
To change the default IP address information for the network element, enter the
following syntax at the TL1 command line interface:
ED-IP:[TID]:<aid>:<CTAG>:::[IPADDR=<ipaddr>];
where
aid
Important
is IP-NMS or ENET-1 for the management LAN

is IP-CRAFT or ENET-2 for the craft LAN
Configure the IP-NMS and IP-CRAFT on separate subnets.

Example
To change the IP address on the craft LAN port to 200.1.1.22, enter the following
at the command line interface:
ED-IP:NETSTENDER:IP-CRAFT:100:::IPADDR=200.1.1.22;
Response
The Netstender returns a COMPLD message and a DBCHG message:

NETSTENDER 02-06-30 20:41:44
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-06-30 20:41:45
A
55 REPT DBCHG
"TIME=20-41-45,DATE=02-06-30,SOURCE=100,LINKID=217,USERID=NETSTENDER,BCHGSEQ=30:ED-IP:IPCRAFT:IPADDR=200.1.1.22,IPMASK=255.255.255.0"
;
3.2.4 Changing the default gateway

Superuser
Notes
Provisioning
Maintenance
Surveillance
To change the default gateway for the network element, enter the following syntax
at the TL1 command line interface:
ED-SYS:[TID]::<CTAG>:::[GATEWAY=<gateway>];
where
gateway
Note
is the gateway IP address
The gateway address must be within the same subnet as the provisioned network.
Example
To change the gateway to 156.12.4.12, enter the following at the command line
interface:
ED-SYS:NETSTENDER::100:::GATEWAY=156.12.4.12;
Response

NETSTENDER 02-11-22 13:52:47
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-22 13:52:47
A
68 REPT DBCHG
"TIME=13-52-47,DATE=02-11-22,SOURCE=100,LINKID=2-23,USERID=admin,
DBCHGSEQ=37:ED-SYS:::GATEWAY=156.12.4.12"
;
3.3 Establishing a TL1 session using RS-232

Superuser
Note
Provisioning
Maintenance
Surveillance
Use this procedure to connect a PC to a Netstender through the RS-232 craft serial
port on the shelf.
For Netstender 2060 systems, use cable BP1A58AA with SCP BP1A20AA, and
cable BP1A58EC with MSCP BP1A20BA.
For Netstender 1030 systems, use cable BP1A58AA with SCP BP1A21AA.
Figure 3-5 Establishing a Netstender 2060 TL1 session with RS-232 craft serial port
Craft RS-232
Serial Port
For SCP BP1A20AA,

use cable BP1A58AA.
For MSCP BP1A20BA,
use cable BP1A58EC.
PC or Laptop
Figure 3-6 Establishing a Netstender 1030 TL1 session with RS-232 craft serial port
Craft RS-232
Serial Port
For SCP BP1A21AA,

use cable BP1A58AA.
PC or Laptop
Connecting through the RS-232 craft serial port on the Netstender

Step
Action
Connect the RS-232 Cable
a) Insert one end of the RS-232 cable in the craft serial port on the Netstender.
b) Insert the other end of the RS-232 cable in the RS-232 male connector on your PC or
laptop.
Set the RS-232 Parameters
Set the default RS-232 parameters for the PC to match the Netstender:
Rate
9600 bps
Data Bits
8 bits
Parity
None
Stop Bits
1 bit
Flow Control
None
From a terminal emulator, establish a TL1 session to the Netstender by pressing the
Return key.
Response
The system responds with the Netstender prompt.
Log on to the Netstender
To log on to the Netstender, enter the following at the TL1 command line interface:
where
TID
uid
CTAG
pid

Note: User identifier admin and password identifier admin are the default system
administrator credentials.
Example
Response
3.3.1 RS-232 serial communications

The Netstender has a craft serial port that uses the RS-232 protocol.
Cables required
When connecting a PC or laptop to the craft serial port, use a straight-through

RS-232 cable with a DB-9 pin male connector.
If you anticipate using the RS-232 serial port, determine the length of cable
required to connect the Netstender to your PC, and prepare the cable with the
appropriate male connector.
RS-232 pin assignment
The following figure shows the RS-232 DB-9 pin DCE connector as well as the
RS-232 RJ-45 8 pin connector and the associated pin numbering schemes.
DB-9 Pin Connector and 8 Pin RJ-45 Connector Numbering Schemes
Male
Side
DB-9 Pin Connector
RJ-45 8 Pin Connector
The following table lists the RS-232 pin assignment for the DB-9 pin connector
and RJ-45 connector pin numbering schemes.
Pin Assignments for RS-232 DB-9 Pin Connectors and RS-232 RJ-45 Connectors
DB-9 Pin
Connector
1
2
3
4
5
6
7
8
9
DCE Purpose
Data Terminal Ready
Transmitted Data
Received Data
DTE Ready
Signal Ground
DCE Ready
Clear to Send
Request to Send
Ring Detector
RJ-45
Connector
1
2
3
4
5
6
7
8
DCE Purpose
Request to Send
Data Terminal Ready
Transmitted Data
Signal Ground
Signal Ground
Received Data
DCE Ready
Clear to Send
Note
BTI Systems stocks the following RS-232 serial cables:
For Netstender 2060 systems, use cable BP1A58AA with SCP BP1A20AA,
and cable BP1A58EC with SCP BP1A20BA.
For Netstender 1030 systems, use cable BP1A58AA with SCP BP1A21AA.
The following table lists the BP1A58AA RS-232 cable pin assignment between
the DB-9 pin male connector and the DB-9 pin male connector that is available
from BTI Photonic Systems.
Pin Assignment of the BTI Photonics System RS-232 cable - BP1A58AA
DB-9 Pin
Connector
2
3
5
Color Code
White/Blue
Orange/White
White/Green
Function
Transmit
Receive
Ground
DB-9 Pin
Connector
3
2
5
Color Code
White/Blue
Orange/White
White/Green
Function
Receive
Transmit
Ground
3.4 Establishing a TL1 session using a Hayes modem

Provisioning
Superuser
Maintenance
Surveillance
Use this procedure to connect a PC to the Netstender through a Hayes modem.

The Netstender connects from the craft serial port on the SCP to the Hayes modem
through a null modem cable.
Caution
Unprotected modems should not be connected to the Netstender craft serial port.
The craft serial port does not log users off when the carrier detect is lost, which can
leave a security hole. To avoid this, use a secure modem.
Establishing a TL1 session using a Hayes modem
Craft
Serial Port
Switching
Network
Hayes Modem
Modem
Procedure
Step
Action
Configure the Hayes modem

Before connecting the Hayes modem to the Netstender, ensure that the Hayes
modem is configured for auto-answer by doing the following:
a) Using a null modem cable, connect the serial port of a PC to the serial port of the
Hayes modem. Note: A DB-9 to DB-25 adapter may be required to connect the null
modem cable to the serial port of the Hayes modem.
b) Run HyperTerminal, or another terminal emulation program, on the PC.
c) Power down and then power up the Hayes modem.
d) In the HyperTerminal program window, type the following string and then press
Enter:
AT&F0S0?
e) The modem should respond with either a single 0, a series of 000 and/or an
OK .

Step
Action
1
(contd)
f) After receiving the response, type the following string and then press Enter:
AT&F0S0=1Q1E0&D0&K0&C0&W
where
&F0
S0=1
Q1
E0
&D0
&K0
&C0
&W
is the factory settings

is the auto-answer function
is the result codes off function
is the echo off function
is the ignore DTR function
is the flow control off function
is the force DCD active function
is the store profile function
g) This time there should not be any response from the modem because the
command string disables the output.
h) Connect a telephone line to the RJ-11 input receptacle of the Hayes modem.
i) Test the Hayes modem for auto-answer by dialing in to the modem. The modem
should answer the call.
j) To complete this step, hang up and disconnect the Hayes modem from the PC by
entering the following string and then pressing Enter:
ATH
2
Set up the cabling for the Hayes modem connection to the Netstender
To set up the cabling for the Hayes modem connection to the Netstender, do the
following:
a) Using a null modem cable, connect the serial port of the Hayes modem to the craft
serial port on the SCP of the Netstender. Note: A DB-9 to DB-25 adapter may be
required to connect the null modem cable to the serial port of the Hayes modem.
b) If not already connected, connect the telephone line to the RJ-11 input receptacle of
the Hayes modem.
c) Configure far-end PCs with HyperTerminal, or another terminal emulation program.
d) The far-end PCs also require a modem connection to access the Hayes modem at
the Netstender location.
Establish a TL1 session to the Netstender
Once all the cabling is completed, establish a TL1 session to the Netstender by doing
the following:
a) At the far-end PC, dial in to the Hayes modem.
b) Once the connection is established, press Enter. You should see a TL1 prompt
(that is, >) when the connection is established.
3.5 Connecting management systems to Netstender ports

The Netstender is designed to be easily integrated into existing networks and
managed by third-party element management systems (EMS), network
management systems (NMS), and operation support systems (OSS).
The Netstender supports standard communication interfaces over serial and IP
connections including Telcordia Transaction Language (TL1). In addition, the
Netstender provides the Network Node Controller (NNC), a Java-based craft
management interface.
3.5.1 Netstender SNMP support

The Simple Network Management Protocol (SNMP) is an application-layer
protocol designed to facilitate the exchange of management information between
network devices. SNMP enables trap-directed notification of events on a device.
BTIs SNMP implementation supports SNMP Version 1 (SNMPv1) as defined in
RFCs 1155, 1157, 1212, 1213, and 1215. The SNMP implementation also supports
SNMPv2c as defined in RFCs 1901 through 1907. SNMPv3 is not supported in
this release.
BTI enterprise MIBs, as provided on the Customer Documentation CD, define
BTI-specific MIB objects and notifications. These MIBs are available in both
SNMPv1 and SNMPv2 versions. In addition, BTIs SNMP agent supports both
SNMPv1 and SNMPv2c Protocol Data Unit (PDU) messages.
The system and snmp group objects in MIB-II, as defined in RFC 1213, are
supported for both read and write access. In addition, the Netstender MIB includes
a group of system-related objects under the networkElement branch.
Enterprise-specific fault management trap messages for all alarms and nonalarmed conditions reported by the Netstender are supported.
For each alarm, a raise and clear trap is defined. A read-only table is defined,
which provides a listing of active conditions and alarms on the Netstender.
Performance monitoring of current and historical PM values for optical amplifiers
and optical transceivers can be also retrieved.
Additionally supported is full provisioning, configuration, and status monitoring
support for optical amplifiers and optical transceivers.
Inventory retrieval is available with this latest release.
Support is provided for the optical supervisory channel (OSC) and network management interfaces.
For details about setting up and using SNMP, refer to the SNMP Reference Guide.
3.5.2 Modes of TL1 operation

The Netstender can communicate with EMS, NMS, and OSS in the following two
modes:
Raw TL1 (that is, suitable for machine operators)
Standard TL1 (that is, suitable for verbose manual operators)
Each mode is selectable through separate port numbers in the IP address. The
following table lists the port numbers and describes the difference between the two
TL1 communication modes.
Selectable TL1 communication modes
IP Address
TCP Port
Meaning
w.x.y.z1
3082
w.x.y.z1
3083
Port 3082 provides raw TL1 protocol that is faster than standard
TL1 protocol. No prompts, echoes, or online help are available.
Port 3083 provides the standard TL1 protocol that includes
prompts, echoes, and online help.
1. w.x.y.z should be the IP address that you have assigned to your IP-NMS port.
3.6 Establishing an expansion shelf interface CLI session

The Netstender expansion shelf supports the following two communications ports
on an expansion shelf interface circuit pack:
Craft LAN port
RS-232 craft serial port
The following figure shows the location of the two communications ports on the
expansion shelf.
Expansion shelf communication ports
Craft LAN Port
Craft Serial Port
Trouble
Power
PEC
BP1A04AA
PEC
03
BP1A04AA
WR
03
ESD
2
S/N: BTIM01D1BJ25D

view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
Fail Fa
S/N: BTIM01D1BJ25D
CAUTION: I nvisible
Input
SBA
CAUTION: I nvisible

view directly with
Class 1 LASER
PRODUCT
SER
S/N: BTIM01D1BJ25D
Output
Input
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
SER
S/N: BTIM01D1BJ25D
Input
Output
Filler
S/N: BTIM01D1BJ25D
SPA
OPA
6
Output
Expansion Shelf IP Addresses

Communications Port Default IP Address Default IP Mask Default IP Gateway
Default IP Address:
Craft LAN Port
192.168.17.1
For a PC Connected To:1
Craft LAN Port
192.168.17.z2
255.255.255.0
0.0.0.0
255.255.255.0
1. You do not need to configure a default gateway on the PC.

2. Where 2 z 254
Expansion shelf default RS-232 parameters
The default RS-232 parameters for the PC to match the Netstender are:
Rate
Data Bits
Parity
Stop Bits
Flow Control
9600 bps
8 bits
None
1 bit
None
3.6.1 Connecting through the craft LAN port on an ESI circuit pack
Superuser
Provisioning
Maintenance
Surveillance
Use this procedure to connect a PC to the craft LAN port on an expansion shelf
interface (ESI) circuit pack.
To connect a PC directly to the craft LAN port on an ESI circuit pack, you require
a CAT 5 shielded, grounded Ethernet cable of sufficient length with RJ-45 male
connectors.
The craft LAN port automatically determines what device is attached and it
automatically configures the input and output signals for the Ethernet cable used.
As a result, either straight-through or crossover Ethernet cables can be used.
Connecting through the craft LAN port
Step
Action
Connect the Ethernet cable
a) Insert one end of the shielded and grounded Ethernet cable in the craft LAN port.
female Ethernet LAN connector on your PC or laptop.
Establish a telnet session
From a command prompt window, establish an Ethernet session to the craft LAN port
by typing the following at the command line prompt:
telnet 192.168.17.1 30831

Response
A telnet session is established and the system responds by displaying the ESI main
menu. For further details about the ESI command line interface, refer to Appendix D:
ESI command line interface .
address.
3.6.2 Connecting through the craft serial port on an ESI circuit pack
Superuser
Note
Restriction
Provisioning
Maintenance
Surveillance
Use this procedure to connect a PC to the RS-232 craft serial port on the expansion
shelf interface (ESI) circuit pack.
An RS-232 straight-through cable of sufficient length with an RJ-45 male
connector for the Netstender and an appropriate DB-9 pin female connector for the
PC are required.
The Ethernet port on the ESI circuit pack labelled To Extension is currently not
supported.
Connecting through the RS-232 craft serial port on the expansion shelf interface
Step
Action
Connect the RS-232 Cable
a) Insert one end of the RS-232 cable in the craft serial port on the expansion shelf
interface (ESI) circuit pack.
b) Insert the other end of the RS-232 cable in the RS-232 female connector on your PC
or laptop.
Set the RS-232 Parameters
Set the default RS-232 parameters for the PC to match the Netstender:
Rate
9600 bps
Data Bits
8 bits
Parity
None
Stop Bits
1 bit
Flow Control
None
From a terminal emulator, establish a command line interface session to the ESI circuit
pack by pressing the Return key.
Response
A session is established and the system responds by displaying the ESI main menu.
For further details about the ESI command line interface, refer to Appendix D: ESI
command line interface .
3.7 Understanding the audible and visual indications

3.7.1 Location of Netstender 2060 main shelf and system alarms
Figure 3-7 indicates the location of the main shelf and system alarms on the MSI
circuit pack.
Figure 3-7 Netstender 2060 shelf and system alarm locations
System Alarms
Shelf Alarms
3.7.2 Location of Netstender 2060 expansion shelf alarms

Figure 3-8 indicates the location of the expansion shelf alarms on the ESI circuit
pack.
Figure 3-8 Netstender expansion shelf alarm location
Expansion Shelf Alarms
Shelf Alarms
Trouble
Power
PEC
BP1A04AA
PEC
03
S/N: BTIM01D1BJ25D
Input
SBA
SER
S/N: BTIM01D1BJ25D
Output
Filler
S/N: BTIM01D1BJ25D
03
S/N: BTIM01D1BJ25D
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
BP1A04AA
Eth 1
Fail
3.7.3 Location of Netstender 1030 shelf and system alarms

Figure 3-9 indicates the location of the shelf and system alarms on the SCP circuit
pack.
Figure 3-9 Netstender 1030 shelf and system alarm locations
Shelf Alarms
System Alarms
3.7.4 Netstender system alarm LEDs

Both the Netstender 1030 1U shelf and the Netstender 2060 main shelf have three
alarm LEDs. Figure 3-10 explains the meaning of the different LED displays.
Figure 3-10 Netstender system alarm LEDs
Critical Major Minor Definition

Critical alarm
Major alarm
Minor alarm
Normal operation,
no alarms
Note
There can be any combination of alarm occurrences. As a result, there can be any
combination of system alarm LEDs lit at any time.
3.7.5 Audible alarms and office alarms

The office alarm interface on the Netstender 1030 system control processor (SCP)
and the Netstender 2060 management shelf interface (MSI) circuit packs provide
audible and visual office alarms.
For the Netstender 2060, if the MSI or the MSCP circuit packs are out of service or
experiencing a fault, the office alarms are not available.
For the Netstender 1030, if the SCP circuit pack is out of service or experiencing a
fault, the office alarms are not available.
For further information, see the Installation and Commissioning Guide.
3.7.6 Shelf and circuit pack LED behavior

The Netstender has light emitting diodes (LEDs) that provide visual indications of
shelf and circuit pack behavior.
Netstender shelf LEDs
Each Netstender 2060 main shelf has a Trouble (red) and a Power (green) LED.
For the Netstender 2060, the LEDs are located on the Main Shelf Interface (MSI)
circuit pack.
For the Netstender 1030, the LEDs are located on the Netstender 1030 system
control processor circuit pack.
Netstender circuit pack LEDs
Note
Most circuit packs have a Fail (red), Active (green), and Fault (Yellow) LED.
During circuit pack initialization, the red and green LEDs will be on for about 90
seconds before the green LED is the only remaining LED that is on in a no-fault
situation.
3.7.6.1 Netstender 2060

Figure 3-11 summarizes the LED behavior for the Netstender 2060.
Figure 3-11 Netstender 2060 LED behavior
Off
On Normal
Off
On
Off Normal operation
On
Fault on shelf
On or Shelf Interface
Off
On
On External fault
On
Off
Off Equipment fault
Off Power failure
On
On
Off Equipment fault
Recommended actions:
On
Off
Confirm LEDs are working by

pressing the Lamptest button.
Equipment and
On external fault
On
On
Equipment and
On external fault
Off
Off
Off Power failure
Off
For more information, refer to the

Alarm and Troubleshooting
Guide.
3.7.6.2 Netstender 1030

Figure 3-12 summarizes the LED behavior for the Netstender 1030.
Figure 3-12 Netstender 1030 LED behavior
3.7.7 Alarm cutoff and lamp test button

The alarm cutoff and lamp test button serves two purposes.
First, if an audible alarm is present, the alarm can be stopped by pressing the alarm
cutoff/lamp test button momentarily. This results in the audible alarms being
cutoff. If any new alarm appears, it re-triggers the audible alarm.
Second, if no audible alarm is present, pressing the alarm cutoff/lamp test button
continuously for two seconds has the following effect:
For Netstender 2060 main shelf: Turns on all of the management shelf interface
(MSI) LEDs and all of the circuit pack LEDs in the main shelf for a 10-second
lamp test.
For Netstender 2060 expansion shelf: Turns on all of the expansion shelf
interface (ESI) LEDs, except for the daisy chain port SFP LEDs. Additionally,
all of the circuit pack LEDs in the expansion shelf turn on for a 10-second lamp
test.
Note
For Netstender 1030: Turns on all of the Netstender 1030 System Control
Processor (SCP) LEDs and all of the circuit pack LEDS for a 10-second lamp
test.
If an LED does not turn on during the test, the circuit pack needs to be replaced.
3.7.8 Alarm masking

Alarm masking occurs when an alarm with a higher level of importance takes
precedence over an alarm of less importance. Alarms at the shelf level override
alarms at the circuit pack level. Likewise, circuit pack alarms override alarms at
subordinate levels (for example, optical amplifiers, optical supervisory channel,
wavelength regenerator, and wavelength translator).
For further information about alarm masking, see the Alarm and Troubleshooting
Guide.
3.8 TL1 identifiers

Based on TL1 requirements, the Netstender uses a hierarchical structure that is
reflected in the system identifiers (SID) and access identifiers (AID) that are part
of the TL1 commands and messaging.
3.8.1 Network element SID
Note
The Netstender is defined as a network element. Each individual network element

should have a unique SID, such as NETSTENDER12, if the network elements
communicate to a common management system.
The default SID for the Netstender is NETSTENDER. Each individual network
element should have a unique SID.
3.8.2 Subordinate elements AID

Subordinate entities in a network element are identified through AIDs. The AID
identifies the equipment, facility, or specific management entity in a particular
network element that is to be addressed in a command string.
The AID parameter typically consists of a number of fields separated by hyphens,
which describe the physical location of the target for the TL1 request.
The following table lists the AIDs that the Netstender supports.
Table 3-1
Netstender Access Identifier Structure
AID
Syntax Structure
Inventory
CU-<shelf#>
ES-<shelf#>
ESFP-<shelf#>-<slot#>-<port#>
ESFP-<shelf#>-<port#>
MS-<shelf#>
SFP-<shelf#>-<slot#>-<port#>
SH-<shelf#>
SI-<shelf#>
SLOT-<shelf#>-<slot#>
XFP-<shelf#>-<slot#>-<port#>
C1ADM-<shelf#>-<slot#>
C2ADM-<shelf#>-<slot#>
C4MD-<shelf#>-<slot#>
CDSC-<shelf#>-<slot#>
CS-<shelf#>-<slot#>
D1ADM-<shelf#>-<slot#>
Equipment
Table 3-1
AID
Optical Amplifier
Optical Supervisory Channel

OSPF
OSPF Interface
4-Channel CWDM Mux/Demux
Modules 1-4 (channels 1-4, 5-8, 9-12,
13-16)
Syntax Structure
D4MD-<shelf#>-<slot#>
D32AMD1-<shelf#>-<slot#>
D32MD1-<shelf#>-<slot#>
ES-<shelf#>
MS-<shelf#>
MXP-<shelf#>-<slot#>
OBA-<shelf#>-<slot#>
OCT-<shelf#>-<slot#>
OLA-<shelf#>-<slot#>
OLAM-<shelf#>-<slot#>
OPA-<shelf#>-<slot#>
OSC-<shelf#>-<slot#>
SCP-<shelf#>-<slot#>
SH-<shelf#>
SMF20-<shelf>-<slot#>
SMF40-<shelf>-<slot#>
SMF60-<shelf#>-<slot#>
SMF80-<shelf#>-<slot#>
SBA-<shelf#>-<slot#>
SPA-<shelf#>-<slot#>
WM-<shelf#>-<slot#>
WR-<shelf#>-<slot#>
WT-<shelf#>-<slot#>
OLA-<shelf#>-<slot#>-<#>
OLAM-<shelf#>-<slot#>-<#>
OBA-<shelf#>-<slot#>-<#>
OPA-<shelf#>-<slot#>-<#>
SBA-<shelf#>-<slot#>-<#>
SPA-<shelf#>-<slot#>-<#>
OSC-<shelf#>-<slot#>
OSPF-<shelf#>-<slot#>
OSPF-<shelf#>-<slot#>-<#>
C4MD-<shelf#>-<slot#>-<line#>
C4MD-<shelf#>-<slot#>-<line#>-E (expansion)
C4MD-<shelf#>-<slot#>-<line#>-<channel#>
Table 3-1
AID
Syntax Structure
1-Channel CWDM OADM
C1ADM-<shelf#>-<slot#>-<line#>
C1ADM-<shelf#>-<slot#>-<P> (passthrough)
C1ADM-<shelf#>-<slot#>-<line#>-<channel#>
CDSC-<shelf#>-<slot#>-<line#>
CDSC-<shelf#>-<slot#>-<line>-C (CWDM)
CDSC-<shelf#>-<slot#>-<line#>-D (DWDM)
CS-<shelf#>-<slot#>-<line#>
D1ADM-<shelf#>-<slot#>-<line#>
D1ADM-<shelf#>-<slot#>-<line#>-<P> (passthrough)
D1ADM-<shelf#>-<slot#>-<line#>-<channel#>
D2ADM-<shelf#>-<slot#>-<line#>-<P> (passthrough)
D4ADM-<shelf#>-<slot#>-<line#>--P (passthrough)
D4MD-<shelf#>-<slot#>-<line#>
D4MD-<shelf#>-<slot#>-<line#>-E (expansion)
D4MD-<shelf#>-<slot#>-<line#>-<channel#>
D32AMD1-<shelf#>-<slot#>-<line#>
D32AMD1-<shelf#>-<slot#>-<line#>-E (expansion)
D32AMD1-<shelf#>-<slot#>-<line#>-<channel#>
D32MD1-<shelf#>-<slot#>-<line#>
D32MD1-<shelf#>-<slot#>-<line#>-E (expansion)
D32MD1-<shelf#>-<slot#>-<line#>-<channel#>
Double 1-Channel OADM
2-Channel CWDM OADM
CWDM and DWDM Splitter/Combiner
DWDM Bi-Directional Coupler/Splitter

1-Channel DWDM OADM
2-Channel DWDM OADM
4-Channel DWDM OADM
4-Channel DWDM Mux/Demux
32-Channel DWDM Active Mux/

Demux Module 1 (channels 1 to 8)
Module 1 (channels 1 to 8)
Table 3-1
AID
Syntax Structure

SMF40-<shelf#>-<slot#>-<port#>-<channel#>
SMF20-<shelf#>-<slot#>-<port#>
WM-<shelf#>-<slot#>-<port#>
WR-<shelf#>-<slot#>-<port#>
WT-<shelf#>-<slot#>-<port#>
MXP-<shelf#>-<slot#>-<L1,L2, C1,C2,C3,C4>
MXP-<shelf#>-<slot#>-<L1,L2, C1,C2,C3,C4>-<facility#>

SMF Dispersion Compensating Fiber
Modules
Wavelength Manager Transceiver

Wavelength Regenerator Transceiver
Wavelength Translator Transceiver
2-Port GE Muxponder
STS1 (SONET)/VC4 (SDH) Path
Facility Object
Virtual Concatenation Group
Product Release Number Software
Image
IP Interface
Management Port/Channel/Interface
User
User Profile
VCG-<shelf#>-<slot#>-<L1,L2>-<VCG#>
ACTIVE
INACTIVE
IP-<shelf#>-<slot#>-<port#>
IP-NMS or ENET-1
IP-CRAFT or ENET-2
SER-1
USER
USER
3.9 Events, conditions and alarms

3.9.1 Events
An event is an autonomous message that is reported from a network element
across its management interfaces. An event can indicate status, a periodic report of
information, or asynchronous command completion information. There are no
raise or clear semantics associated with events.
The information that is typically reported with an event includes the AID of the
entity reporting the event, the event type, whether the event is service affecting, the
date and time of the event, and a text description of the event being reported.
General events are reported using the REPTÊVT message as well as other
specific autonomous messages. The most common types of events issued by the
Netstender include database change (REPT^DBCHG) events and state change
(REPT^RMV and REPT^RST) events. These are used to keep the operator
informed of the state of the Netstender and are also used by the NNC to remain
synchronized with the Netstender.
Additionally, threshold crossing alerts are reported to the Operations Support
System (OSS) in the form of REPTÊVT^XCVR system messages.
3.9.2 Conditions
When a fault is detected on a network element and continues to exist for a
minimum time period, it raises a fault condition that is an indication of whether or
not this particular fault currently exists on the NE. When the fault is resolved, the
fault condition is cleared (that is, removed from the system).
3.9.3 Alarms
Depending on the state of the system or equipment at the time, fault conditions can
be reported as alarms. An alarm is an autonomous message that is reported from a
network element across its management interfaces corresponding to the act of
raising and clearing of the underlying fault condition.
If equipment is in-service or out-of-service autonomous, then any fault conditions
pertaining to that equipment are reported autonomously as alarms. An alarm may
not be reported if it is outranked by another active alarm. Each alarm is sent with
the AID of the entity that has the alarmed condition, the notification code of the
alarmed condition (one of critical, major or minor), the condition type, whether the
alarmed condition is service affecting or not, the date and time when the alarmed
condition was raised, and a text description of the alarmed condition. A list of the
active alarms can also be retrieved by the TL1 command RTRV-ALM-ALL.
If equipment is out-of-service maintenance, then autonomous alarm reporting is
suppressed for the entity. If the entity transitions from in-service to out-of-service
maintenance, then any raised alarms are cleared. However, in both cases, the
conditions still exist and can be retrieved by the TL1 command
RTRV-COND-ALL. Each condition is listed with the AID of the entity that has
the condition, the notification code of the condition (critical, major or minor), the
condition type, whether the condition is service affecting or not, the date and time
when the condition occurred, and a text description of the condition.
3.10 Circuit pack detection

The multiport system control processor (MSCP) detects when circuit packs are
inserted and removed from any of the Netstender shelves that make up the network
element.
When a circuit pack is inserted, it is initialized to a default state and checked for
slot compatibility as well as for hardware and firmware revision compatibility. If
the circuit pack is found to be compatible, any pre-provisioned information is
downloaded to the circuit pack. When a circuit pack is removed, the system sends
an event message and raises an equipment missing alarm. Additional alarms may
also be triggered.
The Netstender is capable of differentiating between the following slot conditions:
an empty slot
a single-width and a double-width slot
a double-width slot that contains two single-width circuit packs
a slot populated with a filler circuit pack
a slot populated with any circuit pack that is operating normally
a slot populated with any circuit pack that has failed
a slot populated with a circuit pack that is unknown to the system (an inserted
circuit pack can be unknown because it is not supported by the current software
load)
3.10.1 System responses for common equipment circuit packs

The following table lists the system responses to common equipment circuit packs.
System response to common equipment circuit pack deployments
Provisioned
Slot
Equipment
Inserted
Cooling Unit
Cooling Unit
Cooling Unit
None
Main Shelf
Interface
(for Netstender
2060 only)
Main Shelf
Interface
(for Netstender
2060 main shelf
only)
Expansion Shelf
Interface
(for Netstender
2060 expansion
shelf only)
Expansion Shelf
Interface
(for Netstender
2060 expansion
shelf only)
Slot 3
(for Netstender
1030 only)
Slot 3
(for Netstender
1030 only)
Slot 3
(for Netstender
1030 only)
Slot 5
(for Netstender
2060 only)
Slot 5
(for Netstender
2060 only)
Slot 5
(for Netstender
2060 only)
Main Shelf
Interface
System Response
Normal situation for a provisioned slot.
Major alarm situationthe slot is unequipped and empty.
A Cooling Unit circuit pack must be inserted.
None

An MSI circuit pack must be inserted.
Expansion Shelf
Interface
None

An ESI circuit pack must be inserted.
System Control
Processor
None
Major situationthe slot is unequipped and empty. An

SCP circuit pack must be inserted. Slot 3 of the shelf is
always auto provisioned with SCP equipment.
Other
Critical situationthe slot is equipped with a mismatched

circuit pack. Replace the existing circuit pack with an SCP
circuit pack.
System Control
Processor
None
Major situationthe slot is unequipped and empty. An

MSCP circuit pack must be inserted. Slot 5 of the main
shelf (1) is always auto provisioned with MSCP equipment.
Other
Critical situationthe slot is equipped with a mismatched

circuit pack. Replace the existing circuit pack with an
MSCP circuit pack.
3.10.2 System responses for various circuit packs

The following table lists the system responses to various provisioned and inserted
circuit pack combinations.
System response to various circuit pack deployments
Provisioned
Slot
Equipment
Inserted
None
None
None
None
Filler Circuit
Pack
Any
Any
None
Any
Filler Circuit
Pack
Any
Any
Match
Mismatch
Any
Failed
Slot 1 of a 2-Slot
Configuration
(for Netstender
1030 only)
Single-Width
Circuit Pack in
Either Slot of a
Double-Width
Slot
None
Slot 1 of a 2-Slot
Configuration
(for Netstender
1030 only)
Slot 1 of a 2-Slot
Configuration
(for Netstender
1030 only)
Unknown
System Response
Major alarm situationthe slot is empty.
A filler circuit pack must be inserted to preserve EMC/EMI
and cooling airflow.
Normal situation for an empty slot when the equipment is in
the AINS state.
Normal situation for an unprovisioned slot. Operators often
store inventory in unused slots.
A filler circuit pack or a circuit pack corresponding to the
provisioned circuit pack must be inserted to preserve the
EMC/EMI and cooling airflow.
No alarmthe slot(s) is pre-provisioned for a filler circuit
pack, a filler circuit pack is inserted, and the equipment is in
the AINS state.
Major alarm situationthere is an equipment mismatch
when the equipment is not in the AINS state.
Note: The Netstender is capable of reporting on the
inventory of inserted circuit packs as a distinctly different
set than the provisioned circuit packs.
A circuit pack corresponding to the provisioned circuit pack
should be inserted, or the equipment provisioning should
be changed.
Major or Critical alarm situationthe system responds
based on the nature of the problem.
Critical or Major alarm situationequipment is missing in
the Netstender. The REPLUNITMISS alarm indicates that
slot 1 is missing equipment, even though the equipment is
in slot 1 of a 2-slot configuration
slot 1 is missing equipment, even though no equipment is
present.
Critical or Minor alarm situationequipment is unknown in
the Netstender. The REPLUNITUNK alarm indicates that
slot 1 has equipment that is unknown to the system.
System response to various circuit pack deployments (Continued)

Provisioned
Slot
Equipment
Inserted
Slot 1 or Slot 3
of a 5-Slot or
4-Slot Shelf
Configuration
(for Netstender
2060 only)
Single-Width
Circuit Pack in
Either Slot of a
Double-Width
Slot
Slot 1 or Slot 3
of a 5-Slot or
4-Slot Shelf
Configuration
(for Netstender
2060 only)
Slot 1 or Slot 3
of a 5-Slot or
4-Slot Shelf
Configuration
(for Netstender
2060 only)
None
Unknown
System Response
either slot 1 or slot 3 is missing equipment, even though the
equipment is either
- in slot 1 or slot 2 of a 5-slot configuration
- in slot 3 or slot 4 of a 4-slot configuration
either slot 1 or slot 3 is missing equipment, even though no
equipment is present.
Critical or Minor alarm situationequipment is unknown in

the Netstender. The REPLUNITUNK alarm indicates that
either slot 1 or slot 3 has equipment that is unknown to the
system.
3.11 In-service shelf reconfiguration of a Netstender 2060

Note
To reconfigure a Netstender 1020, 1030, or a non-powered 2060 shelf, see the

Installation and Commissioning Guide.
To remove the center supports from a powered Netstender 2060 shelf, use the
following procedure.
Reconfiguring the center supports of a powered Netstender 2060 shelf
Step
Action
Determine which version of center support is in your Netstender shelf

There are currently two versions of center supports in use:
- Version 1 uses a rear fastener
- Version 2 uses a front fastener
Version 1
Version 1 center supports have a hole at the front, through which a screwdriver is used
to access the rear-mounted fastener.
Note: Do not perform this procedure on an in-service or powered Version 1 system.
Use the procedure called Removing Netstender 2060 center supports from an
unpowered shelf.
Center Support
If your Netstender 2060 uses a Version 1 center support, DO NOT continue. Follow the
note that appears above.
Version 2
Version 2 center supports have a screw fastener at the front.
Center Supports with Front Screw Fasteners
If your Netstender 2060 uses a Version 2 center support, go to step 2.

Step
Action
Version 2 center supports can be removed from an in-service or powered system.

Locate the center supports, as shown in the illustration.
Center Supports with Front Screw Fasteners
4
5
Using a Phillips screwdriver, loosen the front screw while holding its locking nut from
behind to prevent the nut from rotating.
With the screw loosened, pull the center support forward approximately 1/8" and move it
sideways about 1/2-inch until the support clears the dowel pin.
With the center support clear of the dowel pin, pull the guide out of the shelf completely.
Pull out the removable dowel pin with your fingers. Either save or discard the dowel and
guide. A kit for replacing the guide and pin can be purchased in the future if the shelf
configuration is to be changed back to single-slot configurations. Otherwise, store the
removed hardware in a safe place in case you need to reconfigure the shelf to another
configuration in the future.
Dowel Pin
If required, remove the second center support by repeating steps 3 through 5.

Then go to step 7.

Step
Action
Re-initialize the SCP by entering the following syntax at the TL1 command line
interface:
INIT-SYS:[TID]:SCP-1-5:<CTAG>::<ph>:[CMDMDE=<cmdmde>];
where
ph
cmdmde
is the phase. It must be 1 for a cold SCP restart.

is the command mode. It can be either NORM for normal or FRCD for
forced.
Example
INIT-SYS:NETSTENDER:SCP-1-5:100::1;
NETSTENDER 02-11-22 18:32:02
M
100 COMPLD
;
8
Log on to the Netstender 2060 and verify that the software is finding the new
configuration by entering the following syntax at the TL1 command line interface:
RTRV-INV:[TID]:[<aid>]:<CTAG>;
3.12 Shutting down the system

Use this procedure to shut down the Netstender.
What you need
None
Prerequisites
Ensure that you are logged into the system.

Shutting down the system
Step
Action
Reroute the Traffic

Before proceeding with the shut down, reroute traffic that is currently supported by the
Netstender to another Netstender system.
Remove the Application Facilities from Service
Once traffic has been transferred, start removing the application facilities from service.
Application facilities include optical amplifiers, optical supervisory channels, SFP
transceivers, etc.
For each application facility, enter the appropriate remove command at the TL1
command line interface.
Example
RMV-OA:NETSTENDER:OLA-1-1-1:100;
Response
NETSTENDER 02-08-27 00:22:59

M
100 COMPLD
;
3
Remove the Optical Circuit Packs from Service

With the application facilities out of service, enter the appropriate remove command for
each optical circuit pack at the TL1 command line interface.
Example
RMV-EQPT:NETSTENDER:OLA-1-1:100;
Response
NETSTENDER 02-08-27 00:29:32

M
100 COMPLD
Shutting down the system (Continued)

Step
Action
Remove the MSCP from Service

With the application facilities and their supporting circuit packs out of service, enter the
following at the command line interface:
RMV-EQPT:[TID]:SCP-1-5:<CTAG>;
Example
RMV-EQPT:NETSTENDER:SCP-1-5:100;
Response
NETSTENDER 02-08-27 00:30:52

M
;
5
100 COMPLD
Remove the Main Shelf from Service

With the optical amplifiers, supporting circuit packs, and MSCP out of service, enter the
following at the command line interface:
RMV-EQPT:[TID]:<aid>:<CTAG>;
Example
RMV-EQPT:NETSTENDER:SH-1:100;
Response
NETSTENDER 02-08-27 00:34:26

M
;
6
100 COMPLD
Shut Off the Power

With all of the circuit packs now in the out-of-service state, turn the Netstender power off
at the breaker interface panel.
H A P T E R
4.0 Installing optional Netstender circuit

packs
This chapter discusses the following circuit packs:
4.1, Installing optical amplifier circuit packs
4.2, Installing optical supervisory channel circuit packs
4.3, Installing wavelength conversion circuit packs
4.4, Installing Muxponder circuit packs
4.5, Installing optical add-drop module circuit packs
4.6, Installing optical component tray circuit packs
4.7, Installing multiplexer/demultiplexer circuit packs
4.8, Installing DWDM bi-directional coupler/splitter circuit packs
4.9, Installing dispersion compensation module circuit packs
4.10, Installing filler circuit packs
Installing optional Netstender circuit packs
4.1 Installing optical amplifier circuit packs

Use this procedure to install any of the following amplifier circuit packs:
DWDM Optical Line Amplifier with Mid-stage (OLAM) access
DWDM C-Band Booster Amplifier (OBA)
DWDM C-Band Pre-Amplifier (OPA)
Single-Channel/Sub-Band Booster Amplifier (SBA)
Single-Channel/Sub-Band Pre-Amplifier (SPA)
These amplifiers are available with built-in power monitors. The power monitors
allow one percent of the signal to be redirected for monitoring purposes.
What you need
Slot-head or Phillips screwdriver

Electrostatic discharge (ESD) wrist strap
Optical amplifier circuit pack
Isopropyl alcohol and lint-free pads
2.5 mm Huxcleaner (recommended) for up to 500 cleanings per unit. Use
ordering code BP1A5033.
Prerequisites
None
Laser Warning
Caution
Invisible laser radiation can be emitted from the aperture ports of various
optical circuit packs when no fiber cable is connected. Avoid exposure and
do not stare into open apertures to avoid permanent eye damage.
Electrostatic Discharge
Use an ESD wrist strap whenever you open the equipment, particularly
when you are handling circuit packs as well as SFP and XFP transceivers.
To work properly, the wrist strap must make good contact at both ends (that
is, with your skin at one end and with the chassis at the other).
Recommendation
For fiber management purposes, it is recommended that slots two, four, and six in
the Netstender shelf be the first slots populated with optical amplifier circuit packs.
Important
If you need to remove the center supports of the Netstender shelf, refer to the
Installation and Commissioning Guide before proceeding with this procedure.
Power monitor ports
The latest version of Netstender amplifiers incorporate built-in power monitor

ports. The power monitors provide a 1% tap of the incoming signal.
The power monitor port provides a convenient means of checking the incoming
optical power received.
The illustration below shows a Single-channel/Sub-band Pre-Amplifier (SPA) and
where its power monitor port is located.
Power Monitor Port on SPA
Power Monitor Port

PEC
BP1A05PB-UC
REL 01
SPA
SER
Monitor
Fail
The following figure shows an optical amplifier circuit pack and its key features
for this procedure.
Optical amplifier key features
Optical Input
Optical Output
Screw
Handles
Screw
The following figure shows a typical SBA or SPA optical amplifier with a power
monitor.
Optical amplifier with power monitor
Screw
Optical input
Optical output
Handle
Power Monitor
Screw
The following figure shows an optical line amplifier with mid-stage (OLAM)
access circuit pack and its key features for this procedure.
Optical line amplifier with mid-stage access key features
Optical Input
Screw
Optical Output
Mid-Stage Connectors
Screw
Handles
The following figure shows a typical OLAM optical amplifier with a power monitor.
Optical line amplifier with mid-stage access and power monitor
Optical input
Screw
Optical output
Handle
Power Monitor
Screw
Dual LC Mid-Stage
Connector
Procedure
Installing an optical amplifier circuit pack
Step
Action
At the Netstender Shelf:

Remove the existing Circuit Pack
If a circuit pack currently occupies the slot in which you want to install the amplifier circuit
pack, use this step first. Otherwise, go to step 2.
a) Facing the front of the Netstender, disconnect any fibers, if applicable.

b) Locate the circuit pack screws and using a slot-head or Phillips screwdriver, unfasten
the circuit pack screws.
c) Using the handles, carefully pull the circuit pack straight out.
Insert the Amplifier Circuit Pack
a) Align the amplifier circuit pack to the slot in which the circuit pack is being inserted.
b) Carefully push the circuit pack straight into the slot.
c) Push with sufficient pressure until the LEDs come on and the faceplate of the circuit
pack matches the position of the adjacent circuit pack.
Attach the Faceplate Screws
a) Facing the front of the Netstender, align the amplifier circuit pack with its mounting
holes.
b) Using a slot-head or Phillips screwdriver, carefully tighten the two faceplate screws:
- Partially tighten the center support screw.
- Partially tighten the other screw.
- Fully tighten the center support screw.
- Fully tighten the other screw.
5
6
Caution: Tighten to a torque that is no more than 4.7 in-lbs.

Clean the Ends of the Fiber Optic Cables
Use lint-free pads with isopropyl alcohol to clean the ends of the fiber optic cables.
Use a Huxcleaner (BP1A5033) to clean the internal 2.5 mm fiber connectors.
Connect the Optical Cables
Connect the input and output optical cables to the faceplate of the circuit pack.
Replace Cables
If any cables were moved to access the amplifier slot, replace the cables to their original
locations.
Note: A replacement kit of five sets of UC (FC, SC and ST) removable connector caps is
orderable as item BP1A5035.
4.2 Installing optical supervisory channel circuit packs

Information about how to initially install an Optical Supervisory Channel (OSC)
circuit pack is located in the Installation and Commissioning Guide.
For details about how to provision and replace an OSC circuit pack, refer to the
OSC Operations, Administration, Maintenance and Provisioning Guide.
4.3 Installing wavelength conversion circuit packs

Use this procedure to install any of the following wavelength conversion circuit
packs:
4-Port 2.5G Wavelength Manager SONET-SDH & Data (WM2.5G) BP1A43AA
2-Port 10G Wavelength Regenerator (WR10G) - BP1A47AB, BP1A47BB
4-Port 2.5G Wavelength Regenerator (WR2.5G) - BP1A42AA, BP1A42AB
4-Port 1G Wavelength Regenerator (WR1G) - BP1A42BA, BP1A42BB
Notes
4-Port 1G Wavelength Translator (WT1G) - BP1A41BA

The 2-Port 10G WR can be installed only in slots two, four and six of a Netstender
2060 Main Shelf when the BP1A52BA cooling unit is installed in that main shelf.
When the BP1A52CA cooling unit is installed in a 2060 shelf, the 10G WR can be
installed in slots one, two, three, four, and six of the main shelf, and in slots one to
six of an expansion shelf.
The 2-Port 10G WR cannot be installed in a 1030 shelf.
What you need

WM, WR, or WT circuit pack
Small form factor pluggable (SFP) transceivers
1.25 mm Huxcleaner (recommended). Use ordering code BP1A5034.
Prerequisites
None
Important
To ensure that the WR10G circuit pack (BP1A47AB, BP1A47BB) is not

damaged, the maximum input power for the MSA port (that is, port 1) must
be -4 dBm or less.
Caution
The following figure shows a wavelength conversion circuit pack. The key
features for this procedure are indicated.
Wavelength conversion circuit pack key features
Screw
Handle
Port 4
Port 3
Port 2
Port 1
Ports with
SFPs Inserted
Screw
The following figure shows a 2-Port 10G Wavelength Regenerator conversion

circuit pack. The key features for this procedure are indicated.
2-Port 10G Wavelength Regenerator circuit pack
Screw
Handle
XFP Transceiver Port
(Port 2)
Screw
300-Pin MSA Transceiver Port

(Port 1)
Procedure
Inserting a wavelength conversion circuit pack
Step
Action
Insert the Wavelength Conversion Circuit Pack
a) Align the wavelength conversion circuit pack to the slot in which the circuit pack is
being inserted.
a) Facing the front of the Netstender, align the wavelength conversion circuit pack with
its mounting holes.
Inserting a wavelength conversion circuit pack

Step
Action
Insert SFP transceivers

Note: The XFP transceiver is shipped already installed in the 2-Port 10G Wavelength
Regenerator circuit pack. Do not remove the transceiver.
Once the wavelength conversion circuit pack is secured to the Netstender shelf, use
procedure 8.3.1, Installing SFP transceivers or 4.3.2, Installing 10G Wavelength
Regenerator XFP transceivers in this document to insert the SFPs into the circuit pack.
After procedure Installing SFP transceiversis completed, return to this procedure.
Replace Cables
If any cables were moved to access the wavelength conversion circuit pack slot, replace
the cables to their original locations.
4.3.1 Installing SFP transceivers

Use this procedure to install small form factor pluggable (SFP) transceivers.
What you need

SFP transceiver
Prerequisites
None
Laser Warning
Caution
The following figure shows a typical SFP transceiver with a bale-clasp latch.
SFP transceiver with a bale-clasp latch
Bale-Clasp Latch
in Closed Position
Bale-Clasp Latch
in Open Position
The following figure shows an SFP transceiver about to be inserted into its slot.
SFP insertion
Screw
Port 4
Port 3
Port 2
Port 1
Handle
Screw
SFP about to be
Inserted into the slot
Out In
(Tx) (Rx)
Note: The connector interface supports

LC connectors only.
Precautions
To prevent potential damage from electrostatic discharge, observe the following

when handling SFP transceivers:
Do not remove an SFP transceiver from its packaging until you are ready to
install it into a circuit pack.
Do not touch any of the pins, connections, or components of an SFP transceiver.
Important
Always store or transport an SFP transceiver in anti-static packaging.

DWDM SFPs take about 90 seconds to reach a stable operating temperature. As a
result, the REPLUNITFAIL (SFP Failure) alarm is disabled for 95 seconds after an
SFP is seated. If there is a DWDM SFP hardware fault, the REPLUNITFAIL (SFP
Failure) alarm is raised after the 95-second time delay.
Procedure
Inserting an SFP transceiver
Step
Action
Insert the SFP Transceiver

Note: SFP transceiver ports are numbered one through four starting on the right side of
the wavelength conversion circuit pack.
2
3
a) Hold the transceiver so that the optical connectors face you and the product label is
visible.
b) Ensure the latch is in the closed position.
c) Align the transceiver to the port in which the transceiver is being inserted.
d) Carefully slide the transceiver straight into the port until it clicks.
- If the red Fail LED turns on, there is a transceiver fault. To clear the fault,
refer to the Alarm and Troubleshooting Guide.
- If the yellow LOS LED turns on, there is no valid modulated signal connected to the
transceiver. This condition clears once a valid modulated signal is connected.
e) Remove the plastic protective cover, if fitted.
Note: Before connecting the optical cables to the transceiver, ensure that both the
optical cable connectors and the transceiver optical surfaces are clean and that there is
no residue on the optical surfaces.
Connect the input and output optical cables to the transceiver as follows:
Note: The input or receiver is on the right side of the transceiver.
The output or transmitter is on the left side of the transceiver.
a) Ensure that the latch of the transceiver is in the closed position.
b) Carefully slide the bottom of the male optical connector along the bottom of the
transceiver opening.
c) Gently push the male optical connector into the transceiver until a distinctive click is
heard. Then continue exerting pressure on the connector to ensure a good
connection is achieved.
Note: A Loss of Signal (LOS) alarm can occur when no coherent modulated signal is
connected to the transceiver. To clear an LOS alarm, see the Alarm and
Troubleshooting Guide.
4.3.2 Installing 10G Wavelength Regenerator XFP transceivers

Use this procedure to install 10Gbps small form factor pluggable (XFP)
transceivers.
What you need

XFP transceiver
Prerequisites
None
Laser Warning
Caution
The following figure shows a typical XFP transceiver with a bale-clasp latch.
XFP Transceiver key features
Bale-Clasp Latch
in Closed Position
Bale-Clasp Latch
in Open Position
The following figure shows an XFP transceiver about to be inserted into its slot.
Figure 4-1 XFP insertion
XFP about to be
Out In
(Tx) (Rx)
Precautions

when handling XFP transceivers:
Do not remove an XFP transceiver from its packaging until you are ready to
Do not touch any of the pins, connections, or components of an XFP transceiver.
Always store or transport an XFP transceiver in anti-static packaging.
Important
DWDM XFPs take about 90 seconds to reach a stable operating temperature. As a

result, the REPLUNITFAIL (SFP or XFP Failure) alarm is disabled for 95 seconds
after an XFP is seated. If there is a DWDM XFP hardware fault, the
REPLUNITFAIL (SFP or XFP Failure) alarm is raised subsequent to the 95
second time delay.
Procedure
Installing an XFP transceiver in a 10G wavelength regenerator
Step
Action
Insert the new XFP transceiver
a) Hold the new XFP transceiver so that the optical connectors face you and the product
label is visible.
b) Ensure the latch handle is in the closed position:
- For a bale-clasp latch, this is in the upright position.
c) Align the XFP transceiver to the port in which the transceiver is being inserted.
d) Carefully slide the XFP tranceiver straight into the port until it clicks.
Install Circuit Pack
a) Align the circuit pack to the slot in which the circuit pack is being installed.
Fasten Faceplate Screws
a) Facing the front of the Netstender, align the circuit pack with its mounting holes.
b) Using a slot-head or Phillips screwdriver, carefully tighten the faceplate screws:
4
5

Note: Before connecting the optical cables to the XFP transceiver, ensure that both the
optical cable connectors and the XFP optical surfaces are clean and that there is no
residue on the optical surfaces.
Connect the input and output optical cables to the XFP transceiver as follows:
a) Ensure that the latch handle (or bail) of the XFP transceiver is in the closed
(up) position.
b) Carefully slide the bottom of the male optical connector along the bottom of the XFP
c) Gently push the male optical connector into the opening until a distinctive click is
4.4 Installing Muxponder circuit packs

Use this procedure to install any of the following Muxponder circuit packs:
2-Port GE MuxponderSONET (MXP2.5G) - BP1A46AA
2-Port GE MuxponderSDH (MXP2.5G) - BP1A46BA
What you need

Prerequisites
None
Restrictions
The cross connections between client ports and line ports are fully non-blocking.
In release 6.1, the Muxponder supports the add/drop type of cross connection in
protected and unprotected modes only.
Caution
The following figure shows a 2-Port GE Muxponder circuit pack. The key features
for this procedure are indicated.
2-Port GE Muxponder circuit pack key features
t4
en nt 3 2
i
l
C lie
t
C
1
en
Cli ient
l
C
e2
Lin ne 1
Li
Screw
Handle
Screw
Procedure
Inserting a Muxponder circuit pack
Step
Action
Insert the Muxponder Circuit Pack
a) Align the Muxponder circuit pack to the slot in which the circuit pack is being inserted.
a) Facing the front of the Netstender, align the Muxponder circuit pack with its mounting
holes.
- Partially tighten the first support screw.
- Fully tighten the first support screw.

Insert SFP transceivers
Once the Muxponder circuit pack is secured to the Netstender shelf, use procedure
Installing SFP transceiversin this document to insert the SFPs into the circuit pack.
After the procedure Installing SFP transceiversis completed, return to this procedure.
Replace Cables
If any cables were moved to access the Muxponder circuit pack slot, replace the cables
to their original locations.
4.5 Installing optical add-drop module circuit packs

Use this procedure to install any of the following optical add-drop module
(OADM) circuit packs:
CWDM OADMs:
1 Channel CWDM OADM (C1ADM)

Double 1 Channel CWDM OADM (C1ADM)
2 Channel N+1 CWDM OADM (C2ADM)
DWDM OADMs:
1 Channel DWDM OADM (D1ADM)

4 Channel N+1, 2, 3 DWDM OADM (D4ADM)
4 Channel DWDM OADM, Channels 53, 55, 57, 59 (D4ADM)
Typical deployment
In most cases, the add-drop module is used to split and combine one or more
wavelengths with others, as indicated in the following figure.
Typical deployment of a 1-channel Add-Drop Module
OADM
9 Incoming
Wavelengths
Splitter
8 Outgoing
Wavelengths
Combiner
8 Incoming
Wavelengths
1 Outgoing
Wavelength
1 Incoming
Wavelength
9 Outgoing
Wavelengths
Note
These circuit packs use only LC single-mode fiber connectors with 2.0 mm
jackets.
What you need

OADM circuit pack
Prerequisites
None
Laser Warning
Caution
Important
If you need to remove the center supports of the Netstender shelf, refer to the
Installation and Commissioning Guide before proceeding with this procedure.
The following figure shows a 2-Channel N+1 DWDM OADM circuit pack and its
key features for this procedure.
2-Channel N+1 DWDM OADM key features
Add/Drop Channel 2
Add/Drop Channel 1
Passthrough
Line
Handle
Screw
Procedure
Installing an OADM circuit pack
Step
Action

If a circuit pack currently occupies the slot in which you want to install the OADM circuit

Insert the OADM
a) Align the OADM to the slot in which the circuit pack is being inserted.
a) Facing the front of the Netstender, align the OADM with its mounting holes.
4
5
6

Replace Cables
If any cables were moved to access the slot, replace the cables to their original
locations.
4.6 Installing optical component tray circuit packs

Note
Use this procedure to install any Optical Component Tray (OCT) circuit pack.
The connector interface supports LC connectors only.
What you need

OCT circuit pack
Prerequisites
None
Caution
Recommendation
The OCT family of circuit packs can be installed in any available single-width slot
of the Netstender shelf.
The following figure shows the key features of an OSC Double Coupler/Splitter
1510nm circuit pack for this procedure.
OSC Double Coupler/Splitter 1510nm circuit pack key features
10
15
Screw
1
C
nd
ba
1
e1
Lin
10
15
2
C
nd
ba
2
e2
Lin
Handle
Screw
Procedure
Installing an OCT circuit pack
Step
Action

If a circuit pack currently occupies the slot in which you want to install the OCT, use this
step first. Otherwise, go to step 2.

Insert the OCT
a) Align the OCT circuit pack to the slot in which the circuit pack is being inserted.
a) Facing the front of the Netstender, align the OCT circuit pack with its mounting holes.

Installing an OCT circuit pack

Step
Action
Connect the Fiber Optic Cables

Connect the input and output optical cables to the connectors on the faceplate of the
circuit pack.
Replace Cables
If any cables were moved to access the OCT slot, replace the cables to their original
locations.
4.7 Installing multiplexer/demultiplexer circuit packs

Use this procedure to install any of the following multiplexer/demultiplexer circuit
packs:
CWDM multiplexers:
4-Channel CWDM Mux/Demux Module (C4MD)

DWDM multiplexers:
32 Channel DWDM Active Mux/Demux Module 1 (D32AMD1-4)

32 Channel DWDM Mux/Demux Module 1 (D32MD1)
Important
Note

For release 6.1, the D32BMD24 and D32BMD42 circuit packs must be installed in
a passive shelf only.
The connector interface supports LC connectors only.
Typical deployment
In most cases, a multiplexer/demultiplexer is used to split and combine

wavelengths, as shown in in the following figure.
Typical deployment of a multiplexer/demultiplexer
Mux/Demux
Note
Multiple Incoming
Wavelengths
Outgoing
Wavelengths Multiplexed
Multiple Outgoing
Wavelengths
Demultiplexed
Incoming
Wavelengths Multiplexed
Due to the number of fibers that terminate at the fiber tray, all fibers connecting at
the fiber tray must have 2 mm jackets to accommodate the required number of
fibers.
What you need

Mux/Demux circuit pack
Prerequisites
None
Laser Warning
Caution
Note
The 32 Channel DWDM Mux/Demux module is a double-width circuit pack. The

8 Channel CWDM Mux/Demux occupies two slots.
Important
If you need to remove the center supports of the Netstender chassis, refer to section
5.3, Preparing the slot configuration of a Netstender shelf in the Installation and
Commissioning Guide before proceeding with this procedure.
DWDM mux/demux circuit pack
The following figure shows an eight-channel module of the 32-channel DWDM

active mux/demux.
32-channel DWDM active mux/demux circuit pack
Screw
or
nit
Mo
el
nn
a
Ch
8
l7
ne
an
Ch
el
nn
a
Ch
6
l5
ne
an
Ch
l
ne
an
Ch
n/
xI
u
em
Handle
A
VO
el
nn
a
Ch
Ou
3
el
nn
a
Ch
2
el
nn
a
Ch
Handle
ion
ns
pa
Ex
Lin
Screw
Procedure
Installing a Mux/Demux circuit pack
Step
Action

If a circuit pack currently occupies the slot in which you want to install the Multiplexer/
Demultiplexer circuit pack, use this step first. Otherwise, go to step 2.

Insert the Mux/Demux
a) Align the Mux/Demux to the slot in which the circuit pack is being inserted.
a) Facing the front of the Netstender, align the Mux/Demux with its mounting holes.
- Partially tighten the first screw.
- Fully tighten the first screw.
- Fully tighten the remaining screw.
4
5
6

Replace Cables
If any cables were moved to access the slot, replace the cables to their original
locations.
4.8 Installing DWDM bi-directional coupler/splitter circuit packs

Use this procedure to install the DWDM Bi-directional Coupler/Splitter circuit
pack (CS).
What you need

DWDM bi-directional coupler/splitter circuit pack
Prerequisites
None
Caution
The following figure shows the DWDM Bi-Directional Coupler/Splitter circuit
pack. The key features for this procedure are indicated.
Out 2
Line 2
In 2
Out 1
Not Connected
Ports for Line 2
Line 1
In 1
Not Connected
Ports for Line 1
Installing a DWDM Bi-Directional Coupler/Splitter circuit pack

Step
Action
Install Coupler/Splitter Circuit Pack
a) Align the coupler/splitter circuit pack to the slot in which the circuit pack is being
installed.
Tighten Faceplate Screws
a) Facing the front of the Netstender, align the DWDM Bi-Directional Coupler/Splitter
circuit pack with its mounting holes.

Connect Optical Cables
Clean the optical cables and then connect them to the circuit pack.
4.9 Installing dispersion compensation module circuit packs

Use this procedure to install any of the following Dispersion Compensating Fiber
Modules (DCM):
SMF DCM 20 km
SMF DCM 40 km
SMF DCM 60 km
SMF DCM 80 km
SMF ITU-T DCM 40 km
SMF ITU-T DCM 60 km
Note
SMF ITU-T DCM 80 km

The connector interface supports UC (FC, SC and ST) and LC connectors.
Typical deployment
The DCM can be used between the first-stage amplifier and the second-stage
amplifier of an optical line amplifier with mid-stage access (OLAM), as indicated
in the following figure.
Typical deployment of dispersion compensating fiber modules
Dispersion
Compensation
Module
DCM
2nd-Stage Input
1st-Stage Output
OLAM
1st-Stage Input
2nd-Stage Output
Optical Line Amplifier

with Mid-Stage Access
The DCM can also be used in-line after a Single-channel/Sub-band Pre-Amplifier

(SPA), as indicated in the following figure.
Typical deployment of dispersion compensating fiber modules
SPA
Single-channel/
Sub-band Pre-Amplifier
DCM
Dispersion
Compensation
Module
What you need

DCM circuit pack
1.25 mm and 2.5 mm Huxcleaners (recommended)
Use ordering code BP1A5034 for the 1.25 mm Huxcleaner for LC

connectors.
Use ordering code BP1A5033 for the 2.5mm Huxcleaners for UC connectors.
Prerequisites
None
Laser Warning
Caution
The following figure shows a DCM circuit pack and its key features for this
procedure.
Dispersion compensating fiber module key features
Screw
Handle
Optical Input
Optical Output
Screw
Procedure
Installing a dispersion compensating fiber module circuit pack
Step
Action

If a circuit pack currently occupies the slot in which you want to install the DCM circuit

Insert the DCM Circuit Pack
a) Align the DCM circuit pack to the slot in which the circuit pack is being inserted.
c) Push the circuit pack into place.
a) Facing the front of the Netstender, align the DCM circuit pack with its mounting holes.
4
5

According to the deployment configuration, connect the input and output optical cables
to the faceplate of the circuit pack.
Replace Cables
If any cables were moved to access the DCM slot, replace the cables to their original
locations.
4.10 Installing filler circuit packs

Use this procedure to install a Filler circuit pack.
What you need

Filler circuit pack
Prerequisites
None
Caution
Important
If you need to reconfigure the width of some circuit pack slots in the Netstender
chassis, refer to the Installation and Commissioning Guide before proceeding with
this procedure.
The following figure shows a filler circuit pack and its key features for this
procedure.
Filler circuit pack key features
Screw
Handle
Screw
Procedure
Installing a filler circuit pack
Step
Action
Insert Circuit Pack
a) Align the filler circuit pack to the guides of the slot in which the circuit pack is being
inserted.
Tighten Face Plate Screws
b) Using a slot-head or Phillips screwdriver, carefully tighten the two face plate screws:

Replace Cables
If any cables were moved to access the filler slot, replace the cables to their original
locations.
H A P T E R
5.0 Connecting circuit packs

This chapter discusses connecting the following circuit packs:
5.1, Amplifier configurations
5.2, OADM configurations
Connecting circuit packs
5.1 Amplifier configurations

5.1.1 Connecting fibers between an OLAM and a DCM
Connecting fiber patch cables between an optical line amplifier with mid-stage
access (OLAM) and a dispersion compensating fiber module (DCM) is quite
straightforward.
Use the following procedure to connect the fiber patch cables between an OLAM
and a DCM.
Connecting fibers between an OLAM and a DCM
Step
Action
For convenience, provision the OLAM and DCM circuit packs adjacent to each other as
shown in the figure below.
Using a fiber patch cable with LC connectors on both ends, connect the fibers to the
appropriate input and output LC connectors on the DCM.
Carefully wrap the fiber patch cable around the fiber management spool to take up slack
in the fibers.
Connect the other ends of the fiber patch cables to the appropriate second-stage input
and first-stage output connectors on the OLAM.
Connect the first-stage input and second-stage output connectors on the OLAM to their
respective input and output fibers.
Note: Do not wrap the main input and output fibers around the fiber management spool.
Use an appropriate fiber slack management system inside the rack or cabinet to
manage the main input and output optical fibers.
2
3
4
5
The following figure shows the fibers that connect each OLAM from their small
mid-stage ports to their respective ports on the associated DCMs. The fiber
management spool is used to take up slack from the fiber patch cables. LC
connectors are used on both ends of the fiber patch cables.
Connecting fibers between an OLAM and a DCM
Note
For the Netstender 1030, the fiber management spool is not applicable.
5.2 OADM configurations

5.2.1 Basic cascading of OADMs to provide mux/demux functionality
Optical add/drop modules (OADM) can be cascaded to provide the functional
equivalent of a mux/demux.
In the example shown below, a two-channel OADM is deployed on day one with
two input wavelengths that are combined into a composite output from the line
port.
In the future, on day two a second two-channel OADM is deployed that adds
channels three and four. The composite line output from the second OADM is
added to the first OADM through the pass through port. This results in the four
wavelengths being combined into a composite output from the line port of the first
OADM.
Two-wavelength OADMs serving as a mux/demux
Module 1 to deploy day 1
Drop
Drop
Add
Add
Pass
CH 2
CH 1
Through
Line
Output
Input
Input
Output
Drop 2
Add 2
Drop 1
Add 1
CLEI
To line day 1
CH 2
Drop 4
Module 2 to deploy day 2
Add 4
CH 1
Drop 3
Add 3
Output
Input
Input
Output
CLEI
CH 4
CH 3
Output to connect to the pass thru

port of module 1, no service
interruptions during Day 2 upgrades.
If there is only the need to add a third wavelength, it could be added to the first
OADM through the pass through port and the second OADM would not be
necessary.
5.2.2 OADM survivability of upstream and downstream traffic

Optical add/drop modules (OADM) can be combined to ensure that upstream and
downstream traffic can survive even if there is a circuit pack failure at a line site.
In the example shown below, a pair of two-channel OADMs are deployed where
two wavelengths are dropped and then added back to the composite signal that
passes through the site. Traffic upstream and downstream from a line site failure is
not affected.
The inbound composite traffic is connected to the line-in port of the first OADM.
The two selected wavelengths are dropped by the first OADM and the remaining
composite traffic exits through the pass through output port of the first OADM.
The composite traffic is then connected to the pass through input port of the
second OADM. At the second OADM, two selected wavelengths are added back
to the composite traffic that exits through the line output port.
For traffic flowing in the opposite direction, the remaining OADM ports are used.
OADM survivability of upstream and downstream traffic
Passthru (E to W)
Line Out (W)
Add (W)
Drop (W)
Line In (E)
Passthru in Passthru out
Drop (E)
Add (E)
Passthru out Passthru in
Line Out (E)
Line In (W)
Passthru (W to E)
The following illustration indicates what the fiber connections would look like for
this example.
OADM survivability fiber connections

Drop
Drop
Add
Add
CH 2
CH 1
Pass
Through
Line
Output
Input
Input
Output
E to W traffic
Module 1 to
deploy day 1
Drop 2
Add 2
Drop 1
Add 1
From line day 1
CLEI
W to E traffic
CH 2 (W to E) CH 1 (W to E)
Module 2 to
deploy day 1
Drop 2
Add 2
Drop 1
Add 1
Output
Input
W to E traffic
From line day 1
To line day 1
Input
Output
CLEI
CH 2 ( E to W) CH 1 ( E to W)
E to W traffic
To line day 1
5.2.3 Cascading OADMs for survivability and future growth

The concepts of OADM cascading and survivability can be combined to provide a
robust configuration that allows for future growth in the number of wavelengths
that are added and dropped at a site.
In the example shown below, four two-channel OADMs are deployed where four
wavelengths are dropped and then added back to the composite signal that passes
through the site. Traffic upstream and downstream from a line site failure is not
affected.
The inbound composite traffic is connected to the line in port of the first OADM.
The first two selected wavelengths are dropped by the first OADM and the
remaining composite traffic exits through the pass through output port of the first
OADM. The composite traffic is then connected to the line input port of the second
OADM. At the second OADM, two more wavelengths are dropped and the
remaining composite traffic exits through the pass through output port.
The composite traffic is then connected to the pass through input port of the third
OADM. At the third OADM, two selected wavelengths are added back to the
composite traffic that exits through the line output port. The composite traffic is
then connected to the pass through input port of the fourth OADM. At the fourth
OADM, two more selected wavelengths are added back to the composite traffic
that exits through the line output port.
For traffic flowing in the opposite direction, the remaining OADM ports are used.
Cascading OADMs for survivability and future growth
Add (W)
2
Drop (W)
Drop (E)
(E to W)
Add (E)
Drop (W)
Passthru out Passthru in
Drop (E)
2
Passthru out
Line In (E)
Line In
Line Out
Add (W)
Passthru out
Passthru in Passthru out
Passthru in
Line Out (W)
Add (E)
Passthru in
(W to E)
Line In (W)
Line In
Line Out
Line Out (E)
The following illustration indicates what the fiber connections would look like for
this example.
Cascading OADMs for survivability and future growth fiber connections

Drop
Drop
Add
Add
Pass
CH 2
CH 1
Through
Line
Output
Input
Input
Output
E to W traffic
Module 1 to
deploy day 1
Drop 2
Add 2
Drop 1
Add 1
From line day 1
CLEI
W to E traffic
To line day 1
CH 2 (W to E) CH 1 (W to E)
Drop 4
Drop 3
Add 3
Add 4
Since the fibering is quite

different between having 1
OADM module and 2 OADM
modules in series at an A/D site,
the installation/fibering of all
modules for Day N services has
to be installed Day 1.
Output
Input
Input
Output
Module 2 to
deploy Day 1
CLEI
CH 4
Drop 4
Add 4
CH 3
Drop 3
Add 3
Output
Input
Module 2 to
deploy Day 1
Input
Output
CLEI
CH 4
W to E traffic
CH 3
From line day 1
Module 1 to
deploy day 1
Drop 2
Add 2
Drop 1
Add 1
Output
Input
Input
Output
CLEI
CH 2 ( E to W) CH 1 ( E to W)
E to W traffic
To line day 1
H A P T E R
6.0 Connecting expansion shelves

This chapter discusses how to connect expansion shelves. Information in this
chapter is organized as follows:
6.1, Netstender 2060 expansion shelves overview
6.2, Connecting local expansion shelves
6.3, Connecting remote expansion shelves
Connecting expansion shelves
6.1 Netstender 2060 expansion shelves overview

The Netstender 2060 expansion shelves can be deployed either locally or remotely
to the Netstender 2060 main shelf.
The following figure shows the various deployment options.
Netstender 2060 main shelf with expansion shelves
Mon Line I n
D32MDE2
Out
ESD
2
In
Mon Line Out
S/N: BTIM01D1BJ25D
Fail
WR
WR
SER
4
F il
S/N: BTIM01D1BJ25D
MSCP
Shelf 2
S/N: BTIM01D1BJ25D
Electrical
Cable
2
ESI
Shelf 3
Fail
F il
Shelf 4
F il
S/N: BTIM01D1BJ25D
Shelf 5
Shelf 6
SCP
OSC 1
Dro p
Eth 1
Craft
CAUTION: I nvisible

view directly with
Class 1 LASER
PRODUCT
Fail
2
PEC
BP1A04AA
03
CAUTION: I nvisible
CAUTION: I nvisible

view directly with
Class 1 LASER
PRODUCT
est
S/N: BTIM01D1BJ25D
Fail
In p ut
Fail
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
In p ut
OSC
6
OSC
Tray
SB A

view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
Outp ut
SMF60
Input
Outp ut
Input
Outp ut
PEC
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
SER
S/N: BTIM01D1BJ25D
Outp ut
Main
shelf
Fail Fa
OSC 2
Filler
ESD
ES11
SMF60
Local
expansion shelf
Filler
SER
6
S/N: BTIM01D1BJ25D
Fiber Cable
Pairs Between
Locations
Trouble
Power
S/N: BTIM01D1BJ25D
PEC
BP1A04AA
PEC
03
BP1A04AA
WR
03
ESD
ES21
est
S/N: BTIM01D1BJ25D
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
Fail Fa
S/N: BTIM01D1BJ25D
In p ut
SB A
PEC
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
SER
S/N: BTIM01D1BJ25D
Output
Filler
In p ut
Eth 1
OSC 2
Drop
CAUTION: I nvisible

view directly with
Class 1 LASER
PRODUCT
Dro
Fail
S/N: BTIM01D1BJ25D
SPA
4
Outp ut
OSC 1
Dro p
OSC
6
Tray
Remote
expansion shelf
Trouble
Power
PEC
BP1A04AA
PEC
03
BP1A04AA
WR
03
ESD
2
est
S/N: BTIM01D1BJ25D
S/N: BTIM01D1BJ25D
CAUTION: I nvisible

view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
In p ut
SB A
Fail Fa
Fail Fa
PEC
CAUTION: I nvisible

view directly with
Class 1 LASER
PRODUCT
SER
S/N: BTIM01D1BJ25D
Output
Filler
In p ut
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
In p ut
ES31
Outp ut
PEC
SER
S/N: BTIM01D1BJ25D
SPA
OPA
6
Outp ut
Note: Altough the expansion shelf fiber cables are shown on the left side of the shelves,
the fiber cables should be run to the right side of the shelves.
The Netstender 2060 main shelf can be connected to local expansion shelves
through an SFP plug style electrical cable that is up to 10 m (32.8 ft.) in length. For
remotely located expansion shelves, they are connected to the Netstender 2060
main shelf using the 100FX (fast Ethernet) protocol over either single-mode or
multimode optical fiber cable.
6.2 Connecting local expansion shelves

Local expansion shelves are collocated with the Netstender 2060 main shelf. This
usually means mounting the Netstender 2060 main shelf with the Netstender 2060
expansion shelf in close proximity to each other (that is, within 10 m, or 32.8 ft., of
each other).
As a result, it is possible to connect the two shelves through an SFP plug style
electrical interface cable as shown in the following figure.
Connecting a local expansion shelf to the Netstender 2060 main shelf
Mon Line I n
D32MDE2
Out
ESD
2
In
Mon Line Out
S/N: BTIM01D1BJ25D
Li
WR
WR
SER
Expansion
shelf MSCP
Fail F
S/N: BTIM01D1BJ25D
Shelf 2
S/N: BTIM01D1BJ25D
Electrical
Cable
2
ESI
Shelf 3
Fail
Fail Fa
Shelf 4
Fail F
S/N: BTIM01D1BJ25D
OSC 1
OSC 2
SCP
OSC 1
Drop
Eth 1
Craft
OSC 2
Drop
Fail
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
03
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
Fail
Input
Fail
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
Input
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
Output
Input
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
SER
Output
Filler
PEC
Input
SBA
ESD
ES11
Output
SMF60
S/N: BTIM01D1BJ25D
OSC
Tray
PEC
BP1A04AA
Main 2060
shelf
Fail Fa
SMF60
4
Output
Local 2060
expansion sh
Filler
SER
6
S/N: BTIM01D1BJ25D
S/N: BTIM01D1BJ25D
Use the following procedure to connect a local expansion shelf to the main shelf.
Connecting a local expansion shelf to the main shelf
Step
Action
Ensure that there is a multiport system control processor (SCP) circuit pack plugged in
to the Netstender 2060 main shelf as shown above. The multiport SCP must be product
equipment code BP1A20BA.
Ensure that there is an expansion shelf interface (ESI) circuit pack plugged in to the
Netstender expansion shelf as shown above. The ESI must be product equipment code
BP1A54AA.
Insert one end of the electrical interface cable into the expansion shelf port that is
labelled To Main on the ESI circuit pack.
Note: The connector latch must be positioned on the top of the connector. When
removing a connector, gently press the latch down and remove the connector.
Follow the cabling rules below:
- Route the electrical interface cable to the left side of the Netstender shelf.
- Ensure sufficient slack is left so that there is no strain on the cable.
- Allow a minimum bending radius for the cable that is no less than three times the
diameter of the cable.
2
3
Connecting a local expansion shelf to the main shelf

Step
Action
Insert the other end of the electrical interface cable into one of the three expansion shelf
ports on the multiport SCP circuit pack in the main shelf.
Note: The connector latch must be positioned on the bottom of the connector. When
removing a connector, gently press the latch up and remove the connector.
Follow the cabling rules below:
- Route the electrical interface cable to the left side of the Netstender shelf.
- Ensure sufficient slack is left so that there is no strain on the cable and the fan
unit can be easily removed, if necessary.
- Allow a minimum bending radius for the cable that is no less than three times the
diameter of the cable.
Note: The expansion shelf ports on the multiport SCP circuit pack must be used in
numerical sequence. For example, the first expansion shelf is connected to the Shelf 11
port and subsequent expansion shelves are connected to the Shelf 21 and Shelf 31
ports in sequence.
Secure any excess electrical cable to either the rack frame, cabling troughs, or fiber
management trays, if available.
If long lengths of excessive cable exist, carefully loop the cable back upon itself and
secure appropriately.
SFP plug style electrical interface cables
The following table lists the SFP plug style electrical interface cables that are
available from BTI.
SFP Electrical Interface Cables
Order Code
Item
BP1A58DD-01
BP1A58DD-03
BP1A58DD-10
Single Expansion Shelf Cable SFP-SFP, shielded copper - 1 m

6.3 Connecting remote expansion shelves
Note
Remote expansion shelves are not located within 10m, or 32.8 ft., of the
Netstender 2060 main shelf. An optical cable using the 100FX protocol must
connect the two shelves together as shown in the following figure.
The Netstender 2060 expansion shelf can be located up to the distance supported
by the SFPs used in your equipment. If you wish to connect a remote expansion
shelf at a greater distance, please consult with BTI Photonic Systems customer
support personnel for deployment recommendations.
Connecting a remote expansion shelf to the Netstender 2060 main shelf

Mon Line I n
D32MDE2
Out
ESD
2
In
Mon Line Out
S/N: BTIM01D1BJ25D
WR
WR
SER
Expansion
shelf MSCP
S/N: BTIM01D1BJ25D
Fail Fa
Fail
Fail Fa
Shelf 2
Shelf 3
Shelf 4
Fail Fa
S/N: BTIM01D1BJ25D
Shelf 5
Shelf 6
SCP
OSC 1
Drop
Eth 1
OSC 2
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
Dro
S/N: BTIM01D1BJ25D
Fiber
Cable
Trouble
Power
Craft
Fail
2
PEC
BP1A04AA
PEC
03
BP1A04AA
OSC
6
OSC
Tray
WR
03
Main
shelf
ESD
ES21
2
S/N: BTIM01D1BJ25D
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
S/N: BTIM01D1BJ25D
Input
SBA
PEC
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
SER
S/N: BTIM01D1BJ25D
Output
Filler
S/N: BTIM01D1BJ25D
Fail Fa
S/N: BTIM01D1BJ25D
Input
OSC 1
Drop
Eth 1
OSC 2
Drop
Fail
2
SPA
4
Output
CAUTION: I nvisible
view directly with
Class 1 LASER
PRODUCT
OSC
6
Tray
Use the following procedure to connect a remote expansion shelf to the main shelf.
Connecting a remote expansion shelf to the main shelf
Step
Action
Ensure that there is a multiport system control processor (MSCP) circuit pack plugged
in to the Netstender 2060 main shelf as shown above. The multiport SCP must be
product equipment code BP1A20BA.
Ensure that there is an expansion shelf interface (ESI) circuit pack plugged in to the
expansion shelf as shown above. The ESI must be product equipment code
BP1A54AA.
Insert an appropriate SFP transceiver into the expansion port of the ESI circuit pack and
another SFP transceiver into the multiport SCP circuit pack. Ensure that the SFPs are
functioning correctly.
Attach one end of the two fiber optic cables to the expansion shelf port of the ESI circuit
pack. Note: Use fiber optic cables with 40-degree boots that are available from BTI.
See the Installation and Commissioning Guide for information.
Attach the other end of the two fiber optic cable to the expansion shelf port of the
multiport SCP circuit pack in the main shelf. Ensure that attenuation is in the range
supported by the SFPs.
Note: The expansion shelf ports on the multiport SCP must be used in numerical
sequence. For example, the first expansion shelf is connected to the Shelf 11 port and
subsequent expansion shelves are connected to the Shelf 21 and Shelf 31 ports in
sequence.
2
3
4
5
H A P T E R
7.0 Provisioning the Netstender

This chapter explains how to provision the Netstender and how to perform
provisioning-related activities. The following sections explain how to provision
the Netstender:
7.1, How Netstender provisioning works
7.2, Hierarchical organization of Netstender components
7.3, Designating names and IDs to system components
7.4, System provisioning
7.5, Expansion shelf provisioning
7.6, Equipment provisioning
7.7, Optical amplifier provisioning
7.8, OSC provisioning
7.9, Wavelength conversion provisioning
7.10, 2-Port GE Muxponder provisioning
7.11, Provisioning active mux/demux ports
7.12, Provisioning non-powered circuit pack ports
Provisioning the Netstender
7.1 How Netstender provisioning works

Netstender provisioning can be accomplished either manually, using TL1
commands or the Netstender Node Controller (NNC) interface, or automatically
through auto provisioning.
Provisioning commands include those that allow the operator to enter new
information, modify information, delete information, or remove equipment from
or restore it to service. The operator can also query the current system
configuration using the retrieve commands.
With shelves and/or circuit packs physically installed, these components can be
provisioned in the standard manner.
7.1.1 Auto provisioning

Auto provisioning allows an unprovisioned hardware component, such as a circuit
pack, to be automatically provisioned. This includes hardware components, such
as circuit packs and ports.
Auto provisioning is triggered by the plugging in (that is, the insertion) of a circuit
pack or transceiver.
7.1.1.1 Controlling auto provisioning

Auto provisioning is controlled by the AUTOP parameter that is accessed through
the ED-SYS command. There are four possible settings for the AUTOP parameter:
AINS Both equipment and supporting facilities are provisioned with the state set
to OOS-AU,AINS. The AINS system default timer is used.
IS
The hardware component is auto provisioned, set to the in-service state,

and all settable parameters are set to default values.
OOS The hardware component is auto provisioned, set to the out-of-service

state, and all settable parameters are set to default values.
OFF
The auto provisioning feature is turned off; no auto provisioning occurs.
For Wavelength Manager SDH customers only
Auto provisioning is not supported for SDH applications. If you are provisioning
SDH applications, ensure that the AUTOP parameter is set to OFF.
Restrictions
When a circuit pack is inserted into an unprovisioned slot, auto provisioning is

only initiated if the circuit pack is not in one of the following conditions:
Unknown
Communications Failure
Upgrade In Progress
Upgrade Failed
If a circuit pack is present in an unprovisioned slot and then restarted by the
INIT-SYS command, auto provisioning is not initiated.
Auto provisioning is also not initiated on slots that are already provisioned. As a
result, you must use manual provisioning if you need to add more supported
entities to the equipment in that slot.
If auto provisioning fails, the circuit pack or port is not provisioned in the system
and an event message is generated.
7.1.1.2 Amplifier circuit packs

When an amplifier circuit pack is inserted into an unprovisioned slot:
The circuit pack is auto provisioned with the primary state set to the same value
as the AUTOP parameter.
The supported amplifier is auto provisioned with the same primary state as the
circuit pack and all settable parameters are set to default values.
7.1.1.3 OSC circuit packs

When an optical supervisory channel (OSC) circuit pack is inserted into an
unprovisioned slot:
The OSC is auto provisioned with the primary state set to the same value as the
AUTOP parameter.
All supported IP interface ports are auto provisioned. The logical port inherits
the supporting circuit packs state. All other ports are set to UNASSIGNED
with the primary state set to OOS.
OSPF is not auto provisioned.
7.1.1.4 Active mux/demux circuit packs

Ten ports (1 line, 1 expansion, and 8 channels) exist on the active mux/demux
circuit pack. When an active mux/demux circuit pack is inserted into an
unprovisioned slot, the circuit pack and all ten ports are auto provisioned.
The state of the circuit pack is set to the same value as the AUTOP parameter.
The state of a port is set to the same value as the AUTOP parameter.
7-3
7.1.1.5 Passive circuit packs

When a passive circuit pack is inserted into an unprovisioned slot:
The passive circuit pack is auto provisioned with the primary state set to the
same value as the AUTOP parameter.
All supported passive ports are auto provisioned and they carry no primary state.
7.1.1.6 Wavelength conversion circuit packs

When a wavelength conversion circuit pack is inserted into an unprovisioned slot:
The wavelength conversion circuit pack is auto provisioned with the primary
state set to the same value as the AUTOP parameter. The wavelength manager
circuit pack ports may be auto provisioned. For further details, see 7.1.1.7,
Wavelength manager ports.
The wavelength translator and wavelength regenerator circuit pack ports must
be manually provisioned.
7.1.1.7 Wavelength manager ports

When an SFP transceiver is plugged into a wavelength manager port that is not yet
provisioned, a corresponding transceiver port is auto provisioned according to the
AUTOP parameter setting as shown in the following table. The port is auto
provisioned with the WAVELENGTH parameter set to the wavelength of the SFP
transceiver that was inserted. A REPT^DBCHG system message is sent from the
network element indicating that the port is provisioned.
AUTOP Parameter Settings
AUTOP Setting
Means
NONE
IS
OOS
AINS
No auto provisioning occurs.

The SFP transceiver is auto provisioned to the OOS-AU,FLT&NALM state.
The SFP transceiver is auto provisioned to the OOS-AUMA,FLT state.
The SFP transceiver is auto provisioned to the OOS-AU,FLT&AINS state.
If an SFP transceiver is inserted into a wavelength circuit pack that is not

provisioned, then auto provisioning does not occur.
Cross-connect pairs
As shown in the following figure, each port is part of a cross-connect pair. Ports 1
and 2 form one pair while ports 3 and 4 form another cross-connect pair. A given
ports mate is the other port in the cross-connect pair. For instance, port 1 is the
mate of port 2 and similarly, port 2 is the mate of port 1.
Wavelength Manager Cross-Connect Pairs
Wavelength Manager
Circuit Pack
Port 4
Port 3
Port 2
Port 1
2-way, 2-port Cross Connects
Protocol assignment
The protocol that is assigned to a transceiver port is determined as follows:

If the mate port is not yet provisioned or if the mate port is provisioned with the
PROTOCOL parameter set to AUTO, then the new port is also assigned with
PROTOCOL=AUTO.
If the mate port is already assigned with a valid protocol, then the new port is
given the same protocol and a 2WAY cross-connect is automatically created
between the two ports.
When a port is assigned PROTOCOL=AUTO, the wavelength manager circuit
pack starts scanning the incoming signal, looking for a valid signal. Once a valid
signal is found, such as OC-48, the transceiver port is configured with
PROTOCOL=OC48. If the mates transceiver port is still scanning for a signal,
then that port is also configured to PROTOCOL=OC48 and a 2WAY crossconnect is provisioned between the two ports.
Whenever the protocol changes from AUTO to a supported protocol, a
corresponding REPT^DBCHG system message is sent from the network element.
Whenever a 2WAY cross-connect gets auto provisioned, a corresponding
REPT^DBCHG system message is sent from the network element.
When a Muxponder circuit pack in inserted into an uprovisioned slot:
7.1.1.8 Muxponder circuit packs

When a Muxponder circuit pack is inserted into an unprovisioned slot:
The Muxponder circuit pack is auto provisioned with the primary state set to the
same value as the AUTOP parameter. The Muxponder circuit pack ports may be
auto provisioned. For further details, see 7.1.1.9, Muxponder circuit pack
ports.
7-5
7.1.1.9 Muxponder circuit pack ports

All ports (FE and GE client side, and OC-48 or STM-16 line side) of a
Muxponder circuit pack may be auto provisioned upon the auto provisioning of
the Muxponder circuit pack.
The two GE client side ports and the OC-48 or STM-16 line side ports can be
auto provisioned only when SFPs are plugged into the SFP cages.
Cross-connections between ports of a Muxponder circuit pack are not auto
provisioned.
7.1.1.10 Expansion shelves

When an expansion shelf is connected to an unprovisioned multi-shelf port on an
MSCP:
The expansion shelf is auto created with the discovered shelf configuration.
Since the expansion shelf is auto created, it does not depend on the AUTOP flag
being set.
If the AUTOP parameter is set to IS, every slot in the expansion shelf that has a
circuit pack present is auto provisioned. Additionally, all of the circuit packs
supported facilities are also auto provisioned.
If the AUTOP parameter is set to OFF, no slot in the expansion shelf is
provisioned.
7.1.2 Auto de-provisioning
Note
Auto de-provisioning allows a provisioned hardware component, such as a circuit

pack, to be automatically deleted from the system if it is removed. This includes all
facilities that are supported by the hardware component, such as ports.
Auto de-provisioning is off by default.
7.1.2.1 Controlling auto de-provisioning

Auto de-provisioning is controlled by the AUTOD parameter that is accessed
through the ED-SYS command. The AUTOD parameter (using the hh-mm format)
sets the length of time for the Netstender to wait before deleting the provisioning
information of the hardware component.
The AUTOD parameter has a range from 00-00 to 96-00 hours, a default value of
00-00 hours, and a minimum time of 00-05.
If a circuit pack is removed from its provisioned slot, and
AUTOD is not 00-00, and
the corresponding equipment or facility port is not in the AINS state,
Note
then an AUTOD timer starts counting down to 00-00 for this equipment or facility.
Once the timer counts down to 00-00, the equipment and all supported entities are
automatically deleted from the system.
If the AUTOD parameter is 00-00, the circuit pack is disabled.
Restrictions
If a piece of hardware is removed from its provisioned slot and the corresponding
equipment or facility is in the AINS state, a timer is not started for this equipment
or facility. As a result, the equipment or facility is not auto de-provisioned.
If a hardware component is replaced with mismatched hardware, the
corresponding equipment or facility is not in the AINS state (that is,
OOS-AU,MEA), and the AUTOD parameter is not 00-00, the auto deprovisioning timer will continue counting for this equipment or facility.
If the value of the AUTOD parameter is edited after a timer has already started
counting and the timer has already passed the new value set for the AUTOD
parameter, auto de-provisioning is applied immediately to the corresponding
equipment or facility and all the supported entities as well.
If an SFP is removed from its provisioned port, an AUTOD timer is started for the
port. If there is a cross-connect on this port and the timer expires, the cross-connect
and any protection group are deleted first and then the port is deleted.
If an MSCP restart occurs, all auto de-provisioning timers are reset.
The RTRV-AUTOD command shows how much time is left before the
corresponding equipment or facility port is auto de-provisioned.
7.1.2.2 Expansion shelves

For the auto de-provisioning feature, the following conditions apply to expansion
shelves:
If the AUTOD parameter is set to greater than 00-00 and the SFP or cable is
removed, then detaching the link to the MSCP circuit pack deletes everything
that is provisioned in the expansion shelf, as well as the expansion shelf.
If the AUTOD parameter is set to 00-00, the auto de-provisioning feature is
turned off. The contents of an expansion shelf must be deleted manually in the
following sequence:
1
Delete the supported facilities in each slot, such as amplifiers or ports. (See
the relevant section in this chapter, such as, 7.7.6, Deleting an optical
amplifier.)
Delete the equipment in each slot, such as an OLA or D1ADM. (See section
7.6.7, Deleting equipment in this document.)
Disconnect the link from the expansion shelf to the MSCP circuit pack in the
main shelf.
7-7
Delete the expansion shelf from the system. (See section 7.6.7, Deleting
equipment in this document.)
7.1.3 Pre-provisioning
Pre-provisioning refers to the systems ability to receive and process provisioning
commands for equipment that is not currently present in the Netstender shelf. The
provisioning sequence is similar to that for normal provisioning commands, with
the exception that no action can be taken to activate the provisioning change.
The Netstender supports provisioning the following components before they are
actually present:
expansion shelves
optical amplifier circuit packs
optical supervisory channel circuit pack
wavelength conversion circuit packs
optical add-drop module circuit packs
active and passive multiplex/demultiplex module circuit packs
dispersion compensation module circuit packs
7.1.4 Automatic in service secondary state

When provisioned hardware has a secondary state of Automatic In Service
(AINS), the hardware is in a delay transition (to the IS) state. Alarms and threshold
crossing alerts (TCA) are not generated for the hardware if AINS is present. Once
the fault conditions clear, the timer starts counting down and the hardware
transitions to In Service when the timer expires.
Note
The system-wide default timer setting for AINS is 08-00 hours. The timer can be
configured up to 96-00 (96 hours). If the system-wide default timer for AINS is
reset, it will not affect the active timer currently set on a piece of equipment.
However, the timer on a specific piece of equipment is reset if the timer for that
equipment is changed.
The shelf and multiport system control processor (MSCP) are automatically
provisioned as part of system commissioning.
7.1.4.1 ENT commands

When using an ENT command to provision a piece of equipment, the state can be
specified as one of the values shown in the following table.
ENT command states
State
Means
IS
OOS
IS,AINS
In-Service
Out-Of-Service
In-Service, Automatic IN-Service
7.1.4.2 Forcing a transition from the AINS state to the IS state

Two methods are available to force a transition from the AINS state to the IS state:
1
ED commands can force a piece of equipment from the IS,AINS state to the IS
state.
Use a RMV command followed by a RST command to force transition a piece

of equipment from the IS,AINS state to the IS state.
7.1.4.3 Viewing AINS timers

To view the AINS timers for a piece of equipment, use the RTRV command for
the equipment. The following two parameters appear, which are explained in the
following table.
AINS timers
Parameter
Means
AINSTMR
is the automatic in-service timer in the format HH-MM. This parameter is the
provisioned value. The maximum value is 96-00 and the default value is
08-00.
is the active automatic in-service timer in the format HH-MM. This parameter
is the time remaining before transition to the in-service state. The maximum
value is 96-00 and there is no default value.
ACTAINSTMR
7.1.4.4 MSCP or MSI restart or replacement

If either the MSCP or MSI circuit packs are restarted or replaced, all active AINS
timers in the system are restarted. For example, if the AINS timer is set to 01:00
and an optical amplifier has counted down to 00:30 and then the MSI is replaced,
the optical amplifier counter is reset to 01:00.
7.1.4.5 Retrieving the faults against equipment in the AINS state

To retrieve a list of faults against equipment in the AINS state, enter the following
syntax at the TL1 command line interface:
RTRV-COND-ALL:[TID]:[<aid>]:<CTAG>;
7-9
7.2 Hierarchical organization of Netstender components

The Netstender organizes its hardware components and software in a hierarchy.
This is reflected in the order that components can be added to and removed from
the Netstender, restored to service, and removed from service. The following
figure shows a partial example of the hierarchical organization that the Netstender
uses.
Netstender hierarchical organization
Site
System
Equipment
Facility
SITE
Netstender
MAIN
SHELF
CU
MSI
SCP
DCM*
Common Equipment
Circuit Packs
ports
DWDM
amplifier
C1ADM
Application
Circuit Packs
ports
PMT*
ports
EXTENSION
SHELF
CU
ESI
DCM*
Common Equipment
Circuit Packs
ports
DWDM
amplifier
C1ADM
Application
Circuit Packs
ports
DCM is the generic term for Dispersion Compensating Fiber Module that
includes: SMF5, SMF10, SMF15, SMF20, SMF30, SMF40, SMF60, and SMF80.
PMT is the generic term for Power Monitor Tap that refers PMT1 (1%).
7.2.1 Site
At the highest level, the Netstender is located at a physical site that is identified
through provisionable site elements, such as site identifier, site name, and time
zone.
7.2.2 System
From within a site, one or more Netstenders can be deployed. As a result, each
Netstender must be uniquely identified with system-level parameters, such as
network element (NE) name and system identifier (SID).
7.2.3 Equipmentshelves and circuit packs

Each system consists of one main shelf and, optionally, additional expansion
shelves that are classified as equipment. Within each shelf is a combination of
common equipment circuit packs and provisionable slots for application circuit
packs. These components are discussed in the following sections.
7.2.3.1 Shelves
Each shelf has a unique shelf number. For example, the main shelf is designated as
1 and expansion shelves are designated as 11, 21, or 31.
7.2.3.2 Common equipment circuit packs

In each shelf there are circuit packs that are considered common equipment.
Table 7-1 lists the common equipment that is required in a Netstender shelf.
Table 7-1
Common equipment
Shelf Type
Shelf Number
Common Equipment Circuit Pack
1030 Shelf
2060 Main Shelf
2060 Expansion Shelf
11, 21, or 31
Cooling Unit (CU) circuit pack1

System Control Processor (SCP) circuit pack1
Main Shelf Interface (MSI) circuit pack2
Multiport System Control Processor (MSCP) circuit
pack3
Expansion Shelf Interface (ESI) circuit pack4
1. The CU and SCP for the 1030 Shelf have dedicated slots in which they are installed.
2. Both the MSI and CU for the 2060 Main Shelf have dedicated slots in which they are installed.
3. The MSCP for the 2060 Main Shelf must be installed in Shelf 1, Slot 5. For further details, see the
Netstender Installation and Commissioning Guide.
4. Both the ESI and CU for the 2060 Expansion Shelf have dedicated slots in which they are
installed.
7-11
7.2.3.3 Provisionable slots for application circuit packs

In each shelf there are a number of provisionable slots for application circuit
packs. Each slot is identified by the type of application circuit pack provisioned in
the slot.
Table 7-2 lists the various types of application circuit packs that are available.
Table 7-2
Application circuit packs
Application
Circuit Pack
Optical Amplifiers
DWDM C-Band Booster Amplifier (OBA)

DWDM C-Band Pre-Amplifier (OPA)
Optical Line Amplifier (OLA)
Optical Line Amplifier with Mid-Stage Access (OLAM)
Single Optical Supervisory Channel (OSC)
Wavelength Manager (WM)
Wavelength Regenerator (WR)
Wavelength Translator (WT)
Double 1-Channel CWDM OADM (C1ADM)
4-Channel CWDM Mux/Demux (C4MD)
2-Channel N+1 DWDM OADM (D2ADM)
4-Channel N+1,2,3 DWDM OADM (D4ADM)
32-Channel DWDM Mux/Demux Module 1 (D32MD1)
32-Channel DWDM Active Mux/Demux Module 1 (D32AMD1)
SMF DCM 20 km (SMF20)
Optical Supervisory Channel

Wavelength Conversion
Muxponder Modules
Multiplex/Demultiplex Modules
Dispersion Compensation
Modules
Table 7-2
Application circuit packs (Continued)
Application
Circuit Pack
SMF ITU-T DCM 40 km
SMF ITU-T DCM 60 km
SMF ITU-T DCM 80 km
7.2.4 Applications
Many provisionable circuit packs contain one or more facilities. Each
provisionable piece of equipment has its own identifiers that are provisioned at the
facilities level.
7.2.5 Supporting and supported relationships
Important
Based on the hierarchical organization of the Netstender, a supporting-supported

relationship exists between the higher-level supporting hardware equipment and
subservient supported equipment.
To provision a lower-level piece of equipment, the higher-level supporting
equipment must be provisioned first. Likewise, when removing equipment from
service, the lower-level supported equipment must be removed from service before
the supporting equipment can be removed from service.
7-13
7.3 Designating names and IDs to system components

In setting parameter values during the provisioning process, various elements and
components of the Netstender system can be given names and identifiers.
The following figure shows the various elements and components that can be
designated with names and identifiers during provisioning.
Designating names and IDs to system components
Site
System
Equipment
Facility
Site-Name and Site-ID
SITE
Netstender
NE-Name and NE-ID

Shelf ID
SHELF
CU
MSI
SCP
DCM*
SCP-ID
ports
Circuit Pack ID
ID1 and ID2
Circuit Pack ID
amplifier
ID1 and ID2
amplifier
Circuit Pack ID
ID1 and ID2
ports
Circuit Pack ID
ID1 and ID2
ports
Circuit Pack ID
ID1 and ID2
ports
Circuit Pack ID
ID1 and ID2
DWDM
CWDM
C8MD
C1ADM
PMT*
In addition, the three custom

fields custom1, custom2, and
custom3 are available for adding
other system information.
Table 7-3 lists the names and identifiers that need to be provisioned and the system
limits that pertain to each.
Table 7-3
Names, identifiers, and custom field limits
Names and
Identifiers
Limits
Site Name
Site ID
NE Name
NE ID
Shelf ID
SCP ID
Circuit Pack ID
ID1
ID2
Custom1
Custom2
Custom3
Up to 20 alphanumeric characters
Integer between 0 and 65535
Up to 20 alphanumeric characters and a dash (-)
Integer between 0 and 65535
7.4 System provisioning

7.4.1 Network element, site, time zone, and system identification code
7.4.1.1 Editing the network element, site, and time zone
Superuser
Provisioning
Maintenance
Surveillance
To edit system-wide provisioning information, enter the following at the TL1

command line interface:
ED-SYS:[TID]::<CTAG>[:[:[:[[NEID=<neid>][,NENAME=<nename>]
[,GATEWAY=<gateway>][,SECGATEWAY=<secgateway>][,SITEID=<siteid>]
[,SITENAME=<sitename>][,TZ=<tz>][,AUTODST=<autodst>][,AUTOP=<autop>]
[,AUTOD=<autod>][,<AINSTMR=ainstmr>]]]]];
Example
ED-SYS:NETSTENDER::100::TZ=CANADAEASTERN,AUTODST=Y;
Response
The Netstender returns a COMPLD message:

NETSTENDER 02-10-22 13:52:47
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-10-22 13:52:47
A
68 REPT DBCHG
DBCHGSEQ=37:ED-SYS::TZ=CANADAEASTERN,AUTODST=Y,AUTOP=AINS,
AUTOD=00-00,AINSTMR=08-00"
;
Note
From release 5.2 and up, the new North American daylight-saving-time rules are
automatically supported when AUTODST=Y is applied.
7-15
7.4.1.2 Setting the system identification code

Superuser
Provisioning
Maintenance
Surveillance
The system identification code (SID) is used to identify different network elements
in a network.
To set the system identification code, enter the following at the TL1 command line
interface:
SET-SID:[TID]::<CTAG>::<sid>;
Example
SET-SID:NETSTENDER::100::NETSTENDER23;
Response

NETSTENDER23 02-10-22 13:54:05
M
100 COMPLD
;
NETSTENDER>
NETSTENDER23 02-10-22 13:54:05
A
69 REPT DBCHG
"DATE=02-10-22,TIME=13-54-05,SOURCE=100,LINKID=2-23,USERID=admin,
DBCHGSEQ=38:SET-SID:NETSTENDER23"
;
7.4.1.3 Retrieving the network element, site, time zone, and uptime
To retrieve the network element, site, time zone and uptime information, enter the
following at the TL1 command line interface:
RTRV-SYS:[TID]::<CTAG>;
Example
RTRV-SYS:NETSTENDER23::100;
Response
The Netstender returns the numeric network element identifier, network element
name, numeric site identifier, site name, time zone, daylight savings time, the
system up time, the auto provisioning and auto de-provisioning parameters, as well
as the automatic in-service timer parameter:
NETSTENDER23 04-03-02 18:48:12
M 100 COMPLD
"::TYPE=NETSTENDER2060,NEID=0,NENAME=NETSTENDER,GATEWAY=10.1.1.1,SITEI
D=0,SITENAME=BTI,TZ=USAEASTERN,AUTODST=Y,UPTIME=5122-08-34,AUTOP=IS,
AUTOD=00-00,AINSTMR=00-00"
;
7.4.1.4 Retrieving the vendor, model, NE type and software version

To retrieve the vendor, model, network element type and software version, enter
the following at the TL1 command line interface:
RTRV-NETYPE:[TID]::<CTAG>;
Example
RTRV-NETYPE:NETSTENDER::100;
Response
The Netstender sends back a COMPLD message that indicates the network
element type:
NETSTENDER 02-10-22 13:59:10
M
100 COMPLD
BTI Photonic Systems Inc.,Netstender2060,WDM,4.1.0
;
Note
WDM means wavelength division multiplexing.
7-17
7.4.2 Date and time

7.4.2.1 Editing the date and time
Superuser
Provisioning
Maintenance
Surveillance
To edit the time and date of the Netstender, enter the following at the TL1
ED-DAT:[TID]::<CTAG>::[<YY-MM-DD>],[<HH-MM-SS>];
Note
The valid two-digit date range is from 70-01-01 to 36-02-06 that represents
1970-01-01 (GMT) to 2036-02-06 (GMT).
Example
ED-DAT:NETSTENDER::100:02-10-22,20-30-00;
Response

NETSTENDER 02-10-22 20:30:00
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-10-22 20:30:00
A
71 REPT DBCHG
DBCHGSEQ=40:ED-DAT::02-10-22,20-30-00"
;
7.4.2.2 Editing the date and time during a daylight-saving-time transition

Inaccurate date and time settings can occur if you set the date and time on the
Netstender during a daylight-saving-time (DST) transition. When a time zone
changes to or from DST, the local time can roll back by one hour (for example,
2:00 AM becomes 1:00 AM). The local time during this hour is ambiguous (for
example, 1:15 AM occurs twice on the day that the time zone switches from DST).
To avoid this problem, use the following procedure.
Editing the date and time during a daylight-saving-time transition
Step
Action
Disable the AUTODST parameter

Disable the automatic daylight saving time (DST) parameter by entering the following
ED-SYS:NETSTENDER::100:::AUTODST=N;
2
Set the local time

Set the local time by entering the following syntax at the TL1 command line interface:
ED-DAT:NETSTENDER::100::YY-MM-DD,HH-MM-SS;
where
YY-MM-DD
HH-MM-SS
is the date in a year-month-day format

is the time in an hour-minute-second format
Example
ED-DAT:NETSTENDER::100::02-04-07,00-31-57;
3
Re-enable the AUTODST parameter

Re-enable the automatic daylight saving time (DST) parameter by entering the following
ED-SYS:NETSTENDER::100:::AUTODST=Y;
7-19
7.4.2.3 Retrieving the system identifier, date, and time

System header information
To retrieve basic TL1 header information from the Netstender, enter the following
RTRV-HDR:[TID]::<CTAG>;
Example
RTRV-HDR:NETSTENDER::100::;
Response
The Netstender returns the system identifier, date and time followed by a
COMPLD message:
NETSTENDER 02-10-22 20:31:02
M
100 COMPLD
7.4.3 IP address parameters

7.4.3.1 Editing the IP address
Superuser
Note
Provisioning
Maintenance
Surveillance
Using this command can result in temporary loss of contact with the network
element.
To edit the IP address information for the network element, enter the following at
the TL1 command line interface:
ED-IP:[TID]:<aid>:<CTAG>:::[[,IPADDR=<ipaddr>][,IPMASK=<ipmask>]
[,MEDIARATE=<mediarate>][,C1=<custom1>]][:[<pst>],[<sst>]];
Example
ED-IP:NE-117:IP-NMS:100:::IPADDR=50.1.1.1,IPMASK=255.255.255.0,
MEDIARATE=AUTO;
Response
NE-117 04-02-02 12:28:46
M 100 COMPLD
;
NETSTENDER>
NE-117 04-02-02 12:28:47
A 19 REPT DBCHG
DBCHGSEQ=12:ED-IP:IP-NMS::IPADDR=50.1.1.1,IPMASK=255.255.255.0,
MEDIARATE=AUTO"
;
NE-117 04-02-02 12:28:48
A 20 REPT DBCHG
"TIME=12-28-48,DATE=04-02-02,SOURCE=0000,DBCHGSEQ=13:ED-IP:
IP-NMS:::OOS-AU,UEQ&SGEO"
;
7-21
7.4.3.2 Retrieving the IP address

To retrieve the IP address information for the network element, enter the following
RTRV-IP:[TID]:[<aid>]:<CTAG>;
Example
RTRV-IP:NE-115::100::;
Response
NE115 06-05-09 13:16:31
M
100 COMPLD
"IP-NMS:IPADDR=10.1.1.115,IPMASK=255.0.0.0,IPBCST=10.255.255.255,
TYPE=ETHERNET,UNMBRD=N,SPEED=100,DUPLEX=FULL,MEDIARATE=AUTO,MTU=1500,
MACADDR=0010ec003a38,:,"
"IP-CRAFT:IPADDR=192.168.17.1,IPMASK=255.255.255.0,
IPBCST=192.168.17.255,TYPE=ETHERNET,UNMBRD=N,SPEED=0,MEDIARATE=AUTO,
MTU=1500,MACADDR=0010ec803a38,:,"
"IP-1-6-0:IPADDR=127.0.0.1,IPMASK=255.0.0.0,TYPE=LOGICAL,UNMBRD=N,
SPEED=100,MEDIARATE=AUTO,MTU=33212,:IS-NR,"
"IP-1-6-1:IPADDR=20.1.1.6,IPMASK=255.255.255.0,IPBCST=20.1.1.255,
TYPE=OPTICAL,UNMBRD=N,SPEED=100,MEDIARATE=AUTO,MTU=1500,
MACADDR=0010ec00513f,:IS-NR,"
TYPE=OPTICAL,UNMBRD=N,SPEED=100,MEDIARATE=AUTO,MTU=1500,
TYPE=ETHERNET,UNMBRD=N,SPEED=100,MEDIARATE=AUTO,MTU=1500,
;
Note
IP-NMS
is the management LAN and IP-CRAFT is the craft LAN.
7.4.4 Craft serial interface parameters

When the system is originally commissioned for service, the serial port settings
default to the following values:
Speed = 9600
Data bits = 8
Parity = None
Stop bits = 1
Important
Flow control = None

The following procedure cannot be used to edit the default values of the craft serial
port on an expansion shelf. The RS-232 default values of the ESI craft serial port
are not editable.
7.4.4.1 Editing the craft serial port information

Superuser
Note
Provisioning
Maintenance
Surveillance
Using this command can result in temporary loss of contact with the network
element, if connected through the serial port.
To edit the serial port information for the network element, enter the following at
ED-SER:[TID]:<aid>:<CTAG>:::[[RATE=<rate>][,DATABITS=<databits>]
[,PARITY=<parity>][,STOPBITS=<stopbits>]];
Example
ED-SER:NETSTENDER:SER-1:100:::RATE=9600,DATABITS=8,PARITY=NONE,
STOPBITS=1;
Response

NETSTENDER 02-06-30 20:45:45
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-06-30 20:45:45
A
56 REPT DBCHG
DBCHGSEQ=31:ED-SER:SER-1::RATE=9600,DATABITS=8,PARITY=NONE,STOPBITS=1"
;
7-23
7.4.4.2 Retrieving the craft serial port information

To retrieve the serial port information for the network element, enter the following
RTRV-SER:[TID]:[<aid>]:<CTAG>;
Example
RTRV-SER:NETSTENDER::100::;
Response

NETSTENDER 02-06-30 20:44:11
M
100 COMPLD
"SER-1:RATE=9600,DATABITS=8,PARITY=NONE,STOPBITS=1"
7.5 Expansion shelf provisioning

After the basic system commissioning is completed, expansion shelves can be
provisioned. All provisioning is performed on the main shelf.
Expansion shelves are provisioned as equipment elements and information on
equipment provisioning is provided in the section 7.6, Equipment provisioning
in this document.
The provisioning rules that apply to an expansion shelf are discussed in this
section.
7.5.1 System requirements

Netstender systems with expansion shelves must use MSCP BP1A20BA or higher.
SCP BP1A20AA does not support expansion shelves.
For optical communication between the Netstender main shelf and the expansion
shelves, the MSCP and ESI circuit packs must use BTI approved SFPs that support
the 100FX protocol. These include the following:
The following table lists the SFP transceivers that are recommended for expansion
shelf communications:
SFP transceivers for expansion shelf communications
Bit Rate
Wavelength
Reach
Product Code Purpose
125 Mb/s or 100FX

125 Mb/s or 100FX
125 Mb/s or 100FX
125 Mb/s or 100FX
CWDM
1310 nm
1310 nm
1310 nm
0 to 80 km BP3AE1CL
0 to 40 km BP3AE1MI
0 to 10 km BP3AE1MS
0 to 2 km
BP3AE1MM
Multishelf
Multishelf
Multishelf
Multishelf
7.5.1.1 Restrictions
The Netstender 1030 does not support expansion shelves.
The expansion shelf port on the ESI circuit pack labeled To Expansion is not
supported in this release.
7-25
7.5.2 Expansion shelf provisioning rules

7.5.2.1 Basic provisioning tasks
Expansion shelves can be pre-provisioned with or without being connected to the
main shelf through the MSCP. Use the ENT-EQPT command.
Expansion shelves can be de-provisioned with or without being connected to the
MSCP on the main shelf. Use the DLT-EQPT command.
Expansion shelf parameters can be edited with or without being connected to the
MSCP on the main shelf. Use the ED-EQPT command.
Expansion shelves can be taken out of service with or without being connected to
the MSCP on the main shelf. Use the RMV-EQPT command.
Expansion shelves can be placed in service with or without being connected to the
MSCP on the main shelf. Use the RST-EQPT command.
For further information about how to use the commands discussed above, refer to
section 7.6, Equipment provisioning in this document or refer to the TL1
Reference Guide.
7.5.2.2 Auto creation of expansion shelves

When an expansion shelf is connected to an unprovisioned multi-shelf port, it is
auto created with the discovered shelf configuration. For more information about
expansion shelf auto creation, refer to 7.1.1.10, Expansion shelvesin this
document.
7.5.2.3 Expansion shelf LEDs

The fault LEDs on the expansion shelf SFPs in the Multiport SCP do not activate if
an expansion shelf is not provisioned.
7.5.2.4 Alarms
If an REPLUNITMEA alarm is present on an expansion shelf that is connected to
an MSCP, the expansion shelf can be forced to accept provisioning data by using
the CMMT-ES command.
For further information about how to use the CMMT-ES command, refer to the
TL1 Reference Guide.
7.5.3 Reconfiguring expansion shelves

Expansion shelves can be configured for the following configurations:
3-SLOT
4-SLOT
5-SLOT
6-SLOT
Note
For information on how to physically configure an expansion shelf, refer to the

Installation and Commissioning Guide.
When provisioning an expansion shelf, use the SHCONF field to specify the shelf
configuration. If no SHCONF value is entered, the Netstender automatically
defaults to the 6-SLOT configuration.
7.5.4 Re-purposing expansion shelves

To re-purpose an existing expansion shelf to a main shelf, or vice-versa, the
Netstender shelves must be taken out of service and powered down.
The following equipment is required when changing an expansion shelf to a main
shelf:
main shelf interface (MSI) circuit pack
multiport system control processor (MSCP) circuit pack
The following equipment is required when changing a main shelf to an expansion
shelf:
expansion shelf interface (ESI) circuit pack
7.5.5 Expansion shelf command line interface

The command line interface (CLI) allows users to retrieve inventory information
about SFPs in the expansion shelf interface circuit pack. The ESI CLI is accessed
through the ESI craft serial port. For more information about the ESI CLI, refer to
Appendix D: ESI command line interface.
7-27
7.6 Equipment provisioning

7.6.1 Entering new equipment
The command to enter new equipment is ENT-EQPT.
To enter new equipment provisioning information, enter the following syntax at
ENT-EQPT:[TID]:<aid>:CTAG::<type>[:[ID=<id>][,C1=<custom1>]
[,C2=<custom2>][,C3=<custom3>][,SHCONF=<shconf>][:[<pst>][,<sst>]]];
Note
Expansion shelves can be provisioned without the expansion shelf being

physically connected to the MSCP. If the SHCONF parameter is not specified for
an expansion shelf, the system defaults to a 6-SLOT configuration.
Example
The following example shows how to enter a new optical line amplifier circuit
pack in shelf one, slot two:
ENT-EQPT:NETSTENDER:OPA-1-2:100::BP1A01AA;
Response

NETSTENDER 02-11-05 15:00:03
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-05 15:00:04
A
205 REPT DBCHG
DBCHGSEQ=36:ENT-EQPT:OPA-1-2::BP1A01AA::"
;
7.6.2 Editing equipment

The command to enter new equipment is ED-EQPT.
To edit equipment provisioning information, enter the following syntax at the TL1
ED-EQPT:[TID]:<aid>:<CTAG>:[:[<type>][:[ID=<id>][,C1=<custom1>]
[,C2=<custom2>][,C3=<custom3>][,SHCONF=<shconf>][:[<pst>][,<sst>]]]];
Note
Expansion shelves can be edited without the expansion shelf being physically
connected to the MSCP.
Example
The following example shows how to edit a custom string 1 (C1) with equipment
information:
ED-EQPT:NETSTENDER:OLA-1-6:100:::C1=Line amplifier for downtown link:,;
Response

NETSTENDER 02-11-05 15:00:00
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-05 15:00:01
A
165 REPT DBCHG
DBCHGSEQ=16:ED-EQPT:OLA-1-6:::C1=Line amplifier for downtown link":"
;
Common parameters for circuit packs
Listed below are brief descriptions of the common parameters for circuit packs:
type
is the product equipment code (PEC) of the circuit pack.
id
is a descriptive information field about the circuit pack or shelf

location of up to 20 alphanumeric characters.
custom1
custom2
custom3
are custom strings available for customer use.
shconf
is a field used to edit the shelf configuration of an expansion shelf.
pst
is the primary state of the circuit pack.
sst
is the secondary state of the circuit pack. It is currently not

available for use.
7-29
7.6.3 Removing equipment from service

The command to remove equipment from service is RMV-EQPT.
To remove equipment from service, enter the following syntax at the TL1
Example
The following example shows how to remove an optical line amplifier that is in
shelf one, slot one from service:
Response
The Netstender returns a COMPLD and DBCHG messages:

NETSTENDER 02-11-22 08:06:40
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-22 08:06:40
A
12 REPT RMV EQPT

"OLA-1-1:OOS-MA,MT"
;
NETSTENDER 02-11-22 08:06:40
A
14 REPT DBCHG
"TIME=08-06-40,DATE=02-11-22,SOURCE=100,LINKID=223,USERID=admin,
DBCHGSEQ=4:RMV-EQPT:OLA-1-1"
;
7.6.4 Restoring equipment to service

The command to restore equipment to service is RST-EQPT.
To restore equipment to service, enter the following syntax at the TL1 command
line interface:
RST-EQPT:[TID]:<aid>:<CTAG>;
Example
The following example shows how to restore an optical line amplifier that is in
shelf one, slot one to service:
RST-EQPT:NETSTENDER:OLA-1-1:100;
Response
The Netstender returns a COMPLD message and DBCHG messages:

NETSTENDER 02-11-22 08:13:06
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-22 08:13:06
A
15 REPT RST EQPT

"OLA-1-1:IS-NR,"
;
NETSTENDER 02-11-22 08:13:06
A
17 REPT DBCHG
DBCHGSEQ=6:RST-EQPT:OLA-1-1"
;
7-31
7.6.5 Retrieving equipment attributes

The command to retrieve equipment attributes is RTRV-EQPT.
To retrieve equipment attributes, enter the following syntax at the TL1 command
line interface:
RTRV-EQPT:[TID]:[<aid>]:<CTAG>;
Examples
The following example shows how to retrieve the equipment attributes of an

optical line amplifier that is in shelf one, slot one:
RTRV-EQPT:NETSTENDER::100::;
Response from a Netstender 2060

NETSTENDER 04-08-05 10:24:36
M
100 COMPLD
"MS-1:BP1A56AA:SHCONF=6-SLOT:IS-NR,"
"SCP-1-5:BP1A20AA::IS-NR,"
"OLA-1-1:BP1A03AA-SC::IS-NR,"
"OSC-1-2:BP1A28AA:ID=OSCVince,C2=Test Network OSC,:IS-NR,"

NE117 04-11-18 17:04:26
M
100 COMPLD
"SH-1:BP1A56AA:SHCONF=3-SLOT:IS-NR,"
"SCP-1-3:BP1A20AA::IS-NR,"
"SMF30-1-1:BP1A10CD-LC::IS-NR,"
"SPA-1-2:BP1A05PA::IS-NR,"
7.6.6 Retrieving an equipment inventory

The command to retrieve an equipment inventory for an Netstender is RTRV-INV.
To retrieve an equipment inventory, enter the following syntax at the TL1
Example
The following example shows how to retrieve an equipment inventory for a

Netstender:
RTRV-INV:NETSTENDER::100::;

NETSTENDER 04-11-18 16:59:36
M
100 COMPLD
"MS-1,EQPT:NAME=MS2060,PEC=BP1A50AA,CLEI=None,FNAME=Main Shelf
Netstender 2060,SHCONF=6-SLOT,"
"SH-1,EQPT:NAME=2060,PEC=BP1A5021,CLEI=WMMKTWOKRA,FNAME=Netstender
2060 Shelf,HWREV=\"0\","
"SLOT-1-1,EQPT:NAME=FLLR,PEC=BP1A55AA,CLEI=WMPQALX7AA,FNAME=Filler,
SER=\"N/A\",HWREV=\"0\",MFGDAT=\"N/A\",MFGLOCN=N/A,TSTDAT=N/A,
TSTLOCN=N/A,"
TSTLOCN=N/A,"
TSTLOCN=N/A,"
TSTLOCN=N/A,"
"SLOT-1-5,EQPT:NAME=SCP,PEC=BP1A20AA,CLEI=WMEC170KAA,FNAME=System
Control Processor,SER=\"03190142\",HWREV=\"4\",MFGDAT=\"2004-08-17\",
MFGLOCN=BTI Thurston,TSTDAT=2004-08-17,TSTLOCN=BTI Thurston,"
TSTLOCN=N/A,"
"SI-1,EQPT:NAME=MSI,PEC=BP1A53AA,CLEI=WMEC280KAA,FNAME=Main Shelf
Interface,SER=\"BTI00001627\",HWREV=\"5\",MFGDAT=\"2004-08-04\",
"CU-1,EQPT:NAME=CU,PEC=BP1A52AA,CLEI=CL1A52AA,FNAME=Cooling Unit,
SER=\"454326578\",HWREV=\"1\",MFGDAT=\"2002-07-18\",MFGLOCN=BTI
THURSTON,TSTDAT=2002-07-18,TSTLOCN=BTI THURSTON,"
;
7-33

NE117 04-11-18 17:04:17
M
100 COMPLD
"SH-1,EQPT:NAME=MS1030,PEC=BP1A56AA,CLEI=WMMPA10FRA,FNAME=Main Shelf
Netstender 1030,HWREV=1,SHCONF=3-SLOT,"
"SLOT-1-1,EQPT:NAME=SMF30,PEC=BP1A10CD-LC,CLEI=CLEI,FNAME=Dispersion
Compensation Module 30km,SER=\"11223344\",HWREV=\"1\",
MFGDAT=\"2005-11-12\", MFGLOCN=BTI,TSTDAT=2005-11-12,TSTLOCN=BTI,"
"SLOT-1-2,EQPT:NAME=SPA,PEC=BP1A05PA-SC,CLEI=NotSet,FNAME=Single
Channel Pre-Amplifier-SC,SER=\"BTI00080183\",HWREV=\"5\",
MFGDAT=\"2004-10-14\",MFGLOCN=BTI Thurston,TSTDAT=2004-10-14,TSTLOCN=BTI
Thurston,"
"SLOT-1-3,EQPT:NAME=SCP,PEC=BP1A21AA,CLEI=WMUCAMSLAA,FNAME=System
"CU-1,EQPT:NAME=CU,PEC=BP1A57AA,CLEI=WMPQASP7AA,FNAME=Cooling Unit,
SER=\"454326578\",HWREV=\"1\",MFGDAT=\"2004-10-28\",MFGLOCN=BTI Thurston,
TSTDAT=2004-10-28,TSTLOCN=BTI Thurston,"
;
7.6.7 Deleting equipment

Notes
The command to delete equipment is DLT-EQPT.

To delete equipment, the equipment must be taken out of service first.
Ensure that OSC IP entities are placed out of service (OOS) before you attempt to
delete OSC equipment. For information, see Removing OSC IP interfaces in the
Optical Supervisory Channel OAM&P Guide.
Enter the following syntax at the TL1 command line interface:
DLT-EQPT:[TID]:<aid>:<CTAG>::[<type>]:[CMDMDE=<cmdmde>];
Example
The following example shows how to delete an optical line amplifier in shelf one,
slot one:
DLT-EQPT:NETSTENDER:OLA-1-2:100::BP1A03AA:CMDMDE=NORM;
Response

NETSTENDER 02-11-22 08:29:21
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-22 08:29:21
A
19 REPT DBCHG
DBCHGSEQ=8:DLT-EQPT:OLA-1-2"
;
7-35
7.7 Optical amplifier provisioning

In addition to providing basic signal amplification, the optical amplifiers support
the following features:
Configurable information fields (see Information fields on page 7-41)
Configurable settings (see Operation parameters on page 7-42)
Constant gain or constant power modes
Adjustable tilt compensation
Assignable alarm thresholds (see Alarm thresholds on page 7-43)

Preset shutdown and safety thresholds (see Shutdown thresholds (not
adjustable) on page 7-60)
7.7.1 Provisioning an optical amplifier

Purpose
Use this procedure to provision an optical amplifier in the Netstender shelf.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
Based on the calculations and choices made during the design of the optical link,
the following criteria should be determined already:
type of amplifier to provision
physical slot in the Netstender that the amplifier is to be inserted
To provision the optical amplifier circuit pack, some additional information is
required. Table 7-4 lists the amplifier type, access identifier (AID) and product
equipment code (PEC) that are associated with the various amplifiers.
Table 7-4
Required optical amplifier circuit pack information
Amplifier Type
AID1
PEC
DWDM C-Band Optical Pre-Amplifier

DWDM C-Band Optical Booster Amplifier
DWDM Optical Line Amplifier
DWDM Optical Line Amplifier with 0-15 dB
Mid-stage Access
Single-channel/Sub-band Pre-Amplifier
Single-channel/Sub-band Booster Amplifier
OPA-(1,11,21,31)-{slot#}
OBA-(1,11,21,31)-{slot#}
OLA-(1,11,21,31)-{slot#}
OLAM-(1,11,21,31)-{slot#}
BP1A01DA
BP1A02DA
BP1A03AA
BP1A04BA
SPA-(1,11,21,31)-{slot#}
SBA-(1,11,21,31)-{slot#}
BP1A05PB
BP1A05BB
1. Note that the following restrictions apply:

- Slot 5 in the Netstender 2060 main shelf is always reserved for the multiport system control
processor (MSCP) and it is not available for provisioning an optical amplifier circuit pack.
- Slot 3 in the Netstender 1030 shelf is always reserved for the system control processor (SCP)
and it is not available for provisioning an optical amplifier circuit pack.
7-37
Procedure
Important
Use the following procedure to provision an optical amplifier.

The activity explained in this procedure must be coordinated with the activity in
4.1, Installing optical amplifier circuit packs in this document.
Provisioning an optical amplifier
Step
Action
Provision the optical amplifier circuit pack

Based on the information obtained from Table 7-4, the optical amplifier circuit pack is
provisioned by entering the ENT-EQPT command at the TL1 command line interface:
ENT-EQPT:[TID]:<aid>:<CTAG>::<type>:,,,,,:,;
where
TID
aid
CTAG
type
is the target identifier

is one of the following access identifiers:
OBA-(1,11,21,31)-(1-6)
OLA-(1,11,21,31)-(1-6)
OLAM-(1,11,21,31)-(1-6)
OPA-(1,11,21,31)-(1-6)
SBA-(1,11,21,31)-(1-6)
SPA-(1,11,21,31)-(1-6)
is the correlation tag
is one of the following product equipment codes:
BP1A01DA
BP1A02DA
BP1A03AA
BP1A04BA
BP1A05BB
BP1A05PB
Note: The optical amplifiers can be provisioned with their connector suffix
(such as, -FC, -SC or -ST) as part of the TYPE parameter. If the connector suffix is
used, the Netstender will check to see if the provisioned connector type matches the
inserted circuit pack connector type. If there is a mismatch, the Connector Mismatch
(CONNMEA) alarm is raised.
Provisioning an optical amplifier (Continued)

Step
Action
1
contd
Example input
ENT-EQPT:NETSTENDER:OPA-1-2:100::BP1A01AA;
Example response
NETSTENDER 02-11-05 15:00:03

M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-05 15:00:04
A
205 REPT DBCHG
USERID=admin,DBCHGSEQ=36:ENT-EQPT:OPA-1-2::BP1A01AA::"
;
2
Provision the optical amplifier

Definable parameters for an optical amplifier are provisioned by entering the ENT-OA
command with the following syntax at the TL1 command line interface:
ENT-OA:[TID]:<aid>:<CTAG>:::[ID1=<id1>][,ID2=<id2>]
[,FIBER=<fiber>][,GRID=<grid>][,CHNLS=<chnls>][,C1=<custom1>]
[,C2=<custom2>][,C3=<custom3>][,OAMDE=<oamde>][,GAIN=<gain>]
[,PWR=<pwr>][,CONFIG=<config>][,CHANNEL=<channel>]
[,TLTCOM=<tltcom>] [,CTEMP-HT=<ctempht>][,OPR-LT=<oprlt>]
[,OPR-HT=<oprht>][,OPR-B-HT=<oprbht>][,OPR-R-HT=<oprrht>]
[,OPT-LT=<optlt>][,OPT-B-LT=<optblt>][,OPT-R-LT=<optrlt>]
[,OPT-HT=<optht>][,OPT-B-HT=<optbht>][,OPT-R-HT=<optrht>]
[,SSIOPR-HT=<ssioprht>][,MSLOSS-HT=<mslossht>]
[,AINSTMR=<ainstmr>][:[<pst>][,<sst>]];
where
TID
aid
CTAG

OBA-(1,11,21,31)-(1-6)-1
OLA-(1,11,21,31)-(1-6)-1
OLAM-(1,11,21,31)-(1-6)-1
OPA-(1,11,21,31)-(1-6)-1
SBA-(1,11,21,31)-(1-6)-1
SPA-(1,11,21,31)-(1-6)-1
* The remaining parameters are characterized as belonging to one of the following three
categories:
- Information fields on page 7-41
- Operation parameters on page 7-42
- Alarm thresholds on page 7-43
Note: Refer to the details of each parameter category on the following pages to
understand what range of values is supported for each parameter.
7-39
Provisioning an optical amplifier (Continued)

Step
Action
2
contd
Example input
ENT-OA:NETSTENDER:OPA-1-2-1:100:::;
Example response
NETSTENDER 02-11-05 15:21:01

M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-05 15:21:03
A
206 REPT DBCHG
USERID=admin,DBCHGSEQ=37:ENT-OA:OPA-1-2-1::AINSTMR=00-00:"
;
Note
The example in Step 2 of this procedure is the minimum amount of information

required to provision an optical amplifier and use the default values that are preset.
If additional parameters are specified at the time of initial provisioning, the
additional parameters are included as part of the system response message.
Information fields
Informational fields are those parameters that can be set to track specific
information about the equipment, fibers or connections. Table 7-5 lists the optional
information fields and some of their potential uses.
Although the information fields are optional, they are useful for recording details
about the deployment of the optical amplifier.
Table 7-5
Information fields
Parameter
Range of Values
Description
ID1
ID2
FIBER
1 to 32 alphanumeric characters
DSF
NDSF
NZDSF
Identifier 1 can contain descriptive text.

Fiber type that connects to the optical
amplifier.
GRID
50, 100, or 200 GHz
ITU-T wavelength grid number for DWDM

amplifiers only.
CHNLS
0 to 40
Number of DWDM channels that are

carried by the optical amplifier.
C1
C2
C3
Custom field that is available to users to

provide specific operating company
information.
information.
information.
7-41
Operation parameters
Operation parameters are those parameters that can be set to determine the
behavior of the amplifier. Table 7-6 lists the operation parameters.
Table 7-6
Parameter
Range of Values
Description
OAMDE
COGAIN
COPWR
GAIN
BP1A01DA is 27.0
BP1A02DA is 10.0
BP1A03AA is 16.0 to 26.0
BP1A04BA is 19.0 to 29.0
BP1A05BB is 18.0
BP1A05PB is 27.0
Constant Gain or Constant Power mode

The optical amplifier operates in either the
constant gain or the constant power mode. Select
one mode for the amplifier.
Sets the gain when OAMDE is COGAIN.
If the COPWR mode is selected, the GAIN field is
ignored.
PWR
BP1A01DA is -8 to 10
BP1A03AA is -7 to 16
BP1A04BA is -5 to 18
BP1A05BB is 3 to 18
BP1A05PB is -8 to 5
Sets the output power when the OAMDE is

COPWR.
If the COGAIN mode is selected, the PWR field is
ignored.
config
BLUE
BOTH
RED
CHANNEL
is the selected channel

wavelength.
TLTCOM
BP1A03AA is -3.0 to 3.0

BP1A04BA is -3.0 to 3.0
is the configuration parameter that enables or

disables CWDM Line Amplifier Wideband (CLAW)
alarms. The possible values mean the following:
BLUE (disables red band alarms)
BOTH (enables both red and blue band alarms)
RED (disables blue band alarms)
1530.33 to 1561.42
Note: This parameter is only applicable to the
Single-channel/Sub-band Booster (SBA) and the
Single-channel/Sub-band Pre-Amplifier (SPA).
Tilt Compensation: The OLA and OLAM can
compensate for the gain tilt resulting from
wavelength dependent loss and line nonlinearities. Refer to the Netstender 2060 Product
Description for further information about gain tilt.
Alarm thresholds
Alarm thresholds are those parameters that can be set to raise system-level alarms.
A major alarm is raised against an amplifier when one or more of these thresholds
are crossed. Table 7-7 lists the alarm thresholds.
Table 7-7
Alarm thresholds
Parameter
Case
Temperature
High Threshold
Optical Power
ReceivedLow
and High
Thresholds
Abbrev.
CTEMP-HT
OPR-LT
OPR-HT
Description
Range of Values
Default Value
is the case
temperature
high threshold.
is the optical
power received
low threshold.
45o
60oC
is the optical
power received
high threshold.
C to 75 C
BP1A01DA is -38 to -10

BP1A03AA is -31 to -5
BP1A04BA is -31 to -5
BP1A05BB is -18 to 9
BP1A05PB is -38 to -10
BP1A01DA is -36
BP1A02DA is -16
BP1A03AA is -29
BP1A04BA is -29
BP1A05BB is -16
BP1A05PB is -36
BP1A01DA is 0
BP1A02DA is 11
BP1A03AA is -4
BP1A04BA is -4
BP1A05BB is 10
BP1A05PB is -9
7-43
Table 7-7
Alarm thresholds
Parameter
Abbrev.
Description
Range of Values
Default Value
Optical Power
Transmitted
Low and High
Thresholds
OPT-LT
is the optical
power
transmitted low
threshold.
BP1A05BB is 0 to 18
BP1A05PB is -11 to 7
BP1A01DA is -9
BP1A02DA is -6
BP1A03AA is -8
BP1A04BA is -6
BP1A05BB is 2
BP1A05PB is -9
OPT-HT
is the optical
power
transmitted high
threshold.
BP1A05BB is 3 to19
BP1A05PB is -8 to 8
BP1A01DA is 11
BP1A02DA is 21
BP1A03AA is 17
BP1A04BA is 19
BP1A05BB is 19
BP1A05PB is 8
MSLOSS-HT
is the mid-stage
loss high
threshold.
is the second
stage input
optical power
received high
threshold.
BP1A04BA is 5 to 15
BP1A04BA is 15
BP1A04BA is 5.5
OLAM-Specific
High Thresholds
SSIOPR-HT
7.7.2 Modifying the definable parameters of an optical amplifier

Purpose
Use this procedure to modify the definable parameters of an optical amplifier.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
Ensure that the optical amplifier is provisioned before starting this procedure.
Procedure
Modifying the definable parameters of an optical amplifier
Step
Action
Modify the definable parameters of an optical amplifier

Definable parameters for an optical amplifier are modified by entering the ED-OA
ED-OA:[TID]:<aid>:<CTAG>:::[[ID1=<id1>][,ID2=<id2>]
[,C2=<custom2>][,C3=<custom3>][,OAMDE=<oamde>][,GAIN=<gain>]
[,PWR=<pwr>][,CONFIG=<config>][,CHANNEL=<channel>],
[,TLTCOM=<tltcom>][,CTEMP-HT=<ctempht>][,OPR-LT=<oprlt>]
[,OPR-HT=<oprht>][,OPR-B-HT=<oprbht>][,OPR-R-HT=<oprrht>]
[,OPT-LT=<optlt>][,OPT-B-LT=<optblt>][,OPT-R-LT=<optrlt>]
[,OPT-HT=<optht>][,OPT-B-HT=<optbht>][,OPT-R-HT=<optrht>}]
[,SSIOPRHT=<ssioprht>][,MSLOSSHT=<mslossht>]
[,AINSTMR=<ainstmr>][,CMDMDE=<cmdmde>]][:[<pst>][,<sst>]];
where
TID
aid
CTAG

OBA-(1,11,21,31)-(1-6)-1
OLA-(1,11,21,31)-(1-6)-1
OLAM-(1,11,21,31)-(1-6)-1
OPA-(1,11,21,31)-(1-6)-1
SBA-(1,11,21,31)-(1-6)-1
SPA-(1,11,21,31)-(1-6)-1
7-45
Modifying the definable parameters of an optical amplifier

Step
Action
* The remaining parameters are characterized as belonging to one of the following three
categories:
- Information fields on page 7-41
- Operation parameters on page 7-42
- Alarm thresholds on page 7-43
Note: Refer to the details of each parameter category on the preceding pages to
understand what range of values is supported for each parameter.
Important: Traffic-affecting parameters, such as OAMDE, GAIN, and PWR, must be
either taken out of service first or forced to take effect.
Example input
ED-OA:NETSTENDER:OPA-1-2-1:100:::OAMDE=COGAIN,CMDMDE=FRCD:,;
Example response
NETSTENDER 02-11-05 15:21:01

M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-05 15:21:03
A
206 REPT DBCHG
USERID=admin,DBCHGSEQ=37:ED-OA:OPA-1-2-1::OAMDE=COGAIN,
CMDMDE=FRCD:"
;
7.7.3 Removing an optical amplifier from service

Purpose
Use this procedure to remove an optical amplifier from service.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
Procedure
Removing an optical amplifier from service
Step
Action
Remove an optical amplifier from service

Note: Removing an amplifier from service turns the lasers off and will result in the loss
of traffic.
To remove an optical amplifier from service, enter the RMV-OA command with the
RMV-OA:[TID]:<aid>:<CTAG>;
where
TID
aid
CTAG

OBA-(1,11,21,31)-(1-6)-1
OLA-(1,11,21,31)-(1-6)-1
OLAM-(1,11,21,31)-(1-6)-1
OPA-(1,11,21,31)-(1-6)-1
SBA-(1,11,21,31)-(1-6)-1
SPA-(1,11,21,31)-(1-6)-1
7-47
Removing an optical amplifier from service (Continued)

Step
Action
Example input
RMV-OA:NETSTENDER:OLA-1-1-1:100;
Example response
NETSTENDER 02-11-22 09:09:21

M
100 COMPLD
;
NETSTENDER 02-11-22 09:09:21
A
36 REPT RMV OA
"OLA-1-1-1:OOS-MA,MT"
;
NETSTENDER 02-11-22 09:09:21
A
37 REPT DBCHG
USERID=admin,DBCHGSEQ=19:RMV-OA:OLA-1-1-1:OOS,"
;
2
Remove the optical amplifier circuit pack from service

To remove an optical amplifier circuit pack from service, enter the RMV-EQPT
where
TID
aid
CTAG
mode
pst

OBA-(1,11,21,31)-(1-6)
OLA-(1,11,21,31)-(1-6)
OLAM-(1,11,21,31)-(1-6)
OPA-(1,11,21,31)-(1-6)
SBA-(1,11,21,31)-(1-6)
SPA-(1,11,21,31)-(1-6)
is one of the following command modes:
NORM
FRCD
is one of the following primary states:
IS
OOS
Removing an optical amplifier from service (Continued)

Step
Action
Example input
Example response
NETSTENDER 02-11-22 10:06:40

M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-22 10-:06:40
A
12 REPT RMV EQPT

OLA-1-1:OOS-MA,MT
;
NETSTENDER 02-11-22 10:06:40
A
14 REPT DBCHG
TIME=10-06-40,DATE=02-11-22,SOURCE=100,LINKID=223,
USERID=admin,DBCHGSEQ=4:RMV-EQPT:OLA-1-1:OOS,
7-49
7.7.4 Restoring an optical amplifier to service

Purpose
Use this procedure to restore an optical amplifier to service. When an amplifier

returns to service, its pump lasers are turned on.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
Ensure that the optical amplifier is removed from service before starting this
procedure.
Procedure
Restoring an optical amplifier to service
Step
Action
Restore an optical amplifier circuit pack to service

Note: This step restores an optical amplifier circuit back to an in-service state (IS) from
an out-of-service maintenance (OOS-MA) state.
To restore an optical amplifier circuit pack, enter the RST-EQPT command with the
RST-EQPT:[TID]:<aid>:<CTAG>;
where
TID
aid
CTAG

OBA-(1,11,21,31)-(1-6)
OLA-(1,11,21,31)-(1-6)
OLAM-(1,11,21,31)-(1-6)
OPA-(1,11,21,31)-(1-6)
SBA-(1,11,21,31)-(1-6)
SPA-(1,11,21,31)-(1-6)

Step
Action
Example input
RST-EQPT:NETSTENDER:OLA-1-1:100;
Example response
NETSTENDER 02-11-22 08:13:06

M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-22 08:13:06
A
15 REPT RST EQPT

"OLA-1-1:IS-NR,"
;
NETSTENDER 02-11-22 08:13:06
A
17 REPT DBCHG
USERID=admin,DBCHGSEQ=6:RST-EQPT:OLA-1-1"
;
2
Restore an optical amplifier to service

Note: Restoring an optical amplifier to service turns the pump lasers on.
To restore an optical amplifier to service, enter the RST-OA command with the following
RST-OA:[TID]:<aid>:<CTAG>;
where
TID
aid
CTAG

OBA-(1,11,21,31)-(1-6)-1
OLA-(1,11,21,31)-(1-6)-1
OLAM-(1,11,21,31)-(1-6)-1
OPA-(1,11,21,31)-(1-6)-1
SBA-(1,11,21,31)-(1-6)-1
SPA-(1,11,21,31)-(1-6)-1
7-51

Step
Action
Example input
RST-OA:NETSTENDER:OLA-1-1-1:100;
Example response
NETSTENDER 02-11-22 09:17:55

M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-22 09:17:55
A
39 REPT RST OA
"OLA-1-1-1:IS-NR,"
;
NETSTENDER 02-11-22 09:17:55
A
40 REPT DBCHG
USERID=admin,DBCHGSEQ=21:RST-OA:OLA-1-1-1"
;
7.7.4.1 Using the OPR-OBR-HTSO command
Note
The OPR-OBR-HTSO command is used to troubleshoot and resolve Optical Back

Reflection - High Threshold alarms. This command operates an override timer that
activates the lasers of the amplifier for 20 to 600 seconds in duration.
The only amplifiers that are affected are the Optical Line Amplifier (OLA),
Optical Line Amplifier with Mid-stage access (OLAM), Optical Booster Amplifier
(OBA) and the Single-channel/Sub-band Booster Amplifier (SBA).
To use the OPR-OBR-HTSO command, enter the following at the TL1 command
line interface:
OPR-OBR-HTSO:[TID]:<aid>:<CTAG>:::[TIME=<time>];
Example
OPR-OBR-HTSO:NETSTENDER:OBA-1-2-1:100:::TIME=30;
Response
NETSTENDER 04-07-12 13:16:33
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 04-07-12 13:16:34
*
1232 REPT ALM OA
"OBA-1-2-1:MN,OBR-HTSO,NSA,07-12,13-16-33,,,,,:\"Optical back
reflection safety override.\",,,:,"
;
Note
For information on clearing an OBR-HTS alarm, see the Alarm and

7-53
7.7.5 Retrieving optical amplifier settings and status

Purpose
Use this procedure to retrieve optical amplifier settings, parameters and status.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
Procedure
Retrieving optical amplifier settings and status
Step
Action
Retrieve an optical amplifiers settings and status

The settings and status of an optical amplifier are retrieved by entering the RTRV-OA
RTRV-OA:[TID]:[<aid>]:<CTAG>;
where
TID
aid
CTAG

ALL
OBA-(1,11,21,31)-(1-6)-1
OLA-(1,11,21,31)-(1-6)-1
OLAM-(1,11,21,31)-(1-6)-1
OPA-(1,11,21,31)-(1-6)-1
SBA-(1,11,21,31)-(1-6)-1
SPA-(1,11,21,31)-(1-6)-1
Retrieving optical amplifier settings and status

Step
Action
Example input
RTRV-OA:NETSTENDER:ALL:100::;
Example response
NETSTENDER 03-01-29 09:19:17

M
100 COMPLD
"OLAM-1-2-1:LASERSTATUS=ON,OAMDE=COGAIN,GAIN=22.0,PWR=-5.0,
TLTCOM=0.0,CTEMP-HT=60,CTEMP-HTS=75,LTEMP-LTS=16,LTEMPHTS=34,
PL1CURCAL=310.8,PL2CURCAL=303.0,OPR-LT=-29.0,OPR-HT=-4.0,
SSIOPR-HT=17.0,OPT-LT=-6.0,OPT-HT=19.0,OBR-HTS=-4.0,
MSLOSS-HT=10.0,OASTATUS=COGAIN,AINSTMR=00-00:IS-NR,"
;
Explanation of response
The RTRV-OA command returns information fields, operation parameters, alarm

thresholds, shutdown thresholds, laser calibration data, and the optical amplifier
status and state.
7-55
Information fields
Informational fields are those parameters that can be set to track specific
information about the equipment, fibers or connections. Table 7-8 lists the
information fields.
Table 7-8
Information fields
Parameter
Range of Values
Description
ID1
ID2
FIBER
DSF
NDSF
NZDSF

amplifier.
GRID
50, 100, or 200 GHz
ITU-T wavelength grid numbers for DWDM

amplifiers only.
CHNLS
0 to 40

carried by the DWDM optical amplifiers.
C1, C2, C3
Custom fields that are available to users to

information.
Operation parameters are those parameters that can be set to determine the
behavior of the amplifier. Table 7-9 lists the operation parameters.
Table 7-9
Parameter
Range of Values
Description
LASERSTATUS
ON or OFF
OAMDE
COGAIN
COPWR
Lasers are on if the amplifier is in service (IS).

Lasers are off if the amplifier is out of service
(OOS).
Note: LASERSTATUS is a read only parameter.
Constant Gain or Constant Power mode
GAIN
BP1A01DA is 27.0
BP1A02DA is 10.0
BP1A03AA is 16.0 to 26.0
BP1A04BA is 19.0 to 29.0
BP1A05BB is 18.0
BP1A05PB is 27.0
Adjusts the gain when OAMDE is COGAIN.
PWR
BP1A05BB is 3 to 18
BP1A05PB is -8 to 5
Adjusts the output power when the OAMDE is

COPWR.
CHANNEL
is the selected channel

wavelength.
TLTCOM
BP1A03AA is -3.0 to 3.0

BP1A04BA is -3.0 to 3.0
1530.33 to 1561.42
Note: This parameter is only applicable to the
Single-channel/Sub-band Booster Amplifier
(SBA) and the Single-channel/Sub-band PreAmplifier (SPA).
Tilt Compensation: The OLA and OLAM can
compensate for the gain tilt resulting from
wavelength dependent loss and line nonlinearities. Refer to the Product Description for
further information about gain tilt.
7-57
Alarm thresholds
Alarm thresholds are those parameters that can be set to raise system-level alarms.
A major alarm is raised against an amplifier when one or more of these thresholds
are crossed. Table 7-10 lists the alarm thresholds.
Table 7-10 Alarm thresholds
Parameter
Case
Temperature
High Threshold
Optical Power
ReceivedLow
and High
Thresholds
Abbrev.
CTEMP-HT
OPR-LT
OPR-HT
Description
Range of Values
Default Value
is the case
temperature
high threshold.
is the optical
power received
low threshold.
45o
60oC
BP1A01DA is -38 to -10

BP1A01DA is -36
BP1A02DA is -16
BP1A03AA is -29
BP1A04BA is -29
BP1A05BB is -16
BP1A05PB is -36
is the optical
power received
high threshold.
BP1A01DA is 0
BP1A02DA is 11
BP1A03AA is -4
BP1A04BA is -4
BP1A05BB is 10
BP1A05PB is -9
C to 75 C
Table 7-10 Alarm thresholds (Continued)
Parameter
Abbrev.
Description
Range of Values
Default Value
Optical Power
Transmitted
Low and High
Thresholds
OPT-LT
is the optical
power
transmitted low
threshold.
BP1A05BB is 0 to 18
BP1A05PB is -11 to 7
BP1A01DA is -9
BP1A02DA is -6
BP1A03AA is -8
BP1A04BA is -6
BP1A05BB is 2
BP1A05PB is -9
OPT-HT
is the optical
power
transmitted
high threshold.
BP1A05BB is 3 to19
BP1A05PB is -8 to 8
BP1A01DA is 11
BP1A02DA is 21
BP1A03AA is 17
BP1A04BA is 19
BP1A05BB is 19
BP1A05PB is 8
MSLOSS-HT
is the midstage loss high

threshold.
is the second
stage input
optical power
received high
threshold.
BP1A04BA is 5 to 15
BP1A04BA is 15
BP1A04BA is 5.5
OLAM-Specific
High
Thresholds
SSIOPR-HT
7-59
Shutdown thresholds (not adjustable)
A critical alarm is raised against an amplifier when one or more of the shutdown
thresholds are crossed. The lasers are automatically turned off when a shutdown
threshold is crossed. Refer to the Alarm and Troubleshooting Guide for further
details. Table 7-11 lists the shutdown thresholds.
Table 7-11 Shutdown thresholds
Parameter
Abbreviation
Preset
Value
Case
Temperature
Laser
Temperature
CTEMP-HTS
75oC
LTEMP-LTS
LTEMP-HTS
16oC
34oC
Description
Internal temperature limit for the amplifier circuit
pack.
Normal operating temperature is 25oC.
Back reflection/eyesafe thresholds (not adjustable)
A critical alarm is raised against an amplifier when the optical back reflection
safety threshold is crossed. Output power is automatically reduced to 0 dBm when
the back reflection threshold is crossed. Refer to the Alarm and Troubleshooting
Guide for further details. Table 7-12 lists the shutdown thresholds.
Table 7-12 Back reflection/eyesafe threshold
Parameter
Optical Back
Reflection1
Abbreviation
Preset
Value
Description
OBR-HTS
-4 dBm
4% of 10 dBm
1. For next generation amplifiers BP1A02DA and BP1A05BB, the OBR-HTS threshold is
dynamically determined relative to the current output power of the amplifier.
Note
The optical back reflection threshold is not applicable to the Optical Pre-Amplifier
(OPA) or the Single-channel/Sub-band Pre-Amplifier (SPA).
Laser calibration data
The laser calibration data is used with the L1CUR and L2CUR performance
monitoring parameters to provide a normalized laser bias current (LBCnormal)
value. The LBCnormal value provides a measurement of the health of each laser.
Table 7-13 lists the laser calibration data.
Table 7-13 Laser calibration data
Parameter
Abbreviation
Description
Laser 1 current
calibration
Laser 2 current
calibration
L1CURCAL
Indication of the current calibration that was set for

laser one at the time of manufacture.
Indication of the current calibration that was set for
laser two at the time of manufacture.
L2CURCAL
To calculate the LBCnormal value, use the following formula:

LBCnormal = LXCUR / LXCURCAL x 100
where
LXCUR
LXCURCAL
is the actual laser current performance measurement

for either laser one or laser two.
is the maximum laser current that was set at the
time of manufacture.
7-61
Optical amplifier status and state
The optical amplifier status and state can differ from the provisioned value (that is,
OAMDE) if there is a fault on the amplifier. Table 7-14 lists the optical amplifier
status values and states.
Table 7-14 Optical amplifier status and state
Parameter
Values
Description
OASTATUS
COGAIN
COPWR
EYESAFE
Constant Gain mode

Constant Power mode
Output power is reduced due to back reflection
detected on output port.
Shutdown is due to CTEMP, LTEMP, or back
reflection.
Amplifier circuit pack is not present in the slot
(pre-provisioning condition).
In service, normal
In service, abnormal
Out of service, autonomous
Out of service, management
Out of service, management and abnormal
Out of service, autonomous and management
Automatic in service (controllable)
Communication error
Fault
Mismatch of equipment and attributes
Maintenance
Loss of shelf power
Supporting entity outage
Standby
Software download
Unequipped
SHUTDOWN
NONE
PST-PSTQ
SST
IS-NR
IS-ANR
OOS-AU
OOS-MA
OOS-MAANR
OOS-AUMA
AINS
COMM
FLT
MEA
MT
PWR
SGEO
STDBY
SWDL
UEQ
7.7.6 Deleting an optical amplifier

Purpose
Use this procedure to delete an optical amplifier from a Netstender shelf.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
Procedure
Deleting an optical amplifier
Step
Action
Delete an optical amplifier

Note: To delete equipment, the equipment must be taken out of service first or the
FRCD parameter must be used.
To delete an optical amplifier, enter the DLT-OA command with the following syntax at
DLT-OA:[TID]:<aid>:<CTAG>[:[:[:[CMDMDE=<cmdmde>]]]];
where
TID
aid

OBA-(1,11,21,31)-(1-6)-1
OLA-(1,11,21,31)-(1-6)-1
OLAM-(1,11,21,31)-(1-6)-1
OPA-(1,11,21,31)-(1-6)-1
SBA-(1,11,21,31)-(1-6)-1
SPA-(1,11,21,31)-(1-6)-1
CTAG
cmdmde is either NORM or FRCD
7-63

Step
Action
Example input
DLT-OA:NETSTENDER:OLA-1-2-1:100;
Example response
M
;
NETSTENDER 02-11-22 08:16:30

100 COMPLD
NETSTENDER>
NETSTENDER 02-11-22 08:16:30
47 REPT DBCHG
"TIME=09-26-30,DATE=02-11-22,SOURCE=100,
LINKID=2-23,USERID=admin,DBCHGSEQ=25:DLT-OA:OLA-1-2-1"
;
A
Delete the provisioning information of an optical amplifier circuit pack

To delete the provisioning information of an optical amplifier circuit pack, enter the
DLT-EQPT command with the following syntax at the TL1 command line interface:
DLT-EQPT:[TID]:<aid>:<CTAG>::[<type>]:[CMDMDE=<cmdmde>];
where
TID
aid

OBA-(1,11,21,31)-(1-6)
OLA-(1,11,21,31)-(1-6)
OLAM-(1,11,21,31)-(1-6)
OPA-(1,11,21,31)-(1-6)
SBA-(1,11,21,31)-(1-6)
SPA-(1,11,21,31)-(1-6)
CTAG
type
is one of the following product equipment codes:
BP1A01DA
BP1A02DA
BP1A03AA
BP1A04BA
BP1A05BB
BP1A05PB
cmdmde is either NORM or FRCD

Step
Action
Example input
DLT-EQPT:NETSTENDER:OLA-1-2:100::BP1A03AA;
Example response
NETSTENDER 02-11-22 08:29:21

M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-22 08:29:21
A
19 REPT DBCHG
"TIME=08-29-21,DATE=02-11-22,SOURCE=100,LINKID=223,USERID=admin,DBCHGSEQ=8:DLT-EQPT:OLA-1-2"
;
7-65
7.8 OSC provisioning

Information about the provisioning of an Optical Supervisory Channel (OSC)
circuit pack is located in the OSC Operations, Administration, Maintenance and
Provisioning Guide.
Note
For details about how to initially install an OSC circuit pack and its OSC coupler/
splitter assembly, refer to the Installation and Commissioning Guide.
The OSC circuit pack and its OSC coupler/splitter assembly must be installed in
either slot two, four or six of the Netstender 2060 main shelf, or in slot two of the
Netstender 1030 shelf.
As of release 4.1, OSC fuctionality is integrated as part of the Multiport System
Control Processor (MSCP) circuit pack (BP1A20BA). To use the OSC
functionality on the MSCP, a 1310 nm Coupler/Splitter circuit pack (BP1A38AA)
is also required.
7.9 Wavelength conversion provisioning

The process of provisioning wavelength conversion circuit packs involves the
creation of up to four software entities:
Wavelength conversion circuit pack equipment
Transceiver port
Cross-connects
Protection groups
This section is structured as follows:
7.9.1, Provisioning wavelength conversion circuit pack equipment
7.9.2, Provisioning transceiver ports
7.9.3, Provisioning cross-connects on a Wavelength Conversion circuit pack
7.9.4, Provisioning protection groups on a Wavelength Conversion circuit
pack
7-67
7.9.1 Provisioning wavelength conversion circuit pack equipment

Purpose
Use this procedure to provision a wavelength conversion circuit pack (Wavelength

Translator and Wavelength Regenerator) in a Netstender shelf.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
None
Procedure
To provision a wavelength conversion circuit pack, enter the following syntax at
ENT-EQPT:[TID]:<aid>:CTAG[:[:<type>[:[[ID=<id>][,C1=<custom1>]
[,C2=<custom2>][,C3=<custom3>][,SHCONF=<shconf>]][:[<pst>][,<sst>]]]]];
where
<aid>
<type>
is in the form of
WM-(1,11,21,31)-(1-6) or
WR-(1,11,21,31)-(1-6) or
WT-(1,11,21,31)-(1-6)
is either BP1A41BA, BP1A42AA, BP1A42BA, BP1A43AA,
BP1A43BA, BP1A47AA, BP1A47AB, or BP1A47BB
Example
The following example shows how to enter a new wavelength translator circuit
pack in shelf one, slot two:
ENT-EQPT:NETSTENDER:WT-1-2:100::BP1A41BA;
Response

NETSTENDER 05-02-03 15:00:00
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 05-02-03 15:00:01
A
165 REPT DBCHG
DBCHGSEQ=36:ENT-EQPT:WT-1-2:BP1A41BA::"
;
Additional commands available
The following equipment and inventory commands are also available:

ED-EQPT
RMV-EQPT
RST-EQPT
RTRV-EQPT
RTRV-INV
DLT-EQPT
edits equipment entries.

removes equipment from service.
restores equipment to service.
retrieves equipment provisioning information.
retrieves system inventory information.
deletes equipment entries.
For further details about these commands, refer to the TL1 Reference Guide.
7-69
7.9.2 Provisioning transceiver ports

This subsection discusses the provisioning of transceiver ports and is structured as
follows:
7.9.2.1, Retrieving a manufacturers SFP/XFP transceiver inventory
information
7.9.2.2, Provisioning transceiver ports
7.9.2.3, Implementing advanced provisioning features
7.9.2.4, Modifying the definable parameters of a transceiver port
7.9.2.5, Removing a transceiver port from service
7.9.2.6, Restoring a transceiver to service
7.9.2.7, Retrieving transceiver attributes
7.9.2.8, Deleting a transceiver
7.9.2.1 Retrieving a manufacturers SFP/XFP transceiver inventory information
Purpose
Use this procedure to retrieve a manufacturers SFP or XFP transceiver inventory

information.
Maintenance
Provisioning
Superuser
Surveillance
Prerequisites
An SFP or XFP transceiver must be inserted in a port of a wavelength conversion
circuit pack for the transceiver inventory information to be read by the system. The
SFP or XFP does not need to be provisioned for the transceiver inventory
information to be read.
Procedure
To retrieve the manufacturers SFP or XFP transceiver inventory information,
enter the following syntax at the TL1 command line interface:
where
<aid>
is in the form of SFP-(1,11,21,31)-(1-6)-(1-4) or

XFP-(1,11,21,31)-(1-6)-(2)
Example input
The following example shows how to retrieve the system inventory information:
Example response
The Netstender returns a COMPLD message that lists all of the circuit packs, SFP
or transceivers, and common equipment present in the system:
NETSTENDER 05-04-06 15:46:20
M
100 COMPLD
"SH-1,EQPT:NAME=1030,PEC=BP1A5625,CLEI=WMMPA10FRA,FNAME=Netstender
1030 Shelf,HWREV=\"1\",SHCONF=3-SLOT,"
"SLOT-1-1,EQPT:NAME=WR,PEC=BP1A42BA,CLEI=none,FNAME=Wavelength
Regenerator 1.25G,SER=\"BTI00002556\",HWREV=\"0\",MFGDAT=\"2005-03-22\
",MFGLOCN=BTI Thurston,TSTDAT=2005-03-22,TSTLOCN=BTI Thurston,"
"SFP-1-1-1,EQPT:SER=\"6K2042308002\",HWREV=\"10\",MFGDAT=\"2004-06-04\
",WAVELENGTH=1570,REACH=80,NOMBR=2500,ENCODING=NRZ,CONNTYPE=LC,
7-71
VENDORNAME=\"FIBERXON INC.\",VENDORPN=\"FTM-6128C-L8057\",TXFAULTIMP=Y,
TXDISABLEIMP=Y,LOSIMP=Y,DDIAGIMP=Y,MEDIA=OPTICAL"
"SFP-1-1-2,EQPT:PEC=BP3AM1CL-03,SER=\"6386000007\",HWREV=\"C21\
",MFGDAT=\"2005-01-20\",WAVELENGTH=1571,REACH=80,MINBR=50,MAXBR=3000,
NOMBR=2500,ENCODING=SONET_SCRAMBLED,CONNTYPE=LC,VENDORNAME=\"JDS
UNIPHASE\",VENDORPN=\"CT2-ML2LBCW61C1\",TXFAULTIMP=Y,TXDISABLEIMP=Y,
LOSIMP=Y,DDIAGIMP=Y,MEDIA=OPTICAL"
UNIPHASE\",VENDORPN=\"CT2-ML2LBCW61C1\",TXFAULTIMP=Y,TXDISABLEIMP=Y,
UNIPHASE\",VENDORPN=\"CT2-ML2LBTD51C1\",TXFAULTIMP=Y,TXDISABLEIMP=Y,
"SLOT-1-3,EQPT:NAME=SCP,PEC=BP1A21AA,CLEI=WMUCAMSLAA,FNAME=System
"CU-1,EQPT:NAME=CU,PEC=BP1A57AA,CLEI=WMPQASP7AA,FNAME=Cooling
Unit,SER=\"12345\",HWREV=\"1\",MFGDAT=\"2004-10-28\",MFGLOCN=BTI
Thurston,TSTDAT=2004-10-28,TSTLOCN=BTI Thurston,"
;
As seen in the example response above, SLOT-1-1 is equipped with a BP1A42BA

wavelength regenerator (WR) circuit pack. Inserted in the WR are four SFP
transceivers in ports one through four.
Table 7-15 lists the parameters that can be part of the manufacturers SFP or XFP
transceiver.
Table 7-15 Manufacturers SFP and XFP transceiver parameters
Parameter
Range of Values
Description
AID
SFP-(1,11,21,31)-(1-6)(1-4)
XFP-(1,11,21,31)-(1-6)(2)
EQPT
AID is the access identifier for the transceiver in the

Netstender.
AIDTYPE
NAME
PEC
CLEI
SER
HWREV
WM
WR
WT
string
string
alphanumeric
characters
alphanumeric
characters
AIDTYPE is the equipment type that is targeted by

the message.
NAME is the abbreviated name of the circuit pack.
PEC is the product equipment code.

CLEI is the common language equipment identifier.
SER is the serial number of the transceiver.
HWREV is the hardware revision number of the
transceiver.
Table 7-15 Manufacturers SFP and XFP transceiver parameters (Continued)
Parameter
Range of Values
Description
MFGDAT
YYYY-MM-DD-xx
WAVELENGTH
numerical or
TUNABLE
REACH
integer
MINBR
integer
MAXBR
integer
NOMBR
integer
ENCODING
8B10B
4B5B
NRZ
MANCHESTER
SONET_SCRAMBLED
CONNTYPE
LC
VENDORNAME
alphanumeric
characters
Note: This parameter
consists of escaped
string values that are
surrounded by \ and \
characters.
MFGDAT is the manufacture date of the transceiver

and, if provided, the two-character lot number of the
manufacturer in ASCII.
Note: The lot number is not always provided by the
manufacturer. In which case, only the manufacture
date is provided.
WAVELENGTH is the wavelength of the transceiver
in nm. Some transceivers only specify their
wavelength to the nearest nm whereas others
specify wavelength to the nearest 0.01 nm.
Note: If a transceiver is inserted into a circuit pack
and the transceiver does not have a wavelength
value specified in its memory, the Netstender raises
a REPLUNITUNK alarm against the transceiver.
REACH is the maximum transmit distance of the
transceiver in km using nine micron SM fiber.
Note: If an SFP transceiver is inserted into a circuit
pack and the transceiver does not have a reach
a REPLUNITUNK alarm against the transceiver. This
applies to SFPs only.
MINBR is the minimum bit rate supported by the
transceiver.
MAXBR is the maximum bit rate supported by the
transceiver.
NOMBR is the nominal bit rate supported by the
transceiver.
pack and the transceiver does not have a nominal
baud rate value specified in its memory, the
Netstender raises a REPLUNITUNK alarm against
the transceiver. This applies to SFPs only.
ENCODING indicates the encoding scheme for the
transceiver.
Note: The Netstender does not use the encoding
parameter. It is the operating companys
responsibility to ensure that both end points of a
span use the same encoding.
CONNTYPE is one of the listed transceiver
connector types.
VENDORNAME is the transceiver vendor name.
7-73
Table 7-15 Manufacturers SFP and XFP transceiver parameters (Continued)
Parameter
Range of Values
Description
VENDORPN
alphanumeric
characters
consists of escaped
characters.
string
VENDORPN is the transceiver vendor part number.
VENDOROUI
TXFAULTIMP
Y
N
TXDISABLEIMP
Y
N
LOSIMP
Y
N
DDIAGIMP
Y
N
MEDIA
ELECTRICAL
OPTICAL
UNKNOWN
VENDOROUI is the vendor organizational unique

identifier.
Note: This parameter consists of escaped string
values that are surrounded by \ and \ characters.
TXFAULTIMP is the transceiver fault implemented
flag.
Note: BTI recommends only using transceivers that
have TXFAULTIMP=Y.
TXDISABLEIMP is the transceiver disable
implemented flag.
Note: This parameter indicates whether the
transmitter disable function is supported on that
transceiver. If TXDISABLEIMP=Y and FPSD=ON,
then the REPLUNITMEA alarm is enabled.
See section 7.9.2.3, Implementing advanced
provisioning features for additional details.
LOSIMP is the loss of signal implementation flag.
Note: This parameter indicates whether the loss of
signal (LOS) notification function is supported on that
transceiver. If LOSIMP=N, then the LOS alarm
cannot be raised.
BTI recommends only using transceivers that have
LOSIMP=Y.
DDIAGIMP is the digital diagnostic implementation
flag. When set to Y, this parameter enables the
recording of performance monitoring data in
historical bins.
Note: This parameter indicates whether the digital
diagnostics function is supported on that transceiver.
If not, then PMs and PHYPMMON are not available.
All PM historical bins for that transceiver are filled
with dummy values and marked as invalid.
BTI recommends only using transceivers with
DDIAGIMP=Y.
Media is the type of connector used by the
transceiver.
7.9.2.2 Provisioning transceiver ports
Purpose
Use this procedure to provision transceiver ports for a wavelength conversion

circuit pack.
Provisioning
Superuser
Maintenance
Surveillance
Prerequisites
None
Procedure
To provision transceivers for a wavelength translator, a wavelength regenerator, or
a wavelength manager, enter the following syntax at the TL1 command line
interface:
ENT-XCVR:[TID]:<aid>:<CTAG>:::[ID1=<id1>][,ID2=<id2>][,FIBER=<fiber>]
[,GRID=<grid>][,C1=<custom1>][,C2=<custom2>][,C3=<custom3>],
PROTOCOL=<protocol>[,WAVELENGTH=<wavelength>][,PHYPMMON=<phypmmon>]
[,FPSD=<fpsd>][,VENDORPN1=<vendorpn1>][,VENDORPN2=<vendorpn2>]
[,VENDORPN3=<vendorpn3>][,PEC=<pec>][,AINSTMR=<ainstmr>]:
[,<pst>][,<sst>];
where
<aid>
Note:
is in the form of
WM-(1,11,21,31)-(1-6)-(1-4)
WR-(1,11,21,31)-(1-6)-(1-4)
WT-(1,11,21,31)-(1-6)-(1-4)
or
or
The remaining parameters are discussed in Table 7-16, Transceiver port

parameters on page 7-76.
Example input
The following example shows how to enter a new SFP transceiver port for a
wavelength translator circuit pack in shelf one, slot two, port one:
ENT-XCVR:NETSTENDER:WT-1-2-1:100:::PROTOCOL=OC48,WAVELENGTH=1550:;
Example response
The Netstender returns a COMPLD message, a REPT RMV XCVR message, and
a DBCHG message:
NETSTENDER 05-02-03 07:30:00
M
100 COMPLD
7-75
;
NETSTENDER>
NETSTENDER 05-02-03 07:30:00
A
496 REPT RMV XCVR

"WR-1-1-1:OOS-AU,UEQ&SGEO"
;
NETSTENDER 05-02-03 07:39:50
A 497 REPT DBCHG
"TIME=07-39-50,DATE=05-02-03,SOURCE=100,LINKID=2-15,USERID=admin2,
DBCHGSEQ=273:ENT-XCVR:WR-1-1-1::PROTOCOL=OC48,WAVELENGTH=1550"
;
Transceiver parameters
Table 7-16 lists the transceiver parameters that can be provisioned by entering the
ENT-XCVR command. This command can also be used to provision the
wavelength of the line side port (MSA) on only a tunable 10G Wavelength
Regenerator circuit pack (BP1A47BB). See table Table 7-18 for a list of the 36
BTI-supported wavelengths that can be provisioned on this circuit pack.
Table 7-16 Transceiver port parameters
Parameter
Range of Values
Description
ID1
0 to 32 alphanumeric
characters
characters
DSF
NDSF
NZDSF
50, 100, 200 GHz or 20 nm
Identifier 1 can contain descriptive text. This is

an optional field.
Identifier 2 can contain descriptive text. This is
an optional field.
Fiber type that connects to the transceiver.
This is an optional field.
ID2
FIBER
GRID
C1, C2, C3
characters.
ITU-T wavelength grid numbers. This is an

optional field.
information. These are optional fields.
Table 7-16 Transceiver port parameters (Continued)
Parameter
Range of Values
Description
PROTOCOL
10GELAN
10GELANFEC
ESCON
FC100
FC200
FDDI
FE
GE
OC3
OC12
OC48
OC192FEC
OC192
SMPTE259
SMPTE292
SMPTE344
STM1
STM4
STM16
STM64
STM64FEC
Protocol is the protocol used by the

transceiver. This is a mandatory field.
Note: The protocol entered must fall within the
supported range of bit rates that are supported
by the transceiver.
For example, the bit rate of the OC-48 protocol
is 2.488 Gb/s. Therefore, the following formula
applies:
WAVELENGTH
floating-point decimal
PHYPMMON
OFF
ON
FPSD
OFF
ON
( MinBitRate ( 2.488Gbps MaxBitRate ) )

The minimum and maximum bit rates can be
retrieved by using procedure 7.9.2.1,
Retrieving a manufacturers SFP/XFP
transceiver inventory information.
Note: Protocols SMPTE259, SMPTE292 and
SMPTE344 are supported only on the
wavelength translator circuit pack.
Note: The wavelength manager supports only
GE, OC3, OC12, OC48 and STM16 in this
release.
Note: The 10G wavelength regenerator
supports only 10GELAN, 10GELANFEC,
OC192, OC192FEC, STM64, and
STM64FEC.
Note: See Table 7-17, Protocols supported
on 10G Wavelength Regenerator ports for
information on the protocols supported on the
client (XFP) and line (MSA) side ports of the
10G Wavelength Regenerator.
Wavelength is the wavelength used by the
transceiver. This is a mandatory field for SFP
and XFP transceivers on wavelength
conversion circuit packs, and for the line side
port (MSA) on a tunable 10G Wavelength
Regenerator (BP1A47BB).
Note: See Table 7-18 for a list of the 36 BTIsupported wavelengths that can be
provisioned on the line side port (MSA) of a
tunable 10G Wavelength Regenerator
(BP1A47BB).
PHYPMMON is the threshold crossing alarm
monitoring flag.
Note: This parameter can only be OFF for the
FPSD is the fault propagation shutdown
enabled flag.
Note: For more information about FPSD, see
7.9.2.3, Implementing advanced provisioning
features in this document.
Note: This parameter cannot be set to ON for
the 10G Wavelength Regenerator.
7-77
Parameter
Range of Values
Description
VENDORPN1
VENDORPN2
VENDORPN3
0 to 20 characters
PEC
11 characters
OPTLT
integer
OPTHT
integer
OPRLT
integer
OPRHT
integer
LASERSTATUS
IDLE
OFF
ON
AIS-L
ODU2-AIS
MS-AIS
AINSTMR
00-00 to 96-00
Vendor part numbers 1, 2 and 3 are for

entering the transceiver part number(s). If the
vendor part numbers are used, the PEC is
ignored.
Note: If the vendor part number(s) are
entered, the system compares the provisioned
values with the part number(s) of the
transceiver that is physically equipped in the
wavelength conversion circuit pack.
If a mismatch is detected by the system, an
REPLUNITMEA alarm is raised.
is the Product Equipment Code. If the PEC is
used, the vendor part numbers are ignored.
Note: If the PEC is entered, the system
compares the provisioned values with the PEC
of the transceiver that is physically equipped in
is the optical power transmitted low threshold.
Note: This parameter does not apply to the
is the optical power transmitted high threshold.
is the optical power received low threshold.
is the optical power received high threshold.
is the status of the transmitter laser.
Note: IDLE does not apply to the 10G
wavelength regenerator.
Note: AIS-L applies to wavelength manager
and 10G wavelength regenerator circuit packs
only. AIS-L applies to protocol OC192 and all
wavelength manager supported SONET
protocols.
Note: ODU2-AIS applies to protocols
10GELANFEC, OC192FEC, and STM64FEC
only.
Note: MS-AIS applies to protocols STM16 and
STM64 only.
is the automatic in-service timer in the format
HH-MM.
Parameter
Range of Values
Description
PST
IS
OOS
AINS
COMM
FLT
FRCD
LKDO
LPBK
MEA
MT
PWR
SGEO
STDBY
SWDL
UEQ
WRK
PST is the primary state of the transceiver.
SST
SST is the secondary state of the equipment.
Protocols supported on the 10G Wavelength Regenerator
The following table lists the protocols supported on 10G Wavelength Regenerator
ports.
Table 7-17 Protocols supported on 10G Wavelength Regenerator ports
Client side (XFP)
Line side (MSA)
Supported in this release
10GELAN
10GELAN
10GELANFEC
10GELANFEC
OC192
OC192
OC192FEC
OC192FEC
STM64
STM64
STM64FEC
STM64FEC
10GELAN
10GELANFEC
10GELANFEC
10GELAN
0C192
OC192FEC
0C192FEC
OC192
STM64
STM64FEC
STM64FEC
STM64
Yes
Yes
Yes
No
Yes
Yes
Yes
No
Yes
Yes
Yes
No
7-79
BTI-supported Wavelengths
Note
Table 7-18 lists the 36 BTI-supported wavelengths that can be provisioned on the
line side port (MSA) of a tunable 10G Wavelength Regenerator (BP1A47BB).
The Wavelength parameter cannot be provisioned on the MSA port of a
10G Wavelength Regenerator that is not equipped with a tunable MSA (as in
BP1A47AB).
Table 7-18 BTI-supported wavelengths for a tunable 10G Wavelength Regenerator
ITU-T 100GHZ
Channel
THz
Wavelength
BTI Channel
59
58
57
56
55
54
53
52
195.9
195.8
195.7
195.6
195.5
195.4
195.3
195.2
1530.33
1531.12
1531.90
1532.68
1533.47
1534.25
1535.04
1535.82
32
31
30
29
28
27
26
25
51
195.1
1536.61
59
49
48
47
46
45
44
43
42
194.9
194.8
194.7
194.6
194.5
194.4
194.3
194.2
1538.19
1538.98
1539.77
1540.56
1541.35
1542.14
1542.94
1543.73
24
23
22
21
20
19
18
17
41
194.1
1544.53
57
39
38
37
36
35
34
33
32
193.9
193.8
193.7
193.6
193.5
193.4
193.3
193.2
1546.12
1546.92
1547.72
1548.51
1549.32
1550.12
1550.92
1551.72
16
15
14
13
12
11
10
09
31
193.1
1552.52
55
Table 7-18 BTI-supported wavelengths for a tunable 10G Wavelength Regenerator
ITU-T 100GHZ
Channel
THz
Wavelength
BTI Channel
29
28
27
26
25
24
23
22
192.9
192.8
192.7
192.6
192.5
192.4
192.3
192.2
1554.13
1554.94
1555.75
1556.55
1557.36
1558.17
1558.98
1559.79
08
07
06
05
04
03
02
01
21
192.1
1560.61
53
7.9.2.3 Implementing advanced provisioning features

This section discusses the implementation of a few advanced provisioning features
for transceiver ports.
Enabling fault propagation shutdown
When a loss of light occurs on a pluggable receiver interface, the corresponding

transmitting laser at the far end of the link continues to function and can transmit
unreliable information.
Fault propagation shutdown (FPSD) provides a means to quickly shut down a
transmitting laser and pass the fault to the downstream device when a receiver
signal failure occurs. Loss of light can result from a failure in upstream optics or in
the client equipment, a laser shutdown on an upstream node in the network, or a
receiver failure in the module.
FPSD and laser status
The following rules apply to FPSD settings and laser status on the wavelength
conversion circuit packs:
In general, if FPSD is set to ON on a wavelength conversion circuit pack and when
it is not transmitting a valid signal, the laser is turned OFF.
If FPSD is set to ON on the Wavelength Manager, the laser transmits an IDLE
status.
If FPSD is set to ON on the 10G Wavelength Regenerator, the laser is OFF.
If FPSD is set to OFF on the Wavelength Manager for SONET protocols, the laser
transmits AIS-L (Alarm Indication Signal on the Line).
If FPSD is set to OFF on the Wavelength Translator, the laser transmits an IDLE
status.
7-81
If FPSD is set to OFF on all Wavelength Regenerators for SONET protocols, the
laser transmits AIS-L.
If FPSD is set to OFF on all Wavelength Regenerators for SDH protocols, the laser
transmits MS-AIS.
If FPSD is set to OFF on the 10G Wavelength Regenerator when the protocol is set
to 10GELANFEC, OC192FEC, or STM64FEC, the laser transmits ODU2-AIS.
Enabling threshold crossing alarms
The following four threshold crossing alarms are available to most transceiver
ports equipped with SFPs:
optical power transmitted low threshold (OPTLT)
optical power transmitted high threshold (OPTHT)
optical power received low threshold (OPRLT)
optical power received high threshold (OPRHT)
Note
The threshold crossing alarms only work on a transceiver if the digital diagnostics
implementation (DDIAGIMP) flag is set to Y in the inventory entry, and the
physical PM monitor (PHYPMMON) is set to ON for the provisioned transceiver
port.
The PHYPMMON parameter is not supported for the 10G Wavelength
Regenerator.
7.9.2.4 Modifying the definable parameters of a transceiver port
Purpose
Note
Use this procedure to modify the definable parameters of a transceiver port,

including the wavelength of the line side port (MSA) of a tunable 10G Wavelength
Regenerator circuit pack (BP1A47BB).
This procedure cannot be used to change the provisioned protocol of a
10G Wavelength Regenerator circuit pack. For information about how to change
the provisioned protocol for this circuit pack, refer to 5.5, Changing the
provisioned protocol of a 10G Wavelength Regenerator in the Alarm and
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
All cross-connects and protection groups associated with a transceiver port must
be deleted before the protocol or wavelength parameters can be modified.
The transceiver must then be removed from service to edit the protocol or
wavelength parameters, or the CMDMDE=FRCD parameter must be used.
Procedure
To modify the definable parameters of a transceiver port, enter the following
ED-XCVR:[TID]:<aid>:<CTAG>:::[ID1=<id1>][,ID2=<id2>][,FIBER=<fiber>]
[,GRID=<grid>][,C1=<custom1>][,C2=<custom2>][,C3=<custom3>]
[,PROTOCOL=<protocol>][,WAVELENGTH=<wavelength>][,PHYPMMON=<phypmmon>]
[,FPSD=<fpsd>][,VENDORPN1=<vendorpn1>][,VENDORPN2=<vendorpn2>]
[,VENDORPN3=<vendorpn3>][,PEC=<pec>][,AINSTMR=<ainstmr>]
[,CMDMDE=<cmdmde>][:[<pst>],[<sst>]];
where
aid

WM-(1,11,21,31)-(1-6)-(1-4) or
WR-(1,11,21,31)-(1-6)-(1-4) or
WT-(1,11,21,31)-(1-6)-(1-4)
protocol
is the protocol parameter that is one of the following:

10GELAN
10GELANFEC
AUTO
7-83
ESCON
FC100
FC200
FDDI
FE
GE
OC3
OC12
OC48
OC192
OC192FEC
SMPTE259
SMPTE292
SMPTE344
STM1
STM4
STM16
STM64
STM64FEC
Note: Protocols SMPTE259, SMPTE292 and SMPTE344 are

supported only on the wavelength translator circuit pack.
wavelength
is the channel wavelength in nm.
cmdmde
is the command mode that is one of the following:

NORM (default value)
FRCD
Note:
The remaining parameters are discussed in Table 7-16, Transceiver port

parameters on page 7-76.
Example input
ED-XCVR:NETSTENDER:WR-1-1-1:100:::WAVELENGTH=1530,CMDMDE=FRCD:;
Example response
NETSTENDER 05-02-03 07:40:50
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 05-02-03 07:40:51
A
498 REPT DBCHG
DBCHGSEQ=274:ED-XCVR:WR-1-1-1::WAVELENGTH=1530"
;
7.9.2.5 Removing a transceiver port from service
Purpose
Important
Use this procedure to remove a transceiver port from service.

Transceiver ports are removed from service to edit the protocol or wavelength
parameters.
Removing a transceiver port from service is traffic affecting. In addition, all SFP
and XFP related alarms are suppressed. Faults can still be queried by using the
RTRV-COND-ALL command.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
If a transceiver port belongs to a protection group, the working transceiver cannot
be taken out of service.
Procedure
To remove a transceiver from service, enter the following syntax at the TL1
RMV-XCVR:NETSTENDER:WR-1-1-1:;
where
aid

WM-(1,11,21,31)-(1-6)-(1-4) or
WR-(1,11,21,31)-(1-6)-(1-4) or
WT-(1,11,21,31)-(1-6)-(1-4)
Example input
RMV-XCVR:NETSTENDER:WR-1-6-1:100::;
Example response
NETSTENDER 06-05-03 13:49:18
M
100 COMPLD
;
NETSTENDER 06-05-03 13:49:18
A
52 REPT ALM XCVR
"WR-1-6-1:CL,LOS,SA,05-03,13-46-40,,,,,:\"Clear Loss Of Signal.\

",,,:,"
7-85
;
NETSTENDER 06-05-03 13:49:18
A
53 REPT ALM XCVR
"WR-1-6-1:CL,T-OPR-LT,NSA,05-03,13-46-57,,,,,:\"Clear optical power

received min threshold exceeded.\",,,:,"
;
NETSTENDER 06-05-03 13:49:19
A
54 REPT DBCHG
"TIME=13-49-19,DATE=06-05-03,SOURCE=0000,DBCHGSEQ=14:ED-XCVR:
WR-1-6-1:::OOS-AUMA,MT&FLT"
;
NETSTENDER 06-05-03 13:49:19
A
55 REPT DBCHG
"TIME=13-49-19,DATE=06-05-03,SOURCE=100,LINKID=2-19,USERID=kriss1,
DBCHGSEQ=15:RMV-XCVR:WR-1-6-1"
;
7.9.2.6 Restoring a transceiver to service
Purpose
Important
Use this procedure to restore a transceiver to service.

Restoring a transceiver to service enables traffic and related alarms.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
None
Procedure
To restore a transceiver to service, enter the following syntax at the TL1 command
line interface:
RST-XCVR:[TID]:<aid>:<CTAG>;
where
aid

WM-(1,11,21,31)-(1-6)-(1-4) or
WR-(1,11,21,31)-(1-6)-(1-4) or
WT-(1,11,21,31)-(1-6)-(1-4)
Example input
RST-XCVR:NETSTENDER:WR-1-1-1:100;
Example response
NETSTENDER 05-02-03 07:48:10
100 COMPLD
M
;
NETSTENDER>
NETSTENDER 05-02-03 07:48:11
A 505 REPT DBCHG
"TIME=07-48-11,DATE=05-02-03,SOURCE=0000,DBCHGSEQ=281:ED-XCVR:
WR-1-1-1:::OOS-AU,UEQ&SGEO"
;
NETSTENDER 05-02-03 07:48:11
A 506 REPT DBCHG
DBCHGSEQ=282:RST-XCVR:WR-1-1-1"
;
7-87
7.9.2.7 Retrieving transceiver attributes
Purpose
Use this procedure to retrieve transceiver attributes.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
None
Procedure
To retrieve transceiver attributes, enter the following syntax at the TL1 command
line interface:
RTRV-XCVR:[TID]:[<aid>]:<CTAG>;
where
aid

ALL
WM-(1,11,21,31)-(1-6)-(1-4)
WR-(1,11,21,31)-(1-6)-(1-4)
WT-(1,11,21,31)-(1-6)-(1-4)
or
or
Example input
RTRV-XCVR:NETSTENDER:ALL:;
Example response
NETSTENDER 06-05-03 13:54:19
M
100 COMPLD
"WR-1-6-1:PROTOCOL=OC48,WAVELENGTH=1551,PHYPMMON=ON,FPSD=ON,
PEC=BP3AM1CL-04,SDBER=0,OPT-LT=0.0,OPT-HT=5.0,OPR-LT=-30.9,
OPR-HT=-6.4,LASERSTATUS=IDLE, AINSTMR=08-00,:OOS-AUMA,MT&FLT"
;
The RTRV-XCVR command returns information fields, operation parameters,

alarm thresholds, laser status and state.
Transceiver parameters
Table 7-19 lists of transceiver parameters that can be returned by entering the
RTRV-XCVR command.
Table 7-19 Transceiver parameters
Parameter
Range of Values
Description
ID1
characters
characters
DSF
NDSF
NZDSF
20
characters.
ID2
FIBER
GRID
C1, C2, C3
PROTOCOL
10GELAN
10GELANFEC
AUTO
ESCON
FC100
FC200
FDDI
FE
GE
OC3
OC12
OC48
OC192
OC192FEC
SMPTE259
SMPTE292
SMPTE344
STM1
STM4
STM16
STM64
STM64FEC

ITU-T wavelength grid numbers.

information
Protocol is the protocol used by the
transceiver.
Note: Protocols SMPTE259, SMPTE292 and
SMPTE344 are supported only on the
Wavelength Translator circuit pack.
Note: The Wavelength Manager only
supports GE, OC3, OC12, OC48 and STM16
in this release.
Note: The 10G Wavelength Regenerator
supports only 10GELAN, 10GELANFEC,
OC192, OC192FEC, STM64, and
STM64FEC.
Note: See Table 7-17, Protocols supported
on 10G Wavelength Regenerator ports for
information on the protocols supported on the
client (XFP) and line (MSA) side ports of the
Note: When a port is assigned
PROTOCOL=AUTO, the wavelength
manager circuit pack starts scanning the
incoming signal, looking for a valid signal.
Once a valid signal is found, such as OC48,
the transceiver port is configured with
PROTOCOL=OC48. If the mates transceiver
port is still scanning for a signal, then that port
is also configured to PROTOCOL=OC48 and
a 2WAY cross-connect is provisioned
between the two ports.
7-89
Table 7-19 Transceiver parameters (Continued)
Parameter
Range of Values
Description
WAVELENGTH
PHYPMMON
OFF
ON
FPSD
OFF
ON
VENDORPN1
VENDORPN2
VENDORPN3
0 to 20 characters
PEC
OPTLT
is the Product Equipment

Code
is the signal degrade BER
threshold
Note: This parameter does
not apply to an XFP.

transceiver, or by the line side port (MSA) of a
(BP1A47BB).
Note: See Table 7-18 for a list of the 36 BTIsupported wavelengths that can be
provisioned on the MSA port (Line 1) of a
(BP1A47BB).
PHYPMMON is the physical PM threshold
monitoring flag.
Note: This parameter can only be OFF for the
enabled flag.
Vendor part numbers 1, 2 and 3 are
transceiver part numbers.
These are optional parameters.
OPTHT
OPRLT
OPRHT
SDBER
6 to 12 corresponding to 10^-6 (high) - 10^-12

(low)
Note: Setting the value to 0 will disable the
SD monitor.
OPTLT is the optical power transmitted low
threshold.
OPTHT is the optical power transmitted high
threshold.
OPRLT is the optical power received low
threshold.
OPRHT is the optical power received high
threshold.
Table 7-19 Transceiver parameters (Continued)
Parameter
Range of Values
Description
LASERSTATUS
IDLE
OFF
ON
AIS-L
ODU2-AIS
MS-AIS
AINSTMR
00-00 to 96-00
ACTAINSTMR
00-00 to 96-00
PST
IS
OOS
COMM
FLT
LPBK
MEA
MT
SGEO
UEQ
LASERSTATUS is the status of the

transceiver laser.
ON means the laser transmits the bit pattern
on the data path.
OFF means the laser is disabled and 0 mW of
optical power are being transmitted.
IDLE means the laser is in an idle pattern.
Note: IDLE does not apply to the 10G
wavelength regenerator.
Note: AIS-L means the alarm indicator signal
line, and applies to protocol OC-192 and all
wavelength manager supported SONET
protocols.
Note: ODU2-AIS applies to protocols
10GELANFEC, OC192FEC, and STM64FEC
only.
Note: MS-AIS means the laser is transmitting
SDH AIS, and applies to protocols STM-16
and STM-64 only.
is the automatic in-service timer in the format
HH-MM.
is the active automatic in-service timer in the
format HH-MM.
SST
SST is the secondary state of the transceiver
7-91
7.9.2.8 Deleting a transceiver
Purpose
Use this procedure to delete a transceiver.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
All cross-connects and protection groups associated with a transceiver must be
deleted before the transceiver can be deleted.
The transceiver ports must be out of service before it is deleted. Otherwise, the
CMDMDE=FRCD parameter must be used to delete a transceiver that is in
service.
Procedure
To delete a transceiver, enter the following syntax at the TL1 command line
interface:
DLT-XCVR:[TID]:<aid>:<CTAG>[:[:[:[CMDMDE=<cmdmde>]]]];
where
WM-(1,11,21,31)-(1-6)-(1-4) or
WR-(1,11,21,31)-(1-6)-(1-4) or
aid
WT-(1,11,21,31)-(1-6)-(1-4)
cmdmde

NORM
FRCD
Example input
DLT-XCVR:NETSTENDER:WR-1-1-1:100:::CMDMDE=FRCD;
Example response
NETSTENDER 05-02-03 07:36:00
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 05-02-03 07:36:01
495 REPT DBCHG
DBCHGSEQ=272:DLT-XCVR:WR-1-1-1";
7.9.3 Provisioning cross-connects on a Wavelength Conversion circuit

pack
This subsection discusses the provisioning of cross-connects and is structured as
follows:
7.9.3.1, Provisioning cross-connects on a Wavelength Conversion circuit pack
7.9.3.2, Retrieving cross-connect port information from a Wavelength
Conversion circuit pack
7.9.3.3, Deleting a cross-connect on a Wavelength Conversion circuit pack
7.9.3.1 Provisioning cross-connects on a Wavelength Conversion circuit pack
Purpose
Note
Use this procedure to provision cross-connects that provide transceiver port

connectivity on a wavelength conversion circuit pack.
No connectivity exists between transceiver ports until a cross-connect is created
that associates the two ports as end points.
The illustration below shows the two types of cross-connects that are currently
supported:
2-way 2-port cross-connect
1-way 1-port cross-connect
The wavelength regenerator, wavelength translator and wavelength manager
circuit packs support 2-way 2-port and 1-way 1-port cross-connects. The 10G
wavelength regenerator circuit pack supports the 2-way 2-port cross-connect only.
Wavelength conversion cross-connects
2-way
2-way
2-port
SFP1
1-way
1-port
SFP2
SFP1
7-93
Note
For the wavelength regenerator, wavelength translator, and wavelength manager

circuit packs, the only supported 2-port cross-connect configurations are between
ports 1 and 2 as well as ports 3 and 4. The 10G wavelength regenerator circuit pack
supports the 2-port cross-connect configuration between ports 1 and 2 only.
2-Port Cross-Connects for Wavelength Conversion circuit packs
Circuit Pack
Port 4
Port 3
Port 2
Port 1
Circuit Pack
Port 4
Port 3
Port 2
Port 1
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
Transceivers must be provisioned with the same protocol before cross-connects
can be created.
Procedure
To provision cross-connects between transceiver ports, enter the following syntax
ENT-CRS-XCVR:[TID]:<src_aid>,<dst_aid>:<CTAG>::<ctype>;
where
<src_aid>
is the source AID in the form of

WM-(1,11,21,31)-(1-6)-(1-4) or
WR-(1,11,21,31)-(1-6)-(1-4) or
WT-(1,11,21,31)-(1-6)-(1-4)
<dst_aid>
is the destination AID in the form of

WM-(1,11,21,31)-(1-6)-(1-4) or
WR-(1,11,21,31)-(1-6)-(1-4) or
WT-(1,11,21,31)-(1-6)-(1-4)
<ctype>
is the cross-connect type of either: 1WAY or 2WAY

- 1WAY is a cross-connect that is simply a
uni-directional connection where the source AID is the
receiver side of the SFP and the destination AID is the
transmitter side of the SFP.
- 2WAY is a cross-connect that is a bi-directional
connection where the source AID is the receiver side of one
transceiver and the destination AID is the transmitter side
of another transceiver.
Note: 2WAY cross-connects can only be created between
port 1 and port 2, or between port 3 and port 4 for the
wavelength translator, wavelength regenerator, and
wavelength manager. The 10G wavelength regenerator circuit
pack supports the 2-port cross-connect configuration between
ports 1 and 2 only.
Example
The following example shows how to enter two-way cross-connects between two
SFP transceiver ports:
ENT-CRS-XCVR:NETSTENDER:WR-1-1-1,WR-1-1-2:100::2WAY;
Response

NETSTENDER 05-02-03 07:32:56
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 05-02-03 07:32:57
A 493 REPT DBCHG
DBCHGSEQ=270:ENT-CRS-XCVR:WR-1-1-1,WR-1-1-2:2WAY"
;
Restrictions
1
The wavelength translator, wavelength regenerator, and wavelength manager

circuit packs support the following cross-connects only:
WT/WR/WM-<shelf#>-<slot#>-1,WT/WR/WM-<shelf#>-<slot#>-1:1WAY
7-95
Note: The 10G wavelength regenerator circuit pack supports the following
cross-connect configuration only at this time:
WR-<shelf#>-<slot#>-1,WR-<shelf#>-<slot#>-2:2WAY
2
Once the cross-connect is created, the source AID, destination AID, and the
cross-connection type cannot be changed. To modify a cross-connect, delete the
existing one and then create a new cross-connect.
Two or more source AIDs cannot be multiplexed to a single destination AID.
A single source AID can be connected to multiple destination AIDs.
The creation of a cross-connect fails if the protocol fields of the end points are
not an exact match.
7.9.3.2 Retrieving cross-connect port information from a Wavelength Conversion

circuit pack
Purpose
Use this procedure to retrieve cross-connect port information.
Provisioning
Superuser
Maintenance
Surveillance
Prerequisites
None
Procedure
To retrieve cross-connect port information, enter the following syntax at the TL1
RTRV-CRS-XCVR:[TID]:[<src_aid>],[<dst_aid>]:<CTAG>;
where
<src_aid>

WM-(1,11,21,31)-(1-6)-(1-4) or
WR-(1,11,21,31)-(1-6)-(1-4) or
WT-(1,11,21,31)-(1-6)-(1-4)
<dst_aid>

WM-(1,11,21,31)-(1-6)-(1-4) or
WR-(1,11,21,31)-(1-6)-(1-4) or
WT-(1,11,21,31)-(1-6)-(1-4)
Example
The following example shows how to retrieve cross-connect port information:

RTRV-CRS-XCVR:NETSTENDER:,:100;
Response
NETSTENDER 05-02-03 07:55:14
M 100 COMPLD
"WR-1-1-1,WR-1-1-1:1WAY"
;
7-97
7.9.3.3 Deleting a cross-connect on a Wavelength Conversion circuit pack
Purpose
Use this procedure to delete a cross-connect between transceiver ports.
Provisioning
Superuser
Maintenance
Surveillance
Prerequisites
None
Procedure
To delete a cross-connect between transceiver ports, enter the following syntax at
DLT-CRS-XCVR:[TID]:<src_aid>,<dst_aid>:<CTAG>;
where
<src_aid>

WM-(1,11,21,31)-(1-6)-(1-4) or
WR-(1,11,21,31)-(1-6)-(1-4) or
WT-(1,11,21,31)-(1-6)-(1-4)
<dst_aid>

WM-(1,11,21,31)-(1-6)-(1-4) or
WR-(1,11,21,31)-(1-6)-(1-4) or
WT-(1,11,21,31)-(1-6)-(1-4)
Example
DLT-CRS-XCVR:NETSTENDER:WR-1-1-1,WR-1-1-2:;
Response
NETSTENDER 05-02-03 07:34:04
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 05-02-03 07:34:06
A 494 REPT DBCHG
DBCHGSEQ=271:DLT-CRS-XCVR:WR-1-1-1,WR-1-1-2"
;
7.9.4 Provisioning protection groups on a Wavelength Conversion circuit

pack
This subsection discusses the provisioning of protection groups and is structured
as follows:
7.9.4.1, How protection switching works
7.9.4.2, Provisioning rules
7.9.4.3, Example scenarios
7.9.4.4, Provisioning a protection group
7.9.4.5, Modifying the definable parameters of a protection group
7.9.4.6, Retrieving protection group parameters
7.9.4.7, Deleting a protection group
7-99
7.9.4.1 How protection switching works

The wavelength regenerator circuit pack supports the configuration of two
transceiver ports in a 1+1 unidirectional, non-revertive protection arrangement.
The protection model borrows from those provided by Telcordia, GR-253-CORE
for SONET LTE protection switching. However, the protection switching
capability is not a SONET line-switched or path-switched device. The protection
switching capability is a customized physical-layer switching solution.
Note
The wavelength regenerator circuit packs with protection switching do not use, or
insert, any data into the K bytes of the SONET frame. Additionally, the protection
switching feature is supported not only for transceivers receiving SONET signals,
but also for facilities of any of the approved signal protocols. The trigger for
wavelength regenerator circuit packs is the optical loss of signal (LOS).
The 10G wavelength regenerator (WR10G) does not support protection switching.
7.9.4.2 Provisioning rules

Two transceiver ports (that is, ports 1 and 3 as well as ports 2 and 4) on a
wavelength regenerator circuit pack can be provisioned as a protection pair, using
the ENT-FFP-XCVR command:
1
The working and protecting transceivers must be provisioned with the same
protocol.
Both the working and the protecting transceivers must be provisioned in an

existing Wavelength Regenerator protection pair.
The protecting transceiver must not be involved in any provisioned crossconnects on the wavelength regenerator circuit pack.
On a 2.5G Wavelength Regenerator, both the working and protecting

transceivers must be provisioned with the same Fault Propagation Shutdown
setting; that is, the FPSD parameter on both ports is either enabled or disabled.
Cross-connects and protection group pairs
It is recommended to configure cross-connects on the wavelength regenerator

ports prior to provisioning protection group pairs.
Protected port order
Port 4 protects port 2, or vice versa.

Port 3 protects port 1, or vice versa.
Any attempt to delete an SFP transceiver is rejected if that transceiver is currently
involved in a protection pair. The protection provisioned and cross-connects, if
they exist, must be deleted before deleting the SFP transceiver.
Provisioned protection pairs can be deleted using the DLT-FFP-XCVR command.
To retrieve a list of provisioned protection pairs, use the RTRV-FFP-XCVR
command. If a protection pair is deleted during a forced switch or a lockout, then

the forced switch and lockout are released when the protection pair is deleted.
7.9.4.3 Example scenarios

Scenario 1 Internal traffic flow on a two-way cross-connect
In the following example scenario, the indicated provisioning commands would be

issued to generate the protection switching arrangement:
ENT-CRS-XCVR:NETSTENDER:WR-1-2-1,WR-1-2-2:2WAY;
ENT-FFP-XCVR:NETSTENDER:WR-1-2-1,WR-1-2-3:::;
A signal failure occurs on WR-1-2-1. As a result, the protecting link from

WR-1-2-3 to WR-1-2-2 becomes the working link that takes over from WR-1-2-1
to WR-1-2-2.
Traffic flow on a two-way cross-connect
Before
Tx
Tx
WR-1-2-1
WR-1-2-2
Rx
Rx
Tx
Tx
WR-1-2-4
WR-1-2-3
Rx
Rx
After
Tx
Tx
WR-1-2-1
WR-1-2-2
Rx
Rx
Tx
Tx
WR-1-2-4
WR-1-2-3
Rx
Rx
Note
In a protection pair, one of the facilities serves as the working facility, and the
other serves as the protecting facility. As the protection pair works as a 1+1 nonrevertive switch, the switching algorithm does not place any preference on either
of the ports to be the working facility. At any point, either the working or the
protecting facility can be carrying traffic if both are fault free.
Automatic protection switching is not available for the wavelength manager circuit
pack in this release.
7-101
Automatic protection switching occurs when a fault is detected on the working

facility, and the protecting facility is free of faults, or the protecting facility has
only less severe faults than the working facility. Under these circumstances, an
automatic protection switch occurs to make the protecting facility the working and
the working facility the protecting.
Scenario 2 Protection switching between sites
In the following example scenario, three sites are connected in a ring

configuration. A fiber cut or SFP failure between sites one and three triggers
protection switching. Prior to the line failure, the working path is at port one and
the protected path uses port three. After the failure, between sites one and three,
the wavelength regenerator automatically selects port three as the working line.
Protection switching between sites
Wavelength
Regenerator
ADM
ADM
SITE 2
Wavelength
Regenerator
SITE 1
ADM
ADM
1
Wavelength
Regenerator
SITE 3
ADM
ADM
Port 1
Port 2
1
Wavelength
Regenerator
Port 3
For further details regarding the use of protection switching, see section 9.3,
Protection switching in this document.
7.9.4.4 Provisioning a protection group

The command to enter a new protection group is ENT-FFP-XCVR.
To enter new protection group provisioning information, enter the following
ENT-FFP-XCVR:[<TID>]:<work>,<protect>:<CTAG>[:[:[:[PROTID=<protid>]]]];
Note
Before the protection group can be established using the command syntax
described above, either a 1WAY or a 2WAY cross-connect must be created
between ports 1 and 2 or ports 3 and 4 of the wavelength regenerator using the
ENT-CRS-XCVR command. See section 7.9.3.1, Provisioning cross-connects on
a Wavelength Conversion circuit pack for details.
Example
The following example shows how to enter a new protection group for a
wavelength regenerator located in shelf 1, slot 2, with port 2 serving as the
working port and port 4 as the protecting port in the protection group:
ENT-FFP-XCVR:NETSTENDER:WR-1-2-2,WR-1-2-4:100:::PROTID=2;
Response

NETSTENDER 05-06-05 15:00:01
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 05-06-05 15:00:03
A
207 REPT DBCHG
DBCHGSEQ=38:ENT-FFP-XCVR:WR-1-2-2,WR-1-2-4:100::PROTID=2"
;
7-103
7.9.4.5 Modifying the definable parameters of a protection group

The command to edit a protection group is ED-FFP-XCVR.
To edit protection group provisioning information, enter the following syntax at
ED-FFP-XCVR:[<TID>]:<work>,<protect>:<CTAG>[:[:[:[PROTID=<protid>]]]];
Example
The following example shows how to edit the protection group identifier to 11:
ED-FFP-XCVR:NETSTENDER:WR-1-2-2,WR-1-2-4:100:::PROTID=11;
Response

NETSTENDER 05-06-05 15:00:00
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 05-06-05 15:00:01
A
170 REPT DBCHG
DBCHGSEQ=20:ED-FFP-XCVR:WR-1-2-2,WR-1-2-4::PROTID=11"
;
7.9.4.6 Retrieving protection group parameters

The command to retrieve protection group parameters is RTRV-FFP-XCVR.
To retrieve protection group parameters, enter the following syntax at the TL1
RTRV-FFP-XCVR:[<TID>]:<work>,<protect>:<CTAG>;
Example
The following example shows how to retrieve the protection group parameters:
RTRV-FFP-XCVR:NETSTENDER:WR-1-2-2,WR-1-2-4:100;
Response

NETSTENDER 05-06-05 15:00:00
M CTAG COMPLD
"WR-1-2-2,WR-1-2-4::PROTID=2"
;
7.9.4.7 Deleting a protection group

The command to delete a protection group is DLT-FFP-XCVR.
To delete a protection group, enter the following syntax at the TL1 command line
interface:
DLT-FFP-XCVR:[<TID>]:<work>,<protect>:<CTAG>;
Example
The following example shows how to delete a protection group:

DLT-FFP-XCVR:NETSTENDER:WR-1-2-2,WR-1-2-4:100;
Response

NETSTENDER 05-06-22 09:26:30
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 05-06-22 09:26:30
A
47 REPT DBCHG
DBCHGSEQ=25:DLT-FFP-XCVR:WR-1-2-2,WR-1-2-4"
;
7-105
7.10 2-Port GE Muxponder provisioning

The provisioning of a 2-Port GE Muxponder circuit pack involves provisioning the
synchronization feature, client side ports, line side ports, cross-connects, and
protection switching.
This section is structured as follows:
7.10.1, Provisioning 2-Port GE Muxponder circuit pack equipment
7.10.2, Provisioning synchronization
7.10.3, Provisioning Fast Ethernet client side ports
7.10.4, Retrieving a manufacturers SFP transceiver inventory
7.10.5, Provisioning gigabit Ethernet client side ports
7.10.6, Provisioning OC-48 line side ports
7.10.7, Provisioning STM-16 line side ports
7.10.8, Retrieving Virtual Concatenation Group attributes
7.10.9, Provisioning cross-connections on a Muxponder circuit pack
7.10.10, Provisioning protection switching on a Muxponder circuit pack
7.10.1 Provisioning 2-Port GE Muxponder circuit pack equipment

The 2-Port GE Muxponder circuit pack is available in the following
configurations, each with its own PEC:
2-Port GE Muxponder SONET (MXP2.5G), BP1A46AA: This Muxponder
circuit pack features two line side ports configured for SONET (OC-48)
physical layer operating mode.
2-Port GE Muxponder SDH (MXP2.5G), BP1A46BA: This Muxponder
circuit pack features two line side ports configured for SDH (STM-16)
operating mode.
Purpose
Use this procedure to provision a Muxponder circuit pack in a Netstender shelf.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
None
Procedure
To provision a Muxponder circuit pack, enter the following syntax at the TL1
ENT-EQPT:[TID]:<aid>:CTAG[:[:<type>[:[[ID=<id>][,C1=<custom1>]
[,C2=<custom2>][,C3=<custom3>][,SHCONF=<shconf>]][:[<pst>][,<sst>]]]]];
where
<aid>
<type>
is in the form of MXP-(1,11,21,31)-(1-6)

is either BP1A46AA or BP1A46BA
Example
The following example shows how to enter a new Muxponder circuit pack in
shelf one, slot two:
ENT-EQPT:NETSTENDER:MXP-1-2:100::BP1A46AA;
Response

NETSTENDER 05-02-03 15:00:00
M
100 COMPLD
7-107
NETSTENDER>
NETSTENDER 05-02-03 15:00:01
A
165 REPT DBCHG
DBCHGSEQ=36:ENT-EQPT:MXP-1-2:BP1A46AA::"
;
The following equipment and inventory commands are also available:

ED-EQPT
RMV-EQPT
RST-EQPT
RTRV-EQPT
RTRV-INV
DLT-EQPT
edits equipment entries.

removes equipment from service.
restores equipment to service.
retrieves equipment provisioning information.
retrieves system inventory information.
deletes equipment entries.
For further details about these commands, refer to the Netstender TL1 Reference
Guide.
7.10.2 Provisioning synchronization

This subsection discusses the provisioning of the timing mode and the timing
reference on a 2-Port GE Muxponder circuit pack, and is structured as follows:
7.10.2.1, Provisioning the timing mode
7.10.2.2, Retrieving timing-mode information
7.10.2.3, Provisioning the timing reference
7.10.2.4, Retrieving timing-reference information
7.10.2.1 Provisioning the timing mode

The 2-Port GE Muxponder has two line side ports configured as either OC-48
(SONET) or STM-16 (SDH). The purpose of this circuit pack is to multiplex
gigabit Ethernet traffic coming from the two client side ports (GE) and carry over
an OC-48 or STM-16 optical signal, and vice versa.
Because the line side network on the Muxponder circuit pack is synchronous, any
entity (circuit pack or Network Element) connecting to the Muxponder line side
network has to set proper timing so that the entity can be synchronized to the entire
line side network.
The Muxponder circuit pack supports the following timing modes:
Internal, which has a clock accuracy of 2.5 parts per million
Line, which supports a primary timing reference and a secondary timing
reference
Purpose
Use this procedure to provision the timing mode on a Muxponder circuit pack.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
Ensure that the Muxponder circuit pack is provisioned before starting this
procedure.
Procedure
To provision the timing mode on a Muxponder circuit pack, enter the following
SET-TMG-MODE:[TID]:<aid>:[CTAG]::MODE=<mode>;
where
<aid>
<mode>

is either INT or LINE
Example
The following example shows how to provision the timing mode on a Muxponder
circuit pack:
SET-TMG-MODE:NETSTENDER:MXP-1-6:100::MODE=LINE;
7-109
Response
NNETSTENDER 07-07-29 10:04:59
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 07-07-29 10:05:00
A
441 REPT DBCHG
DBCHGSEQ=188:SET-TMG-MODE:MXP-1-6:,,,LINE"
;
7.10.2.2 Retrieving timing-mode information
Purpose
Use this procedure to retrieve timing-mode information from a Muxponder circuit

pack.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
None
Procedure
To retrieve timing-mode information from a Muxponder circuit pack, enter the
RTRV-TMG-MODE:[TID]:<aid>:[CTAG];
where
<aid>
Example
The following example shows how to retrieve timing-mode information from a

Muxponder circuit pack:
RTRV-TMG-MODE:NETSTENDER:MXP-1-6:100::;
Response
NETSTENDER 07-07-29 10:08:32
M
;
100 COMPLD
"MXP-1-6:MODE=LINE"
7.10.2.3 Provisioning the timing reference
Purpose
Use this procedure to provision the timing reference on a Muxponder circuit pack.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
See Rules for primary and secondary timing references, which follows this
procedure.
Procedure
To provision the timing reference on a Muxponder circuit pack, enter the
SET-TMREF:[TID]:<aid>:[CTAG]:::PRI=<pri>,SEC=<sec>;
where
<aid>
<mode>
<pri>
<sec>

is either INT or LINE
is the primary timing reference in the form of
MXP-(1,11,21,31)-(1-6)-(L1,L2) or NONE
is the secondary timing reference in the form of
MXP-(1,11,21,31)-(1-6)-(L1,L2) or NONE
7-111
Example
The following example shows how to provision the timing reference on a

SET-TMREF:NETSTENDER:MXP-1-6:100:::PRI=MXP-1-1-L1,SEC=MXP-1-1-L2;
Response
NETSTENDER 07-09-21 10:28:08
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 07-09-21 10:28:09
A
8098 REPT DBCHG
"TIME=10-28-09,DATE=07-09-21,SOURCE=100,LINKID=2-15,USERID=ADMIN,
DBCHGSEQ=102:SET-TMREF:MXP-1-1:PRI=MXP-1-1-L1,SEC=MXP-1-1-L2"
;
Rules for primary and secondary timing references

1
Primary and secondary timing references can be provisioned only if the

Muxponder circuit pack is provisioned for Line timing mode. For information,
see 7.10.2.1, Provisioning the timing mode.
Only a line side port (OC-48 or STM-16) can be provisioned as a primary or

secondary timing reference.
To be provisioned as a primary or secondary timing reference, a line side port

must be provisioned.
A line side port involved in a timing reference must cannot be deleted; however,
it can be put out of service manually.
In the event of a loss of the primary timing reference, the Muxponder circuit
pack will switch to the secondary timing reference provided that the secondary
timing reference has been provisioned. If the secondary timing reference has not
been provisioned, the Muxponder circuit pack will go into Holdover mode. In
Holdover mode, the clock accuracy is 100 parts per billion and is relative to the
last available clock (that is, either the primary timing reference or the systems
internal clock).
In the event of a loss of both the primary and secondary timing references, the
Muxponder circuit pack will go into Holdover mode.
7.10.2.4 Retrieving timing-reference information
Purpose
Use this procedure to retrieve timing-reference information from a Muxponder

circuit pack.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
None
Procedure
To retrieve timing-reference information from a Muxponder circuit pack, enter the
RTRV-TMREF:[TID]:<aid>:[CTAG];
where
<aid>
Example
The following example shows how to retrieve timing-reference information from

a Muxponder circuit pack:
RTRV-TMREF:NETSTENDER:MXP-1-1:100::;
Response
NETSTENDER 07-09-21 10:28:29
M
100 COMPLD
"MXP-1-1:PRI=MXP-1-1-L1,:WRK"
"MXP-1-1:SEC=MXP-1-1-L2:STDBY"
7-113
7.10.3 Provisioning Fast Ethernet client side ports

This subsection discusses the provisioning of Fast Ethernet (FE) client side ports
on a 2-Port GE Muxponder circuit pack and is structured as follows:
7.10.3.1, Provisioning an FE client side port
7.10.3.2, Modifying the provisionable parameters of an FE client side port
7.10.3.3, Retrieving FE client side port attributes
7.10.3.4, Deleting an FE client side port
7.10.3.1 Provisioning an FE client side port
Purpose
Use this procedure to provision a Fast Ethernet (FE) client side port of a
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
procedure.
Procedure
To provision an FE client side port, enter the following syntax at the TL1
ENT-FE:[TID]:<aid>:[CTAG]:::[ID1=<id>],[C1=<custom1>];
where
is in the form of MXP-(1,11,21,31)-(1-6)-(C3-C4)
The remaining parameters are discussed in Table 7-20, FE client side port
parameters.
<aid>
Note:
Example input
The following example shows how to provision FE client side port C3 of a

Muxponder circuit pack in shelf one, slot six:
ENT-FE:NETSTENDER:MXP-1-6-C3:100:::ID1=idtest,C1=c1test;
Example response
NETSTENDER 07-07-25 13:46:36
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 07-07-25 13:46:37
A
318 REPT DBCHG
DBCHGSEQ=81:ENT-FE:MXP-1-6-C3::id1=idtest,c1=c1test"
;
FE client side port parameters
Table 7-20 lists the FE client side port parameters that can be provisioned by
entering the ENT-FE command.
Table 7-20 FE client side port parameters
Parameter
Range of Values
Description
ID1
characters
characters
ID1 is identifier 1, which can contain

descriptive text. This is an optional field.
provide specific operating-company
information. This is an optional field.
C1
7-115
7.10.3.2 Modifying the provisionable parameters of an FE client side port
Purpose
Use this procedure to modify the provisionable parameters of a Fast Ethernet (FE)
client side port of a Muxponder circuit pack.
Provisioning
Superuser
Maintenance
Surveillance
Prerequisites
Ensure that the FE client side port is provisioned before starting this procedure.
Procedure
To modify the provisionable parameters of an FE client side port, enter the
ED-FE:[TID]:<aid>:[CTAG]:::[ID1=<id>],[C1=<custom1>];
where
aid
Note:
The remaining parameters are discussed in Table 7-20, FE client side port
parameters.
Example input
The following example shows how to edit the provisionable parameters of FE

client side port C3 of a Muxponder circuit pack in shelf one, slot six:
ED-FE:NETSTENDER:MXP-1-6-C3:100:::ID1=IDTEST,C1=C1TEST;
Example response
NETSTENDER 07-07-25 14:21:27
M
100 COMPLD
NETSTENDER>
NETSTENDER 07-07-25 14:21:32
A
325 REPT DBCHG
DBCHGSEQ=88:ED-FE:MXP-1-6-C3::ID1=IDTEST,C1=C1TEST"
;
7.10.3.3 Retrieving FE client side port attributes
Purpose
Use this procedure to retrieve the attributes of a Fast Ethernet (FE) client side port
of a Muxponder circuit pack.
Provisioning
Superuser
Maintenance
Surveillance
Prerequisites
Ensure that the FE client side port is provisioned before starting this procedure.
Procedure
To retrieve the attributes of an FE client side port, enter the following syntax at the
TL1 command line interface:
RTRV-FE:[TID]:<aid>:CTAG;
where
<aid>
Example input
The following example shows how to retrieve the attributes of FE client side port
C3 of a Muxponder circuit pack in shelf one, slot six:
RTRV-FE:NETSTENDER:MXP-1-6-C3:100::;
Example response
The Netstender returns a COMPLD message and values for both the provisionable
and read-only parameters of the FE client side port:
NETSTENDER 07-07-28 10:20:40
M
100 COMPLD
"MXP-1-6-C3:SPEED=100,DUPLEX=FULL,MTU=9600,MACADDRESS=0014d0000273";
7-117
Table 7-21 lists the information fields and operation parameters returned by the
RTRV-FE command.
Table 7-21 Retrievable FE client side port parameters
Parameter
Range of Values
Description
AID
MXP-(1,11,21,31)-(1-6)(C3,C4)
characters
characters
Access identifier of the Fast Ethernet client side

port.
ID1
C1
SPEED
10
100
DUPLEX
MTU
FULL
9600
MACADDRESS
integer
ID1 is identifier 1, which can contain descriptive

text.
Custom field that is available to users to provide
specific operating-company information. This is an
optional field.
SPEED is the speed of the Fast Ethernet client
side port.
Note: If the MEDIARATE parameter is set to AutoNegotiate on the FE port, the SPEED parameter
indicates the actual negotiated speed of the
interface.
DUPLEX is the duplex mode.
MTU is the maximum transmission unit (that is,
packet size) of the Fast Ethernet client side port.
MACADDRESS is the MAC address expressed as
00-00-00-00-00-00.
7.10.3.4 Deleting an FE client side port
Purpose
Use this procedure to delete a Fast Ethernet (FE) client side port of a Muxponder
circuit pack.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
All cross-connects associated with an FE client side port must be deleted before
the FE client side port can be deleted.
Procedure
To delete an FE client side port, enter the following syntax at the TL1 command
line interface:
DLT-FE:[TID]:<aid>:[CTAG];
where
aid
Example input
The following example shows how to delete FE client side port C3 of a

Muxponder circuit pack in shelf one, slot one:
DLT-FE:NETSTENDER:MXP-1-1-C3:100::;
Example response
NETSTENDER 07-08-13 13:04:16
M
100 COMPLD
;
NETSTENDER>
NETSTENDER>
NETSTENDER 07-08-13 13:04:17
A
41 REPT DBCHG
DBCHGSEQ=5:DLT-FE:MXP-1-1-C3"
;
7-119
7.10.4 Retrieving a manufacturers SFP transceiver inventory

Purpose
Use this procedure to retrieve a manufacturers transceiver inventory information

for SFPs present in any of the gigabit Ethernet (GE) client side ports and the
OC-48 or STM-16 line side ports of a Muxponder circuit pack.
Provisioning
Superuser
Maintenance
Surveillance
Prerequisites
An SFP transceiver must be inserted in a port of a Muxponder circuit pack for the
transceiver inventory information to be read by the system. The SFP does not need
to be provisioned for the transceiver inventory information to be read.
Procedure
To retrieve the manufacturers SFP transceiver inventory information, enter the
where
<aid>
Example input
The following example shows how to retrieve the system inventory information:
Example response
The Netstender returns a COMPLD message that lists all of the circuit packs, SFP
transceivers and common equipment present in the system:
NETSTENDER 07-09-14 11:44:30
M
100 COMPLD
"MS-1,EQPT:NAME=MS2060,PEC=BP1A5021,CLEI=WMMKTWOKRA,FNAME=Main Shelf
Netstender 2060,HWREV=\"0\",SHCONF=6-SLOT,"
"SLOT-1-1,EQPT:NAME=MXP2.5G,PEC=BP1A46BA,CLEI=NotSet,FNAME=2-PORT 2.5G
MUXPONDER - SDH,SER=\"SN00004114\",HWREV=\"1\",MFGDAT=\"2007-09-14\",
MFGLOCN=BTI Northside,TSTDAT=2007-09-14,TSTLOCN=BTI Northside,"
"SFP-1-1-L1,EQPT:PEC=BP3AM1DE-26,SER=\"NT0069\",HWREV=\"0003\",
MFGDAT=\"2006-07-24-01\",WAVELENGTH=1535.04,REACH=80,MINBR=150,
NOMBR=2500,ENCODING=SONET SCRAMBLED,CONNTYPE=LC,VENDORNAME=\"FUJITSU\",
VENDORPN=\"FIM32160/206W53\",TXFAULTIMP=Y,TXDISABLEIMP=Y,LOSIMP=Y,
DDIAGIMP=Y,MEDIA=OPTICAL"
"SFP-1-1-L2,EQPT:PEC=BP3AM1LL,SER=\"6335000525\",HWREV=\"C21\
NOMBR=2500,ENCODING=SONET SCRAMBLED,CONNTYPE=LC,VENDORNAME=\"JDS
"SFP-1-1-C1,EQPT:PEC=BP3AM1MI,SER=\"6332001588\",HWREV=\"D15\
UNIPHASE\",VENDORPN=\"CT2-MI1LBTD33C5\",TXFAULTIMP=Y,TXDISABLEIMP=Y,
"SFP-1-1-C2,EQPT:PEC=BP3AM1LL,SER=\"6335000552\",HWREV=\"C21\
;
As seen in the example response above, SLOT-1-1 is equipped with a BP1A46BA

Muxponder circuit pack. Inserted in the Muxponder are four SFP transceivers in
ports L1, L2, C1, and C2.
Table 7-22 lists the parameters that can be part of a manufacturers SFP
transceiver inventory.
Table 7-22 Manufacturers SFP transceiver parameters
Parameter
Range of Values
Description
AID
SFP-(1,11,21,31)-(1-6)(L1,L2,C1,C2)
EQPT
AID is the access identifier for the transceiver in the

Netstender.
AIDTYPE is the equipment type that is targeted by
the message.
NAME is the abbreviated name of the circuit pack.
PEC is the product equipment code.
CLEI is the common language equipment identifier.
SER is the serial number of the transceiver.
AIDTYPE
NAME
PEC
CLEI
SER
HWREV
MFGDAT
MXP
string
string
alphanumeric
characters
alphanumeric
characters
YYYY-MM-DD-xx
HWREV is the hardware revision number of the

transceiver.
MFGDAT is the manufacture date of the transceiver
and, if provided, the two-character lot number of the
manufacturer in ASCII.
Note: The lot number is not always provided by the
manufacturer. In which case, only the manufacture
date is provided.
7-121
Table 7-22 Manufacturers SFP transceiver parameters (Continued)
Parameter
Range of Values
Description
WAVELENGTH
numerical
REACH
integer
MINBR
integer
MAXBR
integer
NOMBR
integer
ENCODING
8B10B
4B5B
NRZ
MANCHESTER
SONET_SCRAMBLED
CONNTYPE
LC
VENDORNAME
alphanumeric
characters
consists of escaped
characters.
alphanumeric
characters
consists of escaped
characters.
string
WAVELENGTH is the wavelength of the transceiver

in nm. Some transceivers only specify their
wavelength to the nearest nm whereas others
specify wavelength to the nearest 0.01 nm.
Note: If a transceiver is inserted into a circuit pack
and the transceiver does not have a wavelength
REACH is the maximum transmit distance of the
transceiver in km using nine micron SM fiber.
pack and the transceiver does not have a reach
MINBR is the minimum bit rate supported by the
transceiver.
MAXBR is the maximum bit rate supported by the
transceiver.
NOMBR is the nominal bit rate supported by the
transceiver.
pack and the transceiver does not have a nominal
baud rate value specified in its memory, the
Netstender raises a REPLUNITUNK alarm against
the transceiver.
ENCODING indicates the encoding scheme for the
transceiver.
Note: The Netstender does not use the encoding
parameter. It is the operating companys
responsibility to ensure that both end points of a
span use the same encoding.
CONNTYPE is one of the listed transceiver
connector types.
VENDORNAME is the transceiver vendor name.
VENDORPN
VENDOROUI
VENDORPN is the transceiver vendor part number.
VENDOROUI is the vendor organizational unique

identifier.
Note: This parameter consists of escaped string
values that are surrounded by \ and \ characters.
Table 7-22 Manufacturers SFP transceiver parameters (Continued)
Parameter
Range of Values
Description
TXFAULTIMP
Y
N
TXDISABLEIMP
Y
N
LOSIMP
Y
N
DDIAGIMP
Y
N
MEDIA
ELECTRICAL
OPTICAL
UNKNOWN
TXFAULTIMP is the transceiver fault implemented

flag.
Note: BTI recommends only using transceivers that
have TXFAULTIMP=Y.
TXDISABLEIMP is the transceiver disable
implemented flag.
Note: This parameter indicates whether the
transmitter disable function is supported on that
transceiver. If TXDISABLEIMP=Y and FPSD=ON,
then the REPLUNITMEA alarm is enabled.
LOSIMP is the loss of signal implementation flag.
Note: This parameter indicates whether the loss of
signal (LOS) notification function is supported on that
transceiver. If LOSIMP=N, then the LOS alarm
cannot be raised.
BTI recommends only using transceivers that have
LOSIMP=Y.
DDIAGIMP is the digital diagnostic implementation
flag. When set to Y, this parameter enables the
recording of performance monitoring data in
historical bins.
Note: This parameter indicates whether the digital
diagnostics function is supported on that transceiver.
If not, then PMs and PHYPMMON are not available.
All PM historical bins for that transceiver are filled
with dummy values and marked as invalid.
BTI recommends only using transceivers with
DDIAGIMP=Y.
Media is the type of connector used by the
transceiver.
7.10.5 Provisioning gigabit Ethernet client side ports

This subsection discusses the provisioning of gigabit Ethernet (GE) client side
ports and is structured as follows:
7.10.5.1, Provisioning a GE client side port
7.10.5.2, Implementing advanced provisioning features
7.10.5.3, Modifying the provisionable parameters of a GE client side port
7.10.5.4, Removing a GE client side port from service
7.10.5.5, Restoring a GE client side port to service
7.10.5.6, Retrieving GE client side port attributes
7.10.5.7, Deleting a GE client side port
7-123
7.10.5.1 Provisioning a GE client side port
Purpose
Use this procedure to provision a gigabit Ethernet (GE) client side port of a
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
procedure.
Procedure
To provision a gigabit Ethernet client side port, enter the following syntax at the
ENT-GE:[TID]:<aid>:[CTAG]:::[ID1=<id>],[FIBERTYPE=<fibertype>],
[MEDIARATE=<mediarate>],[C1=<custom1>],WAVELENGTH=<wavelength>,
[PHYPMMON=<phypmmon>],[FPSD=<fpsd>],[VENDORPN1=<vendorpn1>],
[VENDORPN2=<vendorpn2>],[VENDORPN3=<vendorpn3>],[PEC=<pec>],
[AINSTMR=<ainstmr>]:[<pst>],[<sst>];
where
<aid>
is in the form of
MXP-(1,11,21,31)-(1-6)-(C1-C2)
is the channel wavelength in nm

The WAVELENGTH parameter for the GE client side port must be provisioned.
<wavelength>
Notes:
The remaining parameters are discussed in Table 7-23, Gigabit Ethernet client
side port parameters.
Example input
The following example shows how to provision GE client side port C1 of a

ENT-GE:NETSTENDER:MXP-1-1-C1:100:::WAVELENGTH=1559.79;
Example response
NETSTENDER 07-08-13 13:14:53
M
100 COMPLD
NETSTENDER 07-08-13 13:14:54

A
43 REPT DBCHG
DBCHGSEQ=6:ENT-GE:MXP-1-1-C1::WAVELENGTH=1559.79"
;
GE client side port parameters
Table 7-23 lists the GE client side port parameters that can be provisioned by
entering the ENT-GE command.
Table 7-23 Gigabit Ethernet client side port parameters
Parameter
Range of Values
Description
ID1
characters
DSF
MULTIMODE
NDSF
NONE
NZDSF
1000FD
AUTO
characters

descriptive text.
FIBERTYPE
MEDIARATE
C1
WAVELENGTH
PHYPMMON
OFF
ON
OFF
ON
FPSD
VENDORPN1
VENDORPN2
VENDORPN3
0 to 20 characters
MEDIARATE is the Ethernet speed and

duplex rate in Mbps.
transceiver. This is a mandatory field for the
SFP transceivers.
monitoring flag.
enabled flag.
7.10.5.2, Implementing advanced
provisioning features in this document.
ignored.
7-125
Table 7-23 Gigabit Ethernet client side port parameters (Continued)
Parameter
Range of Values
Description
PEC
11 characters
AINSTMR
00-00 to 96-00
PST
IS
OOS
AINS
PEC is the Product Equipment Code. If the

PEC is used, the vendor part numbers are
ignored.
AINSTMR is the automatic in-service timer in
the format HH-MM.
SST
7.10.5.2 Implementing advanced provisioning features

This section discusses the implementation of various advanced provisioning
features for the GE client side port.
Enabling fault propagation shutdown
If there is a client-side failure at the near end of the link, the corresponding
transmitting laser at the far end of the link continues to function and can transmit
unreliable information. Fault propagation shutdown (FPSD) provides a means to
quickly shut down a transmitting laser and pass the fault to the downstream device
when a receiver signal failure occurs.
On the Muxponder circuit pack, FPSD is supported on the two gigabit Ethernet
client side ports only, and may be used to configure the behavior of the transmitted
signal on the transmit side of the GE client side ports in the event of a fault
scenario.
The following are the FPSD values supported:
ON In the event of LAN or WAN failure, or the receipt of Client Signal Fail
(CSF), the transmit laser is shut down.
OFF In the event of a fault scenario, the transmit laser is not affected.
LAN-side failure can be any of the following conditions:
SFP missing
Loss of signal (LOS) on the GE client side port
Loss of synchronization (LOSYNC) on the GE client side port
GE Virtual Concatenation Group (VCG) loss of multiframe (LOM)
GE Virtual Concatenation Group (VCG) loss of alignment (LOA)
GE Virtual Concatenation Group (VCG) sequence mismatch
WAN-side failure can be any of the following conditions:

SFP missing
OCn RX loss of signal
OCn RX loss of frame
OCn RX AIS-L
FPSD and laser status
The following rules apply to FPSD settings and laser status on the Muxponder
circuit pack:
1
The default FPSD setting for both GE client side ports is OFF.
When the FPSD setting for a GE client port is OFF, the transmit laser is on.
When the FPSD setting for a GE client port is ON and the GE client side port is
cross-connected, the transmit laser is on provided that there are no alarms on the
GE client side port.
Enabling threshold crossing alarms
The following threshold crossing alarms are supported on the GE client side ports:
The threshold crossing alarms work on the SFP inserted in the GE client side port
only if the digital diagnostics implementation (DDIAGIMP) flag is set to Y in the
inventory entry and the physical PM monitor (PHYPMMON) parameter is set to
ON for the provisioned GE client side port. For information about DDIAGIMP,
see Table 7-22, Manufacturers SFP transceiver parameters.
7-127
7.10.5.3 Modifying the provisionable parameters of a GE client side port
Purpose
Use this procedure to modify the provisionable parameters of a gigabit Ethernet

(GE) client side port of a Muxponder circuit pack.
Provisioning
Superuser
Maintenance
Surveillance
Prerequisites
All cross-connects associated with a GE client side port must be deleted before the
wavelength parameter can be modified.
The GE client side port must be removed from service before the wavelength
parameter can be modified, otherwise the CMDMDE=FRCD parameter must be
used.
Procedure
To modify the provisionable parameters of a GE client side port, enter the
ED-GE:[TID]:<aid>:[CTAG]:::[ID1=<id>],[FIBERTYPE=<fibertype>],
[MEDIARATE=<mediarate>],[C1=<custom>],[WAVELENGTH=<wavelength>],
[PHYPMMON=<phypmmon>],[FPSD=<fpsd>],[VENDORPN1=<vendorpn1>],
[VENDORPN2=<vendorpn2>],[VENDORPN3=<vendorpn3>],[PEC=<pec>],
[AINSTMR=<ainstmr>],[CMDMDE=<cmdmde>]:[<pst>],[<sst>];
where
aid
cmdmde

NORM
FRCD
Note:
Example input
The following example shows how to edit the provisionable parameters of GE

client side port C2 of a Muxponder circuit pack in shelf one, slot six:
ED-GE:NETSTENDER:MXP-1-6-C2:100:::ID1=IDTEST;
Example response
NETSTENDER 07-07-28 11:28:32
M
100 COMPLD;
NETSTENDER>
NETSTENDER 07-07-28 11:28:33
A
106 REPT DBCHG
DBCHGSEQ=70:ED-GE:MXP-1-6-C2::ID1=IDTEST";
7.10.5.4 Removing a GE client side port from service
Purpose
Important
Use this procedure to remove from service a gigabit Ethernet (GE) client side port
of a Muxponder circuit pack.
Removing a GE port from service is traffic affecting. In addition, all SFP-related
alarms are suppressed. Faults can still be queried by using the RTRV-COND-GE
or the RTRV-COND-ALL command.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
None
Procedure
To remove a GE client side port from service, enter the following syntax at the
RMV-GE:[TID]:<aid>:[CTAG];
where
aid
Example input
The following example shows how to remove from service GE client side port C1
of a Muxponder circuit pack in shelf one, slot one:
RMV-GE:NETSTENDER:MXP-1-1-C1:100::;
Example response
NETSTENDER 07-08-13 14:19:56
M
100 COMPLD
7-129
;
NETSTENDER 07-08-13 14:19:57
A
24 REPT DBCHG
"TIME=14-19-57,DATE=07-08-13,SOURCE=0000,DBCHGSEQ=11:ED-GE:
MXP-1-1-C1:::OOS-AUMA,MT&FLT"
;
NETSTENDER 07-08-13 14:19:57
A
25 REPT DBCHG
DBCHGSEQ=12:RMV-GE:MXP-1-1-C1"
;
7.10.5.5 Restoring a GE client side port to service
Purpose
Important
Use this procedure to restore to service a gigabit Ethernet (GE) client side port of a
Restoring a GE client side port to service enables traffic and related alarms.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
None
Procedure
To restore a GE client side port to service, enter the following syntax at the TL1
RST-GE:[TID]:<aid>:[CTAG]::::[<pst>],[<sst>];
where
aid
Note:
Example input
The following example shows how to restore to service GE client side port C2 of a
RST-GE:NETSTENDER:MXP-1-6-C2:100::::,;
Example response
NETSTENDER 07-07-28 11:38:15
M
100 COMPLD
;
NETSTENDER 07-07-28 11:38:16
A
119 REPT DBCHG
"TIME=11-38-16,DATE=07-07-28,SOURCE=0000,DBCHGSEQ=77:ED-GE:
MXP-1-6-C2:::OOS-AU,FLT"
;
NETSTENDER 07-07-28 11:38:17
A
120 REPT DBCHG
DBCHGSEQ=78:RST-GE:MXP-1-6-C2"
;
7.10.5.6 Retrieving GE client side port attributes
Purpose
Use this procedure to retrieve the attributes of a gigabit Ethernet (GE) client side
port of a Muxponder circuit pack.
Provisioning
Superuser
Maintenance
Surveillance
Prerequisites
Ensure that the GE client side port is provisioned before starting this procedure.
Procedure
To retrieve the attributes of a GE client side port, enter the following syntax at the
RTRV-GE:[TID]:<aid>:CTAG;
where
<aid>
Example input
The following example shows how to retrieve the attributes of GE client side port
C2 of a Muxponder circuit pack in shelf one, slot one:
RTRV-GE:NETSTENDER:MXP-1-1-C2:100::;
7-131
Example response
and read-only parameters of the GE client side port:
NETSTENDER 07-08-13 14:27:54
M
100 COMPLD
"MXP-1-1-C2:PHYPMMON=OFF,LASERSTATUS=ON,OPRHT=4.0,OPRLT=-22.0,
OPTHT=0.0,OPTLT=-5.0,SPEED=1000,DUPLEX=FULL,MTU=9600,MEDIARATE=AUTO,
WAVELENGTH=1310,FPSD=OFF,MACADDRESS=0014d0000270,AINSTMR=08-00,:IS-NR,";
Table 7-24 lists the information fields, operation parameters, alarm thresholds,
laser status, and state that are returned by the RTRV-GE command.
Table 7-24 Retrievable GE client side port parameters
Parameter
Range of Values
Description
AID
MXP-(1,11,21,31)-(1-6)(C1,C2)
characters
characters
Access identifier of the gigabit Ethernet client side

port.
ID1
C1
PEC
11 characters
PHYPMMON
OFF
ON
ON
OFF
integer to one decimal
place of accuracy
LASERSTATUS
OPRHT
OPRLT

place of accuracy
OPTHT

place of accuracy
OPTLT

place of accuracy

text.
optional field.
PEC is the Product Equipment Code. If the PEC is
Note: If the PEC is entered, the system compares
the provisioned values with the PEC of the
monitoring flag.
LASERSTATUS is the status of the transmit laser.
threshold.
Note: The PHYPMMON parameter must be set to
ON.
OPRLT is the optical power received low threshold.
ON.
threshold.
ON.
threshold.
ON.
Table 7-24 Retrievable GE client side port parameters (Continued)
Parameter
Range of Values
Description
FIBERTYPE
Fiber type that connects to the transceiver. This is

an optional field.
DUPLEX
DSF
MULTIMODE
NDSF
NONE
NZDSF
0
1000
FULL
MTU
integer
MEDIARATE
1000FD
AUTO
SPEED
WAVELENGTH
FPSD
OFF
ON
VENDORPN1
VENDORPN2
VENDORPN3
0 to 20 characters
AINSTMR
00-00 to 96-00
ACTAINSTMR
PST
string
IS
OOS
AINS
SST
SPEED is the speed of the gigabit Ethernet client

side port.
DUPLEX is the transmission mode of the gigabit
Ethernet client side port.
is the maximum transmission unit (that is, packet
size) of the gigabit Ethernet client side port.
MEDIARATE is the Ethernet speed and duplex
rate in Mbps.
WAVELENGTH is the wavelength used by the
transceiver. This is a mandatory field for the SFP
transceivers.
FPSD is the fault propagation shutdown enabled
flag.
Vendor part numbers 1, 2 and 3 are for entering
the transceiver part number(s). If the vendor part
numbers are used, the PEC is ignored.
Note: If the vendor part number(s) are entered, the
system compares the provisioned values with the
part number(s) of the transceiver that is physically
equipped in the wavelength conversion circuit
pack.
AINSTMR is the automatic in-service timer in the
format HH-MM.
ACTAINSTMR is the active auto in-service timer.
7-133
7.10.5.7 Deleting a GE client side port
Purpose
Use this procedure to delete a gigabit Ethernet (GE) client side port of a
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
All cross-connects associated with a GE client side port must be deleted before the
GE client side port can be deleted.
The GE client side port must be out of service before it is deleted, otherwise the
CMDMDE=FRCD parameter must be used.
Procedure
To delete a GE client side port, enter the following syntax at the TL1 command
line interface:
DLT-GE:[TID]:<aid>:[CTAG]:::[CMDMDE=<cmdmde>];
where
aid
cmdmde
is MXP-(1,11,21,31)-(1-6)-(C1-C2)
NORM
FRCD
Example input
The following example shows how to delete GE client side port C1 of a

DLT-GE:NETSTENDER:MXP-1-1-C1:100:::CMDMDE=;
Example response
NETSTENDER 07-08-13 14:24:39
M
100 COMPLD
;
NETSTENDER 07-08-13 14:24:40
A
35 REPT DBCHG
DBCHGSEQ=17:DLT-GE:MXP-1-1-C1";
7.10.6 Provisioning OC-48 line side ports

This subsection discusses the provisioning of OC-48 line side ports and is
structured as follows:
7.10.6.1, Provisioning an OC-48 line side port
7.10.6.2, Enabling threshold crossing alarms on OC-48 line side ports
7.10.6.3, Modifying the provisionable parameters of an OC-48 line side port
7.10.6.4, Removing an OC-48 line side port from service
7.10.6.5, Restoring an OC-48 line side port to service
7.10.6.6, Retrieving OC-48 line side port attributes
7.10.6.7, Deleting an OC-48 line side port
7.10.6.1 Provisioning an OC-48 line side port
Purpose
Important
Use this procedure to provision an OC-48 line side port of a Muxponder circuit
pack.
When the provisioning information for an OC-48 line side port is entered, the
associated Virtual Concatenation Groups (VCGs) are automatically created. VCGs
are virtual objects that create an associationin a defined formatbetween a line
side port and a client side port. For more information about VCGs, see 7.10.8,
Retrieving Virtual Concatenation Group attributes in this document.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
procedure.
7-135
Procedure
To provision an OC-48 line side port, enter the following syntax at the TL1
ENT-OC48:[TID]:<aid>:[CTAG]:::[ID1=<id>],[FIBERTYPE=<fibertype>],
[C1=<custom>],WAVELENGTH=<wavelength>,[PHYPMMON=<phypmmon>],
[SDBER=<sdber>],[VENDORPN1=<vendorpn1>],[VENDORPN2=<vendorpn2>],
[VENDORPN3=<vendorpn3>],[PEC=<pec>],[AINSTMR=<ainstmr>]:[<pst>],[<sst>];
where
<aid>
is in the form of
MXP-(1,11,21,31)-(1-6)-(L1-L2)

The WAVELENGTH parameter for the OC-48 line side port must be provisioned.
<wavelength>
Notes:
The remaining parameters are discussed in Table 7-25, OC-48 line side port
parameters.
Example input
The following example shows how to provision OC-48 line side port L1 of a
ENT-OC48:NETSTENDER:MXP-1-1-L1:100:::WAVELENGTH=1310;
Example response
The Netstender returns a COMPLD message and the VCGs that are automatically
created:
NETSTENDER 07-08-13 14:31:49
M
100 COMPLD
;
NETSTENDER 07-08-13 14:31:50
A
39 REPT RMV OC48

"MXP-1-1-L1:OOS-AU,AINS"
;
NETSTENDER 07-08-13 14:31:50
A
40 REPT DBCHG
"TIME=14-31-50,DATE=07-08-13,SOURCE=0000,DBCHGSEQ=20:ED-OC48:
MXP-1-1-L1:::OOS-AU,AINS&FLT"
;
NETSTENDER 07-08-13 14:31:51
A
41 REPT DBCHG
"TIME=14-31-51,DATE=07-08-13,USERID=,DBCHGSEQ=21:ENT-VCG:
VCG-1-1-L1-1::FORMAT=STS1C21V,TSINDEX=1&&6&13&&21&25&&30"
;
NETSTENDER 07-08-13 14:31:51

A
42 REPT DBCHG
VCG-1-1-L1-2::FORMAT=STS1C21V,TSINDEX=7&&12&31&&45"
;
NETSTENDER 07-08-13 14:31:51
A
43 REPT DBCHG
VCG-1-1-L1-3::FORMAT=STS1C2V,TSINDEX=22&&24"
;
NETSTENDER 07-08-13 14:31:51
A
44 REPT DBCHG
VCG-1-1-L1-4::FORMAT=STS1C2V,TSINDEX=46&&48"
;
OC-48 line side port parameters
Table 7-25 lists the OC-48 line side port parameters that can be provisioned by
entering the ENT-OC48 command.
Table 7-25 OC-48 line side port parameters
Parameter
Range of Values
Description
ID1
characters
DSF
MULTIMODE
NDSF
NONE
NZDSF
characters

descriptive text.
FIBERTYPE
C1
WAVELENGTH
PHYPMMON
OFF
ON
10-5 to 10-8
SDBER

SFP transceivers.
monitoring flag.
SDBER is the signal degrade bit error rate
threshold.
7-137
Table 7-25 OC-48 line side port parameters (Continued)
Parameter
Range of Values
Description
VENDORPN1
VENDORPN2
VENDORPN3
0 to 20 characters
PEC
11 characters
AINSTMR
00-00 to 96-00
PST
IS
OOS
AINS

ignored.
ignored.
the format HH-MM.
SST
7.10.6.2 Enabling threshold crossing alarms on OC-48 line side ports

The following threshold crossing alarms are supported on the OC-48 line side
ports of the Muxponder circuit pack:
The threshold crossing alarms work on the SFP inserted in the OC-48 line side port
only if the digital diagnostics implementation (DDIAGIMP) flag is set to Y in the
inventory entry and the physical PM monitor (PHYPMMON) parameter is set to
ON for the provisioned OC-48 line side port. For information about DDIAGIMP,
see Table 7-22, Manufacturers SFP transceiver parameters.
7.10.6.3 Modifying the provisionable parameters of an OC-48 line side port
Purpose
Use this procedure to modify the provisionable parameters of an OC-48 line side
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
All cross-connects associated with an OC-48 line side port must be deleted before
the wavelength parameter can be modified.
The OC-48 line side port must be removed from service before the wavelength
used.
7-139
Procedure
To modify the provisionable parameters of an OC-48 line side port of a
Muxponder circuit pack, enter the following syntax at the TL1 command line
interface:
ED-OC48:[TID]:<aid>:[CTAG]:::[ID1=<id>],[FIBERTYPE=<fibertype>],
[C1=<custom>],[WAVELENGTH=<wavelength>],[PHYPMMON=<phypmmon>],
[VENDORPN3=<vendorpn3>],[PEC=<pec>],[AINSTMR=<ainstmr>],[CMDMDE=<cmdmde>]
:[<pst>],[<sst>];
where
aid
cmdmde
is in the form of MXP-(1,11,21,31)-(1-6)-(L1-L2)

NORM
FRCD
Note:
parameters.
Example input
The following example shows how to edit the provisionable parameters of OC-48
line side port L1 of a Muxponder circuit pack in shelf one, slot one:
ED-OC48:NETSTENDER:MXP-1-1-L1:100:::ID1=IDTEST;
Example response
NETSTENDER 07-08-13 15:11:20
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 07-08-13 15:11:21
A
47 REPT DBCHG
DBCHGSEQ=27:ED-OC48:MXP-1-1-L1::ID1=IDTEST"
;
7.10.6.4 Removing an OC-48 line side port from service
Purpose
Important
Use this procedure to remove from service an OC-48 line side port of a
Removing an OC-48 line side port from service is traffic affecting. In addition, all
SFP-related alarms are suppressed. Faults can still be queried by using the
RTRV-COND-OC48 or RTRV-COND-ALL command.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
None
Procedure
To remove an OC-48 line side port from service, enter the following syntax at the
RMV-OC48:[TID]:<aid>:[CTAG];
where
aid
Example input
The following example shows how to remove from service OC-48 line side port
L1 of a Muxponder circuit pack in shelf one, slot one:
RMV-OC48:NETSTENDER:MXP-1-1-L1:100::;
Example response
NETSTENDER 07-08-13 15:12:36
M
100 COMPLD;
NETSTENDER 07-08-13 15:12:37

A
48 REPT DBCHG
MXP-1-1-L1:::OOS-AUMA,MT&FLT";;
NETSTENDER 07-08-13 15:12:37
A
49 REPT DBCHG
DBCHGSEQ=29:RMV-OC48:MXP-1-1-L1"
;
7-141
7.10.6.5 Restoring an OC-48 line side port to service
Purpose
Important
Use this procedure to restore an OC-48 line side port of a Muxponder circuit pack
to service.
Restoring an OC-48 line side port to service enables traffic and related alarms.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
None
Procedure
To restore an OC-48 line side port to service, enter the following syntax at the TL1
RST-OC48:[TID]:<aid>:[CTAG]::::[<pst>],[<sst>];
where
parameters.
aid
Note:
Example input
The following example shows how to restore to service OC-48 line side port L1 of
a Muxponder circuit pack in shelf one, slot one:
RST-OC48:NETSTENDER:MXP-1-1-L1:100::::,;
Example response
NETSTENDER 07-08-13 15:18:52
M
100 COMPLD
;
NETSTENDER 07-08-13 15:18:54
A
215 REPT DBCHG
MXP-1-1-L1:::OOS-AU,FLT"
;
NETSTENDER 07-08-13 15:18:54
A
216 REPT DBCHG
DBCHGSEQ=46:RST-OC48:MXP-1-1-L1"
;
7.10.6.6 Retrieving OC-48 line side port attributes
Purpose
Use this procedure to retrieve the attributes of an OC-48 line side port of a
Provisioning
Superuser
Maintenance
Surveillance
Prerequisites
Ensure that the OC-48 line side port is provisioned before starting this procedure.
Procedure
To retrieve the attributes of an OC-48 line side port, enter the following syntax at
RTRV-OC48:[TID]:[<aid>]:[CTAG];
where
<aid>
Example input
The following example shows how to retrieve the attributes of an OC-48 line side
port L1 of a Muxponder circuit pack in shelf one, slot one:
RTRV-OC48:NETSTENDER:MXP-1-1-L1:100::;
7-143
Example response
and read-only parameters of the OC-48 line side port:
NETSTENDER 07-08-13 14:34:15
M
100 COMPLD
"MXP-1-1-L1:PHYPMMON=OFF,SDBER=10MINUS6,LASERSTATUS=ON,OPRHT=-7.0,
OPRLT=-50.0,OPTHT=-1.0,OPTLT=-16.0,WAVELENGTH=1310,AINSTMR=08-00,
:OOS-AU,AINS&FLT"
;
laser status and state that are returned by RTRV-OC48.
Table 7-26 Retrievable OC-48 line side port parameters
Parameter
Range of Values
Description
AID
MXP-(1,11,21,31)-(1-6)(L1,L2)
characters
characters
Access identifier of the OC-48 line side port.
ID1
C1
PEC
11 characters
PHYPMMON
OFF
ON
10-5 to 10-8
SDBER
LASERSTATUS
OPRHT
ON
OFF
place of accuracy
OPRLT

place of accuracy
OPTHT

place of accuracy

text.
optional field.
monitoring flag.
threshold.
threshold.
ON.
ON.
threshold.
ON.
Table 7-26 Retrievable OC-48 line side port parameters (Continued)
Parameter
Range of Values
Description
OPTLT

place of accuracy
FIBERTYPE
DSF
MULTIMODE
NDSF
NONE
NZDSF

threshold.
ON.
an optional field.
WAVELENGTH
VENDORPN1
VENDORPN2
VENDORPN3
0 to 20 characters
AINSTMR
00-00 to 96-00
ACTAINSTMR
PST
string
IS
OOS
AINS
SST

transceivers.
pack.
format HH-MM.
ACTAINSTMR active auto in-service timer.
7-145
7.10.6.7 Deleting an OC-48 line side port
Purpose
Important
Use this procedure to delete an OC-48 line side port of a Muxponder circuit pack.
When the provisioning information for an OC-48 line side port is deleted, the
associated Virtual Concatenation Groups (VCGs) are automatically deleted.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
All cross-connects associated with an OC-48 line side port must be deleted before
the OC-48 line side port can be deleted.
Important
An OC-48 line side port must be removed from service before it is deleted,
otherwise, the CMDMDE=FRCD parameter must be used.
An OC-48 line side port that is involved in a timing reference must be removed
from the timing reference before it can be deleted.
Procedure
To delete an OC-48 line side port of a Muxponder circuit pack, enter the following
DLT-OC48:[TID]:<aid>:[CTAG]:::[CMDMDE=<cmdmde>];
where
aid
cmdmde
is MXP-(1,11,21,31)-(1-6)-(L1-L2)
NORM
FRCD
Example input
The following example shows how to delete OC-48 line side port L1 of a
DLT-OC48:NETSTENDER:MXP-1-1-L1:100:::CMDMDE=FRCD;;
Example response
deleted:
NETSTENDER 07-08-13 15:16:46
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 07-08-13 15:16:47
A
200 REPT DBCHG

"TIME=15-16-47,DATE=07-08-13,USERID=,DBCHGSEQ=32:DLT-VCG:VCG-1-1-L1-1"
;
NETSTENDER 07-08-13 15:16:48
A
201 REPT DBCHG

;
NETSTENDER 07-08-13 15:16:48
A
202 REPT DBCHG

;
NETSTENDER 07-08-13 15:16:48
A
203 REPT DBCHG

;
NETSTENDER 07-08-13 15:16:48
A
204 REPT DBCHG
DBCHGSEQ=36:DLT-OC48:MXP-1-1-L1"
;
7-147
7.10.7 Provisioning STM-16 line side ports

This subsection discusses the provisioning of STM-16 line side ports and is
structured as follows:
7.10.7.1, Provisioning an STM-16 line side port
7.10.7.2, Enabling threshold crossing alarms on STM-16 line side ports
7.10.7.3, Modifying the provisionable parameters of an STM-16 line side port
7.10.7.4, Removing an STM-16 line side port from service
7.10.7.5, Restoring an STM-16 line side port to service
7.10.7.6, Retrieving STM-16 line side port attributes
7.10.7.7, Deleting an STM-16 line side port
7.10.7.1 Provisioning an STM-16 line side port
Purpose
Important
Use this procedure to provision an STM-16 line side port of a Muxponder circuit
pack.
When the provisioning information for an STM-16 line side port is entered, the
associated Virtual Concatenation Groups (VCGs) are automatically created. VCGs
are virtual objects that create an associationin a defined formatbetween a line
side port and a client side port. For more information about VCGs, see Retrieving
Virtual Concatenation Group attributes in this document.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
procedure.
Procedure
To provision an STM-16 line side port, enter the following syntax at the TL1
ENT-STM16:[TID]:<aid>:[CTAG]:::[ID1=<id>],[FIBERTYPE=<fibertype>],
[C1=<custom>],WAVELENGTH=<wavelength>,[PHYPMMON=<phypmmon>],
[VENDORPN3=<vendorpn3>],[PEC=<pec>],[AINSTMR=<ainstmr>]:[<pst>],[<sst>];
where
<aid>
is in the form of
MXP-(1,11,21,31)-(1-6)-(L1-L2)

The WAVELENGTH parameter for the STM-16 line side port must be
provisioned.
<wavelength
Notes:
The remaining parameters are discussed in Table 7-27, STM-16 line side port
parameters.
Example input
The following example shows how to provision STM-16 line side port L1 of a
ENT-STM16:NETSTENDER:MXP-1-6-l1:100:::WAVELENGTH=1559.79;
Example response
created:
NETSTENDER 07-07-28 13:01:53
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 07-07-28 13:01:54
A
200 REPT RMV STM16

"MXP-1-6-L1:OOS-AU,AINS"
;
NETSTENDER 07-07-28 13:01:54
A
201 REPT DBCHG
"TIME=13-01-54,DATE=07-07-28,SOURCE=0000,DBCHGSEQ=145:ED-STM16:
MXP-1-6-L1:::OOS-AU,AINS&FLT"
;
NETSTENDER 07-07-28 13:01:54
A
202 REPT DBCHG
VCG-1-6-L1-1::FORMAT=VC47V,TSINDEX=1&&2&5&&7&9&&10"
;
NETSTENDER 07-07-28 13:01:54
A
203 REPT DBCHG
7-149
VCG-1-6-L1-2::FORMAT=VC47V,TSINDEX=3&&4&11&&15"
;
NETSTENDER 07-07-28 13:01:54
A
204 REPT DBCHG
VCG-1-6-L1-3::FORMAT=VC41V,TSINDEX=8"
;
NETSTENDER 07-07-28 13:01:55
A
205 REPT DBCHG
VCG-1-6-L1-4::FORMAT=VC41V,TSINDEX=16"
;
STM-16 line side port parameters
Table 7-27 lists the STM-16 line side port parameters that can be provisioned by
entering the ENT-STM16 command.
Table 7-27 STM-16 line side port parameters
Parameter
Range of Values
Description
ID1
characters
DSF
MULTIMODE
NDSF
NONE
NZDSF
characters

descriptive text.
FIBERTYPE
C1
WAVELENGTH
PHYPMMON
OFF
ON
10-5 to 10-8
SDBER

SFP transceivers.
monitoring flag.
threshold.
Table 7-27 STM-16 line side port parameters (Continued)
Parameter
Range of Values
Description
VENDORPN1
VENDORPN2
VENDORPN3
0 to 20 characters
PEC
11 characters
AINSTMR
00-00 to 96-00
PST
IS
OOS
AINS

ignored.
ignored.
the format HH-MM.
SST
7.10.7.2 Enabling threshold crossing alarms on STM-16 line side ports

The following threshold crossing alarms are supported on the STM-16 line side
ports of the Muxponder circuit pack:
The threshold crossing alarms work on the SFP inserted in the STM-16 line side
port only if the digital diagnostics implementation (DDIAGIMP) flag is set to Y in
the inventory entry and the physical PM monitor (PHYPMMON) parameter is set
to ON for the provisioned STM-16 line side port. For information about
DDIAGIMP, see Table 7-22, Manufacturers SFP transceiver parameters.
7-151
7.10.7.3 Modifying the provisionable parameters of an STM-16 line side port
Purpose
Use this procedure to modify the provisionable parameters of an STM-16 line side
Provisioning
Superuser
Maintenance
Surveillance
Prerequisites
All cross-connects associated with an STM-16 line side port must be deleted
before the wavelength parameter can be modified.
The STM-16 line side port must be removed from service before the wavelength
used.
Procedure
To modify the provisionable parameters of an STM-16 line side port of a
Muxponder circuit pack, enter the following syntax at the TL1 command line
interface:
ED-STM16:[TID]:<aid>:[CTAG]:::[ID1=<id>],[FIBERTYPE=<fibertype>],
[C1=<custom>],[WAVELENGTH=<wavelength>],[PHYPMMON=<phypmmon>],
[SDBER=<sdber>],[VENDORPN1=<vendorpn>],[VENDORPN2=<vendorpn2>],
[VENDORPN3=<vendorpn3>],[PEC=<pec>],[AINSTMR=<ainstmr>],[CMDMDE=<cmdmde>]
:[<pst>],[<sst>];
where
aid
cmdmde

NORM
FRCD
Note:
parameters.
Example input
The following example shows how to edit the provisionable parameters of

STM-16 line side port L1 of a Muxponder circuit pack in shelf one, slot six:
ED-STM16:NETSTENDER:MXP-1-6-L1:100:::ID1=idtest;
Example response
NETSTENDER 07-07-28 13:09:34
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 07-07-28 13:09:35
A
212 REPT DBCHG
DBCHGSEQ=155:ED-STM16:MXP-1-6-L1::ID1=idtest"
;
7.10.7.4 Removing an STM-16 line side port from service
Purpose
Important
Use this procedure to remove from service an STM-16 line side port of a
Removing an STM-16 line side port from service is traffic affecting. In addition,
all SFP-related alarms are suppressed. Faults can still be queried by using the
RTRV-COND-STM16 or RTRV-COND-ALL command.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
None
Procedure
To remove an STM-16 line side port from service, enter the following syntax at the
RMV-STM16:[TID]:<aid>:[CTAG];
where
aid
Example input
The following example shows how to remove from service STM-16 line side port
L1 of a Muxponder circuit pack in shelf one, slot six:
RMV-STM16:NETSTENDER:MXP-1-6-L1:100::;
7-153
Example response
NETSTENDER 07-10-15 02:05:09
M
100 COMPLD
;
NETSTENDER>
NETSTENDER>
NETSTENDER 07-10-15 02:05:14
A
115 REPT RMV STM16

"MXP-1-6-L1:OOS-MA,MT"
;
NETSTENDER 07-10-15 02:05:14
A
116 REPT DBCHG
DBCHGSEQ=41:RMV-STM16:MXP-1-6-L1"
;
7.10.7.5 Restoring an STM-16 line side port to service
Purpose
Important
Use this procedure to restore an STM-16 line side port of a Muxponder circuit
pack to service.
Restoring an STM-16 line side port to service enables traffic and related alarms.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
None
Procedure
To restore an STM-16 line side port to service, enter the following syntax at the
RST-STM16:[TID]:<aid>:[CTAG]::::[<pst>],[<sst>];
where
parameters.
aid
Note
Example input
The following example shows how to restore to service STM-16 line side port L1
of a Muxponder circuit pack in shelf one, slot one:
RST-STM16:NETSTENDER:MXP-1-6-l1:100::::;
Example response
NETSTENDER 07-07-28 13:07:49
M
100 COMPLD
;
NETSTENDER>
NETSTENDER>
NETSTENDER 07-07-28 13:07:50
NETSTENDER 07-07-28 13:07:51
A
210 REPT DBCHG
"TIME=13-07-51,DATE=07-07-28,SOURCE=0000,DBCHGSEQ=153:ED-STM16:
MXP-1-6-L1:::OOS-AU,FLT"
;
NETSTENDER 07-07-28 13:07:51
A
211 REPT DBCHG
DBCHGSEQ=154:RST-STM16:MXP-1-6-L1"
;
7-155
7.10.7.6 Retrieving STM-16 line side port attributes
Purpose
Use this procedure to retrieve the attributes of an STM-16 line side port of a
Provisioning
Superuser
Maintenance
Surveillance
Prerequisites
Ensure that the STM-16 line side port is provisioned before starting this procedure.
Procedure
To retrieve the attributes of an STM-16 line side port, enter the following syntax at
RTRV-STM16:[TID]:<aid>:CTAG;
where
<aid>
Example input
The following example shows how to retrieve the attributes of STM-16 line side
port L1 of a Muxponder circuit pack in shelf one, slot one:
RTRV-STM16:NETSTENDER:MXP-1-6-L1;
Example response
and read-only parameters of the STM-16 line side port:
NETSTENDER 07-07-28 12:10:25
M
100 COMPLD
"MXP-1-6-L1:PHYPMMON=OFF,SDBER=10MINUS6,LASERSTATUS=OFF,OPRHT=0.0,
OPRLT=0.0,OPTHT=0.0,OPTLT=0.0,WAVELENGTH=1559.79,AINSTMR=08-00,
:OOS-AU,AINS&UEQ"
;
laser status and state returned by RTRV-STM16.
Table 7-28 Retrievable STM-16 line side port parameters
Parameter
Range of Values
Description
AID
MXP-(1,11,21,31)-(1-6)(L1,L2)
characters
characters
Access identifier of the STM-16 line side port.
ID1
C1
PEC
11 characters
PHYPMMON
OFF
ON
10-5 to 10-8
SDBER
LASERSTATUS
OPRHT
ON
OFF
place of accuracy
OPRLT

place of accuracy
OPTHT

place of accuracy
OPTLT

place of accuracy
FIBERTYPE
DSF
MULTIMODE
NDSF
NONE
NZDSF
WAVELENGTH

text.
optional field.
monitoring flag.
threshold.
threshold.
ON.
ON.
threshold.
ON.
threshold.
ON.
an optional field.

transceivers.
7-157
Table 7-28 Retrievable STM-16 line side port parameters (Continued)
Parameter
Range of Values
Description
VENDORPN1
VENDORPN2
VENDORPN3
0 to 20 characters
AINSTMR
00-00 to 96-00
ACTAINSTMR
PST
string
IS
OOS
AINS

pack.
format HH-MM.
ACTAINSTMR active auto in-service timer.
SST
7.10.7.7 Deleting an STM-16 line side port
Purpose
Important
Use this procedure to delete an STM-16 line side port of a Muxponder circuit pack.
When the provisioning information for an STM-16 line side port is deleted, the
associated Virtual Concatenation Groups (VCGs) are automatically deleted.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
All cross-connects associated with an STM-16 line side port must be deleted
before the STM-16 line side port can be deleted.
Important
An STM-16 line side port must be out of service before it is deleted, otherwise the
CMDMDE=FRCD parameter must be used.
An STM-16 line side port that is involved in a timing reference must be removed
from the timing reference before it can be deleted.
Procedure
To delete an STM-16 line side port of a Muxponder circuit pack, enter the
DLT-STM16:[TID]:<aid>:[CTAG]:::[CMDMDE=<cmdmde>];
where
aid
cmdmde
is MXP-(1,11,21,31)-(1-6)-(L1-L2)
NORM
FRCD
Example input
The following example shows how to delete STM-16 line side port L2 of a
DLT-STM16:NETSTENDER:MXP-1-6-L2:100:::CMDMDE=FRCD;
7-159
Example response
deleted:
NETSTENDER 07-07-28 12:04:36
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 07-07-28 12:04:37
A
128 REPT DBCHG

;
NETSTENDER 07-07-28 12:04:37
A
129 REPT DBCHG

;
NETSTENDER 07-07-28 12:04:37
A
130 REPT DBCHG

;
NETSTENDER 07-07-28 12:04:37
A
131 REPT DBCHG

;
NETSTENDER 07-07-28 12:04:37
A
132 REPT DBCHG
DBCHGSEQ=86:DLT-STM16:MXP-1-6-L2"
;
7.10.8 Retrieving Virtual Concatenation Group attributes
Important
A Virtual Concatenation Group (VCG) is a virtual object that creates an

associationin a defined formatbetween a line side port and a client side port of
a Muxponder circuit pack. VCGs can be looked at as non-contiguous concatenated
signals.
VCGs are created automatically when a line side port is provisioned on a
Muxponder circuit pack. When a line side port is deleted, its VCGs are
automatically deleted.
VCG formats for SONET or SDH line side ports
On a 2-Port GE Muxponder SONET (BP1A46AA), the VCGs that associate

gigabit Ethernet (GE) ports with the OC-48 line side ports are of the STS1c21v
format, and the VCGS that associate FE ports with OC-48 line side ports are of the
format STS1c3v.
On a 2-Port GE Muxponder SDH (BP1A46BA), the VCGs that associate gigabit
Ethernet (GE) ports with the STM-16 line side ports are of the VC47v format, and
the VCGS that associate FE ports with STM-16 line side ports are of the format
VC41v.
The members of each VCG are statically chosen and are fixed. The following table
lists the VCG format for the corresponding client or line side port, as well as the
VCG number.
7-161
VCGs formats
Protocol
SONET
SDH
VCG AID1
Format
VCG-1-1-L1-1
STS1c21v
VCG-1-1-L1-2
STS1c21v
VCG-1-1-L1-3
VCG-1-1-L1-4
VCG-1-1-L2-1
STS1c3v
STS1c3v
STS1c21v
VCG-1-1-L2-2
STS1c21v
VCG-1-1-L2-3
VCG-1-1-L2-4
STS1c3v
STS1c3v
VCG-1-1-L1-1
VC47v
VCG-1-1-L1-2
VC47v
VCG-1-1-L1-3
VCG-1-1-L1-4
VCG-1-1-L2-1
VC41v
VC41v
VC47v
VCG-1-1-L2-2
VC47v
VCG-1-1-L2-3
VCG-1-1-L2-4
VC41v
VC41v
VCG
index
WKG
line
1 to 6
13 to 21
25 to30
7 to 12
31 to 45
22 to 24
46 to 48
1 to 6
13 to 21
25 to30
7 to 12
31 to 45
22 to 24
46 to 48
1 to 2
5 to 7
9 to 10
3 to 4
11 to 15
8
16
1 to 2
5 to 7
9 to 10
3 to 4
11 to 15
8
16
PROT
line
GE 1
(C1)
GE 2
(C2)
FE 1
(C3)
FE 2
(C4)
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
1. VCG AID is in the form of VCG-<shelf#>-<slot#>-<L1,L2>-<VCG#>.
The following figure shows the VCGs (associations) on a Muxponder circuit pack
configured with OC-48 line side ports.
VCG and OC-48 line side port associations
OC48
GE
VCG
Client 1
GE
STS 1-6, 13-21,

25-30
Client 2
STS 7-12, 31-45
Line 1
STS 22-24
FE
STS 46-48
Client 3
Protected
FE
Line 2
Client 4
Purpose
OC48
Use this procedure to retrieve the attributes of a SONET or SDH VCG associated
with a line side port of a Muxponder circuit pack.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
To retrieve the attributes of a VCG, the line side ports (OC-48 or STM-16) of the
Muxponder circuit pack must be provisioned.
Procedure
To retrieve the attributes of a VCG, enter the following syntax at the TL1
RTRV-VCG:[TID]:[<aid>]:CTAG;
where
<aid>
is in the form of VCG-(1,11,21,31)-(1-6)-(L1-L2)-(1-4)
Example input for a SONET (OC-48) VCG
The following example shows how to retrieve information about a VCG that
associates an OC-48 line side port with a client side port on a Muxponder circuit
pack:
7-163
RTRV-VCG:NETSTENDER:VCG-1-1-L1-1:100::;
Example response
The Netstender returns a COMPLD message and values for the format and index
of the VCG:
NETSTENDER 07-08-13 15:29:56
M
100 COMPLD
"VCG-1-1-L1-1:STS1C21V:1&&6&13&&21&25&&30"
Table 7-29 lists the information fields returned by RTRV-VCG.

Table 7-29 Retrievable attributes for a SONET VCG
Parameter
Range of Values
Description
AID
VCG-(1,11,21,31)-(1-6)(L1,L2)-(1-4)
STS1C21V, STS1C3V
1&&6, 7&&12, 13&&21,
22&&24, 25&&30,
46&&48
Access identifier of the VCG.
FORMAT
TSINDEX
FORMAT is the type of concatenation.

TSINDEX is the STS1 index.
Example input for an SDH (STM-16) VCG
The following example shows how to retrieve information about a VCG that
associates an STM-16 line side port with a client side port on a Muxponder circuit
pack:
RTRV-VCG:NETSTENDER:VCG-1-6-L1-1:100::;
Example response
The Netstender returns a COMPLD message and values for the format and index
of the VCG:
NETSTENDER 07-07-28 13:16:40
M
100 COMPLD
"VCG-1-6-L1-1:VC47V:1&&2&5&&7&9&&10"
Table 7-30 lists the information fields returned by RTRV-VCG.

Table 7-30 Retrievable attributes for an SDH VCG
Parameter
Range of Values
Description
AID
VCG-(1,11,21,31)-(1-6)(L1,L2)-(1-4)
Access identifier of the VCG.
Table 7-30 Retrievable attributes for an SDH VCG (Continued)
Parameter
Range of Values
Description
FORMAT
TSINDEX
VC41V, VC47V
1&&2, 3&&4, 5&&7, 8,
9&&10, 11&&15, 16
FORMAT is the type of concatenation.

TSINDEX is the VC4 index.
7.10.9 Provisioning cross-connections on a Muxponder circuit pack

This subsection discusses the provisioning of cross-connections and is structured
as follows:
7.10.9.1, Provisioning a cross-connection on a Muxponder circuit pack
7.10.9.2, Retrieving cross-connection information from a Muxponder circuit
pack
7.10.9.3, Deleting a cross-connection on a Muxponder circuit pack
7-165
7.10.9.1 Provisioning a cross-connection on a Muxponder circuit pack
Purpose
Note
Use this procedure to provision a cross-connection that provides connectivity

between two ports on a Muxponder circuit pack.
No connectivity exists between two ports until a cross-connection is created that
associates the ports as end points.
The Muxponder circuit pack supports only the following cross-connect types:
2WAY (unprotected, bidirectional, logical; i.e., add/drop, pass-through)
Note
2WAYPR (protected, bidirectional, logical)

In a pass-through cross-connection, the Muxponder circuit pack functions as Line
Terminating Equipment.
The following figure shows a 2WAY add/drop cross-connection between a
working path (source), whose AID is in the form of VCG-(1,11,21,31)-(1-6)(L1,L2)-(1-4), and a client side port (destination), whose AID is in the form of
MXP-(1,11,21,31)-(1-6)-(C1-C4).
2WAY add/drop cross-connection
Client
Note
Working path
The following figure shows a 2WAY pass-through cross-connection between a

Virtual Concatenation Group (VCG) of a line side port (source), whose AID is in
the form of VCG-(1,11,21,31)-(1-6)-(L1,L2)-(1-4), and a VCG of the other line
side port (destination), whose AID is in the form of VCG-(1,11,21,31)-(1-6)(L1,L2)-(1-4).
To correctly provision a pass-through cross-connection, the VCG number
(that is, 1-4) specified in the destination AID must match the VCG number
specified in the source AID.
2WAY pass-through cross-connection
Working path
Working path
The following figure shows a 2WAYPR cross-connection between a working path

(source), whose AID is in the form of VCG-(1,11,21,31)-(1-6)-(L1,L2)-(1-4), and
a client side port (destination), whose AID is in the form of MXP-(1,11,21,31)-(16)-(C1-C4), with a protection path (switch mate), whose AID is in the form of
VCG-(1,11,21,31)-(1-6)-(L1,L2)-(1-4).
2WAYPR cross-connect
Working Path
Client
Protection Path
STS1 and VC4 path facility objects
Path facility objects are automatically created when a cross-connect is provisioned

on a Muxponder circuit pack.
For a 2-Port GE Muxponder SONET, each OC-48 line side port has 48 STS1
path facility objects. For a 2-Port GE Muxponder SDH, each STM-16 line side
port has 16 VC4 path facility objects.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
See Restrictions for cross-connections on a Muxponder circuit pack, which
follows this procedure.
Procedure
To provision cross-connections, enter the following syntax at the TL1 command
line interface:
ENT-CRS-VCG:[TID]:<src_aid>,<dst_aid>:[CTAG]::<cct>:[SWMATE=<swmate>];
where
<src_aid>

VCG-(1,11,21,31)-(1-6)-(L1-L2)-(1-4)
<dst_aid>

MXP-(1,11,21,31)-(1-6)-(C1-C4) or
VCG-(1,11,21,31)-(1-6)-(L1-L2)-(1-4)
7-167
is the cross-connect type, which is one of the following:
cct
2WAY
2WAYPR
swmate
is the protection AID for the path-protected

connection in the form of
VCG-(1,11,21,31)-(1-6)-(L1,L2)-(1-4)
Example
The following example shows how to provision a 2WAY add/drop crossconnection between a VCG of a line side port on a Muxponder circuit pack and a
client side port on the same Muxponder circuit pack:
ENT-CRS-VCG:NETSTENDER:VCG-1-6-L1-4,MXP-1-6-C4:100::2WAY;
Response
NETSTENDER 07-07-28 16:11:04
M
100 COMPLD
;
NETSTENDER>
NETSTENDER>
NETSTENDER 07-07-28 16:11:05
A
432 REPT DBCHG
DBCHGSEQ=179:ENT-CRS-VCG:VCG-1-6-L1-4,MXP-1-6-C4:2WAY"
;
Example
The following example shows how to provision a 2WAY pass-through crossconnection between a VCG of a line side port on a Muxponder circuit pack and a
VCG of the other line side on the same Muxponder circuit pack:
ENT-CRS-VCG:NETSTENDER:VCG-1-6-L1-4,VCG-1-6-L2-4:100::2WAY;
Response
NETSTENDER 07-07-28 16:13:10
M
100 COMPLD
;
NETSTENDER>
NETSTENDER>
NETSTENDER 07-07-28 16:13:11
A
432 REPT DBCHG
DBCHGSEQ=179:ENT-CRS-VCG:VCG-1-6-L1-4,VCG-1-6-L2-4:2WAY"
;
Example
The following example shows how to provision a 2WAYPR cross-connection

between a VCG of a line side port on a Muxponder circuit pack and a client side
port on the same Muxponder circuit pack:
ENT-CRS-VCG:NETSTENDER:VCG-1-6-L1-4,MXP-1-6-C4:100::2WAYPR:
SWMATE=VCG-1-6-L2-4;
Response
NETSTENDER 07-07-28 16:15:14
M
100 COMPLD
;
NETSTENDER 07-07-28 16:15:15
A
432 REPT DBCHG
DBCHGSEQ=183:ENT-CRS-VCG:VCG-1-6-L1-4,MXP-1-6-C4:2WAYPR"
;
Restrictions for cross-connections on a Muxponder circuit pack

1
The Muxponder circuit pack supports only the following cross-connections:
2WAY cross-connection between a client side port (GE or FE) and a line side
port
2WAY cross-connection between two line side VCGs
2WAYPR cross-connection between a client side port (GE or FE) and a line
side port
A cross-connection between two client side ports is not supported.
Once a cross-connection is created, the source AID, destination AID, and crossconnection type cannot be changed. To modify a cross-connection, delete the
existing one and then create a new cross-connection.
For an add/drop pass-through 2WAY cross-connections, a client side port (GE

or FE) can be only the destination AID and the line side VCG can be only the
source AID.
For a pass-through cross-connection, the VCG number (that is, 1-4) specified in
the destination AID must match the VCG number specified in the source AID.
For 2WAYPR cross-connections, a supported line side port (OC-48 or STM-16)

can be only the source AID.
7-169
For 2WAYPR cross-connections, a supported client side port (GE or FE) can be
only the destination AID.
For 2WAYPR cross-connections, the switch mate (SWMATE) parameter must

be specified and can be only a line side VCG AID.
7.10.9.2 Retrieving cross-connection information from a Muxponder circuit pack
Purpose
Use this procedure to retrieve cross-connect information from a Muxponder circuit

pack.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
Ensure that the cross-connection is provisioned before starting this procedure.
Procedure
To retrieve cross-connection information, enter the following syntax at the TL1
RTRV-CRS-VCG:[TID]:[<src_aid>],[<dst_aid>]:[CTAG]::[<cct>]:
[SWMATE=<swmate>]:[DISPLAY=<display>];
where
<src_aid>

VCG-(1,11,21,31)-(1-6)-(L1,L2)-(1-4)
<dst_aid>
is the destination AID in the form:
cct
MXP-(1,11,21,31)-(1-6)-(C1,C2,C3,C4)or
VCG-(1,11,21,31)-(1-6)-(L1-L2)-(1-4)
2WAY
2WAYPR
swmate
is the protection AID for the path-protected

connection in the form:
VCG-(1,11,21,31)-(1-6)-(L1,L2)-(1-4)
display
is the type of path activity, which is one of the following:

PROV
ACT
Note: Display of path activity is available for path-protected (2WAYPR)

connections only.
Example
The following example shows how to retrieve cross-connection information for a

2WAY add/drop cross-connection:
RTRV-CRS-VCG:NETSTENDER:VCG-1-6-L1-4,MXP-1-6-C4:100::;
Response
NETSTENDER 07-07-28 16:26:46
M
100 COMPLD
"VCG-1-6-L1-4,MXP-1-6-C4:2WAY::"
Example

2WAY pass-through cross-connection:
RTRV-CRS-VCG:NETSTENDER:VCG-1-6-L1-4,VCG-1-6-L2-4:100::;
Response
NETSTENDER 07-07-28 16:27:15
M
100 COMPLD
"VCG-1-6-L1-4,VCG-1-6-L2-4:2WAY::"
7-171
Example

2WAYPR cross-connection:
RTRV-CRS-VCG:NETSTENDER:VCG-1-1-L1-1,MXP-1-1-C1:100::2WAYPR:
SWMATE=VCG-1-1-L2-1
Response
NETSTENDER 07-09-14 11:50:25
M
100 COMPLD
"VCG-1-1-L1-1,MXP-1-1-C1:2WAYPR:VCG-1-1-L2-1:
7.10.9.3 Deleting a cross-connection on a Muxponder circuit pack
Purpose
Use this procedure to delete a cross-connection on a Muxponder circuit pack.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
None
Procedure
To delete a cross-connection, enter the following syntax at the TL1 command line
interface:
DLT-CRS-VCG:[TID]:<src_aid>,<dst_aid>:[CTAG]::<cct>;
where
<src_aid>

VCG-(1,11,21,31)-(1-6)-(L1-L2)-(1-4)
<dst_aid>

MXP-(1,11,21,31)-(1-6)-(C1-C4) or
VCG-(1,11,21,31)-(1-6)-(L1-L2)-(1-4)
cct

2WAY
2WAYPR
Example
DLT-CRS-VCG:NETSTENDER:VCG-1-6-L1-1,MXP-1-6-C1:100::2WAY;
Response
NETSTENDER 07-07-28 16:43:24
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 07-07-28 16:43:26
A
434 REPT DBCHG
DBCHGSEQ=181:DLT-CRS-VCG:VCG-1-6-L1-1,MXP-1-6-C1"
;
7.10.10 Provisioning protection switching on a Muxponder circuit pack

7.10.10.1 How protection switching works
The Muxponder circuit pack is Path Terminating Equipment (PTE). The transport
services it supports can be provided in either protected or unprotected form.
Protection switching is enabled only when a 2WAYPR cross-connect is
provisioned. A 2WAY cross-connect does not provide protection.
For protected services, for which protection is non-revertive, the Muxponder
circuit pack supports Unidirectional Path Switched Ring (UPSR) type protection.
Neither line side port (OC-48/STM-16) on a Muxponder circuit pack is protected.
Thus, automatic protection switching takes place on a per STS1/VC4 path facility
object basis, and not on a per line side port basis.
Individual STS1 and VC4 path facility objects can be either manually switched or
forced switched to the other line, or they can be locked out from switching to the
other line.
If a line side port has path protection enabled and a 2WAYPR cross-connect is
provisioned, putting the line side port out of service can result in a protection
switch. The following are also triggers for automatic protection switching on a
OCn Rx Loss of Signal
OCn Rx Loss of Frame
OCn Rx AIS-L
OCn Rx Signal Degrade
STS Rx AIS
7-173
STS Rx Loss of Pointer

STS Rx Unequipped
STS Rx Signal Degrade
7.10.10.2 Protection switching rules

1
A cross-connect must be provisioned on the Muxponder circuit pack before a

protection switch can be operated. See 7.10.9, Provisioning cross-connections
on a Muxponder circuit pack in this document.
The protection path must be on one of the line side ports (L1 or L2).
The protection path cannot be on the same line side port as the working path.
7.10.10.3 Operating a protection switch using an STS1 path facility object

The command to operate a protection switch using an STS1 path facility is
OPR-PROTNSW-STS1.
OPR-PROTNSW-STS1:[TID]:<aid>:[CTAG]::<sc>;
where
<aid>
is the STS1 facility AID on the line side port

in the form of MXP-(1,11,21,31)-(1-6)-(L1-L2)-(1-48)
<sc>
is the switch command that is to be initiated on

each line or path identified in the AID:
MAN
FRCD
LOCKOUT
Example
The following example shows how to operate a manual protection switch using an
STS1 path facility object:
OPR-PROTNSW-STS1:NETSTENDER:MXP-1-6-l1-1:100::MANIP 100;
Response
NETSTENDER 07-08-17 16:03:35
M
100 COMPLD
;
NETSTENDER>
NETSTENDER>
NETSTENDER 07-08-17 16:03:35
A
1522 REPT EVT STS1
"MXP-1-6-L2-1:MANWKSWPR,TC,08-17,16-03-35,,,,,:\"Active STS1 manually

switched to protection.\",,,:,"
;
7.10.10.4 Releasing an STS1 path facility object protection switch
Important
The command to release an STS1 path facility object protection switch is

RLS-PRONSW-STS1.
Only protection switches operated with the SWITCH COMMAND (<sc>)
parameter set to FRCD or LOCKOUT can be released
RLS-PRONSW-STS1:[TID]:<aid>:[CTAG];
where
<aid>
is the STS1 facility AID on the line side port

in the form of MXP-(1,11,21,31)-(1-6)-(L1-L2)-(1-48);
Example
The following example shows how to release an STS1 path facility object
protection switch:
RLS-PROTNSW-STS1:NETSTENDER:MXP-1-6-L1-1:100::;
Response
NETSTENDER 07-08-17 16:00:25
M
100 COMPLD
7.10.10.5 Operating a protection switch using a VC4 path facility object

The command to operate a protection switch using a VC4 path facility is
OPR-PROTNSW-VC4.
OPR-PROTNSW-VC4:[TID]:<aid>:CTAG;;<SC>;
where
<aid>
is the VC4 facility AID on the line side port

<SC>
is the switch command that is to be initiated on

each line or path identified in the AID:
MAN
FRCD
LOCKOUT
7-175
Example
The following example shows how to operate a manual protection switch using a
VC4 path facility object:
OPR-PROTNSW-VC4:NETSTENDER:MXP-1-6-L1-1:100::MANIP 100;
Response
NETSTENDER 07-08-17 16:05:50
M
100 COMPLD
;
NETSTENDER>
NETSTENDER>
NETSTENDER 07-08-17 16:05:50
A
1522 REPT EVT VC4
"MXP-1-6-L2-1:MANWKSWPR,TC,08-17,16-05-50,,,,,:\"Active VC4manually
switched to protection.\",,,:,"
;
7.10.10.6 Releasing a VC4 path facility object protection switch
Important
The command to release a VC4 path facility object protection switch is

RLS-PRONSW-VC4.
Only protection switches operated with the SWITCH COMMAND (<sc>)
parameter set to FRCD or LOCKOUT can be released.
RLS-PRONSW-VC4:[TID]:<aid>:[CTAG];
where
<aid>
is the VC4 facility AID on the line side port

Example
The following example shows how to release a VC4 path facility object protection
switch:
RLS-PROTNSW-VC4:NETSTENDER:MXP-1-6-L1-1:100::;
Response
NETSTENDER 07-08-17 16:06:01
M
100 COMPLD
7.11 Provisioning active mux/demux ports

When an active mux/demux circuit pack is plugged in to an unprovisioned slot, the
equipment is automatically provisioned with the primary state set to the same
value as the AUTOP flag. The AUTOP flag is set through the ED-SYS command.
Ten facility ports (one line, one expansion, and eight channels) are auto created
with default values when the active mux/demux equipment is created. This occurs
through auto provisioning or through manual provisioning using the ED-AMD
command.
The following active mux/demux commands are also available:

ED-AMD
RMV-AMD
RST-AMD
RTRV-AMD
edits active mux/demux ports.

removes active mux/demux ports from service.
restores active mux/demux ports to service
retrieves active mux/demux port provisioning information.
For further details about these commands, refer to the TL1 Reference Guide.
7-177
7.12 Provisioning non-powered circuit pack ports

Non-powered circuit packs are devices that do not require a source of energy to
function. The following Netstender circuit packs are considered non-powered
devices:
1-Channel OADM (C1ADM)
2-Channel CWDM Optical Add-Drop Module (C2ADM)
4-Channel CWDM Multiplexer/Demultiplexer Modules (C4MD)
DWDM Mux/Demux (D32MD1-4)
DWDM Optical Add-Drop Modules (D1ADM, D2ADM and D4ADM)
SMF Dispersion Compensating Fiber Modules (SMF20, SMF40, SMF60 and
SMF80)
Once these devices are entered into the Netstender using the ENT-EQPT
command, the ports on the non-powered circuit packs are automatically
provisioned by the system.
The following two commands are available for editing and retrieving non-powered
circuit pack ports:
ED-PORT
RTRV-PORT
7.12.1 Modifying the parameters of a port

Purpose
Use this procedure to modify the definable parameters of a non-powered circuit

pack port.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
Ensure that the non-powered circuit pack port is provisioned before starting this
procedure.
Procedure
Modifying the definable parameters of a port
Step
Action
Modify the definable parameters of a non-powered circuit pack

Definable parameters for a non-powered circuit pack are modified by entering the EDPORT command with the following syntax at the TL1 command line interface:
ED-PORT:[TID]:<aid>:<CTAG>[:[:[:[[ID1=<id1>][,ID2=<id2>]
[,C2=<custom2>][,C3=<custom3>]]]]];
where
TID
aid

ALL
C1ADM-(1,11,21,31)-(1-6)-1
C1ADM-(1,11,21,31)-(1-6)-1-P
C1ADM-(1,11,21,31)-(1-6)-1-(1-9)
C1ADM-(1,11,21,31)-(1-6)-(1-2)
C1ADM-(1,11,21,31)-(1-6)-(1-2)-P
C1ADM-(1,11,21,31)-(1-6)-(1-2)-(1-16)
C2ADM-(1,11,21,31)-(1-6)-1
C2ADM-(1,11,21,31)-(1-6)-1-P
C2ADM-(1,11,21,31)-(1-6)-1-(1-16)
C4MD-(1,11,21,31)-(1-6)-1
C4MD-(1,11,21,31)-(1-6)-1-E
C4MD-(1,11,21,31)-(1-6)-1-(1-16)
CDSC-(1,11,21,31)-(1-6)-1
CDSC-(1,11,21,31)-(1-6)-C
CDSC-(1,11,21,31)-(1-6)-D
7-179

Step
Action
CTAG
CS-(1,11,21,31)-(1-6)-(1-2)
CS-(1,11,21,31)-(1-6)-(1-2)-(1-9)
CS-(1,11,21,31)-(1-6)-(1-2)-D
D1ADM-(1,11,21,31)-(1-6)-1
D1ADM-(1,11,21,31)-(1-6)-1-P
D1ADM-(1,11,21,31)-(1-6)-1-(1-32)
D2ADM-(1,11,21,31)-(1-6)-1
D2ADM-(1,11,21,31)-(1-6)-1-P
D2ADM-(1,11,21,31)-(1-6)-1-(1-32)
D4ADM-(1,11,21,31)-(1,3,5)-1
D4ADM-(1,11,21,31)-(1,3,5)-1-P
D4ADM-(1,11,21,31)-(1,3,5)-1-(1-32)
D4MD-(1,11,21,31)-(1-6)-1
D4MD-(1,11,21,31)-(1-6)-1-(1-4)
D32MD1-(1,11,21,31)-(1,3,5)-1
D32MD1-(1,11,21,31)-(1,3,5)-1-U
D32MD1-(1,11,21,31)-(1,3,5)-1-(1-32)
D32MD2-(1,11,21,31)-(1,3,5)-1
D32MD2-(1,11,21,31)-(1,3,5)-1-U
D32MD2-(1,11,21,31)-(1,3,5)-1-(1-32)
D32MD3-(1,11,21,31)-(1,3,5)-1
D32MD3-(1,11,21,31)-(1,3,5)-1-U
D32MD3-(1,11,21,31)-(1,3,5)-1-(1-32)
D32MD4-(1,11,21,31)-(1,3,5)-1
D32MD4-(1,11,21,31)-(1,3,5)-1-U
D32MD4-(1,11,21,31)-(1,3,5)-1-(1-32)
OCT-(1,11,21,31)-(1-6)
SMF20-(1,11,21,31)-(1-6)-1
SMF40-(1,11,21,31)-(1-6)-1
SMF40-(1,11,21,31)-(1-6)-(1-32)
SMF60-(1,11,21,31)-(1-6)-1
SMF60-(1,11,21,31)-(1-6)-(1-32)
SMF80-(1,11,21,31)-(1-6)-1
SMF80-(1,11,21,31)-(1-6)-(1-32)
Note: The remaining parameters are discussed in Table 7-31, Non-powered circuit
pack information fields on page 7-181.

Step
Action
Example input
ED-PORT:NETSTENDER:C8MD-1-3-1:100:::C1=Under Test;
Example response
NETSTENDER 02-11-05 15:00:00

M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-11-05 15:00:01
A
170 REPT DBCHG
"TIME=12-02-38,DATE=03-11-12,SOURCE=100,LINKID=215,USERID=admin,
DBCHGSEQ=28:ED-PORT:C8MD-1-3-1::C1=Under Test"
;
Information fields
Information fields are those parameters that can be set to track specific information
about the equipment, fibers or connections. Table 7-31 lists the information fields.
Table 7-31 Non-powered circuit pack information fields
Parameter
Range of Values
Description
ID1
ID2
FIBER
DSF
NDSF
NZDSF

amplifier.
GRID
50, 100, or 200 GHz
ITU-T wavelength grid numbers for DWDM

amplifiers only.
CHNLS
0 to 40
Number of channels that are carried by the

optical amplifier.
C1, C2, C3

information.
7-181
7.12.2 Retrieving the parameters of a port

Purpose
Use this procedure to retrieve the parameters of a port.
Superuser
Provisioning
Maintenance
Surveillance
Prerequisites
Ensure that a circuit pack is provisioned before starting this procedure.
Procedure
Retrieving the parameters of a port
Step
Action
Retrieve the parameters of a port

The parameters of a port are retrieved by entering the RTRV-PORT command with the
RTRV-PORT:[TID]:[<aid>]:<CTAG>;
where
TID
aid

ALL
C1ADM-(1,11,21,31)-(1-6)-1
C1ADM-(1,11,21,31)-(1-6)-1-P
C1ADM-(1,11,21,31)-(1-6)-1-(1-9)
C1ADM-(1,11,21,31)-(1-6)-(1-2)
C1ADM-(1,11,21,31)-(1-6)-(1-2)-P
C1ADM-(1,11,21,31)-(1-6)-(1-2)-(1-16
C2ADM-(1,11,21,31)-(1-6)-1
C2ADM-(1,11,21,31)-(1-6)-1-P
C2ADM-(1,11,21,31)-(1-6)-1-(1-16)
C4MD-(1,11,21,31)-(1-6)-1
C4MD-(1,11,21,31)-(1-6)-1-E
C4MD-(1,11,21,31)-(1-6)-1-(1-16)
Retrieving the parameters of a port

Step
Action
CTAG
CDSC-(1,11,21,31)-(1-6)-1
CDSC-(1,11,21,31)-(1-6)-C
CDSC-(1,11,21,31)-(1-6)-D
CS-(1,11,21,31)-(1-6)-(1-2)
CS-(1,11,21,31)-(1-6)-(1-2)-(1-9)
CS-(1,11,21,31)-(1-6)-(1-2)-D
D1ADM-(1,11,21,31)-(1-6)-1
D1ADM-(1,11,21,31)-(1-6)-1-P
D1ADM-(1,11,21,31)-(1-6)-1-(1-32)
D4MD-(1,11,21,31)-(1-6)-1
D4MD-(1,11,21,31)-(1-6)-1-(1-4)
D32MD1-(1,11,21,31)-(1,3,5)-1
D32MD1-(1,11,21,31)-(1,3,5)-1-U
D32MD1-(1,11,21,31)-(1,3,5)-1-(1-32)
D32MD2-(1,11,21,31)-(1,3,5)-1
D32MD2-(1,11,21,31)-(1,3,5)-1-U
D32MD2-(1,11,21,31)-(1,3,5)-1-(1-32)
D32MD3-(1,11,21,31)-(1,3,5)-1
D32MD3-(1,11,21,31)-(1,3,5)-1-U
D32MD3-(1,11,21,31)-(1,3,5)-1-(1-32)
D32MD4-(1,11,21,31)-(1,3,5)-1
D32MD4-(1,11,21,31)-(1,3,5)-1-U
D32MD4-(1,11,21,31)-(1,3,5)-1-(1-32)
OCT-(1,11,21,31)-(1-6)
SMF20-(1,11,21,31)-(1-6)-1
SMF40-(1,11,21,31)-(1-6)-1
SMF40-(1,11,21,31)-(1-6)-(1-32)
SMF60-(1,11,21,31)-(1-6)-1
SMF60-(1,11,21,31)-(1-6)-(1-32)
SMF80-(1,11,21,31)-(1-6)-1
SMF80-(1,11,21,31)-(1-6)-(1-32)
Example input
RTRV-PORT:NETSTENDER::100::;
Example response
NETSTENDER 03-01-29 09:19:17

M
100 COMPLD
"SMF40-1-2-1:ID1=Ottawa,"
;
7-183
The RTRV-PORT command returns information fields about a non-powered

circuit pack port.
Information fields
Information fields are those parameters that can be set to track specific information
about the equipment, fibers or connections. Table 7-32 lists the information fields.
Parameter
Range of Values
Description
ID1
ID2
FIBER
DSF
NDSF
NZDSF

amplifier.
GRID
50, 100, or 200 GHz
ITU-T wavelength grid numbers for

DWDM amplifiers only.
CHNLS
0 to 40

carried by the optical amplifier.
C1, C2, C3
Custom fields that are available to users

to provide specific operating company
information.
Parameter
Range of Values
Description
WAVELENGTH
1271
1291
1311
1331
1351
1371
1431
1451
1471
1491
1511
1530.33
1531
1531.12
1531.90
1532.68
1533.47
1534.25
1535.04
1535.82
1538.19
1538.98
1539.77
1540.56
1541.35
1542.14
1542.94
1543.73
1546.12
1546.92
1547.72
1548.51
1549.32
1550.12
1550.92
1551
1551.72
1554.13
1554.94
1555.75
1556.55
1557.36
1558.17
1558.98
1559.79
1559.79-1530.33
1571
1591
1611
1451-1511 and 1571-1611
Wavelength is the provisioned band or

frequency.
7-185
H A P T E R
8.0 Netstender performance monitoring

This chapter discusses performance metrics (PMs), how to start and stop
monitoring, how to schedule and report performance statistics, and how to retrieve
data. The following sections explain Netstender performance monitoring:
8.1, Understanding performance monitoring data
8.2, Retrieving performance monitoring data
Netstender performance monitoring
8.1 Understanding performance monitoring data

The Netstender supports the collecting and reporting of statistical information that
can be used to assess system performance and network health. The operator can
retrieve current and historical performance metrics (PM).
PM types
The following three types of PMs are used:

Gauge takes a snapshot measurement of the PM parameter.
Counters measure the number of events that occur during a given time interval.
Accumulated Counts measure the number of events that have occurred for the
equipment since its last restart.
When users request current PMs, the PMs are retrieved directly from the
provisioned equipment at that particular moment.
Historical PMs
Historical PMs (also known as bins) are available for gauge and counter-type PMs
that are associated with each piece of equipment in the shelf. They are stored at 15minute and 24-hour intervals. The most recent 32 consecutive 15-minute bins and
one 24-hour bin are available for retrieval.
Historical PMs are not available after a system startup or an MSCP reboot until the
first interval turnover occurs. This happens just prior to the quarter hour, half hour,
three-quarter hour, and hour (for example, 10:15, 10:30, 10:45, and 11:00). The
previous days 24-hour bin is recorded at 00:00:00 of the day for gauge PMs. For
counter PMs, the value recorded is the total count of the interval.
Additionally, an untimed bin is supported for all PMs. The untimed bin (1-UNT)
accumulates indefinitely and is reset if the register capacity is exceeded (that is,
2,147,483,647) and rolls over, if the circuit pack is reset, or if the user resets the
1-UNT bin to 0 using the INIT-REG-XCVR TL1 command.
Out-of-service PMs
Performance monitoring data collection is suspended for equipment that is out of

service (OOS). Performance monitoring resumes once the equipment is back in
service (IS). When retrieving PM data, any periods for which no data was recorded
are indicated as NA (that is, not available).
Fault conditions
During some fault conditions it may not be possible to retrieve PM data from a
given circuit pack and/or the value may not be valid (for example, if the equipment
is out of service during the reporting interval). At these times the specific bins are
marked as NA (that is, not available).
Note
All PMs are read only. PMs are static and do not change once recorded in a bin,
although current counter-type PM values can be initialized to zero.
PMs are not backed up in the database. As a result, data is not recovered and all
bins are initialized on MSCP restarts.
8.1.1 PM parameter history

The following table lists the historical modifications that have occurred to the PM
parameters since Release 4.1.
Table 8-1
PM parameter history
Release
Description
4.1
The following PMs are added:

CV
CVS
ES
ESS
LITCHN
SEFS-S
SES
SES
SESS
UAS
The following two types of PMs are added:
Counters
Accumulated counts
The following PM are now applicable to XFP and MSA transceivers:
LBC
OPR
OPT
SUPPLY
TEMP
Added the 1-UNT (untimed) value to the TMPER parameter.
8.1.3, Bin validity qualifiers
8.1.4, Threshold crossing alerts
Added the following PMs:
EB
FRC
FRER
INVBLK
TFRC
Updated the following sections:
8.1, Understanding performance monitoring data
8.1.2, PM parameters
8.2.1, PM retrieval command
Removed the following PMs:
CV
UAS
5.1
8-3
Table 8-1
PM parameter history (Continued)
Release
Description
5.2
Added the following PMs for optical transceivers:

CV
ES
RS-BBE
RS-EB
RS-ES
RS-OFS
RS-SES
SEFS
Updated the following PMs:
CVS
ES
INVBLK
OPR
OPT
SEF-S
SES
Removed the following PMs:
FRC
FRER
TFRC
Added the following PMs:
CV-P
ES-P
FC-P
FCSE-RX
FRDR
HP-EB
HP-BBE
HP-ES
HP-SES
HP-UAS
NUMBITSCR
NUMBYTESCR
SES-P
TFRC-RX
TFRC-TX
UAS-P
UNCRCDWRD
6.1
Updated the following PMs:

CVS
ES
ESS
SEFS
SEFS-S
SES
SES-S
Table 8-1
PM parameter history (Continued)
Release
Description
6.2
Replaced Table 8-2 PM parameters with multiple tables. See 8.1.2, PM

parameters for information.
Added the following PMs to Table 8-7, PM Montypes: 10G Wavelength
Regenerator and Tunable 10G Wavelength Regenerator modules:
BCST
FRDR
FRGT
JABR
MCST
OSIZE
OVER1518
SESS
SIZE64
SIZE65-127
SIZE128-255
SIZE256-511
SIZE512-1023
SIZE1024-1518
TBYC-RX
TFRC-RX
USIZE.
8.1.2 PM parameters
The following sections provide information about the PMs (also known as
MONTYPEs) that are monitored for entities in the Netstender:
8.1.2.1, Optical amplifier modules
8.1.2.2, Optical Supervisory Channel modules
8.1.2.3, Transceiver ports
8.1.2.4, 2.5G Wavlength Manager modules
8.1.2.5, 10G Wavelength Regenerator modules
8.1.2.6, 2-Port GE Muxponder modules
8.1.2.7, DWDM active multiplexer/demultiplexer modules
8-5
8.1.2.1 Optical amplifier modules

The following table lists the PM Montypes supported by the following optical
amplifier modules:
DWDM C-Band Optical Booster Amplifier (OBA)
DWDM C-Band Optical Pre-Amplifier (OPA)
DWDM Optical Line Amplifier with 0 15 dB Mid-stage Access (OLAM)
Single-Channel and Sub-band Booster Amplifier (SBA)
Single-Channel and Sub-band Pre-Amplifier (SPA)
Table 8-2
PM Montypes: optical amplifier modules
Parameter
(MONTYPE)
Full Name and Description
CTEMP
Case temperature
Measures the amplifiers case temperature in degrees
Celsius.
EFFGAIN
Effective gain
Measures the amplifiers effective gain level in dB.
Note: The EFFGAIN is compensated for amplified
spontaneous emissions (ASE).
FSOOPT
First-stage output optical power transmitted

Measures the amplifiers first-stage output optical
power transmitted level in dBm.
Laser ones current
Measures the amplifiers laser number one current in
milliamperes.
L1CUR
L1PWR
L1TEMP
L2CUR
Laser ones power

Measures the amplifiers laser number one power in
milliwatts.
Laser ones temperature
Measures the amplifiers laser number one
temperature in degrees Celsius.
Laser twos current
Measures the amplifiers laser number two current in
milliamperes.
Entities
Supported
PM Type
OBA
OPA
OLA
OLAM
SBA
SPA
OBA
OPA
OLA
OLAM
SBA
SPA
OLAM
Gauge
OBA
OPA
OLA
OLAM
SBA
SPA
OLA
OLAM
Gauge
OLA
OLAM
Gauge
OBA
OPA
OLA
OLAM
SBA
SPA
Gauge
Gauge
Gauge
Gauge
Table 8-2
PM Montypes: optical amplifier modules (Continued)
Parameter
(MONTYPE)
L2PWR
Laser twos power

Measures the amplifiers laser number two power in
milliwatts.
L2TEMP
Laser twos temperature

Measures the amplifiers laser number two
MSLOSS
Mid-stage insertion loss

Measures the amplifiers mid-stage insertion loss in
dB.
Optical back reflection
Measures the amplifiers optical back reflection level
in dB.
OBR
OPR
Optical power received

Measures the amplifiers, SFP or XFP transceivers,
or active mux/demux optical power received level in
dBm.
OPT
Optical power transmitted

Measures the amplifiers, wavelength conversion SFP
or XFP transceivers, or active mux/demux optical
Note: For an active mux/demux, the OPT PM on the
line port represents the attenuated optical power
received after the variable optical attenuator.
Second-stage input optical power received
Measures the amplifiers second-stage input optical
power received level in dBm.
Variable optical attenuators attenuation
Measures the amplifiers variable optical attenuators
attenuation level in dB.
SSIOPR
VOAATN
Note
Entities
Supported
PM Type
OBA
OPA
OLA
OLAM
SBA
SPA
OBA
OPA
OLA
OLAM
SBA
SPA
OLAM
Gauge
OBA
OLA
OLAM
SBA
OBA
OPA
OLA
OLAM
SBA
SPA
OBA
OPA
OLA
OLAM
SBA
SPA
Gauge
OLAM
Gauge
OLA
OLAM
Gauge
Gauge
Gauge
Gauge
Gauge
All composite power measurements reported by optical amplifiers are accurate to

0.2 dB. As a result, gain or loss measurements may vary by 0.4 dB.
8-7
8.1.2.2 Optical Supervisory Channel modules

The following table lists the PM Montypes supported by Optical Supervisory
Channel (OSC) modules.
Table 8-3
PM Montypes: OSC modules
MONTYPE
PM Type
IPFWDDATA
IP forward datagrams
Measures the number of forwarded datagrams.
IP input receives packets
Measures the number of incoming IP packets.
IP output requests
Measures the number of outgoing request packets.
Accumulated
Count
IPINRX
IPOUTREQ
Accumulated
Count
Accumulated
Count
The following table lists the PM Montypes supported by the IP interface on OSC
modules.
Table 8-4
PM Montypes: IP interface on OSC modules
MONTYPE
PM Type
INNONUNICAST
Input non-unicast packets

Measures the number of incoming non-unicast packets.
Input unicast packets
Measures the number of incoming unicast packets.
Output non-unicast packets
Measures the number of outgoing non-unicast packets.
Output unicast packets
Measures the number of outgoing unicast packets.
Accumulated
Count
INUNICAST
OUTNONUNICAST
OUTUNICAST
Accumulated
Count
Accumulated
Count
Accumulated
Count
8.1.2.3 Transceiver ports

The following table lists the PM Montypes supported by SFP, XFP, or MSA
transceiver ports on the following wavelength conversion modules:
4-Port 1G Wavelength Translator (WT)
4-Port 2.5G Wavelength Manager SONET-SDH & Data (WM)
4-Port 1G Wavelength Regenerator (WR)
4-Port 2.5G Wavelength Regenerator (WR)
2-Port 10G Wavelength Regenerator (WR)
2-Port 10G Tunable Wavelength Regenerator (WR)
Table 8-5
PM Montypes: transceiver ports on WT, WM, and WR modules
Parameter
(MONTYPE)
LBC
OPR
OPT
SUPPLY
TEMP
Note
PM Type
Laser bias current

Measures the laser bias current, in milliamperes, of an SFP, XFP, or
MSA transceiver laser in a wavelength conversion circuit pack.
Measures the amplifiers, SFP or XFP transceivers, or active mux/
demux optical power received level in dBm.
Measures the amplifiers, wavelength conversion SFP or XFP
transceivers, or active mux/demux optical power transmitted level in
dBm.
Supply voltage
Measures the SFP or XFP transceivers supply voltage in volts.
Note: This parameter is not supported on the MSA transceiver (line 1)
of the 10G Wavelength Regenerator and Tunable 10G Wavelength
Regenerator modules.
Temperature
Measures the SFP, XFP, or MSA transceivers laser temperature in
degrees Celsius.
Gauge
Gauge
Gauge
Gauge
Gauge
For SFP transceivers, reported power measurements for OPR and OPT are accurate
to 3.0 dB.
8-9
8.1.2.4 2.5G Wavlength Manager modules

The following table lists the PM Montypes supported by the 2.5G Wavelength
Manager module.
Table 8-6
PM Montypes: 2.5G Wavelength Manager modules
MONTYPE
CV
8B/10B coding violations

Measures the number of 8B/10B coding violations.
Section coding violations
Measures the number of BIP errors detected at the
section layer.
Errored seconds
Measures the number of seconds during which one or
more errored blocks/code violations are detected, or
an SEF, LOF (Loss of Frame), or LOS (Loss of
Signal) is detected.
Section errored seconds
Measures the number of seconds during which one
section layer BIP error was detected or an SEF or an
LOS defect was present.
Laser bias current
Measures the laser bias current, in milliamperes, of an
SFP, XFP, or MSA transceiver laser in a wavelength
conversion circuit pack.
CVS
ES
ESS
LBC
OPR

dBm.
OPT

Regenerator section background block error
Measures an errored block not occurring as part of an
SES.
Regenerator section errored block
Measures one or more bits that are in error within a
block.
Regenerator section errored second
Measures a one-second period with one or more
errored blocks or at least one defect.
Regenerator section out of frame seconds
Measures the number of seconds during which a
regenerator section OFS defect was present.
RS-BBE
RS-EB
RS-ES
RS-OFS
Entities
Supported
PM Type
Gigabit Ethernet
Counter
OC-3
OC-12
OC-48
Counter
Gigabit Ethernet
Counter
OC-3
OC-12
OC-48
Counter
Gigabit Ethernet
OC-3
OC-12
OC-48
STM-16
Gigabit Ethernet
OC-3
OC-12
OC-48
STM-16
Gigabit Ethernet
OC-3
OC-12
OC-48
STM-16r
Gauge
STM-16
Counter
STM-16
Counter
STM-16
Counter
STM-16
Counter
Gauge
Gauge
Table 8-6
PM Montypes: 2.5G Wavelength Manager modules (Continued)
MONTYPE
RS-SES
Regenerator section severely errored second

Measures a one-second period that contains 30
percent or more errored blocks or at least one defect.
SES is a subset of ES.
Section severely errored framing seconds
section SEF defect was present.
Severely errored seconds
Measures the number of seconds during which
SESLVL or coding violations are detected, or an SEF
or LOF is present.
Section severely errored seconds
SESLVL or more CV errors were detected or an SEF
or LOS defect was present.
Supply voltage
Measures the SFP or XFP transceivers supply
voltage in volts.
Note: For MSA transceivers, this parameter is not
reported.
Temperature
Measures the SFP, XFP, or MSA transceivers laser
SEFS-S
SES
SESS
SUPPLY
TEMP
Entities
Supported
PM Type
STM-16
Counter
OC-48
Counter
Gigabit Ethernet
Counter
OC-48
Counter
Gigabit Ethernet
OC-3
OC-12
OC-48
STM-16
Gauge
Gigabit Ethernet
OC-3
OC-12
OC-48
STM-16
Gauge
8-11
8.1.2.5 10G Wavelength Regenerator modules

The following table lists the PM Montypes supported by the 10G Wavelength
Regenerator and Tunable 10G Wavelength Regenerator modules.:
Table 8-7
PM Montypes: 10G Wavelength Regenerator and Tunable 10G Wavelength Regenerator

modules
Parameter
(MONTYPE)
BCST
CVS
ES
ESS
FCSE-RX
FRDR
FRGT
INVBLK

Broadcast frames
Measures the total number of good frames received
that were directed to the broadcast address. (This
number does not include frames that were directed to
the multicast address.)
section layer.
Errored seconds
an SEF, LOF (Loss of Frame), or LOS (Loss of
Signal) is detected.
Total number of received frames with CRC (Cyclic
Redundancy Check) error
Measures the number of received frames that had a
valid length but had either a bad Frame Check
Sequence or a bad FCS with a non-integral number of
OCTETS (alignment errors).
Total number of discarded frames
Measures the total number of frames dropped due to
a lack of resources or other reasons. This number is
not necessarily the number of frames dropped, but
rather the number of time that dropped frames could
be detected.
Fragmented frames
Measures the total number of received frames that
were less than 64 octets long (excluding framing bits,
but including Frame Check Sequence (FCS) octets)
and had either a bad FCS with a integral number of
octets (FCS error) or a bad FCS with a non-integral
number of octets (alignment error).
Invalid blocks
Measures the number of invalid 64/66B coding blocks
for the interval.
Entities
Supported
PM Type
10GELAN
Counter
OC-192
Counter
10GELAN
10GELANFEC
Counter
OC-192
OC-192FEC
Counter
10GELAN
Counter
10GELAN
Counter
10GELAN
Counter
10GELAN
Counter
Table 8-7

modules (Continued)
Parameter
(MONTYPE)
JABR
LBC
MCST
NUMBITSCR
NUMBYTESCR
OPR
OPT
OSIZE

Jabbers
were longer than 9600 octets (excluding framing bits,
and had either a bad FCS with an integral number of
octets (FCS error) or a bad FCS with a non-integral
number of octets (alignment error).
Laser bias current
Multicast frames
Measures the total number of good frames received
that were directed to a multicast address. (This
number does not include frames that were directed to
the broadcast address.)
Number of bits corrected
Measures the total number of bits corrected by the
Forward Error Correction (FEC) decoder according to
the Reed-Solomon RS(255,239) forward error
correction scheme.
Number of bytes corrected
Measures the total number of bytes corrected by the
forward error correction scheme.
dBm.
Oversized frames
were longer than 9600 octets (excluding framing bits,
and were otherwise well formed).
Entities
Supported
PM Type
10GELAN
Counter
10GELAN
10GELANFEC
OC-192
OC192FEC
STM-64
STM64FEC
10GELAN
Gauge
Counter
10GELANFEC
OC192FEC
STM64FEC
Counter
10GELANFEC
OC192FEC
STM64FEC
Counter
10GELAN
10GELANFEC
OC-192
OC192FEC
STM-64
STM64FEC
10GELAN
10GELANFEC
OC-192
OC192FEC
STM-64
STM64FEC
Gauge
10GELAN
Counter
Gauge
8-13
Table 8-7

modules (Continued)
Parameter
(MONTYPE)
OVER1518
RS-EB
RS-ES
RS-SES
SEFS-S
SES
SESS
SIZE64
SIZE65-127
SIZE128-255
SIZE256-511

> = 1519 byte frames
Measures the total number of frames received that
were greater than or equal to 1519 bytes in length
(excluding framing bites, but including Frame Check
Sequence (FCS) octets).
block.
or LOF is present.
64 byte frames
Measures the total number of 64 byte frames received
(excluding framing bits, but including Frame Check
65 - 127 byte frames
were 65 - 127 bytes (inclusive) in length (excluding
framing bits, but including Frame Check Sequence
(FCS) octets).
(FCS) octets).
(FCS) octets).
Entities
Supported
PM Type
10GELAN
Counter
STM-64
STM-64
STM64FEC
STM-64
STM64FEC
Counter
OC-192
OC-192FEC
Counter
10GELAN
10GELANFEC
Counter
OC-192
OC192FEC
Counter
10GELAN
Counter
10GELAN
Counter
10GELAN
Counter
10GELAN
Counter
Table 8-7

modules (Continued)
Parameter
(MONTYPE)
SIZE512-1023
SIZE1024-1518
SUPPLY
TBYC-RX
TFRC-RX
TEMP
UNCRCDWRD
USIZE

(FCS) octets).
were 1024 - 1518 bytes (inclusive) in length
(excluding framing bits, but including Frame Check
Supply voltage
voltage in volts.
Note: This parameter is not supported on the MSA
transceiver (line 1) of the 10G Wavelength
Regenerator and Tunable 10G Wavelength
Regenerator modules.
Total byte count received
Measures the total number of bytes of data (including
those in bad frames) received (excluding framing bits,
but including Frame Check Sequence (FCS) octets).
Total frame count received
Measures the total number of frames (bad frames,
broadcast frames, and multicast frames) received.
Temperature
Number of uncorrectable codewords

Measures the total number of uncorrectable code
words received.
Undersized frames
were less than 64 octets long (excluding framing bits,
and were otherwise well formed.
Entities
Supported
PM Type
10GELAN
Counter
10GELAN
Counter
10GELAN
10GELANFEC
OC-192
OC192FEC
STM-64
STM64FEC
Gauge
10GELAN
Counter
10GELAN
Counter
10GELAN
10GELANFEC
OC-192
OC192FEC
STM-64
STM64FEC
10GELANFEC
OC192FEC
STM64FEC
Gauge
10GELAN
Counter
Counter
8-15
8.1.2.6 2-Port GE Muxponder modules

The following table lists the PM Montypes supported by the 2-Port GE
Muxponder SONET and 2-Port GE Muxponder SDH modules.
Table 8-8
PM Montypes: 2-Port GE Muxponder SONET and SDH modules
MONTYPE
CV
8B/10B coding violations

Measures the number of 8B/10B coding violations.
Path coding violation
Measures the number of B3 Bit Interleaved Parity
(BIP) errors at the path layer.
section layer.
Errored seconds
an SEF, LOF (Loss of Frame), or LOS (Loss of Signa)
is detected.
Path errored seconds
Measures the number of seconds during which an
AIS-P (Alarm Indicator Signal - Path) or LOP-P (Loss
of Pointer - Path) defect or a Bit Interleaved Parity
(BIP) error is detected
Failure count at path layer
Measures the number of transitions from a non SESP
second to an SES second.
Total number of received frames with CRC (Cyclic
Redundancy Check) error
Measures the number of received frames that had a
valid length but had either a bad Frame Check
Sequence or a bad FCS with a non-integral number of
OCTETS (alignment errors).
Total number of discarded frames
Measures the total number of frames dropped due to
a lack of resources or other reasons. This number is
not necessarily the number of frames dropped, but
rather the number of time that dropped frames could
be detected.
High order path background block error
Measures the number of blocks in which one or more
B3 Bit Interleaved Parity (BIP) errors are detected,
and that occur in seconds that are not counted as HPSES seconds.
CVP
CVS
ES
ESP
ESS
FC-P
FCSE-RX
FRDR
HP-BBE
Entities
Supported
PM Type
Gigabit Ethernet
Counter
STS-1 path facility

object
Counter
OC-48
Counter
Gigabit Ethernet
Counter
STS-1 path facility

object
Counter
OC-48
Counter
STS-1 path facility

object
Counter
Gigabit Ethernet
Counter
Gigabit Ethernet
Counter
VC4 path facility

objects
Counter
Table 8-8
PM Montypes: 2-Port GE Muxponder SONET and SDH modules (Continued)
MONTYPE
HP-EB
High order path errored block

Measures the number of blocks in which one or more
B3 Bit Interleaved Parity (BIP) errors are detected.
High order path errored seconds
HP-AIS or HP-LOP defect, or a B3 Bit Interleaved
Parity (BIP) error is detected.
High order path severely errored seconds
HP-AIS or HP-LOP defect is detected, or the number
of blocks in which one or more B3 Bit Interleaved
Parity (BIP) errors are detected exceeds 2400.
High order path unavailable seconds
Measures the number of seconds considered
HP-UAS. A second is considered HP-UAS at the
onset of 10 consecutive HP-SES seconds, and is no
longer considered HP-UAS after 10 consecutive
seconds that are not HP-SES seconds.
Laser bias current
dBm.
Regenerator section background block error
Measures an errored block not occurring as part of an
SES.
block.
Regenerator section out of frame seconds
regenerator section OFS defect was present.
HP-ES
HP-SES
HP-UAS
LBC
OPR
OPT
RS-BBE
RS-EB
RS-ES
RS-OFS
Entities
Supported
PM Type
VC4 path facility

objects
Counter
VC4 path facility

objects
Counter
VC4 path facility

objects
Counter
VC4 path facility

objects
Counter
Gigabit Ethernet
OC-48
STM-16
Gauge
Gigabit Ethernet
OC-48
STM-16
Transceiver
Gauge
Gigabit Ethernet
OC-48
STM-16
Gauge
STM-16
Counter
STM-16
Counter
STM-16
Counter
STM-16
Counter
8-17
Table 8-8
PM Montypes: 2-Port GE Muxponder SONET and SDH modules (Continued)
MONTYPE
RS-SES

or LOF is present.
Path severely errored seconds
AIS-P or LOP-P defect is detected, or the number of
B3 Bit Interleaved Parity (BIP) errors exceeds 2400.
Supply voltage
voltage in volts.
Note: For MSA transceivers, this parameter is not
reported.
Temperature
Total byte count in receive direction
Measures the total number of bytes of data (including
those in bad frames) received (excluding framing bits,
but including Frame Check Sequence (FCS) octets).
Total frame count in receive direction
Measures the total number of frames (bad frames,
broadcast frames, and multicast frames) received.
Path service unavailable
service at the path layer is unavailable.
SEFS-S
SES
SESP
SESS
SUPPLY
TEMP
TBYC-RX
TFRC-RX
UASP
Entities
Supported
PM Type
STM-16
Counter
OC-48
Counter
Gigabit Ethernet
Counter
STS-1 path facility

object
Counter
OC-48
Counter
Gigabit Ethernet
OC-48
STM-16
Gauge
Gigabit Ethernet
OC-48
STM-16
Gauge
Gigabit Ethernet
Counter
Gigabit Ethernet
Counter
STS-1 path facility

object
Counter
8.1.2.7 DWDM active multiplexer/demultiplexer modules

The following table lists the PM Montypes supported by the 32-Channel DWDM
Active Multiplexer/Demultiplexer modules (D32AMD1, D32AMD2, D32AMD3,
and D32AMD4).
Table 8-9
PM Montypes: DWDM active mux/demux modules
Parameter
(MONTYPE)
LITCHN
Lit channels
Measures the number of lit channels that are
provisioned and in service.
dBm.
Note: The OPT parameter on the line port represents
the attenuated optical power received after the
variable optical attenuator.
Variable optical attenuators attenuation
Measures the amplifiers variable optical attenuators
attenuation level in dB.
OPR
OPT
VOAATN
Entities
Supported
PM Type
Line ports
Gauge
Line ports
Channel ports
Gauge
Line ports
Channel ports
Gauge
Line ports
Channel ports
Gauge
8.1.3 Bin validity qualifiers

All current and historical bins have a validity qualifier that indicates the
completeness of PM data collection for the interval.
The validity of current bins can change as the bin interval progresses. The validity
of historical bins is the validity that the bin receives when its interval completes.
There are three possible bin validity qualifiers:
CMPL
NA
PRTL
CMPL
The bin validity qualifier is set to CMPL if the collection interval completes
normally. CMPL applies to counter- and gauge-type PMs.
NA
The bin validity qualifier is set to NA if there is no PM collection during the

interval when any one of the following occurs:
8-19
PM collection software fails to collect PMs for the complete duration of the
collection interval.
Equipment is out of service for the interval.
NA applies to counter- and gauge-type PMs.
PRTL
The bin validity qualifier is set to PRTL if any one of the following occurs:
The PM collection is interrupted at any time during the collection interval. This
occurs due to an SFP or XFP transceiver being taken out of service, or if the
circuit pack is inserted after the beginning of a collection interval.
The user manually sets the register to zero using the INIT-REG-XCVR
command with parameter MONVAL= 0. This is the default behavior for the
INIT-REG command) at any time during the collection interval.
Note
The system time is adjusted at any point during the collection interval.
The current interval is always PRTL for counter PMs.
PRTL applies to counter-type PMs only.
8.1.4 Threshold crossing alerts

Table 8-10 lists the threshold crossing alerts (TCA) that can be set for various
protocols.
Table 8-10 Threshold crossing alerts and their associated protocols
GE
CV
ES
FCSE-RX
FRDR
SES
1.
2.
3.
4.
5.
10GELAN
ES
FCSE-RX
FRDR
FRGT
INVBLK
JABR
SES
OSIZE
USIZE
10GELANFEC
OC192FEC
STM64FEC
1
ES
ESS2
RS-ES3
SES1
SESS2
RS-SES3
UNCRCDWRD
OC-3,
OC-12
CVS
ESS
SEFS-S
SES-S
SEFS
OC-48
OC-192
STM-16
STM-64
CVS
ESS
SEFS-S
SES-S
CV-P4
ES-P4
FC-P4
SES-P4
UAS-P4
CVS
ESS
SEFS-S
SESS
RS-BBE
RS-EB
RS-ES
RS-OFS
RS-SES
HP-BBE5
HP-EB5
HP-ES5
HP-SES5
HP-UAS5
RS-EB
RS-ES
RS-SES
Applies only to 10GELANFEC.

Applies only to OC192FEC.
Applies only to STM64FEC
Applies only to STS1 path facility objects on the 2-Port GE Muxponder SONET.
Applies only to VC4 path facility objects on the 2-Port GE Muxponder SDH.
Thresholds for these PMs are set using the SET-TH-xxxx TL1 command for the
entity (i.e., SET-TH-XCVR, SET-TH-GE, SET-TH-OC48, SET-TH-STM16,
SET-TH-STS1, SET-TH-VC4). Only the 15-minute and 1-day bins of countertype PMs are monitored for threshold crossings.
When a threshold is crossed during a 15-minute or 1-day time period, a TCA is

generated on all active TL1 or NNC login sessions in the form of a
REPTÊVT^XCVR system message.
At the beginning of the next 15-minute or 1-day time period, the current bins are
reset to zero and counting continues. If the threshold is crossed again in the new
time period, another TCA is generated.
If a new threshold value is set and then crossed because the new threshold value is
lower than the current count, a TCA is immediately generated provided a TCA has
not been sent already for that time period.
Setting the threshold to zero disables the TCA. By re-initializing the counter to
zero, the TCA is re-alarmed for that time period.
Note
To retrieve each current threshold level of one or more TCAs, use the
RTRV-TH-XCVR command.
For information about enabling SFP, XFP and MSA transceiver TCAs, refer to
Enabling threshold crossing alarms in section 7.9.2.3, Implementing advanced
provisioning features of this document.
8-21
8.2 Retrieving performance monitoring data

8.2.1 PM retrieval command
To retrieve the current or historical set of PMs associated with one piece of
equipment in the network element (for example, an optical amplifier), enter the
following at the TL1 command line interface:
RTRV-PM-OA:[TID]:[<aid>]:<CTAG>::[<montype>],[<monlev>],[<locn>],
[<dirn>],[<tmper>],[<mondat>],[<montm>],[<index>];
where
montype
is the monitoring type of the performance data.

See 8.1.2, PM parameters for a complete list of the
monitoring types.
monlev
is not implemented in this release.
locn
is the location, where

NEND
is the near-end (default)
FEND
is the far-end
dirn
is the direction, where

TRMT
is the transmitter
RCV
is the receiver (default)
tmper
is the time period (that is, either 15-MIN, 1-DAY, or 1-UNT).

The default value is 15-MIN.
Important: You can specify both mondat and montm, or index, but not all three
together.
mondat
is the date of a PM retrieval in the format of YYYY-MM-DD. The

value can also be ALL or a Null string for the current date.
The default value is NULL.
montm
is the time of a PM retrieval in the format of HH-MM-SS.

Montm must be specified precisely up to the minute of the hour
(that is, 00, 15, 30 or 45) when retrieving historical bins.
The value can also be ALL or a Null string for current PM
data. The default value is NULL.
index
is the bin index (that is, from 0 to 32, or ALL) that can be
used to specify a PM bin rather than by mondat and montm. The
default value is 0 for current PM data.
Note: If the time period is set to 15-MIN, then selecting ALL
for index results in bins 1 to 32 being retrieved. If the time
period is set to 1-DAY, the selecting ALL for index results in

one bin being retrieved for the previous days value(s).
8.2.1.1 Other PM retrieval commands

The other TL1 commands that are available to retrieve PMs include the following
commands respectively:
RTRV-PM-AMD:[TID]:<PMaid>:<CTAG>::[<montype>],[<monlev>],[<locn>],
RTRV-PM-IP:[TID]:<PMaid>:<CTAG>::[<montype>],[<monlev>],[<locn>],
RTRV-PM-OSC:[TID]:<PMaid>:<CTAG>::[<montype>],[<monlev>],[<locn>],
RTRV-PM-XCVR:[TID]:<PMaid>:<CTAG>::[<montype>],[<monlev>],[<locn>],
RTRV-PM-GE:[TID]:<aid>:[CTAG]::[<montype>],[<monlev>],[<locn>],[<dirn>],
[<tmper>],[<mondat>],[<montm>],[<index>];
RTRV-PM-OC48:[TID]:<aid>:[CTAG]::[<montype>],[<monlev>],[<locn>],
RTRV-PM-STM16:[TID]:<aid>:[CTAG]::[<montype>],[<monlev>],[<locn>],
RTRV-PM-STS1:[TID]:<aid>:[CTAG]::[<montype>],[<monlev>],[<locn>],
RTRV-PM-VC4:[TID]:<aid>:[CTAG]::[<montype>],[<monlev>],[<locn>],[<dirn>],
[<tmper>],[<mondat>],[<montm>],[<index>];
8.2.2 Retrieving current PM bins

To retrieve the current PM bins for an optical amplifier, enter the following at the
8.2.2.1 Example one

Command
RTRV-PM-OA:NETSTENDER:OLAM-1-2-1:100::,,,,,,,;
Response
Figure 8-1 explains the meaning of the various data fields in a PM.
8-23
Figure 8-1 PM format
AID
PM
Bin Validity
MONTYPE Indicator
Bin Index
Date
"OLAM-1-2-1,OA:CTEMP,22,CMPL,,,15-MIN,09-30,18-49-13,0"
Equipment
Type
PM
Value
Time Period
Time
The Netstender retrieves the requested PMs and returns a COMPLD message in
the format shown in Figure 8-2:
Figure 8-2 Sample PMs for DWDM amplifiers
NETSTENDER 02-12-31 16:22:05

M
100 COMPLD
"OLAM-1-2-1,OA:L1TEMP,25,CMPL,,,15-MIN,12-31,16-22-04,0"
"OLAM-1-2-1,OA:L2TEMP,26,CMPL,,,15-MIN,12-31,16-22-04,0"
"OLAM-1-2-1,OA:L1CUR,265.7,CMPL,,,15-MIN,12-31,16-22-04,0"
"OLAM-1-2-1,OA:L2CUR,26.2,CMPL,,,15-MIN,12-31,16-22-04,0"
"OLAM-1-2-1,OA:L1PWR,177.5,CMPL,,,15-MIN,12-31,16-22-04,0"
"OLAM-1-2-1,OA:L2PWR,7.2,CMPL,,,15-MIN,12-31,16-22-04,0"
"OLAM-1-2-1,OA:OPR,-34.4,CMPL,,,15-MIN,12-31,16-22-04,0"
"OLAM-1-2-1,OA:OPT,-5.6,CMPL,,,15-MIN,12-31,16-22-04,0"
"OLAM-1-2-1,OA:OBR,-15.4,CMPL,,,15-MIN,12-31,16-22-04,0"
"OLAM-1-2-1,OA:VOAATN,11.0,CMPL,,,15-MIN,12-31,16-22-04,0"
"OLAM-1-2-1,OA:EFFGAIN,21.8,CMPL,,,15-MIN,12-31,16-22-04,0"
"OLAM-1-2-1,OA:SSIOPR,7.2,CMPL,,,15-MIN,12-31,16-22-04,0"
"OLAM-1-2-1,OA:FSOOPT,6.9,CMPL,,,15-MIN,12-31,16-22-04,0"
"OLAM-1-2-1,OA:MSLOSS,-0.1,CMPL,,,15-MIN,12-31,16-22-04,0"
8.2.2.2 Example two

Command
RTRV-PM-XCVR:NETSTENDER:WR-1-1-1:::;
Response
NETSTENDER 05-02-03 07:59:41
M
100 COMPLD
"WR-1-1-1,XCVR:TEMP,30.4,CMPL,,,15-MIN,02-03,07-59-41,0"
"WR-1-1-1,XCVR:SUPPLY,3.2,CMPL,,,15-MIN,02-03,07-59-41,0"
"WR-1-1-1,XCVR:LBC,21,CMPL,,,15-MIN,02-03,07-59-41,0"
"WR-1-1-1,XCVR:OPR,-17.5,CMPL,,,15-MIN,02-03,07-59-41,0"
"WR-1-1-1,XCVR:OPT,-0.5,CMPL,,,15-MIN,02-03,07-59-41,0"
8.2.3 Retrieving historical PM bins

To retrieve historical PM bins for an optical amplifier, enter the following at the
Note
There are several ways to retrieve historical PMs:

specify the index between 1 and 32
ALL
retrieves index bins 1 through 32
set the mondat and the montm

ALL
retrieves all of the PMs
specific date and time retrieves only the PMs for the specified period
8.2.3.1 Example
Command
RTRV-PM-OA:NETSTENDER:OLAM-1-6-1:100::CTEMP,,,,,,,ALL;
Response
NETSTENDER 03-02-03 15:48:46
M
100 COMPLD
8-25
;
H A P T E R
9.0 Administering the Netstender

This chapter explains how to access the Netstender, understand security issues,
manage and administer users, manage logs, manage software loads, and perform
software upgrades, database backups, and restores. The following sections discuss
how to administer the Netstender:
9.1, Security management
9.2, Log management
9.3, Protection switching
9.4, Software load management
9.5, Database backup and restore
9.6, Restarting a circuit pack
9.7, Performing a loopback test through an SFP, XFP or MSA transceiver on a
Wavelength Conversion circuit pack
9.8, Performing a loopback test through a port on a Muxponder circuit pack
9.9, Configuration profiles
Administering the Netstender
9.1 Security management

9.1.1 Security user profiles
Each user profile is keyed by a user identifier (UID) and has a password identifier
(PID) for authentication purposes. Each profile is associated with a defined
security authorization level governing the access rights available to the user once
successfully logged in.
9.1.2 Security authorization levels

The Netstender supports the standard operator security authorization levels that are
defined in Telcordia TR-NWT-835. These levels are defined as follows:
Table 9-1
Authorization levels
Authorization
Level
Access Rights
Default
Timeout
Superuser
Provisioning
Maintenance
15 min.
30 min.
45 min.
Surveillance
Notes
Full access to all system operations.

Full access to all system operations except security operations.
Access to system operations except the provisioning and security
operations.
Read only access.
unlimited
The default timeouts cannot be modified.

The system prevents the editing, disabling and deleting of the last superuser userid
to ensure that there is always an account with full system access available. The
only parameter of the last superuser userid that can be modified is the password
identifier.
9.1.3 Security default userid and password

Important
The system has a default security profile with a userid of admin, a password of
admin and an access level of superuser. The default userid permits initial
connectivity to the system.
For security, it is recommended to create a new superuser profile and then delete or
disable the default userid.
The userid and password must not match each other. For example, the userid
george cannot have a password of george.
Any changes to a userid account are not applicable to the active session. Changes
only take effect once a user disconnects and then reconnects to the system.
9.1.4 Security commands and authorization level required

Table 9-2 lists the security commands that are available and the required level of
authorization that is required to use the commands.
Table 9-2
Security commands and authorization level required
Command
ALW-USER-SECU
CANC-USER-SECU
DLT-SNMP-COMMUNITY
DLT-SNMP-TRAPRCV
DLT-USER-SECU
ED-USER-SECU
ENT-SNMP-COMMUNITY
ENT-SNMP-TRAPRCV
ENT-USER-SECU
INH-USER-SECU
RTRV-ACT-USER
RTRV-ATTR-SECULOG
RTRV-SNMP-COMMUNITY
RTRV-SNMP-TRAPRCV
RTRV-USER-SECU
SET-ATTR-SECULOG
ACPT-DB-RST
CANC-DB-RST
CANC-SYS-UPGRD
CHK-SYS-UPGRD
CMMT-DB-RST
CMMT-ES
CMMT-SYS-UPGRD
DLT-ARP-PROXY
DLT-CRS-VCG
DLT-CRS-XCVR
DLT-EQPT
DLT-FE
DLT-FFP-XCVR
DLT-GE
DLT-IP
DLT-NGBR
DLT-OA
DLT-OC48
DLT-OSPF
DLT-OSPF-AREA
DLT-OSPF-IF
Superuser
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Provisioning Maintenance Surveillance
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Table 9-2
Security commands and authorization level required (Continued)
Command
Superuser
DLT-ROUTE-STATIC
DLT-STM16
DLT-XCVR
ED-AMD
ED-DAT
ED-EQPT
ED-FE
ED-FFP-XCVR
ED-GE
ED-IP
ED-NGBR
ED-OA
ED-OC48
ED-OSPF
ED-OSPF-AREA
ED-OSPF-IF
ED-PORT
ED-SER
ED-STM16
ED-SYS
ED-XCVR
ENT-ARP-PROXY
ENT-CRS-VCG
ENT-CRS-XCVR
ENT-EQPT
ENT-FE
ENT-FFP-XCVR
ENT-GE
ENT-IP
ENT-NGBR
ENT-OA
ENT-OC48
ENT-OSPF
ENT-OSPF-AREA
ENT-OSPF-IF
ENT-ROUTE-STATIC
ENT-STM16
ENT-XCVR
INIT-LOG
INIT-REG-GE
INIT-REG-OC48
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Table 9-2
Command
INIT-REG-STM16
INIT-REG-STS1
INIT-REG-VC4
INIT-REG-XCVR
INVK-DB-RST
INVK-SCP-RELNUM
INVK-SYS-UPGRD
LOAD-DB-RST
LOAD-SYS-UPGRD
SET-SID
SET-TH-GE
SET-TH-OC48
SET-TH-STM16
SET-TH-STS1
SET-TH-VC4
SET-TH-XCVR
SET-TMG-MODE
SET-TMREF
STA-LOG
STP-LOG
INIT-SYS
INVK-DB-BKUP
OPR-LPBK-GE
OPR-LPBK-OC48
OPR-LPBK-STM16
OPR-LPBK-XCVR
OPR-OBR-HTSO
OPR-PROTNSW-STS1
OPR-PROTNSW-VC4
OPR-PROTNSW-XCVR
RLS-LPBK-GE
RLS-LPBK-OC48
RLS-LPBK-STM16
RLS-LPBK-XCVR
RLS-PRONSW-STS1
RLS-PRONSW-VC4
RLS-PROTNSW-XCVR
RMV-AMD
RMV-EQPT
RMV-GE
RMV-IP
Superuser
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Table 9-2
Command
Superuser
RMV-OA
RMV-OC48
RMV-OSPF
RMV-OSPF-IF
RMV-STM16
RMV-XCVR
RST-AMD
RST-EQPT
RST-GE
RST-IP
RST-OA
RST-OC48
RST-OSPF
RST-OSPF-IF
RST-STM16
RST-XCVR
ACT-USER
ALW-MSG-ALL
CANC-USER
ED-PID
INH-MSG-ALL
RTRV-ALM-ALL
RTRV-ALM-AMD
RTRV-ALM-EQPT
RTRV-ALM-GE
RTRV-ALM-IP
RTRV-ALM-OA
RTRV-ALM-OC48
RTRV-ALM-SECU
RTRV-ALM-STM16
RTRV-ALM-STS1
RTRV-ALM-VC4
RTRV-ALM-XCVR
RTRV-AMD
RTRV-ARP-ALL
RTRV-ARP-PROXY
RTRV-ATTR-LOG
RTRV-AUTOD
RTRV-COND-ALL
RTRV-COND-AMD
RTRV-COND-EQPT
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Table 9-2
Command
RTRV-COND-GE
RTRV-COND-IP
RTRV-COND-OA
RTRV-COND-OC48
RTRV-COND-SECU
RTRV-COND-STM16
RTRV-COND-STS1
RTRV-COND-VC4
RTRV-COND-XCVR
RTRV-CRS-VCG
RTRV-CRS-XCVR
RTRV-DB-RST
RTRV-EQPT
RTRV-FE
RTRV-FFP-XCVR
RTRV-GE
RTRV-HDR
RTRV-HLP-AID
RTRV-HLP-CMD
RTRV-HLP-ENUM
RTRV-INV
RTRV-IP
RTRV-LOG
RTRV-NETYPE
RTRV-NGBR
RTRV-OA
RTRV-OC48
RTRV-OSPF
RTRV-OSPF-AREA
RTRV-OSPF-IF
RTRV-OSPF-LSDB
RTRV-OSPF-NGHBR
RTRV-PM-AMD
RTRV-PM-GE
RTRV-PM-IP
RTRV-PM-OA
RTRV-PM-OC48
RTRV-PM-OSC
RTRV-PM-STM16
RTRV-PM-STS1
RTRV-PM-VC4
Superuser
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Table 9-2
Command
Superuser
RTRV-PM-XCVR
RTRV-PORT
RTRV-ROUTE-ALL
RTRV-ROUTE-CONN
RTRV-ROUTE-OSPF
RTRV-ROUTE-STATIC
RTRV-SER
RTRV-STM16
RTRV-SYS
RTRV-SYS-RELNUM
RTRV-TH-GE
RTRV-TH-OC48
RTRV-TH-STM16
RTRV-TH-STS1
RTRV-TH-VC4
RTRV-TH-XCVR
RTRV-TMG-MODE
RTRV-TMREF
RTRV-USER
RTRV-VCG
RTRV-VERSION
RTRV-XCVR
SEND-PING
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
9.1.5 Security commands

Important
Security commands are only available to administrators with superuser

authorization.
9.1.5.1 Creating a userid, password and privilege for a user

Userids
Note
The user identifier (UID) is a unique name to identify each authorized system user.
UIDs are between 1 and 10 case-sensitive alphanumeric characters.
The Netstender supports up to 50 UIDs and up to 24 concurrent TL1 sessions. One
UID can have only one active TL1 session at a time.
Passwords
The password identifier (PID) is a confidential code to qualify the authorized

system user to access the account specified by a UID. The PID is case sensitive.
The current PID must be supplied to activate a user login session to the UID
specified, or to change the current PID to a different PID. Password identifiers are
between 6 and 10 characters in length. PIDs are a combination of alphanumeric
(letters A through Z and a through z; numbers 0 through 9) and special characters.
All special characters are supported for passwords except the following:
- = ; : , or ?
Privileges
There are four possible privileges or authorization levels for a user. See 9.1.2,
Security authorization levels for additional information about this parameter.
Procedure
To create a userid, password and privileges for a user, enter the following syntax at
ENT-USER-SECU:[TID]:<uid>:<CTAG>::<pid>,<uap>:[TIMEOUT=<timeout>];
where
uid
pid
uap
timeout
is the user identifier

is the password identifier
is the user access privilege
is the inactivity timeout parameter
Example
To create a new security record for a superuser name james with the password
october and a user access level of superuser, enter the following syntax at the
ENT-USER-SECU:NETSTENDER:james:100::october,superuser:TIMEOUT=15;
Response
The Netstender sends back a COMPLD message to indicate that you have created
a new user.
NETSTENDER 02-10-31 06:06:57
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-10-31 06:06:58
A
2 REPT DBCHG
DBCHGSEQ=1:ENT-USER-SECU:james::*,superuser:TIMEOUT=15"
;
9.1.5.2 Modifying passwords and privileges

To edit the parameters associated with a user, enter the following at the TL1
ED-USER-SECU:[TID]:<uid>:<CTAG>::,[<pid>],[<uap>]:[TIMEOUT=<timeout>];
Example
To change the password of a user named james to city23, enter the following
ED-USER-SECU:NETSTENDER:james:100::,city23,:TIMEOUT=60;
Response
The Netstender sends back a COMPLD message and a DBCHG message to

indicate that the system has changed the password:
NETSTENDER 02-10-31 06:12:20
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-10-31 06:12:21
A
3 REPT DBCHG
DBCHGSEQ=2:ED-USER-SECU:james::,*,:TIMEOUT=60";
9.1.5.3 Deleting a userid

To delete a userid, enter the following at the TL1 command line interface:
DLT-USER-SECU:[TID]:<uid>:<CTAG>;
Example
To delete a user called james, enter the following at the TL1 command line
interface:
DLT-USER-SECU:NETSTENDER:james:100::;
Response

indicate that the system has deleted the userid:
NETSTENDER 02-10-31 06:21:17
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-10-31 06:21:18
A
5 REPT DBCHG
"TIME=06-21-18,DATE=02-10-31,SOURCE=100,LINKID=2-13,USERID=james,
DBCHGSEQ=4:DLT-USER-SECU:james"
;
Note
If the userid that was deleted is the userid that is in use, the current session remains
in effect until the user ends the session and logs out.
9.1.5.4 Inhibiting a userid

To inhibit a userid, enter the following syntax at the TL1 command line interface:
INH-USER-SECU:[TID]:<uid>:<CTAG>;
Example
To inhibit the userid danny, enter the following at the TL1 command line
interface:
INH-USER-SECU:NETSTENDER:danny:100::;
Response

indicate that the command has completed successfully:
NETSTENDER 02-10-25 18:57:12
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-10-25 18:57:12
A
113 REPT DBCHG
DBCHGSEQ=24:INH-USER-SECU:danny"
;
9.1.5.5 Allowing a userid

To allow a userid, enter the following syntax at the TL1 command line interface:
ALW-USER-SECU:[TID]:<uid>:<CTAG>;
Example
To allow the userid danny, enter the following at the TL1 command line
interface:
ALW-USER-SECU:NETSTENDER:danny:100::;
Response

indicate that the command has completed successfully:
NETSTENDER 02-10-25 19:01:29
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-10-25 19:01:29
A
114 REPT DBCHG
DBCHGSEQ=25:ALW-USER-SECU:danny"
9.1.5.6 Retrieving a list of active users and cancelling a users TL1 session
Retrieve active users
To retrieve a list of active users, enter the following syntax at the TL1 command
line interface:
RTRV-ACT-USER:[TID]::<CTAG>;
Example
To retrieve a list of active users, enter the following at the TL1 command line
interface:
RTRV-ACT-USER:NETSTENDER::100;
Response
The Netstender sends back a CMPLD message indicating the active user sessions:
NETSTENDER 03-02-06 09:20:05
M
100 COMPLD
admin:superuser:192.168.172.221:3083
jeff:maintenance:192.168.172.56:3083
Cancel a users TL1 session
To cancel a users TL1 session, enter the following syntax at the TL1 command
line interface:
CANC-USER-SECU:[TID]:<uid>:<CTAG>;
Example
To cancel a users TL1 session, enter the following at the TL1 command line
interface:
CANC-USER-SECU:NETSTENDER:jeff:100::;
Response
The Netstender sends back a COMPLD message:

NETSTENDER 03-02-06 09:37:32
M
100 COMPLD
9.1.6 Common user commands

9.1.6.1 Logging in to a TL1 session
To log in to a TL1 session, enter the following syntax at the TL1 command line
interface:
Note
After three unsuccessful login attempts, a USERLCKOUT alarm is raised and a

security breach is logged. The user must wait about 60 seconds for the alarm to
clear before attempting to log in again.
Example
To log in to a TL1 session as the user admin, enter the following at the TL1
Response
The Netstender sends back a COMPLD message to indicate that the login has
completed successfully:
NETSTENDER 02-10-25 18:40:27
M
100 COMPLD
;
NETSTENDER>
Important
The system has a default security profile with a userid of admin, a password of
admin and an access level of superuser. It is recommended that you change the
default security profile during system commissioning. Although the default
password for the Netstender system is five characters in length, it is required for
security reasons to change the default password to between six and eight
characters in length.
9.1.6.2 Cancelling a TL1 session

To log out from a TL1 session, enter the following syntax at the TL1 command
line interface:
CANC-USER:[TID]:<uid>:<CTAG>;
Example
To cancel a TL1 session as the user admin, enter the following at the TL1
CANC-USER:NETSTENDER:admin:100::;
Response
The Netstender sends back a COMPLD message to indicate that the CANC-USER
command has completed successfully:
NETSTENDER 02-10-25 18:39:44
M
100 COMPLD
;
Note
Once a user logs out of the Netstender, the user should also close the telnet session.
9.1.6.3 Editing a users own password

Notes
The password must be 6 to 10 characters in length.

To edit another users password, refer to 9.1.5.2, Modifying passwords and
privileges.
To edit a users own password, enter the following at the TL1 command line
interface:
ED-PID:[TID]:<uid>:<CTAG>::<oldpid>,<newpid>;
Example
To edit a users own password from city23 to mainstn, enter the following at
ED-PID:NETSTENDER:james:100::city23,mainstn;
Response

indicate that the system has changed the password:
NETSTENDER 02-10-31 06:17:25
M
100 COMPLD
;
NETSTENDER>
NETSTENDER 02-10-31 06:17:26
A
4 REPT DBCHG
"TIME=06-17-26,DATE=02-10-31,SOURCE=100,LINKID=2-13,USERID=james,
DBCHGSEQ=3:ED-PID:james:*"
;
Note
If any subsequent changes are made to the password, only the last change is saved
by the system.
The new password is not effective until the user logs out of the current session.
9.1.6.4 Retrieving a users own security credentials

To retrieve a users own security credentials, enter the following syntax at the TL1
RTRV-USER:[TID]:[<uid>]:<CTAG>;
Example
To retrieve a users own security credentials, enter the following at the TL1
RTRV-USER:NETSTENDER:kriss1:100;
Response
The Netstender sends back a COMPLD message and the users security
credentials:
NETSTENDER 06-05-03 14:16:13
M
100 COMPLD
kriss1:,SUPERUSER:TIMEOUT=0,STATUS=IS
9.2 Log management

9.2.1 Log management history
Table 9-3 lists the historical modifications that have occurred to the logs.
Table 9-3
Log management history
Release
Description
1.0
The following log categories are introduced: alarms, commands, database changes,
events, and security.
The following log commands are introduced: ALW-LOG-SECU, INH-LOG-SECU,
INIT-LOG, INIT-LOG-SECU, RTRV-ATTR-LOG, RTRV-ATTR-SECULOG,
RTRV-LOG, SET-ATTR-SECULOG, STA-LOG, and STP-LOG.
A new operator interrupt q is added to the RTRV-LOG command.
The warning message for the SET-ATTR-SECULOG command can now be up to
70 characters in length.
Added two examples to explain how to retrieve logs selectively through the use of
filter parameters.
Modified the discussion about how to retrieve logs selectively through the use of
filter parameters.
Removed the following log commands: ALW-LOG-SECU, INH-LOG-SECU, and
INIT-LOG-SECU.
Log files are now included as part of the normal database backup process to active
circuit packs.
1.1
2.1
4.1
9.2.2 About logs on the Netstender

The Netstender maintains a log of all actions in the system. The log information is
a replica of the information sent in alarm, event and autonomous reports that are
organized into individual log categories.
All log functionality is available through the TL1 command line interface.
However, the Netstender Node Controller (NNC) provides advanced log sorting
capabilities.
By default, the Netstender is configured to maintain the following log categories:

Alarms (REPT ALM) contain all alarm raise and clear events.
Commands contain all TL1 commands issued.
Database Changes (REPT DBCHG) contain all provisioning change events.
Events (REPT EVT, REPT RMV and REPT RST) contain all of the other
events not included in the database changes category, including removals from
service, restores to service, system upgrades, circuit pack plug-ins, and circuit
pack unplugs.
Security contains all security-related events, such as, login attempts, login
failures and logouts.
ALL contains all of the logs from the previous five log categories.
Logs are retrievable by both date and time, or by general log identifier. The
general log identifier is a sequence number that increments once each time a log of
any category is recorded. Additionally, there is a second sequence number that is
the category log identifier. It increments once each time a log of its specific
category is recorded.
All logs are stored with a general log identifier that can be used for retrieval
purposes. In addition, users can stop and restart a log category (except for the
SECU category).
The log files can contain a limited number of messages. Each time a new message
is added to a log stream, the log is checked to see if it has exceeded its maximum
size. If the log has exceeded its maximum size, the oldest entry is removed from
the log. The maximum size for a log file is 1000 entries.
The log file is designed to provide at least a 24-hour period of logs for a fully
provisioned system with significant activity. If the system is lightly used, more
than a 24-hour period of logs are saved but only up to 1000 entries per category.
Note
The logs are stored persistently during MSCP restarts.

Logs are on by default.
9.2.3 Standard log commands

9.2.3.1 Retrieving logs
Purpose
Note
The RTRV-LOG command instructs a network element to retrieve the contents of

an existing message log category.
To interrupt and stop the RTRV-LOG output while in progress, type q.
Depending on the system connection speed, up to 60 log entries can still be output
after q is pressed.
Command syntax
To retrieve log information, enter the following syntax at the TL1 command line
interface:
RTRV-LOG:[TID]:[<lognm>]:<CTAG>::[<stalogid>],[<stplogid>],[<stadat>],
[<statm>],[<stpdat>],[<stptm>];
where
<lognm>
is one of the following: ALM, CMD, DBCHG, EVT, ALL, SECU.
stalogid
is the general start log identifier in the format of nnnnn.
stplogid
is the general stop log identifier in the format of nnnnn.
stadat
is the starting date of a log category in the format of

YYYY-MM-DD. The value can also be a Null string for all logs.
The default value is 0000-00-00.
statm
is the starting time of a log category in the format of

HH-MM-SS. The value can also be a Null string for all logs.
stpdat
is the stopping date of a log category in the format of

YYYY-MM-DD. The value can also be a Null string for all logs.
The default value is the current date.
is the stopping time of a log category in the format of

HH-MM-SS. The value can also be a Null string for all logs.
The range of logs retrieved can be selectively identified through the use of the
filter parameters listed above. There are basically two methods that you can use:
stptm
Note
For a range of log identifiers, enter the stalogid and or the stplogid.
For a range of logs by date and time, use any or all of the stadat, statm, stpdat
and stptm parameters with the following conditions:
Important
- if the start time is specified, the start date must also be specified
- if the stop time is specified, the stop date must also be specified
Log records are truncated after 200 characters.
Examples
Example 1
RTRV-LOG:NETSTENDER:CMD:100::,,,,,;
Response
Figure 9-1 explains the meaning of the various data fields in a Netstender log.
Figure 9-1 Log format
Log Category
Date
TID
Time
Command Entered
[NETSTENDER][CMD][01001-00996][2002-11-10][04:42:57] "RTRV-USER-SECU::ALL:2"
Log Identifiers
- first five-digits are the General Log Identifier
- second five-digits are the Category Log Identifier
The Netstender retrieves the requested log category and returns a COMPLD
message in the format shown in Figure 9-2:
Figure 9-2 Sample system logs
NETSTENDER 02-10-11 18:02:56

M
100 RTRV
[NETSTENDER] [CMD] [01148-00986] [2002-11-10] [04:30:03] "RTRV-HDR:::206"

[NETSTENDER] [CMD] [00991-00989] [2002-11-10] [04:41:49] "RTRV-USERSECU::ALL:4"
[NETSTENDER] [CMD] [00997-00993] [2002-11-10] [04:42:43] "ACTUSER::ADMIN:76:*"
[NETSTENDER] [CMD] [00999-00994] [2002-11-10] [04:42:53] "RTRV-USERSECU::ALL"
*/
>
NETSTENDER 02-10-11 18:02:58
100 COMPLD
;
Notes
The third information field in the log is a combination of two log identifiers. The
first string is the general log identifier that increments once each time a log of any
category is recorded. The second string is the category log identifier that
increments once each time a log of its specific category is recorded.
Log entries that contain a password have the password replaced by a single
asterisk (*) character.
Example 2
RTRV-LOG:NETSTENDER::100::44205,44206,,,,;
Response
NETSTENDER 04-01-05 12:02:12
M
100 RTRV
/*
[NETSTENDER] [CMD] [44205-41712] [2004-01-03] [06:13:56] "User

'admin': RTRV-OA:NETSTENDER:OLA-1-3-1:166"
[NETSTENDER] [CMD] [44206-41713] [2004-01-03] [06:14:00] "User
'admin': RTRV-PM-OA:NETSTENDER:OLA-1-3-1:167"
*/
>
NETSTENDER 04-01-05 12:02:14
M
100 COMPLD
;
In this example, a specific range of logs are retrieved by requesting the stalogid
(that is, 44205) and the stplogid (that is, 44206). The Netstender retrieves the
requested log range and returns a COMPLD message.
Example 3
RTRV-LOG:NETSTENDER:ALM:100::,,2004-02-03,07-20-00,2004-02-03,07-45-00;
Response
NETSTENDER 04-02-05 13:04:48
M
100 RTRV
/*
[NETSTENDER] [REPT-ALM-EQPT] [43973-39343] [2004-02-03] [07:20:53]

"SLOT-1-6,CL,CONTCOM,NSA,2004-02-03,07-20-53,,,,,,\"Clear communications
failure.\",,,,,"
"SLOT-1-6,MN,UPGRDPROG,NSA,2004-02-03,07-20-54,,,,,,\"Pack Upgrade In
Progress.\",,,,,"
"SLOT-1-6,CL,UPGRDPROG,NSA,2004-02-03,07-20-54,,,,,,\"Clear Pack Upgrade
In Progress.\",,,
,,"
"SLOT-1-6,MN,REPLUNITFAIL,NSA,2004-02-03,07-23-43,,,,,,\"Equipment
failure.\",,,,,"
"SLOT-1-6,CL,REPLUNITFAIL,NSA,2004-02-03,07-43-39,,,,,,\"Clear equipment
failure.\",,,,,"
*/
>
NETSTENDER 04-02-05 13:04:48
M
100 COMPLD
In this example, a specific range of alarm logs are retrieved by requesting the
stadat and statm parameters (that is, 2004-02-03 and 07-20-00) and the stpdat and
stptm parameters (that is, 2004-02-03 and 07-45-00). The Netstender retrieves the
requested log range and returns a COMPLD message.
9.2.3.2 Stopping logs

Purpose
The STP-LOG command instructs a network element to stop the logging of

messages to a specified log category immediately. When this command is
executed, a copy of it is placed in the log. Once message logging is stopped, it can
be started by using the STA-LOG command.
Note
The STP-LOG command only applies to the specified log category. If ALL is
specified, all log categories except security logs are stopped.
Security log recording can never be stopped.
Command syntax
To stop log recording, enter the following syntax at the TL1 command line
interface:
STP-LOG:[TID]:[<aid>]:<CTAG>::<lognm>;
where
<lognm>
is one of the following: ALM, CMD, DBCHG, EVT, ALL.
Example
STP-LOG:NETSTENDER::100::ALM;
Response

NETSTENDER 02-10-11 18:28:41
M
100 COMPLD
9.2.3.3 Starting logs

Purpose
The STA-LOG command instructs a network element to start the logging of

messages to a specific log category immediately. When this command is executed,
a copy of it is placed in the log. Once message logging is started, it can be stopped
by using the STP-LOG command.
Note
The STA-LOG command only applies to the specified log category. If ALL is
specified, all log categories are started.
Logging is on by default.
Command syntax
To start log recording, enter the following syntax at the TL1 command line
interface:
STA-LOG:[TID]:[<aid>]:<CTAG>::<lognm>;
where
<lognm>
Example
STA-LOG:Netstender::100::ALM;
Response

NETSTENDER 02-10-11 18:29:45
M
100 COMPLD
9.2.3.4 Initializing logs

Purpose
Notes
The INIT-LOG command instructs a network element to initialize a specified

message log category immediately. When this command is executed, it does not
change the current log attributes, but rather clears all logs currently recorded for
the specified category and resets the category log identifier specific to that
category. A copy of the command is placed in the log.
This command resets the category log identifier for the specified log category back
to one (that is, 1).
The use of this command to clear security logs is not supported.
Command syntax
To initialize log recording, enter the following syntax at the TL1 command line
interface:
INIT-LOG:[TID]:[<aid>]:<CTAG>::<lognm>;
where
<lognm>
Example
INIT-LOG:NETSTENDER::100::ALM;
Response

NETSTENDER 02-10-11 18:32:02
M
100 COMPLD
9.2.3.5 Retrieving log attributes

Purpose
The RTRV-ATTR-LOG command instructs a network element to retrieve the

current attributes for one or all of the log categories. These attributes include the
on/off status of the log category and the number of permissible logs (that is, 1000).
Command syntax
To retrieve the log attributes for a log category

RTRV-ATTR-LOG:[TID]:[<lognm>]:<CTAG>;
where
<lognm>
Example
RTRV-ATTR-LOG:NETSTENDER::100::;
Response
The Netstender retrieves the requested attributes for one or all of the log categories
in a COMPLD message:
NETSTENDER 02-10-11 16:53:36
M
100 COMPLD
"ALM, ON, 1000"
"CMD, ON, 1000"
"EVT, ON, 1000"
"DBCHG, ON, 1000"
9.2.4 Security log commands

9.2.4.1 Retrieving security log attributes
Purpose
The RTRV-ATTR-SECULOG command instructs a network element to retrieve

the current attributes for a security log. It can be used to review the attributes
before making changes with the SET-ATTR-SECULOG command. The attributes
indicate the on/off status of the log category, the number of permissible logs, and
the message the user sees when connecting to the Netstender.
Command syntax
To retrieve security log attributes, enter the following syntax at the TL1 command
line interface:
RTRV-ATTR-SECULOG:[TID]:[<aid>]:<CTAG>;
Example
RTRV-ATTR-SECULOG:NETSTENDER::100::;
Response

NETSTENDER 02-10-11 17:28:10
M
100 COMPLD
"SECU, ON, 1000"
/*
- WARNING - Only authorized personnel may access this equipment.
*/
9.2.4.2 Setting security log attributes

Purpose
The SET-ATTR-SECULOG command instructs a network element to set the

attributes for a security log. The attributes govern the message that the user sees
when connecting to the Netstender. The warning parameter is a message of up to
70 characters in length.
Command syntax
To set security log attributes, enter the following syntax at the TL1 command line
interface:
SET-ATTR-SECULOG:[TID]:[<aid>]:<CTAG>::[WARN=<warning>];
Example
SET-ATTR-SECULOG:NETSTENDER::100::WARN=" - "WARNING - Only authorized
personnel may access this equipment." ";
Response

NETSTENDER 02-10-11 17:48:12
M
100 COMPLD
9.3 Protection switching
Note
In a facility protection pair, one of the facilities serves as the working facility, and
the other serves as the protecting facility. As the protection pair works as a 1+1
non-revertive switch, the switching algorithm does not place any preference on
either of the ports to be the working facility. At any point, either the working or the
protecting facility can be carrying traffic if both are fault free.
Automatic protection switching is not available for the wavelength manager circuit
pack in this release.
Automatic protection switching occurs when a fault is detected on the working
facility, and the protecting facility is free of faults, or only less severe faults than
the working facility. Under these circumstances, an automatic protection switch
occurs to make the protecting facility the working and the working facility the
protecting.
9.3.1 Protection switching severity levels

For the purposes of protection switching, there are two severity levels relevant to
input facility faults. They are, in increasing severity:
Signal Degrade (SD)
Signal Fail (SF)
When a signal degrade is detected on a facility with the administrative state of
in-service, it is given a secondary state of abnormal (ANR). When a signal fail is
detected on a facility, it is set to the administrative state of OOS-AU. Table 9-4
lists the conditions that result in a signal degrade and signal fail for the supported
protocol types on the wavelength regenerator.
Table 9-4
Conditions that cause SD and SF faults
Protocols
Signal Degrade
Signal Fail
OC-3, OC-12, OC-48,

STM-1, STM-4, STM-16
GE, FC100, FC200
Other
None
LOS
None
None
LOS
LOS
Because the protection switching is non-revertive, once an automatic switch

occurs, traffic does not switch back to the original facility when the fault that
caused the original switch clears.
Here are a couple of examples that illustrate this behavior:
1
Protection pair A and B start with A working and B protecting, with no faults on
either facility. If an signal fail occurs on A, B becomes the working facility and
A becomes the protecting facility. If the signal fail clears on A, B remains
working and A remains protecting.
Protection pair A and B start with A working and B protecting, with no fault on
A and a signal degrade on B. If a signal fail occurs on A, B becomes the
working facility. If the signal fail clears on A, another switch occurs, making A
the working facility again and B the protecting facility.
9.3.2 User-invoked protection switches
In addition to automatic protection switches, the wavelength regenerator supports

user-invoked protection switching and user-modified protection switching through
the use of protection switching commands. To apply a protection switch, enter the
following command syntax:
OPR-PROTNSW-XCVR:[<tid>]:<aid>:<CTAG>::<sc>;
To clear the applied protection switch, enter the following command syntax:
RLS-PROTNSW-XCVR:[<tid>]:<aid>:<CTAG>;
where
aid
sc
is one of the transceivers in the provisioned protection pair.

is for switch command and it can be either
- MAN for manual
- FRCD for forced
- LOCKOUT for lockout
Manual protection switch
A manual protection switch is invoked to cause the working and protecting ports to
switch when both ports are free of faults. The rules for performing a manual
protection switch are as follows:
A manual protection switch can only operate on the working transceiver in a
protection pair.
A manual protection switch is accepted only if no other user-invoked switch is
active, and if the protecting facility is free of faults.
When a manual protection switch is invoked, the working facility becomes the
protecting facility, and the protecting facility becomes the working facility.
There are no further state changes.
Forced protection switch
A forced protection switch is invoked to cause the working and protecting ports to
switch even if the protecting facility is in a signal degrade state. The rules for
performing a forced protection switch are as follows:
A forced protection switch targets the facility in a protection pair from which
traffic is to be switched away from.
A forced protection switch can be used to switch the working facility in a
protection pair to a facility with a signal degrade fault level. It may also be used
to switch the working facility to protecting, if the protecting facility is at the

same fault severity level as the working facility (that is, either in a fault-free
state or a signal-degrade state).
A forced protection switch can be used to target the protecting facility in a
signal degrade or fault free state. This would not cause a protection switch, but
can block an automatic protection switch back to the protecting facility that
might otherwise occur.
A forced protection switch is accepted only if there is no forced or lockout
switch active on either port.
When a forced protection switch is invoked, the target facility goes to the
secondary state of FRCD.
To release a forced protection switch, the RLS-PROTNSW-XCVR command is
used, targeting the transceiver with the FRCD secondary state.
If the working facility experiences a signal fail condition while the protecting
facility is in the forced state, and is not at the signal fail fault severity level, an
automatic protection switch to protecting occurs, and the forced switch on the
protecting facility is automatically released.
Lockout protection switch
The lockout protection switch is invoked to cause the working or protecting ports
to become protecting, and to make the facility unavailable for protection.The rules
for performing a lockout protection switch are as follows:
A lockout protection switch targets the facility in a protection pair from which
traffic is to be switched away from. It can be the working or protecting facility.
When a lockout protection switch is applied to the working facility, a protection
switch immediately occurs, regardless of the state of the protecting facility.
When a lockout protection switch is invoked, the target facility goes to a
secondary state of LKDO. In this state, the facility is no longer available for
protection of the working facility.
Protecting facilities can also be locked out.
A lockout protection switch is accepted only when no other lockout switch is
active on the protection pair.
A lockout protection switch can be cancelled only when the switch is released
using the RLS-PROTNSW-XCVR command that is targeted to the transceiver
in the lockout secondary state.
9.4 Software load management

The Netstender provides two separate software loads:
Software for the Netstender network element
Software for the Netstender Node Controller (NNC)
Note
When a user logs into an NNC connected to a Netstender network element, the
NNC software automatically detects the software version that is running on the
Netstender and launches a compatible NNC version if it is on the computer. If the
NNC software is not available, the user cannot connect and needs to install the
appropriate NNC software version.
Multiple NNC versions can be installed on a computer.
For details regarding specific software upgrades, refer to the applicable Netstender
upgrade guide.
9.5 Database backup and restore

The MSCP maintains all provisionable data in non-volatile storage so that
configuration settings are retained during system shutdowns and restarts. The
configuration database is version controlled to facilitate the detection of an
incompatible software load and/or database.
The Netstender supports user-initiated backup of the configuration database. The
database is uploaded to a user-specified network location (that is, a local PC or a
remote PC) using the file transfer protocol (FTP), or it is stored locally on the
MSCP.
The Netstender supports user-initiated restore of the configuration database. The
database is restored using a version of the file from an FTP server or locally from
the MSCP. The integrity of the file is validated to ensure that it matches the current
software load on the Netstender.
For further details about the configuration database, see Appendix B: Working
with the configuration database in this document.
9.5.1 Database backup

Use this procedure to backup the database. The Netstender supports operatorinitiated backups of the provisioning database.
Three types of database backups are supported:
Local MSCP backup
Local PC FTP backup
Note
Remote PC FTP backup

A fully configured Netstender 2060 main shelf and its log files can create a backup
file of 1 MB in size. If backing up a main shelf and expansion shelves, allow for a
backup file of 2 MB in size.
What you need
None
Prerequisites
The FTP server must be set up for remote backups.

Caution
It is strongly recommended that no alarms be present on the system when a

database backup is performed.
Procedure
Use this procedure to backup the database.

Backing up the database
Step
Action
Check the available space on the FTP Server

If you intend to perform an FTP backup, confirm that the FTP server has at least the
following amounts of free space:
Main Shelf only
1 MB of free space
Main Shelf and Expansion Shelves
2 MB of free space
Invoke the backup process
Invoke the backup process by entering the following syntax at the TL1 command line
interface:
INVK-DB-BKUP:[TID]::<CTAG>::TYPE=<type>,[IPADDR=<ipaddr>],
[PATH=<path>],[USERID=<userid>],[PWD=<pwd>],[CHKALM=<chkalm>];
where
type
ipaddr
path
userid
pwd
chkalm
is either FTP or SCP.

is the IP address of where the backup file is going to
be stored (if doing an FTP backup).
is the path to the directory where the backup file is
to be stored. If TYPE=FTP, then the path must end with
a slash (/).
is the user identifier.
is the password.
is either Y or N for checking the status of alarms.
For added protection, backup the database both locally on the MSCP and remotely
through FTP.
Note: The maximum path length is 54 alphanumeric characters when TYPE=FTP and 48
alphanumeric characters when TYPE=SCP. Some UNIX systems may require that the
entire directory path and backup file name must be entered for the path field.
The system defaults to the following format for the backup file name:
NETSTENDER_<NEName>_<MONTH><DAY>_<YEAR>.
Note: If the CHKALM value is set to Y, then for the file name to function correctly one or
more alphabetic characters and the underscore must precede the NEname field.
Backing up the database (Continued)

Step
Action
Response
The system responds with the following messages:
NETSTENDER 05-12-31 16:22:02

M
100 COMPLD
;
NETSTENDER>
NETSTENDER 05-12-31 16:22:05
A
103 REPT EVT EQPT
"SCP-1-5:DBBKUPPASS,,05-12-31,16-22-04,,,,,:\"Database Backup
Completed Successfully.\",,,:,"
;
9.5.2 Database restore

Use this procedure to restore the system database.
What you need
Backup file of the database

Prerequisites
The FTP server must be set up for remote backups.

Before removing or re-initializing the MSCP, ensure that you perform a local
MSCP database backup. For added protection, a remote database backup can
also be performed.
If restoring a system with one or more expansion shelves, ensure that the MSCP
product equipment code is BP1A20BA or higher.
Caution
Ensure that the database backup file is from the network element you are about to
restore. Failure to do so could cause a loss of traffic or lock you out of the system.
Caution
Restoring the system database causes the current system data to be overwritten by
the backup data. Before you proceed, ensure that you want to replace the current
system data.
Caution
If restoring a database with communication port settings that are different from the
current settings, connectivity to the Netstender can be lost. Reconnect to the
Netstender after the restore process completes using the IP addresses that are in the
restored database.
Caution
It is strongly recommended that no alarms are present on the system when

performing a database restore.
Note
During a database restore operation, provisioning of equipment is not permitted.
Flowchart
Figure 9-3 Flowchart of database restore procedure
Database
Restore
Load database
restore file.
Retrieve database
restore file.
Invoke database
restore file.
Cancel
Accept
restore file or
cancel?
Accept
Cancel
Commit or
Cancel?
Commit
END
Procedure
Use this procedure to restore the database.

Restoring the database
Step
Action
Load the database restore file

Note: As a precaution, it is recommended that you make a local MSCP copy of the
database before proceeding. See 9.5.1, Database backup for details.
Load the database restore file by entering the following syntax at the TL1 command line
interface:
LOAD-DB-RST:[TID]::<CTAG>:::TYPE=<type>,[IPADDR=<ipaddr>],
[PATH=<path>],[USERID=<userid>],[PWD=<pwd>],[TIDCHK=<tidchk>];
where
type
ipaddr
path
userid
pwd
tidchk
is either FTP or SCP.

is the IP address of where the backup file is located.
is the database restore file name.
is the user identifier.
is the password.
is the TID check.
Notes: The maximum path length is 54 alphanumeric characters when TYPE=FTP and
48 alphanumeric characters when TYPE=SCP.
If the path specified includes the TID, then the TID in the backup file name must match
the TID of the system. However, if the default file name is changed, set TIDCHK=N.
Some UNIX systems may require that the entire directory path and backup file name
must be entered for the path field.
Response
The system responds with the message Database Load Completed Successfully:
NYC101 06-01-28 06:22:01

M
100 COMPLD
;
NETSTENDER>
NYC101 06-01-28 06:22:03
A
3 REPT EVT EQPT
"SCP-1-5:DBLOADPASS,,06-01-28,06-22-02,,,,,:\"Database Load
Completed Successfully.\",,\"[NETSTENDER_NYC101_January24_2006]
[10.1.1.100]\",:,"
;
Note: If the message Database Load Failed appears, see the Alarm and
Troubleshooting Guide to correct the error condition.
Restoring the database (Continued)

Step
Action
Retrieve the database restore file

Retrieve the database restore file that has been loaded by entering the following syntax
at the TL1 command line:
RTRV-DB-RST:[TID]::<CTAG>;
Example
RTRV-DB-RST:NYC101::100;
Response
The system responds with a message indicating the name of the database restore file
that is loaded:
NYC101 06-01-28 06:22:02

M
100 COMPLD
"[NETSTENDER_NYC101_January24_2006]";

Step
Action
Invoke the database restore process

Activate the database restore process on the MSCP by entering the following syntax at
INVK-DB-RST:[TID]::<CTAG>:::FILENAME=<filename>,
[CHKALM=<chkalm>];
where
filename
chkalm
is the name of the file.

is either Y or N for checking the status of alarms.
Note: The system defaults to the following format for the filename:
NETSTENDER_<NEName>_<MONTH><DAY>_<YEAR>. For the file name to function
correctly one or more alphabetic characters and the underscore must precede the
NEname field.
Example
INVK-DB-RST:NETSTENDER::100:::
FILENAME=NETSTENDER_NYC101_January24_2006,CHKALM=N;
Response
The system checks the image for integrity and responds with the following autonomous
event messages:
NYC101 06-01-28 06:23:05

M
100 COMPLD
;
NETSTENDER>
NYC101 03-01-28 06:23:06
** 4 REPT ALM EQPT
"SCP-1-5,MJ,DBRSTPROG,NSA,06-01-28,06-23-05,,,,,:\"Database
Restore In Progess.\",,,:,"
;
NYC101 03-01-28 06:23:06
A
5 REPT EVT EQPT
"SCP-1-5:INVKDBRSTPASS,,06-01-28,06-23-05,,,,,:\"Invoke
Database Restore Completed Successfully.\",,,:,"
;
Note: In the event that the INVK-DB-RST command fails, enter the CANC-DB-RST
command and then restart the database restore procedure.

Step
Action
Accept the database restore

If you want to cancel the database restore process, go to step 6.
If you want to accept the database restore process, follow this step.
Accept the database restore (that is, activate the database on circuit packs other than
the MSCP) by entering the following syntax at the TL1 command line interface:
ACPT-DB-RST:[TID]::<CTAG>;
Example
ACPT-DB-RST:NYC101::100;
Response
The system accepts the image and responds with the following autonomous event
message:
NYC101 06-01-28 06:23:32

M
FD COMPLD
;
NETSTENDER>
NYC101 06-01-28 06:23:33
A
6 REPT EVT EQPT
"SCP-1-5:APPLDBRSTPASS,,06-01-28,06-23-32,,,,,:\"Apply
Database Restore Completed Successfully.\",,,:,"
;

Step
Action
Commit or Cancel the database restore process

If you want to cancel the database restore process, go to step 6.
If you want to commit the database restore process, follow this step.
Note: There is no need to restart the MSCP after committing the database restore
process.
Commit the database restore process by entering the following syntax at the TL1
CMMT-DB-RST:[TID]::<CTAG>;
Example
CMMT-DB-RST:NYC101::100;
Response
NYC101 06-01-28 06:23:54

M
DF COMPLD
;
NETSTENDER>
NYC101 06-01-28 06:23:54
A
7 REPT ALM EQPT
"SCP-1-5,CL,DBRSTPROG,NSA,06-01-28,06-23-54,,,,,,\"Clear
Database Restore In Progress.\","
;

Cancel the database restore process
Cancel the database restore process by entering the following syntax at the TL1
CANC-DB-RST:[TID]::<CTAG>;
Note: If the CANC-DB-RST command is used, the system reboots, all TL1 sessions
with the Netstender end, and the user must log in to the system again.
Example
CANC-DB-RST:NYC101::100;
Response
NYC101 06-01-28 06:23:54

A
21 REPT ALM EQPT
"SCP-1-5,CL,DBRSTPROG,NSA,06-01-28,06-23-54,,,,,,\"Clear
Database Restore In Progress.\",,,,,"
;
You have successfully cancelled the database restore process.
9.6 Restarting a circuit pack

Use this procedure to restart the following circuit packs:
Optical Amplifier (OBA, OLA, OLAM, OPA, SBA and SPA)
Multiport System Control Processor (MSCP)
Wavelength Manager
When a circuit pack is restarted by the INIT-SYS command, the following events
occur:
Provisioning information is maintained.
State information is re-synchronized at start up.
Logs are maintained.
Historical performance metric (PM) bins are cleared.
Clock time is kept up to date.
Uptime is reset.
Traffic is maintained.
What you need
None
Prerequisites
None
Use this procedure to restart a circuit pack.

Re-initialize the system
Step
Action
Restart a circuit pack

INIT-SYS:[TID]:[<aid>]:<CTAG>::<ph>:[CMDMDE=<cmdmde>];
where
TID
aid
CTAG
ph

is the access identifier
is the phase of the initialization
0 is for a warm restart
1 is for a cold restart
cmdmde is the command mode
NORM is normal
FRCD is forced
Note: A warm restart of an optical active circuit pack does not
affect traffic.
A cold restart of an optical active circuit pack does
affect traffic. The device must be placed in the
out-of service (OOS) state before the cold
restart is performed, or the FRCD command mode must be used.
Example
INIT-SYS:NETSTENDER:SCP-1-5:100::1;
Response
NETSTENDER 02-11-22 18:32:02

M
100 COMPLD
;
9.7 Performing a loopback test through an SFP, XFP or MSA

transceiver on a Wavelength Conversion circuit pack
Use this procedure to perform a loopback test through an SFP, XFP or MSA
transceiver on a Wavelength Conversion circuit pack.
Perform a loopback test through an SFP, XFP or MSA transceiver
Step
Action
Remove the Transceiver from Service

To remove the transceiver from service, enter the following syntax at the TL1 command
line interface:
RMV-XCVR:[TID]:<aid>:<CTAG>;
where
<aid>
is the selected SFP or XFP transceiver port of a

wavelength conversion circuit pack in the form:
WM-<shelf#>-<slot#>-<port#> or
WR-<shelf#>-<slot#>-<port#> or
Initiate the Remote Loopback Test
To initiate the remote loopback test, enter the following syntax at the TL1 command line
interface:
OPR-LPBK-XCVR:[TID]:<aid>:<CTAG>::[<locn>],,,[<lpbktype>];
where
<aid>
is the selected SFP transceiver port of a

wavelength conversion circuit pack in the form:
is the location NEND.
is the loopback type FACILITY
<locn>
<lpbktype>
Note: For non-FEC protocols, put only one port in loopback at a time to ensure reliability
of the loopback test.
The following illustration shows the path that is established when a transceiver is set up
in the loopback mode.
SFP
Perform a loopback test through an SFP, XFP or MSA transceiver (Continued)

Step
Action
Send a Test Signal Through the Loopback Link

Send a test signal through the loopback link using a bit error rate test (BERT) or packet
generator test to check for error or problems on the link.
- If the transmitted test signal returns without a problem, the link is functioning properly.
- If the transmitted test signal encounters errors or problems, troubleshoot what may be
causing the problem.
Release the Remote Loopback Test
To release the remote loopback test, enter the following syntax at the TL1 command
line interface:
RLS-LPBK-XCVR:[TID]:<aid>:<CTAG>::[<locn>],,,[<lpbktype>];
where
<aid>
is the selected transceiver port of a wavelength

conversion circuit pack in the form:
<locn>
<lpbktype>
is the loopback type FACILITY
Restore the Transceiver to Service
RST-XCVR:[TID]:<aid>:<CTAG>;
where
<aid>
is the selected transceiver port of a wavelength

9.7.1 How to tell when an SFP, XFP or MSA transceiver port on a

Wavelength Conversion circuit pack is in loopback
9.7.1.1 RTRV-XCVR command
To determine if an SFP, XFP or MSA transceiver port is in loopback mode, enter
the following syntax at the TL1 command line interface:
RTRV-XCVR:[TID]:[<aid>]:<CTAG>;
Example
RTRV-XCVR:NETSTENDER:ALL:;
Response
The system responds with the following type of information and the state is
indicated as OOS-MA,MT&LPBK:
NETSTENDER 06-05-03 13:54:19
M
100 COMPLD
"WR-1-6-1:PROTOCOL=OC48,WAVELENGTH=1551,PHYPMMON=ON,FPSD=ON,
PEC=BP3AM1CL-04,SDBER=0,OPT-LT=0.0,OPT-HT=5.0,OPR-LT=-30.9,
OPR-HT=-6.4,LASERSTATUS=IDLE,AINSTMR=08-00,:OOS-MA,MT&LPBK"
;
Note:
The parameters OPT-LT, OPT-HT, OPR-LT, and OPR-HT do not apply to the
9.7.1.2 RTRV-COND-ALL command

To determine if an SFP, XFP or MSA transceiver port is in loopback mode, enter
the following syntax at the TL1 command line interface:
RTRV-COND-ALL:[TID]:[<aid>]:<CTAG>[:[:[<ntfcncde>],[<condtype>],
[<locn>],[<dirn>],[<tmper>]]];
Example
RTRV-COND-ALL:NETSTENDER::100::,,,;
Response
NETSTENDER 06-03-10 12:29:01
M
100 COMPLD
"WR-1-3-4,XCVR:NA,LPBK,NSA,03-10,12-28-52,NEND,,,\"Loopback.\""
9.8 Performing a loopback test through a port on a Muxponder

circuit pack
The 2-Port GE Muxponder circuit pack supports Facility loopback operations on
both gigabit Ethernet (GE) client side ports, and on both OC-48/STM-16 line side
ports.
Important
The GE client side ports support Terminal loopback; however, the OC-48/STM-16
line side ports do not support Terminal loopback.
A GE port must be cross-connected in order for a Terminal loopback operation to
be successful. For information about provisioning cross-connects, see 7.10.9,
Provisioning cross-connections on a Muxponder circuit pack.
The Fast Ethernet (FE) client ports, Virtual Concatenation Groups (VCGs), and
STS1/VC4 path facility objects of a Muxponder circuit pack do not support any
type of loopback operation.
Loopback operations are not persistent and can be performed only on a supported
port that is in the Out-of-Service (OOS) state. Performance parameters for a port
are available while the port is in a loopback state.
Loopback operations can be manually released. Once a loopback is released and
the port is restored to service, traffic continuity is immediately restored if the end
point is cross-connected.
The following figures show Facility and Terminal loopback operations on various
entities.
Line side port (L1) Facility loopback
SFP
PHY
Retimer
PHY
GE1
MAC
GFP/VCG
STS
Line 1
1-21
22-42
GE2
43-44
45-46
1-21
FE1
22-42
FE2
43-44
45-46
RJ45
FE PHY
Line 2
GE client side port (C1) Terminal loopback

SFP
PHY
Retimer
PHY
GE1
MAC
GFP/VCG
STS
Line 1
1-21
22-42
GE2
43-44
45-46
1-21
FE1
22-42
FE2
43-44
45-46
RJ45
FE PHY
Line 2
Procedure
Use this procedure to perform a loopback test through a GE client side port, or an
OC-48 or STM-16 line side port on a Muxponder circuit pack
Perform a loopback test through a port on a Muxponder circuit pack
Step
Action
Remove the Port from Service

To remove the port from service, enter the corresponding syntax at the TL1 command
line interface:
RMV-GE:[TID]:<aid>:<CTAG>; or
RMV-OC48:[TID]:<aid>:<CTAG>; or
RMV-STM16:[TID]:<aid>:<CTAG>;
where
<aid>is the selected port of a
Muxponder circuit pack in the form:
MXP-<shelf#>-<slot#>-<port#>
Initiate the Loopback Test
To initiate the loopback test, enter the corresponding syntax at the TL1 command line
interface:
OPR-LPBK-GE:[TID]:<aid>:<CTAG>::[<locn>],,,[<lpbktype>]; or
OPR-LPBK-OC48:[TID]:<aid>:<CTAG>::[<locn>],,,[<lpbktype>]; or
OPR-LPBK-STM16:[TID]:<aid>:<CTAG>::[<locn>],,,[<lpbktype>];
where
<aid>is the selected port of a
Muxponder circuit pack in the form:
<locn>is the location NEND
<lpbktype>is the loopback type FACILITY or TERMINAL
Send a Test Signal Through the Loopback Link
Send a test signal through the loopback link using a bit error rate test (BERT) or packet
generator test to check for error or problems on the link.
- If the transmitted test signal returns without a problem, the link is functioning properly.
- If the transmitted test signal encounters errors or problems, troubleshoot what may be
causing the problem.
Perform a loopback test through a port on a Muxponder circuit pack

Step
Action
Release the Loopback Test

To release the loopback test, enter the corresponding syntax at the TL1 command line
interface:
RLS-LPBK-GE:[TID]:<aid>:<CTAG>::[<locn>],,,[<lpbktype>]; or
RLS-LPBK-OC48:[TID]:<aid>:<CTAG>::[<locn>],,,[<lpbktype>]; or
RLS-LPBK-STM16:[TID]:<aid>:<CTAG>::[<locn>],,,[<lpbktype>];
where
<aid>
is the selected port of a Muxponder
circuit pack in the form: MXP-<shelf#>-<slot#>-<port#>
<locn>
<lpbktype>
is the loopback type FACILITY or TERMINAL
Restore the port to Service

To restore the port to service, enter the corresponding syntax at the TL1 command line
interface:
RST-GE:[TID]:<aid>:<CTAG>; or
RST-OC48:[TID]:<aid>:<CTAG>; or
RST-STM16:[TID]:<aid>:<CTAG>;
where
<aid> is the selected transceiver port of a wavelength
9.8.2 How to tell when a port on a Muxponder circuit pack is in loopback

9.8.2.1 RTRV-GE, RTRV-OC48, or RTRV-STM16 command
To determine if a GE client side port or an OC-48 or STM-16 line side port is in
loopback mode, enter the corresponding syntax at the TL1 command line
interface:
or
RTRV-OC48:[TID]:[<aid>]:<CTAG>; or
RTRV-GE:[TID]:[<aid>]:<CTAG>;
RTRV-STM16:[TID]:[<aid>]:<CTAG>;
Example
RTRV-GE:NETSTENDER:MXP-1-1-C2:100::;
Response
The system responds with the following type of information and the state is
indicated as OOS-MA,MT&LPBK:
NETSTENDER 07-08-13 14:27:54
M
100 COMPLD
"MXP-1-1-C2:PHYPMMON=OFF,LASERSTATUS=ON,OPRHT=-6.4,OPRLT=-30.9,
OPTHT=4.0,OPTLT=0.0,SPEED=0,MTU=9600,MEDIARATE=AUTO,WAVELENGTH=1555.75,
FPSD=OFF,MACADDRESS=0014d0000279,AINSTMR=08-00,:OOS-MA,MT&LPBK"
9.8.2.2 RTRV-COND-ALL command

To determine if GE client side port or an OC-48 or STM-16 line side port is in
loopback mode, enter the corresponding syntax at the TL1 command line
interface:
Example
RTRV-COND-ALL:NETSTENDER::100::,,,;
Response
NETSTENDER 06-03-10 12:29:01
M
100 COMPLD
"MXP-1-1-C2,GE:NA,LPBK,NSA,03-10,12-28-52,NEND,,,\"Loopback.\""
9.9 Configuration profiles

Configuration profiles are used for the bulk configuration of multiple intelligent
facilities on a circuit pack. A configuration profile can be loaded on to the facilities
of a circuit pack using the Netstender Node Controller (NNC) GUI. Profiles can
only be activated when a circuit pack and its facilities are provisioned. Profiles can
be edited online when the user is connected to the NNC, or offline.
Figure 9-4 Configuration profile for the Active Mux/Demux circuit pack
Note
In this release, configuration profiles are supported on the Active Mux/Demux

circuit pack only.
9.9.1 Creating configuration profiles

Create a profile for simultaneously configuring multiple facilities on a circuit pack,
such as the eight different channel ports on the Active Mux/Demux. A profile can
be created and edited either while working online (connected to the Netstender
using the GUI)) or offline (save the profile with a unique file name).
9.9.1.1 Creating a profile online

Creating profiles online
Step
Action
Right-click on the circuit pack and select Provision from the drop-down menu. The
Profiles window is displayed.
Click on Create to add a new profile to the list. The Create Profile window is displayed.
The values that are currently provisioned for the facilities will be displayed in the table.
Modify the data in the table and assign a name to the new profile. Click Save As when
you are done.
2
3
Click Apply to create the new profile. The profile is automatically added to the list in the
Profiles window.
Creating profiles online (Continued)

Step
Action
The Status window indicates if the file was added successfully.
9.9.1.2 Creating a profile offline

A sample template profile (for example, d32amd1_template.xls) is provided in the
installation directory of the Netstender Node Controller (NNC). The template file
can be edited using Microsoft Excel and saved with a unique file name to create a
new profile. The next time you launch the NNC, you can import the file into the
Profiles list. For more information on importing profiles, refer to 9.9.2, Importing
profiles.
9.9.2 Importing profiles

Once a configuration profile has been created offline, it can be added to the
Profiles list.
Importing profiles
Step
Action
Right-click on the circuit pack to be configured and select Provision from the drop-down
menu. The Profiles window is displayed.
Click on Import. The Import Profile window is displayed.
2
3
Select the profile from the list and click Open. The new profile will appear in the Profiles
list.
Check the Status in the Profiles window to ensure that the file was imported
successfully.
9.9.3 Applying profiles

Once a configuration profile has been created and added to the Profiles list, it can
be applied to the facilities of a circuit pack.
Applying profiles
Step
Action
Right-click on the circuit pack and select Provision... from the drop-down menu. The
Select the profile to be loaded on to the circuit pack from the Profiles list by clicking on it.
2
3
Click on Apply to load the new profile on to the circuit pack. The profile will be validated
by the system.
Check the Status in the Profiles list to ensure that the file was loaded successfully. An
error message will be displayed if the configuration profile does not contain the correct
values for the circuit pack. Select the profile from the Profiles list and click Edit to modify
the parameters in the profile.
9.9.4 Edit, view or delete profiles online

Profiles can be edited, viewed or deleted when the user is online (connected to the
NNC). When in View mode, the profile cannot be edited.
Creating profiles
Step
Action
Right-click on the circuit pack and select Provision... from the drop-down menu. The
Select the profile from the list that you want to edit, view or delete. When you click the
View or Edit button, the profile will be displayed. Click Apply to save changes or Close
to return the Profiles window.
Note: Profiles can be deleted from the list, but they wont be deleted from the directory
on the computer where they were saved.
H A P T E R
10
10.0 Replacing circuit packs

This chapter explains how to replace circuit packs. This section is organized as
follows:
10.1, Common equipment circuit packs
10.2, Optical supervisory channel circuit pack
10.3, Wavelength conversion circuit packs
10.4, Muxponder circuit packs
10.5, Optical amplifier circuit packs
10.6, Dispersion compensating module circuit packs
10.7, Filler circuit packs
10.8, Multiplex/demultiplex module circuit packs
10.9, Optical add-drop module circuit packs
Caution
Note
10.10, DWDM bi-directional coupler/splitter circuit packs

Electrostatic discharge (ESD) is the release of stored static electricity that can
damage electrical circuitry. Static electricity is often stored in your body, and
discharged when you come in contact with something with a different potential. The
ESD wrist strap safely channels this electricity from your body to a proper ground
(the shelf).
Use an ESD wrist strap whenever you open the Netstender, particularly when you
are handling circuit packs. To work properly, the wrist strap must make good
contact at both ends (that is, with your skin at one end, and with the shelf at the
other).
To minimize the interference of optical cables crossing in front of circuit pack
slots, provision slots two, four and six first.
Replacing circuit packs
10.1 Common equipment circuit packs

The Netstender 1030 shelf and the Netstender 2060 shelf both contain common
equipment circuit packs and optional packs.
10.1.1 Netstender 2060 common equipment circuit packs

10.1.1.1 Netstender 2060 common equipment circuit pack locations
The Netstender 2060 shelf includes both common equipment and optional circuit
packs. The Netstender 2060 common equipment includes:
Netstender 2060 Cooling Unit circuit pack
Netstender 2060 Main Shelf Interface circuit pack
Netstender 2060 Expansion Shelf Interface circuit pack
Netstender 2060 System Control Processor circuit pack
The following figure shows the common equipment circuit packs for the
Netstender 2060 main shelf.
Netstender 2060 Main Shelf common equipment circuit packs
Main Shelf Interface or Expansion Shelf Interface
ESD
2
PEC
BP1A20BA
Shelf-11
REL 01
Shelf-21
Shelf-31
OSC 1
OSC 2
SCP
6
Craft
Serial
Fail
Craft
Eth
Active
Cooling Unit
Note
Aux
Eth
Expansion Shelf Ports
OSC Ports
Multiport System Control Processor
An Expansion Shelf Interface circuit pack is only required in a Netstender 2060

Expansion Shelf.
For information about the initial installation of the common equipment circuit
packs, refer to the Installation and Commissioning Guide.
10.1.1.2 Netstender 2060 Cooling Unit circuit pack

Use this procedure to replace a Netstender 2060 Cooling Unit circuit pack.
What you need

Netstender 2060 Cooling Unit (CU) either BP1A52AA, BP1A52BA or
BP1A52CA
Note: The BP1A52BA or BP1A52CA must be installed when 10G Wavelength
Regenerator circuit packs are installed in the shelf.
Prerequisites
None
Caution
Note
The cooling unit is a hot-swappable system component. If replacement of the
cooling unit takes more than 15 minutes to complete, Netstender circuit packs may
generate CTEMPHT and CTEMPHTS alarms.
The following figures show the Netstender 2060 Cooling Unit circuit packs
BP1A52AA, BP1A52BA, and BP1A52CA, and their key features for this
procedure.
10-3
Netstender 2060 Cooling Units BP1A52AA and BP1A52BA key features
Handle
Screw
Netstender Cooling Unit BP1A52CA key features
andle
Screw
Replacing a Netstender 2060 Cooling Unit circuit pack

Step
Action
Move Cables
Shelf cables may need to be moved aside to get clear access to the cooling unit. The
cables rest on the handle that is at the front of the cooling unit tray.
Loosen Faceplate Screw
a) Facing the front of the Netstender, locate the faceplate screw.

b) Using a Phillips screwdriver, loosen the screw.
Remove Cooling Unit Tray
a) Grasp the handle on the front of the cooling unit and firmly pull the cooling unit
straight out.
Note: A fan missing alarm appears once you remove the cooling unit tray.
b) Place the cooling unit tray on a flat work surface.

Step
Action
Replace Cooling Unit Tray
a) Align the replacement cooling unit to the slot in which the cooling unit is being
replaced.
b) Carefully push the circuit pack straight into the slot until the circuit pack LEDs turn on.
Both LEDs remain on 5 to 10 seconds and then go off, after which the green LED
remains on.
Replace Faceplate Screw
a) Facing the front of the Netstender, align the cooling unit with its mounting hole.
b) Using a slot-head or Phillips screwdriver, carefully tighten the faceplate screw.

Replace Cables
If any cables were moved to access the cooling unit, replace the cables to their original
locations.
10-5
10.1.1.3 Netstender 2060 Main Shelf Interface circuit pack

Use this procedure to replace a Netstender 2060 Main Shelf Interface (MSI) circuit
pack.
What you need

Netstender 2060 Main Shelf Interface (MSI) circuit pack
Prerequisites
If you need to replace both an MSI circuit pack and a System Control Processor
(SCP) circuit pack, replace the MSI circuit pack before replacing the SCP circuit
pack.
Caution
The following figure shows a Netstender 2060 MSI circuit pack and its key
features for this procedure.
Netstender 2060 Main Shelf Interface key features
Office Alarm Connector
Screw
Handle
Management LAN Connector
Replacing a Netstender 2060 Main Shelf Interface circuit pack

Step
Action
Move Cables
Important: If you are connected to the Management LAN port and logged into the
Netstender, you will lose connection to the Netstender by disconnecting the
Management LAN cable. To avoid this, log in through the craft LAN or the RS-232 serial
port.
The alarm cable and management LAN cable need to be disconnected and moved
aside to get clear access to the faceplate.
Remove Faceplate Screw
a) Facing the front of the Netstender, locate the main shelf interface circuit pack screw.
b) Using a slot-head or Phillips screwdriver, loosen and remove the screw.
Remove Circuit Pack
Grasp the handle on the front of the circuit pack and firmly pull the circuit pack straight
out.
Note: If you are connected through the craft LAN or RS-232 serial port, an MSI missing
alarm appears once you remove the MSI circuit pack.
Replace Circuit Pack
a) Align the replacement circuit pack to the guides of the slot in which the circuit pack is
being replaced.
The LEDs remain on 5 to 10 seconds and then they provide the current alarm state
of the system.
a) Facing the front of the Netstender, align the MSI circuit pack with its mounting hole.

Replace Cables
Reconnect the alarm cable and the management LAN cable to the faceplate connector
and port.
10-7
10.1.1.4 Netstender 2060 Expansion Shelf Interface circuit pack

Use this procedure to replace a Netstender 2060 Expansion Shelf Interface (ESI)
circuit pack.
What you need

Netstender 2060 Expansion Shelf Interface (ESI) circuit pack
Prerequisites
None
Caution
The following figure shows a Netstender 2060 ESI circuit pack and its key features
for this procedure.
Netstender 2060 Expansion Shelf Interface key features
Expansion Shelf Ports
Replacing a Netstender 2060 Expansion Shelf Interface circuit pack

Step
Action
Move Cables
Important: If you are connected to the main shelf of the Netstender, you will lose
connection to the Netstender by disconnecting the To Main cable.
All cables need to be disconnected and moved aside to get clear access to the
faceplate.
Remove Faceplate Screw
a) Facing the front of the Netstender, locate the expansion shelf interface circuit pack
screw.
b) Using a slot-head or Phillips screwdriver, loosen and remove the screw.
Remove Circuit Pack
Grasp the handle on the front of the circuit pack and firmly pull the circuit pack straight
out.
being replaced.
The LEDs remain on 5 to 10 seconds and then they provide the current alarm state
of the system.
Note: The ESI SFPs are inserted upside down on the circuit pack. As a result, the
transmitter and receiver are also reversed.
a) Facing the front of the Netstender, align the ESI circuit pack with its mounting hole.

Replace Cables
Reconnect the cables to the appropriate ports.
10-9
10.1.1.5 Netstender 2060 Multiport System Control Processor circuit pack

Use this procedure to replace one of the following Netstender 2060 System
Control Processor (SCP) circuit packs:
Netstender 2060 System Control Processor (SCP) with 1 Expansion Connector BP1A20AA
Netstender 2060 SCP with Multi-Shelf and OSC capabilities - BP1A20BA
What you need

Netstender 2060 System Control Processor (SCP) circuit pack
Fiber optic cables with 40-degree boots (BP1A59EA-01, -03, or -10)
Prerequisites
For protection before removing or re-initializing the SCP, please ensure that you
perform a remote database backup.
Do not remove the Main Shelf Interface (MSI) circuit pack while replacing the
SCP circuit pack.
The SCP circuit pack with product code BP1A20AA can only be used with
software loads from release 2.3 and higher.
The SCP circuit pack with product code BP1A20BA can only be used with
software loads from release 4.1 and higher.
Caution
The following figure shows a Netstender 2060 SCP circuit pack with one
expansion shelf connector.
Netstender 2060 SCP with one expansion shelf connector (BP1A20AA)
Screw
Craft LAN
Handle
Craft Serial
Intershelf Connector
Screw
Handle
The following figure shows a Netstender 2060 SCP circuit pack with multi-shelf
and OSC capabilities.
Netstender 2060 SCP with multi-shelf and OSC capabilities (BP1A20BA)
32
S-2
al R
AN
tL
ft
AN
raf
Cra
ft L
yC
a
r
r
a
C
xili
Au
11
elf
21
Sh
elf
31
Sh
elf
Sh
C1
OS
C2
OS
ri
Se
Screw
Handle
Screw
10-11
Replacing a System Control Processor circuit pack

Step
Action
Determine whether the SCP is still functioning

If any of the following conditions apply, the SCP is not functioning:
- CONTCOM (Control Communications) alarm raised against all circuit packs
- REPLUNITFAIL (Equipment Failure) alarm raised against all circuit packs
- No LEDs lit on the SCP
- All LEDs lit on the MSI and SCP for more than five minutes
- Unable to successfully log in to the Netstender through the management or craft LAN
ports or the craft serial port (assuming your PC connection is working correctly)
Based on the status of the above conditions, proceed as follows:
- If the SCP is still functioning, go to the next step.
- If the SCP is not functioning, go to step 3.
Perform a Remote Database Backup
a) Before removing the System Control Processor (SCP) circuit pack, perform a remote
database backup. For further details, see Database Backup in the Operation,
Administration, Maintenance, and Provisioning Guide.
b) Return to this procedure after the database backup is completed.
Disable the office alarms before proceeding
Before proceeding with the replacement of the SCP circuit pack, disconnect the office
alarms connector on the MSI circuit pack. This is to avoid multiple audible and visual
alarms from being raised when booting the SCP.
At the Netstender 2060 Shelf:
Disconnect SCP Cables
Disconnect the SCP cables from the faceplate of the circuit pack. These include the
following:
- Craft LAN cable
- Craft serial cable
Remove Faceplate Screws
a) Facing the front of the Netstender, locate the SCP circuit pack screws.
b) Using a slot-head or Phillips screwdriver, loosen and remove the two screws.
Remove Circuit Pack
Grasp the handles on the front of the SCP circuit pack and firmly pull the circuit pack
straight out.
Note: After the SCP is removed, all TL1 sessions are terminated as connectivity to the
SCP is lost.
a) Align the replacement SCP circuit pack to the guides of the slot in which the circuit
pack is being replaced.
c) Push with sufficient pressure to feel the backplane connector snap into place.
Replacing a System Control Processor circuit pack

Step
Action
Replace Faceplate Screws

a) Facing the front of the Netstender, align the SCP circuit pack with its mounting holes.
9
10
11
12
13

Reconnect the SCP Cables
Reconnect the SCP cables to the faceplate of the circuit pack.
At the TL1 Command Line Interface:
Re-establish a TL1 Session
a) Before re-establishing a TL1 session, wait about 60 seconds or more after inserting
the SCP circuit pack for the SCP to reboot.
b) Reconnect and establish a TL1 session.
Determine whether the system database needs to be restored
- If it was necessary to perform a remote database backup before replacing the SCP, go
to the next step.
- If performing an SCP upgrade, go to the Software upgrade through SCP
replacement procedure in the Upgrade Guide.
Restore the system database
See the Operation, Administration, Maintenance, and Provisioning Guide to restore the
database to service using an FTP backup file. Once the database is restored, go to the
next step.
Re-enable the office alarms
Reconnect the office alarm connector to the MSI circuit pack. This re-establishes the
office alarm connectivity.
10-13
10.1.2 Netstender 1030 common equipment circuit packs

10.1.2.1 Netstender 1030 common equipment circuit pack locations
The Netstender 1030 shelf includes the following common equipment:
Netstender 1030 Cooling Unit (CU) circuit pack
The following figure shows the common equipment circuit packs for the
Netstender 1030 shelf.
Netstender 1030 Shelf Common Equipment circuit packs
REL 01
Alarms
ACO
Mgmnt
Cooling Unit
Craft
Fail Active Fan Critical Major Minor
SCP
Craft
System Control Processor
For information about the initial installation of the common equipment circuit
packs, refer to the Installation and Commissioning Guide.
10.1.2.2 Netstender 1030 Cooling Unit

Use this procedure to replace a Netstender 1030 Cooling Unit.
What you need

Replacement cooling unit circuit pack
Prerequisites
None
Caution
Note
The cooling unit is a hot-swappable system component. If replacement of the
cooling unit takes more than 15 minutes to complete, Netstender circuit packs may
generate CTEMPHT and CTEMPHTS alarms.
The following figure shows a Netstender 1030 cooling unit and its key features for
this procedure.
Netstender 1030 Cooling Unit key features
Screw
Handle
10-15

Step
Action
Move Cables
Shelf cables may need to be moved aside to get clear access to the cooling unit. The
cables rest on the handle that is at the front of the cooling unit tray.
a) Facing the front of the Netstender, locate the faceplate screw.

b) Using a Phillips screwdriver, loosen the screw.
Remove Cooling Unit Tray
a) Grasp the handle on the front of the cooling unit and firmly pull the cooling unit
straight out.
Note: A cooling unit missing alarm appears once you remove the cooling unit tray.
b) Place the cooling unit tray on a flat work surface.

Replace Cooling Unit Tray
Align the replacement cooling unit to the slot in which the cooling unit is being replaced.
a) Facing the front of the Netstender, align the cooling unit with its mounting hole.

Replace Cables
If any cables were moved to access the cooling unit, replace the cables to their original
locations.
10.1.2.3 Netstender 1030 System Control Processor circuit pack

Use this procedure to replace a Netstender 1030 System Control Processor (SCP)
circuit pack.
What you need

Prerequisites
For protection before removing or re-initializing the SCP, please ensure that you
perform a remote database backup.
Caution
The following figure shows a Netstender 1030 SCP circuit pack and its key
features for this procedure.
Netstender 1030 System Control Processor key features
Screw

LEDs
Craft LAN
Handle
Craft Serial
Screw
Handle
10-17
Replacing a Netstender 1030 System Control Processor circuit pack

Step
Action
Determine whether the SCP is still functioning

If any of the following conditions apply, the SCP is not functioning:
- CONTCOM (Control Communications) alarm raised against all circuit packs
- REPLUNITFAIL (Equipment Failure) alarm raised against all circuit packs
- No LEDs lit on the SCP
- All LEDs lit on the SCP for more than five minutes
- Unable to successfully log in to the Netstender through the management or craft LAN
ports or the craft serial port (assuming your PC connection is working correctly)
Based on the status of the above conditions, proceed as follows:
- If the SCP is still functioning, go to the next step.
- If the SCP is not functioning, go to step 3.
Perform a Remote Database Backup
a) Before removing the System Control Processor (SCP) circuit pack, perform a remote
database backup. For further details, see Database Backup in the Operation,
Administration, Maintenance, and Provisioning Guide.
b) Return to this procedure after the database backup is completed.
Disable the office alarms before proceeding
Before proceeding with the replacement of the SCP circuit pack, disconnect the office
alarms. This is to avoid multiple audible and visual alarms from being raised when
booting the SCP.
Disconnect SCP Cables
Disconnect the SCP cables from the faceplate of the circuit pack. These include the
following:
- Craft LAN cable
- Craft serial cable
- Office alarm cable
- Management LAN cable
a) Facing the front of the Netstender, locate the SCP circuit pack screws.
Remove Circuit Pack
Grasp the handles on the front of the SCP circuit pack and firmly pull the circuit pack
straight out.
Note: After the SCP is removed, all TL1 sessions are terminated as connectivity to the
SCP is lost.
a) Align the replacement SCP circuit pack to the guides of the slot in which the circuit
c) Push with sufficient pressure to feel the backplane connector snap into place.
Replacing a Netstender 1030 System Control Processor circuit pack

Step
Action

a) Facing the front of the Netstender, align the SCP circuit pack with its mounting holes.
- Partially tighten the first screw.
- Fully tighten the first screw.
- Fully tighten the remaining screw.
9
10
11
12
13

Reconnect the SCP Cables
Reconnect the SCP cables to the faceplate of the circuit pack.
Re-establish a TL1 Session
a) Before re-establishing a TL1 session, wait about 60 seconds or more after inserting
the SCP circuit pack for the SCP to reboot.
b) Reconnect and establish a TL1 session.
Determine whether the system database needs to be restored
- If it was necessary to perform a remote database backup before replacing the SCP, go
to the next step.
- If performing an SCP upgrade, go to the Software upgrade through SCP
replacement procedure in the Upgrade Guide.
Restore the system database
See the Operation, Administration, Maintenance, and Provisioning Guide to restore the
database to service using an FTP backup file. Once the database is restored, go to the
next step.
Re-enable the office alarms
Reconnect the office alarm connector to the SCP circuit pack. This re-establishes the
office alarm connectivity.
10-19
10.2 Optical supervisory channel circuit pack

Use this procedure to replace the Optical Supervisory Channel (OSC) electronics
circuit pack.
What you need

Ethernet cable to connect the OSC circuit pack to the Main Shelf Interface
(MSI) circuit pack
Replacement OSC electronics circuit pack
OSC filler circuit pack (if no replacement OSC electronics circuit pack is
available)
Prerequisites
None
Caution
The following figure shows the OSC circuit pack and its OSC coupler/splitter
assembly. The key features for this procedure are indicated.
OSC Circuit Pack and Coupler/Splitter Assembly key features
Screw for
OSC Circuit Pack
Retention
RJ-45 Copper
Ethernet Connectors
Handles
LC Optical
Connectors
Screw for OSC Coupler/Splitter

Assembly Retention
Fiber Optic Cables
Procedure
Replacing an OSC Electronics circuit pack
Step
Action
Move Cables
Shelf cables may need to be moved aside to get clear access to the OSC electronics
circuit pack. The cables rest on the handles that are at the front of the OSC circuit pack.
Disconnect Cables
a) Disconnect the optical cables (that is In 1, Out 1, In 2 and Out 2) from the optical
ports on the faceplate of the OSC electronics circuit pack.
Note: Ensure that the optical ports on the circuit pack and the optical cables are
protected with protective caps while disconnected.
b) Disconnect the Ethernet cable(s) from the RJ-45 connector(s) on the faceplate of the
OSC electronics circuit pack.
a) Facing the front of the Netstender, locate the faceplate screw on the left side.
b) Using a slot-head or Phillips screwdriver, loosen the screw on the left side.
Remove OSC Electronics Circuit Pack
a) Grasp the handles on the front of the OSC electronics circuit pack and firmly pull the
OSC electronics circuit pack straight out.
Note: An equipment missing alarm appears once you remove the OSC circuit pack.
b) Place the OSC electronics circuit pack on a flat work surface.
10-21
Replacing an OSC Electronics circuit pack

Step
Action
Replace OSC Electronics Circuit Pack or Insert an OSC Filler

If replacing the OSC electronics circuit pack immediately, go to step 6.
Otherwise, ensure that the Netstender 2060 chassis ventilation continues to operate
properly by inserting an OSC filler:
a) Align the OSC filler to the slot in which the OSC filler is being inserted.
b) Carefully push the OSC filler straight into the slot.
c) Go to step 7 to continue.
Replace OSC Electronics Circuit Pack
a) Align the replacement OSC electronics circuit pack to the slot in which the circuit
pack is being replaced and drop the back edge of the circuit pack onto the guides.
a) Facing the front of the Netstender, align the OSC electronics circuit pack or filler with
its mounting hole.

Reconnect Optical Cables
Clean the four optical cables and then reconnect them from the OSC coupler/splitter
assembly as follows:
Fiber Cable Name
Connects To
OSC Input 1
OSC Output 1
OSC Input 2
OSC Output 2
In 1a
Out 1a
In 2a
Out 2a
9
10
Attach the fiber optic cable to the LC optical connector on the OSC faceplate.
Note: If you loop excess fiber around the fiber management spool, allow sufficient slack
for the fiber management spool to move freely.
Reconnect Ethernet Cable
Reconnect the straight-through Ethernet cable that was removed in step 2.
Replace Cables
If any cables were moved to access the OSC circuit pack, replace the cables to their
original locations.
10.2.1 OSC Coupler/Splitters

Use this procedure to replace any of the following OSC circuit packs:
OSC Double Coupler/Splitter 1510 nm (CS)
OSC Double Coupler/Splitter 1510 nm/1610 nm (CS)
OSC Double Coupler/Splitter 1610 nm (CS)
OSC Single Coupler/Splitter 1510 nm (CS)
1310 nm Coupler/Splitter (CS)
The circuit packs listed above work together with the BP1A20BA SCP/OSC
circuit pack to provide OSC functionality.
What you need

Replacement OSC coupler/splitter circuit pack
Prerequisites
None
Caution
10-23
The following figure shows the OSC coupler/splitter circuit pack. The key features
1310 nm coupler/splitter circuit pack
t
tpu
Ou ut
p
In
t
tpu
Ou ut
p
In
ut
Inp tput
Ou
1310 nm
wavelength 1
C Band 1
Line 1
Replacing an OSC coupler/splitter circuit pack

Step
Action
Reroute Traffic
Important: Failure to reroute traffic can result in lost data. Select an alternate route for
the traffic that passes through the coupler/splitter circuit pack and then transfer traffic to
the alternate route before proceeding with this procedure.
Move Cables
Shelf cables may need to be moved aside to get clear access to the coupler/splitter
circuit pack. The cables rest on the handles that are at the front of the coupler/splitter
circuit pack.
Disconnect Optical Cables
Disconnect the optical cables from the optical ports on the faceplate of the circuit pack.
Loosen Faceplate Screws
a) Facing the front of the Netstender, locate the faceplate screws.

b) Using a slot-head or Phillips screwdriver, loosen the screws.
Replacing an OSC coupler/splitter circuit pack

Step
Action
Remove Coupler/Splitter Circuit Pack

a) Grasp the handles on the front of the coupler/splitter circuit pack and firmly pull the
coupler/splitter circuit pack straight out.
Note: An equipment missing alarm appears once you remove the coupler/splitter
circuit pack.
b) Place the coupler/splitter circuit pack on a flat work surface.
Replace Coupler/Splitter Circuit Pack
a) Align the replacement coupler/splitter circuit pack to the slot in which the circuit pack
is being replaced.
a) Facing the front of the Netstender, align the coupler/splitter circuit pack with its
mounting holes.
8
9

Replace Cables
If any cables were moved to access the coupler/splitter circuit pack, replace the cables
10-25
10.3 Wavelength conversion circuit packs

Use this procedure to replace any of the following circuit packs:
4-Port 2.5G SONET-SDH & Data Wavelength Manager
4-Port 2.5G Wavelength Regenerator
4-Port 1G Wavelength Regenerator
2-Port 10G Wavelength Regenerator
4-Port 1G Wavelength Translator
What you need

Replacement WM/WR/WT circuit pack
Replacement small form factor pluggable (SFP) transceivers
Prerequisites
None
Important
Caution
To ensure that the WR10G circuit pack (BP1A47AB or BB) is not damaged,
the maximum input power for the MSA port (that is, port 1) must be -4 dBm
or less.
The following figure shows a wavelength conversion circuit pack. The key
features for this procedure are indicated.
Wavelength Conversion Circuit Pack key features
Screw
Port 4
Port 3
Port 2
Port 1
Handle
Ports with
SFPs Inserted
Screw
Procedure
Replacing Wavelength Conversion circuit pack
Step
Action
Reroute Traffic
the traffic that passes through the circuit pack and then transfer traffic to the alternate
route before proceeding with this procedure.
Move Cables
Shelf cables may need to be moved aside to get clear access to the wavelength
conversion circuit pack. The cables rest on the handles that are at the front of the circuit
pack.
Disconnect Cables
Disconnect the optical cables from the ports on the faceplate of the wavelength

Remove the Circuit Pack
a) Grasp the handles on the front of the circuit pack and firmly pull the circuit pack
straight out.
Note: An equipment missing alarm appears once you remove the circuit pack.
b) Place the circuit pack on a flat work surface.
10-27
Replacing Wavelength Conversion circuit pack

Step
Action
a) Align the replacement circuit pack to the slot in which the circuit pack is being
replaced.
10

Swap or Replace SFPs
Once the replacement circuit pack is secured to the Netstender shelf, use the procedure
SFP transceivers, in this chapter, to remove the SFPs from the original circuit pack
and then insert the SFPs into the new circuit pack.
After the SFP transceiver procedure is completed, return to this procedure.
Clean the optical cables and then reconnect them to their previous positions.
Replace Cables
If any cables were moved to access the circuit pack, replace the cables to their original
locations.
10.3.1 SFP transceivers

Use this procedure to replace small form factor pluggable (SFP) transceivers.
What you need

Replacement SFP transceiver
Prerequisites
None
Laser Warning
Caution
The following figure shows a typical SFP transceiver with a bale-clasp latch.
SFP Transceiver key features
Bale-Clasp Latch
in Closed Position
Bale-Clasp Latch
in Open Position
Note
SFPs for the expansion shelf interface (ESI) circuit pack are inserted upside down.
10-29
The following figures show an SFP transceiver about to be inserted into its slot.
SFP insertion
Screw
Port 4
Port 3
Port 2
Port 1
Handle
Screw
SFP about to be
Out In
(Tx) (Rx)
Note: The connector interface supports

LC connectors only.
Precautions

when handling SFP transceivers:
Do not remove an SFP transceiver from its packaging until you are ready to
Do not touch any of the pins, connections, or components of an SFP transceiver.
Always store or transport an SFP transceiver in anti-static packaging.
Important
DWDM SFPs take about 90 seconds to reach a stable operating temperature. As a

result, the REPLUNITFAIL (SFP Failure) alarm is disabled for 95 seconds after an
SFP is seated. If there is a DWDM SFP hardware fault, the REPLUNITFAIL (SFP
Failure) alarm is raised subsequent to the 95-second time delay.
Procedure
Replacing an SFP transceiver
Step
Action
Reroute Traffic
the traffic that passes through the SFP transceiver and then transfer traffic to the
alternate route before proceeding with this procedure.
Remove SFP port from service
The SFP port must be taken out of service. For information, see RMV-XCVR in the
Move Cables
Shelf cables may need to be moved aside to get clear access to the SFP transceiver.
The cables rest on the handles that are at the front of the circuit pack.
Disconnect the optical cables from the optical ports of the SFP transceiver.
Note: Ensure that the optical ports on the SFP transceiver and the optical cables are
Disengage Latch Handle
a) Facing the front of the Netstender, locate the latch handle on the SFP transceiver.
b) For a bale-clasp latch, pull the latch handle down until it is at a 90-degree angle to the
transceiver.
Remove Transceiver
a) Grasp the latch handle on the SFP transceiver and firmly pull the transceiver straight
out.
Note: If the SFP transceiver port is provisioned, an SFP missing alarm
(REPLUNITMISS) appears and the red LED turns on once you remove the
transceiver.
b) Place the SFP transceiver into anti-static packaging and then lay it on a flat work
surface.
Insert the SFP transceiver
a) Hold the SFP transceiver so that the optical connectors face you and the product
label is visible.
b) Ensure that the latch handle is in the closed position:
c) Align the SFP transceiver to the port in which the transceiver is being inserted.
d) Carefully slide the SFP transceiver straight into the port until it clicks.
Note: If the SFP port is provisioned and the replacement SFP has the same the
wavelength, the SFP missing alarm (REPLUNITMISS) clears.
Note: If the SFP port is provisioned, but the replacement SFP has a different
wavelength, the SFP mismatch alarm (REPLUNITMEA) appears and the red LED
turns on.
10-31
Replacing an SFP transceiver

Step
Action

Note: Before connecting the optical cables to the SFP transceiver, ensure that both the
optical cable connectors and the optical surfaces are clean and that there is no residue
on the optical surfaces.
Connect the input and output optical cables to the SFP transceiver as follows:
a) Ensure that the latch handle (or bail) of the SFP transceiver is in the closed (up)
position.
b) Carefully slide the bottom of the male optical connector along the bottom of the SFP
Restore SFP port to service
Restore the SFP port to service. For information, see RST-XCVR in the TL1
Reference Guide.
Replace Cables
If any cables were moved to access the SFP transceiver, replace the cables to their
original locations.
10
11
10.3.2 10G Wavelength Regenerator XFP transceivers

Use this procedure to replace 10Gbps small form factor pluggable (XFP)
transceivers.
What you need

Replacement XFP transceiver
Prerequisites
None
Laser Warning
Caution
The following figure shows a typical XFP transceiver with a bale-clasp latch.
XFP Transceiver key features
Bale-Clasp Latch
in Closed Position
Bale-Clasp Latch
in Open Position
10-33
The following figure shows an XFP transceiver about to be inserted into its slot.
XFP insertion
XFP about to be
Out In
(Tx) (Rx)
Precautions

when handling XFP transceivers:
Do not remove an XFP transceiver from its packaging until you are ready to
Do not touch any of the pins, connections, or components of an XFP transceiver.
Always store or transport an XFP transceiver in anti-static packaging.
Important
DWDM XFPs take about 90 seconds to reach a stable operating temperature. As a

result, the REPLUNITFAIL (SFP or XFP Failure) alarm is disabled for 95 seconds
after an XFP is seated. If there is a DWDM XFP hardware fault, the
REPLUNITFAIL (SFP or XFP Failure) alarm is raised subsequent to the 95
second time delay.
Procedure
Replacing an XFP transceiver
Step
Action
Reroute Traffic
the traffic that passes through the XFP transceiver and then transfer traffic to the
Remove XFP port from service
The XFP port (port 2) must be taken out of service. For information, see RMV-XCVR in
the TL1 Reference Guide.
Move Cables
Shelf cables may need to be moved aside to get clear access to the XFP transceiver.
The cables rest on the handles that are at the front of the circuit pack.
Disconnect the optical cables from the optical ports of the XFP transceiver.
Note: Ensure that the optical ports on the XFP transceiver and the optical cables are
Disengage Latch Handle
a) Facing the front of the Netstender, locate the latch handle on the XFP transceiver.
b) For a bale-clasp latch, pull the latch handle down until it is at a 90 degree angle to the
XFP transceiver.
Remove XFP Transceiver
a) Grasp the latch handle on the XFP transceiver and firmly pull the transceiver straight
out.
Note: If the XFP transceiver port is provisioned, a replace unit missing alarm
(REPLUNITMISS) appears once you remove the transceiver.
b) Place the XFP transceiver into anti-static packaging and then lay it on a flat work
surface.
Insert the new XFP transceiver
a) Hold the new XFP transceiver so that the optical connectors face you and the product
label is visible.
b) Ensure the latch handle is in the closed position:
c) Align the XFP transceiver to the port in which the transceiver is being inserted.
d) Carefully slide the XFP transceiver straight into the port until it clicks.
10-35
Replacing an XFP transceiver

Step
Action

Note: Before connecting the optical cables to the XFP transceiver, ensure that both the
optical cable connectors and the XFP optical surfaces are clean and that there is no
residue on the optical surfaces.
Connect the input and output optical cables to the XFP transceiver as follows:
a) Ensure that the latch handle (or bail) of the XFP transceiver is in the closed
(up) position.
b) Carefully slide the bottom of the male optical connector along the bottom of the XFP
Restore XFP port to service
Restore the XFP port (port 2) to service. For information, see RST-XCVR in the TL1
Reference Guide.
Replace Cables
If any cables were moved to access the XFP transceiver, replace the cables to their
original locations.
10
11
10.4 Muxponder circuit packs

Use this procedure to replace any of the following Muxponder circuit packs:
2-Port GE Muxponder - SONET (MXP2.5G) - BP1A46AA
2-Port GE Muxponder - SDH (MXP2.5G) - BP1A46BA
What you need

Prerequisites
None
Restrictions
The cross connections between client ports and line ports are fully non-blocking.
In release 6.1, the Muxponder supports the add/drop type of cross connection in
protected and unprotected modes only.
Caution
The following figure shows a 2-Port GE Muxponder circuit pack. The key features
10-37
2-Port GE Muxponder circuit pack key features
t4
en nt 3 2
i
l
C lie
t
C
1
en
Cli ient
l
C
e2
Lin ne 1
Li
Screw
Handle
Screw
Procedure
Replacing a Muxponder circuit pack
Step
Action
Reroute Traffic
the traffic that passes through the muxponder and then transfer traffic to the alternate
route before proceeding with this procedure.
Remove SFP port from service
The SFP port must be taken out of service. For information, see RMV-XCVR in the
Move Cables
Shelf cables may need to be moved aside to get clear access to the Muxponder circuit
pack. The cables rest on the handles that are at the front of the circuit pack.
Disconnect Cables
Disconnect the optical cables from the ports on the faceplate of the Muxponder circuit
pack.

Remove the Circuit Pack
a) Grasp the handle on the front of the circuit pack and firmly pull the circuit pack
straight out.
Note: An equipment missing alarm appears once you remove the circuit pack.
b) Place the circuit pack on a flat work surface.
Replacing a Muxponder circuit pack

Step
Action
a) Align the replacement circuit pack to the slot in which the circuit pack is being
replaced.
10
11
12

Swap or Replace SFPs
Once the replacement circuit pack is secured to the Netstender shelf, use the procedure
SFP transceivers, in this chapter, to remove the SFPs from the original circuit pack
and then insert the SFPs into the new circuit pack.
After the SFP transceiver procedure is completed, return to this procedure.
Clean the optical cables and then reconnect them to their previous positions.
Restore SFP port to service
Restore the SFP port to service. For information, see RST-XCVR in the TL1
Reference Guide.
Replace Cables
If any cables were moved to access the circuit pack, replace the cables to their original
locations.
10-39
10.5 Optical amplifier circuit packs

Use this procedure to replace any of the following optical amplifier circuit packs:
DWDM optical line amplifier (OLA)
DWDM optical line amplifier with mid-stage access (OLAM1 and OLAM2)
DWDM C-Band optical booster amplifier (OBA)
DWDM C-Band optical pre-amplifier (OPA)
Single-channel/sub-band booster amplifier (SBA)
Single-channel/sub-band pre-amplifier (SPA)
What you need

Replacement circuit pack
Prerequisites
None
Caution
Recommendation
It is recommended that slots two, four, and six in the Netstender shelf be the first
slots populated with optical amplifier circuit packs.
The key features for the circuit packs listed below are shown in the following
figures:
DWDM optical amplifiers (OBA, OLA, and OPA)
Single channel/sub-band booster amplifier (SBA)
Single-channel/sub-band pre-amplifier (SPA)
The following figure shows a typical DWDM, SBA and SPA optical amplifier.
DWDM, SBA and SPA Optical Amplifier key features
Screw
Optical Input
Optical Output
Handles
Screw
The following figure shows a typical DWDM, SBA and SPA optical amplifier
with power monitor.
DWDM, SBA and SPA Optical Amplifier with power monitor
Screw
Optical input
Optical output
Handle
Power Monitor
Screw
10-41
A DWDM optical amplifier with mid-stage access circuit pack and its key features
for this procedure is shown in the following figure.
DWDM Optical Amplifier with Mid-Stage Access key features
Optical Input
Screw
Optical Output
Mid-Stage Connectors
Handles
Screw
A DWDM optical amplifier with mid-stage access circuit pack that includes a
power monitor is shown in the following figure.
DWDM Optical Amplifier with Mid-Stage Access and a power monitor
Optical input
Screw
Optical output
Handle
Power Monitor
Screw
Dual LC Mid-Stage
Connector
Replacing an Optical Amplifier circuit pack

Step
Action
Reroute Traffic
the traffic that passes through the optical amplifier and then transfer traffic to the
Remove optical amplifier from service
To remove the optical amplifier from service, enter the following at the TL1 command
line interface:
RMV-OA:[TID]:<aid>:CTAG;
Example
RMV-OA:NETSTENDER:OBA-1-6-1:100;
Response
The Netstender returns a COMPLD message
Remove circuit pack slot from service
To remove the circuit pack slot from service, enter the following at the TL1command line
interface:
RMV-EQPT:[TID]:<aid>:CTAG;
Example
RMV-EQPT:NETSTENDER:OBA-1-6:100;
Response
The Netstender returns a COMPLD message
Move Optical Cables
Depending on the slot in which the circuit pack is located, optical cables may need to be
moved aside to get clear access to the faceplate. The cables rest on the handles that
are at the front of the amplifier circuit pack.
protected while disconnected.
a) Facing the front of the Netstender, locate the circuit pack screws.
Remove Circuit Pack
Grasp the handles on the front of the circuit pack and firmly pull the circuit pack straight
out.
Response
A REPLUNITMISS alarm appears.
10-43
Replacing an Optical Amplifier circuit pack

Step
Action
being replaced.
The LEDs remain on 5 to 10 seconds and then go off.
Response
The REPLUNITMISS alarm should clear after a few seconds.
10
11
12

Reconnect the Optical Cables
Reconnect the optical cables to the faceplate of the circuit pack.
Replace Optical Cables
If any optical cables were moved to access the faceplate, replace the optical cables to
their original locations.
Restore the circuit pack slot to service
To restore the circuit pack slot to service, enter the following at the TL1 command line
interface:
RST-EQPT:[TID]:<aid>:CTAG;
Example
RST-EQPT:NETSTENDER:OBA-1-6:100;
Response
13
The Netstender returns a COMPLD message.

Restore the Optical Amplifier to Service
To restore the optical amplifier to service, enter the following at the TL1 command line
interface:
RST-OA:[TID]:<aid>:CTAG;
Example
RST-OA:NETSTENDER:OBA-1-6-1:100;
10.6 Dispersion compensating module circuit packs

Use this procedure to replace any of the following dispersion compensating
module circuit packs:
SMF DCM 20 km
SMF DCM 40 km
SMF DCM 60 km
SMF DCM 80 km
SMF ITU-T DCM 40 km
SMF ITU-T DCM 60 km
SMF ITU-T DCM 80 km
What you need

Replacement dispersion compensating module circuit pack
Prerequisites
None
Caution
A dispersion compensating module and its key features for this procedure are
shown in the following figure.
10-45
Dispersion Compensating Module key features
Screw
Optical Input
Handle
Optical Output
Screw
Replacing a Dispersion Compensating Module circuit pack

Step
Action
Reroute Traffic
the traffic that passes through the dispersion compensating module and then transfer
traffic to the alternate route before proceeding with this procedure.
Move Cables
Shelf cables may need to be moved aside to get clear access to the dispersion
compensating module. The cables rest on the handles that are at the front of the
dispersion compensating module.

Remove Dispersion Compensating Module
a) Grasp the handles on the front of the dispersion compensating module and firmly pull
the dispersion compensating module straight out.
Note: An equipment missing alarm appears once you remove the dispersion
compensating module circuit pack.
b) Place the dispersion compensating module on a flat work surface.
Replacing a Dispersion Compensating Module circuit pack

Step
Action
Replace Dispersion Compensating Module
a) Align the replacement dispersion compensating module to the slot in which the circuit
a) Facing the front of the Netstender, align the dispersion compensating module with its
mounting holes.
8
9

Replace Cables
If any cables were moved to access the dispersion compensating module, replace the
cables to their original locations.
10-47
10.7 Filler circuit packs

Note
Use this procedure to replace a filler circuit pack.

A filler circuit pack must be inserted in empty circuit pack slots to ensure proper
cooling of the 2060 main shelf. Fillers are not required in empty circuit pack slots
of the Netstender 2060 and Netstender 1020 passive shelves.
What you need

Replacement filler circuit pack
Prerequisites
None
Caution
A single-width filler circuit pack and its key features for this procedure is shown in
the following figure.
Single-Width Filler Circuit Pack key features
Screw
Handle
Screw
Replacing a Filler circuit pack

Step
Action
Move Optical Cables

Depending on the slot in which the filler circuit pack is located, optical cables may need
to be moved aside to get access to the faceplate. The cables rest on the handles that
are at the front of the filler circuit pack.
a) Facing the front of the Netstender, locate the filler circuit pack screws.
b) Using a slot-head or Phillips screwdriver, loosen the two screws.
Remove Circuit Pack
Grasp the handles on the front of the circuit pack and firmly pull the circuit pack straight
out.
Note: An equipment missing alarm appears once you remove the filler circuit pack.
a) Align the replacement circuit pack to the guides of the single- or double-width slot in
which the circuit pack is being replaced.
b) Carefully push the circuit pack straight into the slot(s).
Note: The equipment missing alarm clears after inserting the filler circuit pack.
a) Facing the front of the Netstender, align the filler circuit pack with its mounting holes.

Replace Optical Cables
If any optical cables were moved to access the faceplate, replace the optical cables to
their original locations.
10-49
10.8 Multiplex/demultiplex module circuit packs

Use this procedure to replace any of the following multiplex/demultiplex module
circuit packs:
32-channel DWDM bi-directional multiplex/demultiplex module (2 doublewidth packs)
32-channel DWDM multiplex/demultiplex module (4 double-width packs)
32-channel DWDM active multiplex/demultiplex module (1 double-width pack)
CWDM and DWDM splitter/combiner module (1 single-width pack)
4-channel CWDM multiplex/demultiplex module (4-channel module ch. 1-4)
(1 single-width pack)
What you need

Replacement multiplex/demultiplex module circuit pack
Prerequisites
None
Caution
The following illustration shows an eight-channel module of the 32-channel
DWDM mux/demux.
32-channel DWDM mux/demux circuit pack
l8
nne
l7
nne
Cha
l6
nne
Cha
l5
nne
Cha
l4
nne
Cha
Cha
l3
nne
Cha
l2
nne
Cha
l1
nne
ion
ans
p
x
E
Line
Cha
10-51
The following illustration shows an eight-channel module of the 32-channel

DWDM active mux/demux.
32-channel DWDM active mux/demux circuit pack
or
nit
Mo
Screw
l8
ne
an
Ch
l7
ne
an
Ch
l6
ne
an
Ch
l5
ne
n
ha
l4
ne
an
Ch
l3
ne
an
Ch
Handle
l2
ne
n
ha
l1
ne
an
Ch
ion
ns
e
Lin
pa
Ex
Handle
Screw
Replacing a Multiplex/Demultiplex Module circuit pack

Step
Action
Reroute Traffic
the traffic that passes through the multiplex/demultiplex module and then transfer traffic
to the alternate route before proceeding with this procedure.
Move Cables
Shelf cables may need to be moved aside to get clear access to the multiplex/
demultiplex module. The cables rest on the handles that are at the front of the multiplex/
demultiplex module.

Replacing a Multiplex/Demultiplex Module circuit pack

Step
Action
Remove Multiplex/Demultiplex Module

a) Grasp the handles on the front of the multiplex/demultiplex module and firmly pull the
multiplex/demultiplex module straight out.
Note: An equipment missing alarm appears once you remove the multiplex/
demultiplex module circuit pack.
b) Place the multiplex/demultiplex module on a flat work surface.
Replace Multiplex/Demultiplex Module
a) Align the replacement multiplex/demultiplex module to the slot in which the circuit
a) Facing the front of the Netstender, align the multiplex/demultiplex module with its
mounting holes.
8
9

Replace Cables
If any cables were moved to access the multiplex/demultiplex module, replace the
cables to their original locations.
10-53
10.9 Optical add-drop module circuit packs

Use this procedure to replace any of the following optical add-drop modules
(OADM) circuit packs:
1-channel DWDM OADM (32 types - single-width circuit pack)
1-channel CWDM OADM (16 types - single-width circuit pack)
Double 1-channel CWDM OADM (16 types - single-width circuit pack)
2-channel CWDM OADM (xx, xx+1) (8 types - single-width circuit pack)
What you need

Replacement OADM circuit pack
Prerequisites
None
Caution
A 2-Channel N+1 DWDM OADM and its key features for this procedure are
shown in the following figure.
2-Channel N+1 DWDM OADM key features
Add/Drop Channel 2
Add/Drop Channel 1
Passthrough
Line
Handle
Screw
10-55
Replacing an OADM circuit pack

Step
Action
Reroute Traffic
the traffic that passes through the OADM and then transfer traffic to the alternate route
before proceeding with this procedure.
Move Cables
Shelf cables may need to be moved aside to get clear access to the OADM. The cables
rest on the handles that are at the front of the OADM.

Remove OADM
a) Grasp the handles on the front of the OADM and firmly pull the OADM straight out.
Note: An equipment missing alarm appears once you remove the OADM circuit pack.
b) Place the OADM on a flat work surface.

Replace OADM
a) Align the replacement OADM to the slot in which the circuit pack is being replaced.
a) Facing the front of the Netstender, align the OADM with its mounting holes.
8
9

Replace Cables
If any cables were moved to access the OADM, replace the cables to their original
locations.
10.10 DWDM bi-directional coupler/splitter circuit packs

Use this procedure to replace a DWDM Bi-Directional Coupler/Splitter (CS)
circuit pack.
What you need

Replacement DWDM bi-directional coupler/splitter circuit pack
Prerequisites
None
Caution
The following figure shows the DWDM Bi-Directional Coupler/Splitter circuit
pack. The key features for this procedure are indicated.
10-57
Out 2
Line 2
In 2
Out 1
Not Connected
Ports for Line 2
Line 1
In 1
Not Connected
Ports for Line 1
Replacing a DWDM Bi-Directional Coupler/Splitter circuit pack

Step
Action
Reroute Traffic
the traffic that passes through the coupler/splitter circuit pack and then transfer traffic to
the alternate route before proceeding with this procedure.
Move Cables
Shelf cables may need to be moved aside to get clear access to the coupler/splitter
circuit pack. The cables rest on the handles that are at the front of the coupler/splitter
circuit pack.

Remove Coupler/Splitter Circuit Pack
a) Grasp the handles on the front of the coupler/splitter circuit pack and firmly pull the
coupler/splitter circuit pack straight out.
Note: An equipment missing alarm appears once you remove the coupler/splitter
circuit pack circuit pack.
b) Place the coupler/splitter circuit pack on a flat work surface.
Replace Coupler/Splitter Circuit Pack
a) Align the replacement coupler/splitter circuit pack to the slot in which the circuit pack
is being replaced.
Replacing a DWDM Bi-Directional Coupler/Splitter circuit pack

Step
Action

a) Facing the front of the Netstender, align the coupler/splitter circuit pack with its
mounting holes.
8
9

Replace Cables
If any cables were moved to access the coupler/splitter circuit pack, replace the cables
10-59
P P E N D I X
Appendix A: Optical back reflection

safety feature
ChapterA
This appendix explains the optical back reflection safety feature. The information
is organized as follows:
A.1, Principle of operation
A.2, Querying back-reflection photo-detector
Product Release 6.2 STANDARD A-1
The optical back reflection safety feature is a laser eye safety mechanism designed
to detect that the output port of the amplifier has been disconnected.
This feature is supported on the SBA, OBA, OLA and OLAM amplifiers. This
feature is not supported on the OPA and SPA amplifiers.
A.1 Principle of operation

The back-reflection photo-detector on the output port of the amplifier measures the
reflected optical power (see the figure below). When the reflected optical power
exceeds -4 dBm the amplifier switches to EYESAFE mode. In this mode, the first
pump laser is turned off and the second pump laser runs in constant power mode
with an output of 0 dBm. The amplifier provides little or no signal amplification in
this mode.
Optical Amplifier block diagram
EDF
Input
EDF
Output
Reflection
PD
Pump
Laser1
Pump
Laser2
OPR
PD
PD
OPR optical power received

OPT optical power transmitted
OBR optical back reflection
EDF erbium doped fiber
PD photo-detector
OBR OPT
Control Algorithm
Reporting
OPR
OPT
OBR
As noted above, the threshold to transition to EYESAFE mode is -4 dBm

(OBR-HTS = -4 dBm). This threshold cannot be edited by the user. The rationale
for this value is as follows:
4% of the transmitted light is reflected from surface of a disconnected output
connector.
Safety is a concern when output power is 10 dBm or greater.
The threshold equals 4% of 10 dBm, or the threshold of -4 dBm is 4% of 10
dBm.
The amplifier reverts back to COGAIN/COPWR mode when back-reflection is
less than or equal to -20 dBm. The design includes hysteresis (-4 dBm to raise and
-20 dBm to clear) so that the amplifier does not toggle between COGAIN/COPWR
and EYESAFE modes. See the next illustration.
A-2 Netstender OAM&P Guide Document Version 01
Optical back reflection safety raising and clearing

10
Optical
back
reflection
(dBm)
Alarm raises
Alarm raises
-4 dBm
-10
-20
Not cleared
Alarm clears
-20 dBm
-30
Time
A.1.1 Next generation OBA and SBA

For the circuit packs with PECs BP1A02DA and BP1A05BB, the back reflection
behavior is slightly modified. Instead of fixed values for the declaring and clearing
of the back reflection alarm, the thresholds are relative to the current output power
of the amplifier. As previously stated, a disconnected fiber has a back reflection of
approximately 4% (14 to 17 dB).
Declaring the alarm
To declare the alarm, the following factors must occur:

The amplifier must be transmitting at greater than +10.0 dBm, and
The back reflection reading must be greater than the transmitted output power of
the amplifier minus 14 to 17 dB (that is, with a transmitted output power of +12
dBm, the reflection must be greater than -2 to -5 dBm).
Clearing the alarm
To clear the alarm, the following factors must occur:

The back reflection alarm must be currently raised, and
The back reflection reading must be less than the transmitted output power of
the amplifier minus 20 dB. (that is, with a transmitted output power of 0 dBm,
the reflection must be less than -20 dBm).
Product Release 6.2 STANDARD A-3
A.2 Querying back-reflection photo-detector

The user can query the power measured by the back-reflection photo-detector. The
system reports the optical back reflected power (OBR) as a percentage of output
power (OPT), that is, in dB, and not as an absolute value. The absolute value can
be calculated by adding OPT and OBR. For example, if OPT is 11 dBm and OBR
is -31 dB, then the absolute power is -20 dBm.
The Netstender Node Controller plots OBR (in dB) as a function of time. The
graph shows the OBR-HTS threshold, however this should be disregarded as the
threshold is in dBm.
A-4 Netstender OAM&P Guide Document Version 01
P P E N D I X
Appendix B: Working with the

configuration database
ChapterB
This appendix explains how to work with the configuration database. The
information is organized as follows:
B.1, Configuration database
B.2, Automatic backup process
B.3, Impact of circuit pack replacement on the database
B.4, Automatic restore process
B.5, Manual backup process
B.6, Manual restore process
B.7, Pre-provisioning circuit packs
B.8, Preconfigured MSCP scenarios
B.9, Replacing a failed MSCP
B.10, Replacing failed circuit packs
B.11, Clearing the database
Product Release 6.2 STANDARD B-1
B.1 Configuration database

All configuration data is stored in a non-volatile database on the system control
processor (MSCP) circuit pack. This includes the following information:
System identifier (SID)
Internet protocol (IP) addresses
Amplifier circuit pack settings (such as, gain, power, etc.)
Wavelength translator, regenerator and manager circuit pack settings
Optical Supervisory Channel (OSC) circuit pack settings
Log files
Simple Network Management Protocol (SNMP) settings
User IDs and passwords
A complete copy of the database is backed-up to volatile memory on each and
every active circuit pack (for example, amplifiers, wavelength translator,
wavelength regenerator, active mux/demux, and OSC circuit packs) in the system.
Additionally, the database is also backed up on the expansion shelf interface (ESI)
circuit pack of each expansion shelf in the system.
When the MSCP is replaced, it automatically acquires the database from the active
packs, once it is inserted into an active system. If no active packs are available, the
MSCP uses its non-volatile database.
Automatic database backup to active circuit packs
Database backed-up to amplifiers,
translators, regenerators, active
mux/demux and OSC
AMP
WR
MSCP DB
OSC
Configuration commands entered
and stored in database on MSCP
B-2 Netstender OAM&P Guide Document Version 01
B.1.1 Database backup precautions

The database is not backed-up to passive circuit packs or fillers. In addition, the
database is not backed-up to intelligent circuit packs in expansion shelves.
Performance monitoring (PM) data is not stored in the database. PM data (stored in
volatile memory) is not maintained on restart of the system or software upgrade.
B.2 Automatic backup process

The database backup process is initiated through any of the following trigger
events:
TL1 provisioning commands
TL1 log file modifications
Manually initiated backup to the MSCP or FTP server
Manually initiated database restore from the MSCP or FTP server
MSCP restart and successful acquisition of the database
Shelf power cycle
Active circuit pack insertion
The database is backed-up from the MSCP to active circuit packs in the shelf and
to the ESI circuit pack in expansion shelves.
The Netstender system does not back up again unless a trigger event occurs.
The following table summarizes the trigger events and the time it takes to backup
the database.
Automatic backup trigger events and backup times
Trigger Event
Time to Backup Database
TL1 provisioning commands

TL1 log file is modified
Manually initiated backup to the MSCP or FTP
server
Manually initiated database restore from the
MSCP or FTP server
MSCP restart
Shelf power cycle
Active circuit pack insertion
Within 60 seconds
Within 60 seconds
After the INVK-DB-BKUP command completes
After the Database restore in-progress alarm
clears
After the successful acquisition of the database
After the system has started completely
After the software on a circuit pack is upgraded
B.3 Impact of circuit pack replacement on the database

The following table lists the impact of circuit pack replacement on the database of
the Netstender.
Removal and insertion of circuit packs
Circuit Pack
Removal
Insertion
Multiport System Control

Processor
Do not remove the MSCP for

at least 60 seconds after the
last TL1 command is entered.
Active Circuit Packs

(such as, amplifiers,
wavelength translators, active
mux/demux, and OSCs)
If there is at least one active

circuit pack left in the system, it
is safe to remove an active
circuit pack.
Note: Backups of the
database are stored in volatile
memory and are lost once an
active circuit pack is removed.
When the MSI is removed, the
MSCP loses communications
to all circuit packs and
backups cannot be supported.
The MSCP acquires the

database from active circuit
packs. (See section B.4,
Automatic restore process for
details.)
The database is backed-up to
active circuit packs after their
software is upgraded.
Main Shelf Interface (MSI)
Passive Circuit Packs

(such as, dispersion
compensation modules, optical
add-drop modules and
multiplexer/demultiplexers)
Cooling Unit
No impact as the passive

circuit packs are not involved
in the backup process.
When the MSI is inserted, the

database is backed-up to new
active circuit packs after they
are inserted and their software
is upgraded.
No impact. The passive circuit
packs are not involved in the
backup process.
No impact as the cooling unit is

not involved in the backup
process.
No impact. The cooling unit is

not involved in the backup
process.
B.3.1 Recommendations when replacing circuit packs

When replacing the MSCP, ensure that one active circuit pack remains in the shelf.
When replacing both the MSCP and the MSI, ensure that the MSI is replaced first.
When replacing the MSCP in a shelf populated with only passive circuit packs:
Perform a database backup through the FTP server.
Replace the MSCP.
Re-enter IP addresses (otherwise, the MSCP starts with the default IP addresses)
Restore the database through the FTP server.
B.4 Automatic restore process

Described below are the three automatic restore processes that can occur.
B.4.1 System running current software, replace MSCP with a unit loaded
with the current software
1
While the MSCP is starting, it queries all active circuit packs for database
revisions.
Selects the database from the pack with the latest revision.
Performs a database integrity check.
Uses the database if the integrity check passes. Otherwise, the MSCP selects
another database and raises the DB recovery failure alarm if all checks fail.
Increments the revision and backs-up the database to all active circuit packs.
B.4.2 System running current software, replace MSCP with a unit loaded
with an earlier or later software load
1
The Release number mismatch alarm is raised.
The MSCP uses the database with factory default settings.
The MSCP can be brought to current software release by loading the correct
software through the FTP server and issuing the INVK-SCP-RELNUM
command.
The MSCP restarts following the previous restore process:

a
revisions.
Selects the database from the pack with the latest revision.
Performs a database integrity check.
Uses the database if the integrity check passes. Otherwise, the MSCP selects
another database and raises the DB recovery failure alarm if all checks fail.
Increments the revision and backs-up the database to all active circuit packs.
B.4.3 System running current software, cycle power

1
revisions.
The circuit packs do not have databases as this is stored in volatile memory.
The MSCP uses its own database and will backup to all of the active circuit
packs.
B.5 Manual backup process

There are two manual backup methods:
Local MSCP backup
A local backup is stored on the MSCP. It consists of one backup file that is
overwritten by new backups. When a local backup occurs, it triggers immediate
backups to the active circuit packs.
Local PC FTP backup
A local backup is stored on a connected PC that acts as an FTP server.

Remote PC FTP backup
Note
A remote backup is stored on an FTP server.

For manual backups to occur, the Netstender system should have no alarms.
However, an alarm override is available but not usually recommended.
The following figure shows how a remote backup to an FTP server occurs.
Remote backup process
Management
station
DB
Remote
backup
FTP
server
Management
network
Management
network
Management Ethernet
AMP1
AMP2
MSCP
OSC
B.6 Manual restore process

The manual restore process uses the following steps1:
1
LOAD transfers the database from the remote FTP server (or from the local
MSCP storage) to the Netstender.
INVOKE allows the user to browse the loaded database using TL1 but the
command does not affect provisioning on the circuit packs. Note: If the
INVOKE fails, cancel the restore process and start this procedure again.
ACCEPT makes the new database active on the system.

Caution: If this is a traffic carrying system, ensure that the new database has the
proper provisioning to carry traffic.
COMMIT makes the new database permanent.
CANCEL rolls the database back. (This step can be issued after an INVOKE or
ACCEPT only.)
You cannot restore a database that is backed-up under a different software release.
5
Note
The following figure shows how a remote restore from an FTP server occurs.
Remote restore process
Management
station
DB
FTP
server
Management
network
Management
network
Remote
restore
Remote
Management Ethernet
AMP1
AMP2
MSCP
OSC
1.The actions shown correspond to the Netstender Node Controller (NNC) commands.
Equivalent TL1 commands are also available. See the TL1 Reference Guide for details.
B.7 Pre-provisioning circuit packs

Circuit packs can be provisioned without being physically present in the shelf.
The following table lists the equipment states that occur depending on the
condition of the slot that has been provisioned.
Pre-provisioning equipment states
Equipment State
Slot Condition
OOS-AU,AINS&MEA
OOS-AU,AINS&UEQ
IS-NR
Circuit pack is not in provisioned slot.

Slot is empty.
Pre-provisioned circuit pack is inserted in slot.
B.8 Preconfigured MSCP scenarios

In some cases, it can be useful to pre-configure an MSCP with all of the
provisioning information and then have the provisioning data automatically sent to
all of the active circuit packs. This procedure only works in the following
scenarios.
Provision the MSCP in shelf-1, then insert the circuit packs in shelf-1
The system automatically provisions the inserted circuit packs using the database
on the MSCP.
Provision the MSCP in shelf-1, move the MSCP to an unequipped shelf 2, then
insert the circuit packs in shelf-2
The system automatically provisions the inserted active circuit packs using the
database on the MSCP.
Provision the MSCP in shelf-1, then move the MSCP to shelf-2 that is equipped
with circuit packs
If the circuit packs do not have a database (that is, if the shelf never had an MSCP
or the shelf was power cycled), the system automatically provisions the active
circuit packs using the database on the MSCP.
If the circuit packs have a database (that is, if the shelf had an MSCP at one time),
then the new MSCP acquires the database from the active circuit packs.
B.9 Replacing a failed MSCP

Under normal circumstances, a new MSCP acquires the database from the active
circuit packs in the shelf.
Database Recovery Failure alarm
It is possible that a Database Recovery Failure alarm can occur. If so, do the
following:
Restore the database from an FTP server. (This presumes that the database was
backed-up remotely to an FTP server.)
or
Provision an MSCP on another shelf, perform a remote backup to an FTP
server, and then restore the database.
or
Provision an MSCP on another shelf, perform a local backup, replace the
MSCP, and then restore the database from the local copy.
or
If working in a lab situation, the easiest solution is to power cycle the shelf and
re-enter the provisioning data.
B.10 Replacing failed circuit packs

When a failed circuit pack is replaced, the new circuit pack is automatically
provisioned using the database on the MSCP.
B.11 Clearing the database

No command exists for clearing the database.
If you need to clear the database, there are two options:
1
Manually delete all of the provisioning data using either the NNC graphical user
interface or the TL1 command line interface.
or
2
Perform a database backup on a new MSCP (that is, there is no provisioning

data), restore this database to systems requiring a blank database.
P P E N D I X
ChapterC
This appendix explains what universal connectors are and how to clean them. The
information is organized as follows:
C.1, About universal connectors
C.2, Cleaning universal connectors
Product Release 6.2 STANDARD C-1
C.1 About universal connectors

A universal connector consists two distinct parts: a connector base, that is
permanently mounted into the faceplate of a Netstender circuit pack, and a
connector cap, that serves as the external connector port.
The principal advantage is that the universal connector parts can be easily accessed
for cleaning of the optical elements.
In addition, a variety of connector caps are available which permit the use of FC,
SC and ST patch cord connectors. All connector caps can be removed and replaced
without special tools.
The following figure shows the various parts of a universal connector.
Parts of a universal connector
Patch cord connects

to connector base inside
circuit pack
Connector Base
Connector Cap
C-2 Netstender OAM&P Guide Document Version 01
Patch cord connects

to connector cap outside
circuit pack
C.2 Cleaning universal connectors

Each universal connector assembly is inspected for debris before it is packaged.
During use, the assembly can become contaminated with debris from multiple
connections or environmental contaminants. This debris is best observed using a
200x scope with backlighting from any safe white light source. If debris is found
on the connector optical surfaces, use the following procedure to safely clean it.
Laser Warning
Use the following procedure to clean universal connectors.

Cleaning universal connectors
Step
Action
Disengage the universal connector

To separate the connector cap from the connector base, do the following:
a) With a patch cord inserted into the connector cap, gently grasp the patch cord sleeve
and press the detent finger end of the connector cap.
b) Still holding the detent finger down, rotate the connector cap counter-clockwise to
disengage, and then the pull connector cap straight out.
Press end detent finger down and

rotate connector cap counter-clockwise
to disengage.
Connector Base
Connector Cap
Product Release 6.2 STANDARD C-3
Cleaning universal connectors

Step
Action
Clean the optical surfaces

Using clean, dry compressed air or gas, hold the optical surfaces approximately one
inch from the end of the nozzle and blow onto the optical surfaces. One inch is a safe
distance to prevent damage.
Clean Exposed Ferrule
of Connector Base
Clean Exposed Outer Ferrule
of Connector Cap
Clean Ceramic Sleeve

Clean Exposed Inner Ferrule
of Connector Cap
Check for debris

CAUTION: Never insert a cleaning stick of any kind into the connector.
Look into the connector housing with a 200x scope. If debris is still present repeat steps
1 through 3 until the element is clean, then go to the next step.
Note: If the connector base or connector cap is damaged, cleaning will not improve the
performance.
Reconnect the universal connector
After cleaning, ensure that there is no patch cord attached to the connector cap, then do
the following:
a) Align the connector cap to the connector base with the connector cap turned slightly
counter-clockwise to the connector base.
b) Carefully insert the ceramic sleeve of the connector cap into the connector base and
then turn the connector cap clockwise until you hear an audible click as the connector
cap latches to the connector base.
c) Confirm that the connector cap has locked onto the connector base by gently pulling
the connector cap straight out. The connector cap should hold firmly to the connector
base.
C-4 Netstender OAM&P Guide Document Version 01
P P E N D I X
ChapterD
This appendix explains the expansion shelf interface (ESI) command line interface
(CLI). The information is organized as follows:
D.1, Expansion shelf interface access
D.2, ESI main menu display
D.3, ESI shelf configuration display
D.4, ESI SFP inventory display
D.5, ESI SFP alarm status display
D.6, ESI SFP digital diagnostics data display
Product Release 6.2 STANDARD D-1
D.1 Expansion shelf interface access
Restriction
The ESI CLI is accessed through the ESI RS-232 craft serial port. For information
about connecting, see 3.6.2, Connecting through the craft serial port on an ESI
circuit pack in this document.
The expansion shelf port on the ESI circuit pack labeled To Expansion, is not
supported in this release.
D.2 ESI main menu display

Once logged on the ESI main menu appears as shown below.
Extension shelf interface main menu
NETSTENDER EXPANSION SHELF 4.1
1.
2.
3.
4.
2006/01/25 17:05:50
Shelf Configuration
ESI SFP Inventory
ESI SFP Alarm Status
ESI SFP Digital Diagnostics
type 'h' for help

NETSTENDER>
The various menu selections are accessed by entering the number of the selection,
followed by the Enter key.
D-2 Netstender OAM&P Guide Document Version 01
D.3 ESI shelf configuration display

Selecting the Shelf Configuration option returns a display of the expansion shelf
data parameters. The example display shown below is for an expansion shelf that
is connected to the main shelf.
Shelf configuration display
Shelf Configuration
===================
Link Status (to Main):
Shelf ID Mismatch Status:
Local Shelf Cached UID Data:
NE TID:
IP-NMS:
Node Id:
MSI Serial No.:
Main Shelf Expected UID Data:
NE TID:
IP-NMS:
Node Id:
MSI Serial No.:
Up
Not raised
NETSTENDER
192.168.17.1
11
SI SN N/A
NETSTENDER
192.168.17.1
11
SI SN N/A
type 'h' for help

NETSTENDER>
Note
In the case of an expansion shelf that has not been connected to the main shelf
since power up, each of the cached data parameters show a blank value to indicate
that no value is available. Likewise, if the link state is down, the following display
can appear.
Shelf configuration display - link state is down

Shelf Configuration
===================
Link Status (to Main):
Shelf ID Mismatch Status:
Local Shelf Cached UID Data:
NE TID:
IP-NMS:
Node Id:
MSI Serial No.:
Main Shelf Expected UID Data:
NE TID:
IP-NMS:
Node Id:
MSI Serial No.:
type 'h' for help
NETSTENDER>
Down
Not raised
0.0.0.0
0
D.4 ESI SFP inventory display

Selecting the ESI SFP Inventory option from the ESI main menu returns a listing
of inventory data from the SFP transceivers seated in the ESI circuit pack.
Although there are two SFP ports on the ESI circuit pack, SFP inventory
information is reported only for SFP port 1 (To Main) in this release. An example
of the output for this selection is shown below.
ESI SFP inventory display - for an expansion shelf with a electric cable connection
ESI SFP Inventory
=================
Port 1 (To Main):
=================
Presence Status:
Vendor Name:
Vendor Part Number:
PEC:
CLEI:
Media Type:
Revision:
Serial Number:
Manufacture Date:
Wavelength:
Nominal Bit Rate:
Maximum Bit Rate:
Minimum Bit Rate:
Tx Fault Implemented:
LOS Implemented:
Present
Molex Inc.
73929-0026
[Not Specified]
[Not Specified]
[Not Specified]
D
533610012
051202
[Not Specified]
2500 Mb/s
2525 Mb/s
100 Mb/s
No
No
type 'h' for help

NETSTENDER>
Note
If the SFP is missing from the To Main port, the presence status parameter would
show as Not Present and the rest of the values would be blank.
For an example of the ESI SFP Inventory display when fiber connection is used in
SFP port 1, see the example that follows.
ESI SFP inventory display - for an expansion shelf with a fiber cable connection
ESI SFP Inventory
=================
Port 1 (To Main):
=================
Presence Status:
Vendor Name:
Vendor Part Number:
PEC:
CLEI:
Media Type:
Revision:
Serial Number:
Manufacture Date:
Wavelength:
Nominal Bit Rate:
Maximum Bit Rate:
Minimum Bit Rate:
Tx Fault Implemented:
LOS Implemented:
type 'h' for help
NETSTENDER>
Present
JDS UNIPHASE
CT2-ML2LBTD51C1
BP3AM1LL
Optical
C21
6335000513
050119
1550 nm
2500 Mb/s
3000 Mb/s
50 Mb/s
Yes
Yes
D.5 ESI SFP alarm status display

Selecting the ESI SFP Alarm Status option from the ESI main menu returns a
listing of the active conditions against the SFP transceivers that are expected to be
seated in the ESI circuit pack. Although there are two SFP ports on the ESI circuit
pack, SFP inventory information is reported only for SFP port 1 (To Main) in this
release. An example of the output for this selection is shown below.
ESI SFP alarm status display
ESI SFP Fault Status
====================
Port 1 (To Main):
=================
REPLUNITMISS
CONTCOM
REPLUNITUNK
REPLUNITFAIL
LOS
T-OPR-LT
T-OPR-HT
T-OPT-LT
T-OPT-HT
(SFP Missing)
(Control Communications Failure with SFP)
(SFP Unknown)
-0026
(SFP Fail)
(SFP Loss
of Signal)
Specified]
(OPR Low Threshold)
(OPR High Threshold)
(OPT Low Threshold)
(OPT High Threshold)
Raised
-
type 'h' for help

NETSTENDER>
Note
If there are no conditions active against any of the SFP transceivers, a dash (-) is
displayed to state that there are no active conditions.
D.6 ESI SFP digital diagnostics data display

Note
The digital diagnostics data display works only if digital diagnostics are supported
by the SFP.
Selecting the ESI SFP Digital Diagnostics option from the ESI main menu returns
a listing of current performance monitoring parameter values, as well as the
current threshold settings for these parameters. Although there are two SFP ports
on the ESI circuit pack, SFP inventory information is reported only for SFP port 1
(To Main) in this release. An example of the output for this selection is shown
below.
ESI SFP digital diagnostics information display
ESI SFP Digital Diagnostics Data
================================
Port 1 (To Main):
=================
Parameter
Current Value
Min. Th.
Max. Th.
========================================================================
Xcvr Temperature
Supply Voltage
Tx Bias Current
Optical Power Tx
Optical Power Rx
80C
3.50V
85mA
3.0dBm
-5.0dBm
80C
3.50V
85mA
3.0dBm
-5.0dBm
80C
3.50V
85mA
3.0dBm
-5.0dBm
type 'h' for help

NETSTENDER>
Note
If the SFP transceiver is missing from the To Main port, the status is shown as
SFP Not Present and the rest of the values are left blank.
If the SFP transceiver does not contain any diagnostic software, the status is shown
as indicated below.
ESI SFP digital diagnostics information display not supported
ESI SFP Digital Diagnostics Data
================================
Port 1 (To Main):
=================
[Digital Diagnostics not supported]
type 'h' for help
NETSTENDER>
P P E N D I X
ChapterE
This appendix explains what information to collect before contacting support. The
appendix topics include the following:
E.1, Before you contact support
E.2, How to collect required information
E.3, How to contact support
E.1 Before you contact BTI support

Before you contact support, please have the following information ready:
Netstender product release number
Details about any affected circuit packs:
Circuit pack name
Product equipment code
Serial number
Hardware revision
Connector type(s)
Detailed description of the problem
Diagnostic error messages
Details about recent configuration changes or network changes
Alarms raised as a result of the problem
Product Release 6.2 STANDARD E-1
E.2 How to collect required information

Depending on whether you are located near the equipment or whether you are
located remotely from the equipment, information can be obtained through
different methods.
E.2.1 Obtaining information locally

The following illustration shows where to look on a circuit pack faceplate to obtain
circuit pack information. Some information, such as connector type, requires a
basic knowledge of the connector types available. However, the same information
can also be obtained through use of the TL1 command line interface. (See
Obtaining information remotely for details.)
Obtaining circuit pack information from the faceplate
Serial Number
Product Equipment Code
Connector Type
E-2 Netstender OAM&P Guide Document Version 01
Circuit Pack Name
E.2.2 Obtaining information remotely

Information about the Netstender can be obtained by logging in to the system and
using the TL1 command interface or the Netstender Node Controller (NNC).
Information presented in this section discusses the use of the TL1 command line
interface. The same information is retrievable through the NNC.
E.2.2.1 Netstender product release number

To obtain the Netstender product release numbers, use any of the following three
TL1 commands:
RTRV-NETYPE
RTRV-SYS-RELNUM
RTRV-VERSION
RTRV-NE-TYPE
To use the RTRV-NETYPE command, enter the following syntax at the TL1
RTRV-NETYPE:[TID]::<CTAG>;
Example input
RTRV-NETYPE:NETSTENDER::100::;
Example response
NETSTENDER 07-01-27 10:26:49
M
100 COMPLD
BTI Photonic Systems Inc.,Netstender2060,WDM,6.1
RTRV-SYS-RELNUM
To use the RTRV-SYS-RELNUM command, enter the following syntax at the

RTRV-SYS-RELNUM:[TID]::<CTAG>::[<type>];
Example input
RTRV-SYS-RELNUM:NETSTENDER::100::;
Example response
NETSTENDER 07-05-03 16:06:26
M
100 COMPLD
"ACTIVE=6.1.0,INACTIVE=6.1.0"
RTRV-VERSION
To use the RTRV-VERSION command, enter the following syntax at the TL1
RTRV-VERSION:[TID]:[<aid>]:[CTAG];
Example input
RTRV-VERSION:NETSTENDER::100;
Example response
NETSTENDER 07-03-02 18:56:38
M
100 COMPLD
"ACT::GISSUE=06-01-0"
E.2.2.2 Circuit pack information

To obtain circuit pack inventory information, enter the following at the TL1
RTRV-INV:[TID]:[<AID>]:<CTAG>;
Example input
RTRV-INV:NETSTENDER::100;
Example output
NETSTENDER 06-05-05 09:09:50
M
100 COMPLD
NETSTENDER 2060, SHCONF=5-SLOT,"
"SH-1,EQPT:NAME=2060,PEC=BP1A5021,CLEI=WMMKTWOKRA,FNAME=NETSTENDER
2060 Shelf, HWREV=\"0\","
"SLOT-1-1,EQPT:NAME=D32MD1,PEC=BP1A35AA,CLEI=WMOMAK8MAA,FNAME=32
Channel DWDM Mux/Demux Module 1,SER=\"NotSet\",HWREV=\"0\",MFGDAT=\"200603-13\",MFGLOCN=BTI Northside,TSTDAT=2006-03-13,TSTLOCN=BTI Northside,"
"SLOT-1-4,EQPT:NAME=CS,PEC=BP1A38AA,CLEI=NotSet,FNAME=Single 1310nm &
C-Band Coupler/Splitter,SER=\"BTI00002645\",HWREV=\"1\",MFGDAT=\"2005-0621\",MFGLOCN=BTI Thurston,TSTDAT=2005-06-21,TSTLOCN=BTI Thurston,"
"SLOT-1-5,EQPT:NAME=SCP,PEC=BP1A20BA,CLEI=CLEI,FNAME=System Control
Processor, SER=\"BTI00002885\",HWREV=\"1\",MFGDAT=\"1\
",MFGLOCN=1,TSTDAT=1,TSTLOCN=1,"
"ESFP-1-5-1,EQPT:SER=\"526320368\",HWREV=\"D\",MFGDAT=\"2005-09-20\",
WAVELENGTH=0,MINBR=199,NOMBR=2500,ENCODING=SONET
SCRAMBLED,CONNTYPE=COPPER_PIGTAIL, VENDORNAME=\"Molex Inc.\",VENDORPN=\
"739300002\",VENDOROUI=\"UNKNOWN\",TXFAULTIMP=N,
TXDISABLEIMP=Y,LOSIMP=Y,DDIAGIMP=N,MEDIA=OPTICAL"
"SLOT-1-6,EQPT:NAME=OLA,PEC=BP1A03AA-SC,CLEI=WMAP600HAA,FNAME=Optical
Line Amplifier-SC,SER=\"BTI00010143\",HWREV=\"6\",MFGDAT=\"2004-08-18\
",MFGLOCN=BTI Thurston,TSTDAT=2004-08-18,TSTLOCN=BTI Thurston,"
Interface, SER=\"BTI00084987\",HWREV=\"7\",MFGDAT=\"2006-04-03\
",MFGLOCN=BTI Northside, TSTDAT=2006-04-03,TSTLOCN=BTI Northside,"
"CU-1,EQPT:NAME=CU,PEC=BP1A52AA,CLEI=WMPQALW7AA,FNAME=Cooling Unit,
SER=\"BTI12345678\",HWREV=\"2\",MFGDAT=\"2006-04-11\",MFGLOCN=BTI
Northside, TSTDAT=2006-04-11,TSTLOCN=BTI Northside,"
"ES-11,EQPT:NAME=ES2060,PEC=BP1A51AA,CLEI=None,FNAME=Expansion Shelf
NETSTENDER 2060,SHCONF=5-SLOT,"
"SLOT-114,EQPT:NAME=FLLR,PEC=BP1A55AA,CLEI=WMPQALX7AA,FNAME=Filler,SER=\"N/A\",
HWREV=\"0\",MFGDAT=\"N/A\",MFGLOCN=N/A,TSTDAT=N/A,TSTLOCN=N/A,"
"SLOT-115,EQPT:NAME=FLLR,PEC=BP1A55AA,CLEI=WMPQALX7AA,FNAME=Filler,SER=\"N/A\",
HWREV=\"0\",MFGDAT=\"N/A\",MFGLOCN=N/A,TSTDAT=N/A,TSTLOCN=N/A,"
"SLOT-11-6,EQPT:NAME=PMT1,PEC=FC9686PM41,CLEI=WMUCAPXCAA,FNAME=4 port
Connectorized Power Monitor Tap 1%,SER=\"SN12345678\",HWREV=\"1\
",MFGDAT=\"2006-05-01\",MFGLOCN=BTI Northside,TSTDAT=2006-0501,TSTLOCN=BTI Northside,"
"SI-11,EQPT:NAME=ESI,PEC=BP1A54AA,CLEI=NoClei,FNAME=Expansion Shelf
Interface, SER=\"K001255745\",HWREV=\"4\",MFGDAT=\"2005-10-13\
",MFGLOCN=BTI Thurston, TSTDAT=2005-10-13,TSTLOCN=BTI Thurston,"
"ESFP-11-1,EQPT:SER=\"526320368\",HWREV=\"D\",MFGDAT=\"2005-09-20\
",WAVELENGTH=0, MINBR=199,NOMBR=2500,ENCODING=SONET
SCRAMBLED,CONNTYPE=COPPER_PIGTAIL,VENDORNAME=\"Molex Inc.\",VENDORPN=\
"73930-0002\",VENDOROUI=\"UNKNOWN\",TXFAULTIMP=N,TXDISABLEIMP=Y,
LOSIMP=Y,DDIAGIMP=N,MEDIA=OPTICAL"
Northside, TSTDAT=2006-01-13,TSTLOCN=BTI Northside,"
;
The following illustration shows how to read circuit pack information that is
imbedded in the system response message for the RTRV-INV command.
Circuit Pack Name
Product Equipment Code

Connector Type
Line Amplifier-SC,SER=\"BTI00010143\",HWREV=\"6\",MFGDAT=\"2004-08-18\",
Serial Number
Hardware Revision
E.2.2.3 SFP and XFP transceiver information

If required, obtain the SFP and XFP transceiver information:
Obtain the FRU data from the SFP transceiver
To obtain the field replaceable unit (FRU) data from the SFP or XFP transceiver,
enter the following at the TL1 command line interface:
RTRV-INV:::;
Example output
NETSTENDER 06-05-05 09:27:38
M
100 COMPLD
NETSTENDER 2060, SHCONF=5-SLOT,"
"SLOT-1-1,EQPT:NAME=D32MD1,PEC=BP1A35AA,CLEI=WMOMAK8MAA,FNAME=32
Channel DWDM Mux/Demux Module 1,SER=\"NotSet\",HWREV=\"0\",MFGDAT=\"200603-13\",MFGLOCN=BTINorthside, TSTDAT=2006-03-13,TSTLOCN=BTI Northside,"
"SLOT-1-3,EQPT:NAME=WR2.5G,PEC=BP1A42AB,CLEI=WMOGAKZGAA,FNAME=4 Port
2.5G Wavelength Regenerator with Protection,SER=\"NotSet\",HWREV=\"0\",
MFGDAT=\"2006-05-04\",MFGLOCN=BTI Northside,TSTDAT=2006-05-04,TSTLOCN=BTI
Northside,"
"SFP-1-3-1,EQPT:PEC=BP3AM1MI,SER=\"6332001451\",HWREV=\"D34\",
MFGDAT=\"2005-02-11\
",WAVELENGTH=1310,REACH=15,MINBR=50,MAXBR=3000,NOMBR=2500,
ENCODING=SONET_SCRAMBLED,CONNTYPE=LC,VENDORNAME=\"JDS UNIPHASE\
",VENDORPN=\"CT2-MI1LBTD33C4\
",TXFAULTIMP=Y,TXDISABLEIMP=Y,LOSIMP=Y,DDIAGIMP=Y,MEDIA=OPTICAL"
"SFP-1-3-2,EQPT:PEC=BP3AM1DE-10,SER=\"6341000290\",HWREV=\"A00\",
MFGDAT=\"2048-12-16\
",WAVELENGTH=1550.92,REACH=100,MINBR=150,MAXBR=2700,NOMBR=2500,
ENCODING=SONET_SCRAMBLED,CONNTYPE=LC,VENDORNAME=\"JDS UNIPHASE\
",VENDORPN=\"CT2-DA21A372S00C\
",TXFAULTIMP=Y,TXDISABLEIMP=Y,LOSIMP=Y,DDIAGIMP=Y,MEDIA=OPTICAL"
"SFP-1-3-3,EQPT:PEC=BP3AM1CL-04,SER=\"6385000071\",HWREV=\"D14\
",MFGDAT=\"2048-10-01\
",WAVELENGTH=1551,REACH=80,MINBR=50,MAXBR=3000,NOMBR=2500,ENCODING=SONET_
SCRAMBLED, CONNTYPE=LC,VENDORNAME=\"JDS UNIPHASE\",VENDORPN=\"CT2ML2LBCW51C4\",TXFAULTIMP=Y,
",MFGDAT=\"2005-02-04\
",WAVELENGTH=1611,REACH=80,MINBR=50,MAXBR=3000,NOMBR=2500,ENCODING=SONET_
SCRAMBLED,CONNTYPE=LC,VENDORNAME=\"JDS UNIPHASE\",VENDORPN=\"CT2ML2LBCW81C1\",TXFAULTIMP=Y,
"SLOT-1-4,EQPT:NAME=CS,PEC=BP1A38AA,CLEI=NotSet,FNAME=Single 1310nm &
C-Band Coupler/Splitter,SER=\"BTI00002645\",HWREV=\"1\",MFGDAT=\"2005-0621\",MFGLOCN=BTI Northside,TSTDAT=2005-06-21,TSTLOCN=BTI Northside,"
"SLOT-1-5,EQPT:NAME=SCP,PEC=BP1A20BA,CLEI=CLEI,FNAME=System Control
Processor, SER=\"BTI00002885\",HWREV=\"1\",MFGDAT=\"1\
",MFGLOCN=1,TSTDAT=1,TSTLOCN=1,"
"ESFP-1-5-1,EQPT:SER=\"526320368\",HWREV=\"D\",MFGDAT=\"2005-09-20\",
WAVELENGTH=0,MINBR=199,NOMBR=2500,ENCODING=UNKNOWN,CONNTYPE=COPPER_PIGTAI
L,VENDORNAME=\"Molex Inc.\",VENDORPN=\"73930-0002\",VENDOROUI=\"UNKNOWN\
",TXFAULTIMP=N, TXDISABLEIMP=Y,LOSIMP=Y,DDIAGIMP=N,MEDIA=UNKNOWN"
Line Amplifier-SC,SER=\"BTI00010143\",HWREV=\"6\",MFGDAT=\"2004-08-18\
",MFGLOCN=BTI Northside,TSTDAT=2004-08-18,TSTLOCN=BTI Northside,"
Interface, SER=\"BTI00084987\",HWREV=\"7\",MFGDAT=\"2006-04-03\
",MFGLOCN=BTI Northside, TSTDAT=2006-04-03,TSTLOCN=BTI Northside,"
Northside,TSTDAT=2006-04-11,TSTLOCN=BTI Northside,"
"ES-11,EQPT:NAME=ES2060,PEC=BP1A51AA,CLEI=None,FNAME=Expansion Shelf
NETSTENDER 2060,SHCONF=5-SLOT,"
"SI-11,EQPT:NAME=ESI,PEC=BP1A54AA,CLEI=NoClei,FNAME=Expansion Shelf
Interface, SER=\"K001255745\",HWREV=\"4\",MFGDAT=\"2005-10-13\
",MFGLOCN=BTI Northside,TSTDAT=2005-10-13,TSTLOCN=BTI Northside,"
"ESFP-11-1,EQPT:SER=\"526320368\",HWREV=\"D\",MFGDAT=\"2005-09-20\
",WAVELENGTH=0,
MINBR=199,NOMBR=2500,ENCODING=UNKNOWN,CONNTYPE=COPPER_PIGTAIL,VENDORNAME=
\"Molex Inc.\",VENDORPN=\"73930-0002\",VENDOROUI=\"UNKNOWN\
",TXFAULTIMP=N,TXDISABLEIMP=Y, LOSIMP=Y,DDIAGIMP=N,MEDIA=UNKNOWN"
Northside,TSTDAT=2006-01-13,TSTLOCN=BTI Northside,"
Obtain SFP transceiver label information
Remove the SFP transceiver from the circuit pack and record the manufacturers
name.
E.2.2.4 Detailed description of the problem

While the problem is fresh in your mind, write down a brief description of the
problem so that you will have this information available when you contact support.
Diagnostic error messages
Collect and print recent error messages that can assist in the diagnosis of the
problem. Enter the following at the TL1 command line interface:
RTRV-LOG:[TID]:[<lognm>]:<CTAG>::[<stalogid>],[<stplogid>],[<stadat>],
[<statm>],[<stpdat>],[<stptm>];
Example input
RTRV-LOG:NETSTENDER:all:100::,,,,,;
Example output
NETSTENDER 2002-11-05 15:00:04
M
100 RTRV
/*

"SLOT-1-4,MJ,REPLUNITMISS,NSA,2002-11-05,15-00-04,,,,,,\"Equipment
missing.\",,,,,"
"SLOT-1-4,CL,REPLUNITMISS,NSA,2002-11-05,15-00-00,,,,,,\"Clear equipment
missing.\",,,,,"
"CU-1,MJ,REPLUNITMISS,NSA,2002-11-05,15-00-00,,,,,,\"Cooling Unit
missing.\",,,,,"
"CU-1,MJ,REPLUNITMISS,NSA,2002-11-05,15-00-04,,,,,,\"Clear Cooling Unit
missing.\",,,,,"
*/
NETSTENDER>
NETSTENDER 2002-11-05 15:00:00
M
100 COMPLD
Details about recent configuration changes or network changes
If there have been any recent changes to either the Netstender or the network that
is used to communicate with the Netstender, make a note of this information so
that you will have this information available when you contact support.
Alarms raised as a result of the problem
If any alarms are raised, make a note of this information so that this information is
available when you contact support.
E.3 How to contact BTI support

For technical support, email support@btisystems.com or call 1-866-431-4967. If
your Netstender equipment is supplied by a licensed reseller, then please call your
resellers support line.
If you are a registered Netstender customer, you can access support services
through the customer portal at www.btisystems.com.
BTI Systems
50 Northside Road
Ottawa, ON K2H 5Z6
(613) 248-9154
Product Release 6.2

Document Version 01
January 2008
Part Number BP1A74FB
STANDARD

Oamp Guide 6-2 Stand 01

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oamp Guide 6-2 Stand 01

Uploaded by

Copyright:

Available Formats

Operations, Administration,

Maintenance & Provisioning Guide

Product Release 6.2

Copyright 2003-2008 BTI Systems All rights reserved.

1.0 Netstender overview

1.1 Netstender features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.0 Netstender state management

2.1 Entity management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Product Release 6.2 STANDARD iii

2.3 Telcordia state attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.0 Operating the Netstender

3.1 Starting up the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

iv Netstender OAM&P Guide Document Version 01

3.5.2 Modes of TL1 operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.0 Installing optional Netstender circuit packs

4.1 Installing optical amplifier circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

5.0 Connecting circuit packs

5.1 Amplifier configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Product Release 6.2 STANDARD

5.1.1 Connecting fibers between an OLAM and a DCM . . . . . . . . . . . . . . . . . . . . . .

6.0 Connecting expansion shelves

6.1 Netstender 2060 expansion shelves overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

7.0 Provisioning the Netstender

7.1 How Netstender provisioning works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

vi Netstender OAM&P Guide Document Version 01

7.4.1.2 Setting the system identification code. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

Product Release 6.2 STANDARD

7.9.2.4 Modifying the definable parameters of a transceiver port . . . . . . . . . . . . 7-83

viii Netstender OAM&P Guide Document Version 01

8.0 Netstender performance monitoring

8.1 Understanding performance monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

9.0 Administering the Netstender

Product Release 6.2 STANDARD

9.1 Security management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

x Netstender OAM&P Guide Document Version 01

9.9 Configuration profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.0 Replacing circuit packs

10.1 Common equipment circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Appendix A: Optical back reflection safety feature

A.1 Principle of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Appendix B: Working with the configuration database

B.1 Configuration database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Product Release 6.2 STANDARD

Appendix C: Universal connectors

C.1 About universal connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Appendix D: ESI command line interface

D.1 Expansion shelf interface access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Appendix E: Contacting BTI support

E.1 Before you contact BTI support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

xii Netstender OAM&P Guide Document Version 01

Product Release 6.2 STANDARD xiii

This document is released.

xiv Netstender OAM&P Guide Document Version 01

Document Revision History

The former Optical Link System (OLS) is rebranded as the

Product Release 6.2 STANDARD xv

Document Revision History

Changed the name Graphical Craft Interface (GCI) to Netstender

xvi Netstender OAM&P Guide Document Version 01

Document Revision History

Added the following equipment to all applicable descriptions and

Product Release 6.2 STANDARD xvii

Document Revision History

xviii Netstender OAM&P Guide Document Version 01