323-1851-221 (6500 R13.0 SLAT) Issue3
323-1851-221 (6500 R13.0 SLAT) Issue3
323-1851-221 (6500 R13.0 SLAT) Issue3
What’s inside...
SLAT process overview
Nodal SLAT procedures
Photonic layer provisioning procedures
Photonic layer site testing procedures
Passive OTS network procedures
Service layer site testing procedures
Wavelength addition and deletion
MSPP network SLAT procedures
Broadband network SLAT procedures
Appendix A: Observing product and personnel safety guidelines
Appendix B: Quick-start turning-up using the Node Setup application—examples
For additional office locations and phone numbers, please visit the Ciena web site at www.ciena.com.
Contents 0
6-13 Testing L2SS, 20G L2SS, and PDH gateway equipment protection 6-58
6-14 Testing RPR circuit packs 6-63
6-15 Testing 1x10GE EPL circuit packs 6-67
6-16 Testing SuperMux circuit packs 6-70
6-17 Setting a hardware terminal loopback for a network element 6-78
6-18 Restoring a network element to its initial state 6-81
Labeling 10-6
Circuit pack labels 10-6
Using optical fibers 10-30
Handling optical fibers 10-30
Splicing optical fibers 10-31
Repairing optical fibers 10-31
Working with systems cooled by forced air 10-32
Working with power 10-33
Grounding requirements 10-33
Working with AC power 10-36
Working with DC power 10-36
Dissipating static electricity 10-40
Preventing circuit pack damage and pluggable module damage 10-46
Handling, installing, storing, or replacing circuit packs and pluggable
modules 10-46
Transporting circuit packs and pluggable modules 10-48
Controlling equipment access 10-48
Controlling equipment environment 10-48
List of procedures
10-1 Applying a 1M Hazard Level Caution label on NTK552AAE5, NTK552BAE5,
NTK552FAE5, NTK552FB, and NTK552GAE5 circuit packs 10-53
Issue 3
The Attention box listing the applications where this software release can be
used has been removed. If you have 6500 Release 13.0 software, refer to the
Planning Guide, Part 1, NTRN10EG, for supported applications. For
information specific to other 6500 13.0x releases, refer to the Planning Guide
Part 1, or the Addendum for that release.
Issue 2
This document was up-issued to include changes to the Attention box to
indicate the applications where this software release can be used.
Issue 1
The following new/enhanced features are covered in this document:
• Packet Transport System (PTS)
Supporting WaveLogic Photonics 6500 Data 6500 Control Plane Submarine Networking
Documentation Coherent Select Application Guide Application Guide Application Guide
(323-1851-980) (NTRN15BA) (NTRN71AA) (NTRN72AA)
6500 Photonic Common 6500 - 5400 / 8700 Fiber Node Return Universal AC Rectifier
Layer Guide Photonic Layer Interworking Solution Configuration Application Note
(NTRN15DA) Technical Publications (323-1851-160) (323-1851-985) (009-2012-900)
Fault Management -
Customer Visible
Logs
(323-1851-840)
BB broadband
CS Coherent Select
DISP dispersion
NE network element
Rx receive
SP shelf processor
TR transmit/receive
Tx transmit
WT wavelength translator
Figure 1-1 on page 1-5 outlines the 6500 end-to-end SLAT process flow. Make
sure you review the “SLAT prerequisites” before starting the SLAT process.
Complete either:
• “Nodal SLAT procedures” at the first 6500 site. See “Node setup solutions”
on page 2-3 for the Node Setup simplification solution introduced in
release 10.0.
• script-based commissioning solution (if a commissioning script file exists).
See “Node setup solutions” on page 2-3.
If the site contains 6500 photonic layer circuit packs, perform the “Photonic
layer provisioning procedures” and “Photonic layer site testing procedures”
while you are at the site. If the site contains service circuit packs, perform the
“Service layer site testing procedures” while you are at the site (optional).
Then move on to the next 6500 site and repeat the same process until all 6500
sites have been visited.
If you are deploying a Passive 6500 photonic layer system, perform the
“Passive OTS network procedures” to turn up the Passive system. (For
information on Passive applications, refer to the 6500 Packet-Optical Platform
Photonic Layer Guide, NTRN15DA.)
If your network contains non-6500 amplifiers, perform nodal SLAT and site
testing at all amplifier sites according to amplifier SLAT documentation.
Once the site testing procedures are done, perform “Wavelength addition and
deletion”. If your network contains non-6500 amplifiers, perform amplifier
network SLAT according to amplifier SLAT documentation.
After completion of the end-to-end SLAT process, you can perform final
system provisioning to customize your system. For 6500 provisioning
procedures, refer to Part 1 and Part 2 of Configuration - Provisioning and
Operating, 323-1851-310, Part 1 to Part 3 of Configuration - Bandwidth and
Data Services, 323-1851-320, and Administration and Security,
323-1851-301.
For PKT/OTN transport and switched services, refer to OTN I/F, PKT I/F, and
PKT/OTN I/F Circuit Packs, 323-1851-102.8 for the provisioning procedures
required to bring the OTN I/F, PKT I/F, and PKT/OTN I/F circuit packs to a
ready to carry traffic state.
For PTS services, refer to PTS Circuit Packs and Modules, 323-1851-102.9
for the provisioning procedures required to bring the PTS circuit packs to a
ready to carry traffic state.
Figure 1-1
End-to-end SLAT process flowchart
See 6500
Packet-Optical
“Photonic layer site testing Platform Submarine
procedures” (Chapter 4) Networking
Application Guide,
NTRN72AA.
Flexible
Grid
Wavelength addition and deletion
(see Configuration - Control
Fixed Plane, 323-1851-330)
grid
“Wavelength addition and deletion”
(Chapter 7)
MSPP Broadband
“MSPP network SLAT “Broadband network SLAT
procedures” procedures”
(Chapter 8) (Chapter 9)
If photonic equipment is present in the network element If photonic equipment is not present in
the network element
Refer to the CPL Technical Publication Library for details on CPL nodal SLAT
and network SLAT.
1600G Demux VOAs can be set to minimum attenuation when 6500 circuit
packs are deployed, because they have their own, built-in VOA.
When performing the 1600G optical link testing, refer to 6500 Procedure 9-2,
“Performing system acceptance testing” for HCCSREF values and
considerations, and eight-hour system soaking.
Refer to the 1600G Technical Publication Library for details on 1600G nodal
SLAT and network SLAT. Refer to the 1600G Supporting Documentation
Library for details on the implementation of unrepeatered DWDM links with
6500 network elements.
MOR/MOR+
Refer to Figure 1-2 on page 1-9 and Figure 1-3 on page 1-10 for an overview
of network SLAT for a system that includes 6500 and MOR/MOR+.
If the 6500 at one end uses OC-192/STM-64 DWDM optical interfaces and at
the other end uses OC-192/STM-64 AM1/AM2 DWDM tunable optical
interfaces, you must contact your Ciena representative for link budget
validation.
Figure 1-2
Overview of 6500 network SLAT with 1600G or MOR+ (Broadband functions)
Adjust Tx powers to
equalize system Autodiscover 6500 wavelengths
Tx dispersion value set
Tx/Rx pairs optimized
by TR control
Line Txs of 6500 BB
circuit packs that do Validate 6500 BB Validate 6500 BB WT TR Control and
not support TR Control OTU connections OTU connections
Dispersion Scan
(Search for CD value to
achieve Tx/Rx continuity)
TR Control
Init Alarm
OOS Optimization
(Coarse adjustment of
optical parameters to
achieve best BER)
SS Optimization No TR Control
(fully optimized) Alarm
Soak ( 8 Hours)
FEC counts match System acceptance testing
expected BER for (Validate that all Line Rxs at all 6500 BB NEs meet
SLAT expected pre-FEC BER)
Figure 1-3
Overview of 6500 network SLAT with 1600G or MOR+ (MSPP functions)
Adjust Tx powers to
equalize system 1600G/MOR+ link equalization
1600G/MOR+ Demux
VOAs adjustments
SLAT prerequisites
To start SLAT, engineering data specific to the deployment must be generated
in the planning stages in the form of an engineering documentation package
(EDP) or international documentation package (IDP) for each site. This
engineering data contains items such as provisioning information, fiber
connections, circuit pack placements, data communications strategy, and link
budget design information.
You must have the following information and equipment and meet the following
pre-requisites before 6500 SLAT can begin.
Equipment requirements
You must have the 6500 equipment specific to the network element as
specified in the EDP or IDP. The circuit packs and their associated slot
numbers must be identified.
Table 1-2
Supporting equipment list
Item Check
Access to the 6500 load (if SP is not equipped with the correct load), see
Note.
Craft computer that meets minimum system requirements—refer to Site
Manager for 6500 and CPL Fundamentals for this release, 323-1851-195,
for details
Current release Site Manager software installed on your craft computer—
refer to Site Manager for 6500 and CPL Fundamentals for this release,
323-1851-195, for installation procedures.
Note 1: Advanced SAT and the Node Setup application support Java 1.7
and higher.
Note 2: After Site Manager is installed, the Nodal SLAT Assistant Tool can
be launched directly from the Site Manager Tools menu for all previous
releases supported by the installer.
If you will be using OneControl: OneControl installed on the OneControl
server—refer to the OneControl documentation suite for more information
Optical fiber numbers or labels for each port to be connected
Table 1-2
Supporting equipment list (continued)
Item Check
Ethernet cables:
• 10Base-T RJ-45 crossover cable (network element to craft computer)
• 10/100Base-T DB-9 to RJ-45 cables (network element to DCN)
• RJ-45/DB-9 adapters
Voltmeter
Optical power meter
Fiber cleaning kit
Fiberscope with LC adapter (and SC adapter for optical layer equipment
as required)
Spare patch cords and adapters
Note: Starting with 6500 Release 12.1, neither a S/W DVD (NTK562xx) nor
release-specific paper certificates (NTK569xx) are available. Use your company's
Ciena portal (portal.ciena.com) to access 6500 software releases and software
licenses. Starting with 6500 Release 12.1, you must order a release-specific
software license (S74-LIC-NTK569xx) for each shelf that runs the release and use
the licensing portal to activate the software licenses generated by the order. The
activated licenses must be uploaded to your company's License Manager and each
6500 shelf configured to retrieve the required license(s). For more information on
software licenses, refer to ‘Licenses and ordering process’ in Planning - Ordering
Information, 323-1851-151.
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
Extended NE 1 to 64 alphanumeric Can include any combination of upper and no
Name characters lower case letters, numbers, or special
characters excluding the following
characters: backslash (\), space,
double-quote ("), colon (:), semicolon (;),
ampersand (&), greater than (>), less than
(<), percent (%), or comma (,).
CLLI Up to 11 11-character alphanumeric code in the form no
characters CCCCSSBBUUU where:
• CCCC denotes the city, town, or locality
code
• SS denotes the geographical area (for
example, state or province code)
• BB denotes the building code or network
site
• UUU denotes the network entity or unique
traffic unit identifier
The combination of these codes comprise a
unique place, a unique building, and a
specific entry.
The CLLI cannot include special characters
but can include spaces. Spaces are included
in the length of the CLLI.
NE Configuration - IPv4 tab (Note 1)
Shelf Number 1 to 254 shelf identifier of the shelf. Must be unique yes
within a site
Photonic shelves (6500 and/or CPL) at a
given site (with the same Site ID) must have
unique logical shelf numbers (also referred to
as Shelf ID), regardless of node name (TID).
Note: A Photonic shelf refers to a shelf with
an OTS provisioned on it.
IPv4 Shelf IP standard dot notation also known as circuitless IP address yes
Address
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
Site ID 0 to 65535 identifier of the site. Must be the same for all yes for
NEs within a site. photonic
In order for Visualization to work properly, the services
Site ID on non-photonics shelves should be
set to match the Site ID of photonic shelves at
the same site.
For SPLI, alarm correlation, and OTS
management to function, the Site ID must be
provisioned to a non-zero value.
Site Name up to 20 characters unique text string assigned to the site no
Location up to 64 alphanumeric The location (latitude and longitude) no
characters associated with the selected shelf. The
preferred format is as follows (note that there
is no space following the comma):
<latitude>,<longitude>
where
<latitude> = -90.000000 to +90.000000 ("+"
optional)
<longitude> = -180.000000 to +180.000000
(“+” optional)
TID DISABLE or ENABLE enables/disables TID consolidation for the yes for
Consolidation NE. photonic
For Control Plane considerations, see Note services
15. (channel
access nodes
only)
TID DISABLE or ENABLE identifies if the NE is a TID consolidation yes for
Consolidation primary. photonic
Primary For Control Plane considerations, see Note services
15. (channel
access nodes
If you are commissioning the Primary shelf of only)
a TIDc that will be managed by OneControl, it
is preferable to enable the SNMP proxy, see
“SNMP Provisioning (Note 5)” on page 1-28.
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
NE Mode SONET/SDH/SDH-J software mode of network element yes
IPv4 ON, OFF You must enable either IPv4, or IPv6, or both. see the
If IPv4 is enabled (ON), you must provision Description
the IPv4 shelf IP address. If IPv4 is not
enabled (OFF), do not provision the IPv4
shelf IP address.
If IPv6 is enabled (ON), you must provision
the IPv6 shelf IP address. If IPv6 is not
enabled (OFF), do not provision the IPv6
shelf IP address.
IPv6 ON, OFF You must enable either IPv4, or IPv6, or both. see the
If IPv4 is enabled (ON), you must provision Description
the IPv4 shelf IP address. If IPv4 is not
enabled (OFF), do not provision the IPv4
shelf IP address.
If IPv6 is enabled (ON), you must provision
the IPv6 shelf IP address. If IPv6 is not
enabled (OFF), do not provision the IPv6
shelf IP address.
IPv6 Hop Limit 1 to 255 Sets the IPv6 hop limit no
Default is 90.
IPv6 Capable YES, NO Indicates whether the NE is IPv6 capable or read only
not.
If the value is NO, IPv6 tabs are not be
displayed in the SLAT tool and the user
cannot perform any IPv6 related provisioning.
The SLAT tool allows IPv6 related
provisioning only if IPv6 Capable is YES.
GCC0 Mode DISABLED, IISIS, controls the auto-provisioning behavior of the no
OSPF GCC0 comms channel. Default = Disabled
NDP mode DISABLED (default), controls the auto-provisioning behavior of the no
ENABLED NDP feature.
If the value is Disabled, there is no action
performed. If the value is enabled, the
NDPMODE is used to auto provision an NDP
link on a GCC0 channel (when a facility is
created). It also enables the NDP feature the
first time a facility is created.
Alarm ON (default), OFF indicates whether the alarm correlation no
Correlation feature is enabled or disabled
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
Bay number 0 (unprovisioned) to 25 unique number assigned to the bay no
Not supported.
Frame up to 21 alphanumeric unique text string assigned to the equipment no
identification characters
code
Subnet name up to 36 alphanumeric unique text string assigned to each shelf no
characters
Shelf Synch YES, NO (default) enables (YES) or disables (NO) shelf synch no
between the primary shelf and the member
shelves
Air Filter ENABLE, enable or disable the “Filter Replacement no
Replacement DISABLE (default) Timer Expired” alarm
Alarm
Air Filter 1 to 1826 (default 731 sets the number of days before the “Filter no
Replacement or 730) Replacement Timer Expired” alarm is raised
Timer (in Days) See Note 15.
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
CS Control • ENABLED Determines whether Coherent Select no
• DISABLED provisioning is enabled or disabled at a nodal
level.
Note: The CS Control value can be changed
on a primary or member shelf of a
consolidated node. However, if Shelf Synch is
enabled, the CS Control parameter cannot be
edited on a member shelf. If the CS Control
parameter is changed on a primary shelf, it
broadcasts the value to all member shelves.
Auto OSC/ • OSPF (default) Defines whether the OSC will be provisioned no
OSPF • DISABLED or not when the SFP on the 2xOSC or
Provisioning SPAP-2 w/2xOSC circuit pack is provisioned.
For more information, see the section on
Optical Service Channel (OSC) interface in
Configuration - Provisioning and Operating,
Part 1 of 2, 323-1851-310.1.
Default Control Flexible Grid Capable, sets the default control mode. Any newly no
Mode Fixed ITU (default) provisioned ROADM or COADM OTSs use
the provisioned value. Value for individual
OTSs can be edited using the OTS
management application, Configuration -
Provisioning and Operating, Part 1 of 2,
323-1851-310.2 for details.
Note: All TIDc nodes in the network must be
set to Flexible Grid Capable before Flexible
Grid can be implemented.
Default 0-4800, default is 6.250 sets the default filer edge spacing each side no
Filter-edge of a media channel (MC). Any newly
Spacing (GHz) provisioned MCs use the provisioned value.
TL1 Gateway DISABLED (default), specifies the TL-1 gateway function as no
GNE ENABLED enabled or disabled. If enabled, the node can
forward TL-1 commands to a remote node.
TL1 Gateway DISABLED (default), indicates whether or not the node accepts no
RNE ENABLED TL-1 sessions from a TL-1 gateway. If
disabled, the node will not accept TL-1
gateway connections.
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
ETH 10G • 10.7G - GFP/OPU2 Determines the system-wide default ETH10G no
Mapping (Standard/MAC mapping when an ETTP or Mapped ETTP
transparent) [default] facility (with a rate of ETH10G) is created.
• 10.7G - GFP/OPU2+7 When set, this parameter does not impact
(Preamble/Ordered existing ETTP and Mapped ETTP facilities.
Set/MAC transparent)
• 11.09G - OPU2e
(PCS transparent)
Line Flapping 30 to 600 Indicates how long (in seconds) the line must no
Alarm Clear (default is 600) be error free to clear the Line Flapping alarm.
Time (30-600 Note: This parameter is only editable if the
Secs)
Line Flapping Alarm parameter is set to
Disabled first. If it is enabled, then disable it,
change the Line Flapping Alarm Clear Time
value, and re-enable the alarm.
Line Flapping • DISABLED (default) Determines whether the Line Flapping alarm no
Alarm • ENABLED is enabled or disabled.
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
Alarm Info Checkboxes: Determines whether enhanced alarm no
• Disabled reporting is enabled or disabled. When
enabled, depending on the option(s)
• Card Type selected, additional details are displayed in
• Wavelength the corresponding columns in the information
• Frame Identification table, “Alarm details” field, and “Event details”
Code field of the Site Manager Active Alarms,
Historical Fault Browser and Consolidated
• Subnet Name Alarms applications.
• Physical Shelf ID • Disabled: disables enhanced alarm
• Bay Number reporting, and “-” is displayed in the columns/
• Label fields below:
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
NE Configuration - IPv6 tab (Note 1)
Aid - Index Index: 1 to 254 index-based AID for the IPv6 shelf address yes - Only
Index can be
modified.
Type and
Shelf are
read-only.
Circuit SHELF-<1 to 255> displays the shelf circuit identifier, which no (cannot be
includes the shelf number changed)
IPv6 Shelf IP eight groups of four also known as circuitless IP address yes
Address hexadecimal digits
separated by colons, as
per RFC 4291
Prefix 128 The IPv6 prefix for the shelf interface. The no (cannot be
only valid value is 128 (this is a host changed)
interface).
GNE Configuration - IPv4 tab
GNE YES, NO specifies whether the shelf is a GNE no
Single Shelf IP YES, NO defines whether shelf IP address should no
equal the COLAN IP address
GNE Group integer (1-255) specifies the redundancy group that the GNE yes only if
belongs to for master/backup negotiation configuration
is
REDUNDANT
ARP
Primary YES, NO defines whether the NE is the primary or yes only if
secondary communication gateway configuration
is
REDUNDANT
ARP
GNE up to 36 alphanumeric a unique name identifies the GNE, for yes if to be
Subnetname characters standalone or redundant private IP managed by
configurations OneControl
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
GNE Standalone ARP, based on the selected comms configuration, yes
configuration Redundant ARP, some GNE parameters are blocked
radio button
Redundant NAT,
Standalone OSPF,
Redundant OSPF,
Standalone Static,
Standalone Private IP,
Redundant Private IP
GNE Configuration - IPv6 tab
GNE YES, NO specifies whether the shelf is a GNE yes
GNE Standalone OSPFv3, specifies the GNE type yes
configuration Redundant OSPFv3,
radio button
Standalone Static,
Standalone ND Proxy
Auto Equipping
Enabled slots slots 1, 2, and 15, 25, Slots equipped with WT, OTR, 2x10G OTR, yes
27, 83-90 for 2-slot OTSC, and MOTR circuit packs must have
shelf auto-equipping enabled.
slots 1 to 7 and 15, 83 SONET and SDH-J NEs have all
to 90 for 7-slot shelf auto-equipping enabled by default.
slots 1 to 16, 83 to 90
for 14-slot shelf
slots 1 to 18, 21 to 28,
31 to 38, 41 and 42, 51
to 62 for 32-slot shelf
slots 1-8, 15, 16, and 83
to 86 for 6500-7
packet-optical shelf
select all, deselect all
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
OSPF Router Provisioning - IPv4 tab and IISIS Router Provisioning (applies to IPv4 only)—see
Table 1-4 on page 1-32.
Before performing the provisioning steps, refer to the data communications planning in Data
Communications Planning and User Guide, 323-1851-101, in order to understand the specific DCN
configuration.
If you will be provisioning OSPF/IISIS router during the Shelf IP, COLAN, or DCC Provisioning SAT
steps, you do not have to provision the router at the OSPF Router Provisioning or IISIS Router
Provisioning step. The OSPF/IISIS router provisioning during the Shelf IP, COLAN, or DCC Provisioning
SAT steps overwrites the router provisioning performed at the OSPF Router Provisioning or IISIS Router
Provisioning step.
OSPF Router Provisioning - IPv6 tab—see Table 1-5 on page 1-37
ILAN Provisioning - IPv4 tab (Note 5 and Note 13)
Aid Index - 1 to 254 Instance-based AID see Note 2
IP Address and standard dot notation ILAN IP address and subnet mask and Note 11
Subnet Mask
Port Enabled YES, NO enables or disables the port
See Note 17.
Routing NONE, OSPF, IISIS, If OSPF, IISIS, or OSPF/IISIS is selected, see Note 9
Protocol OPSF/IISIS you must provision the corresponding circuit
parameters (see Table 1-4 on page 1-32).
ILAN Provisioning - IPv6 tab (Note 5 and Note 13)
Aid - Index Index: 1 to 254 instance-based AID yes
Circuit ILAN-shelf-port Specifies which ILAN port no
IP Address Eight groups of four IPv6 address to assign to ILAN interface. yes
hexadecimal digits
separated by colons, as
per RFC 4291
IP network 1 to 128 The IPv6 prefix associated with the IPv6
prefix address of the ILAN interface
Port Enabled NO (default)/YES Specifies whether port is enabled or not. no
See Note 17.
Routing NONE/OSPFv3 If OSPFv3 is selected, you must provision the see Note 9
Protocol corresponding circuit parameters (see Table
1-5 on page 1-37).
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
Shelf IP Provisioning - IPv4 tab
IP Address and standard dot notation also known as circuitless IP address and see Note 2
Subnet Mask subnet mask
Routing NONE, OSPF, IISIS, If OSPF, IISIS, or OSPF/IISIS is selected,
Protocol OSPF/IISIS you must provision the corresponding circuit
parameters (see Table 1-4 on page 1-32).
Shelf IP Provisioning - IPv6 tab
Aid - Index Index: 1 to 254 instance-based AID yes
Circuit NONE, OSPFV3 If OSPFV3 is selected, you must provision yes
the corresponding circuit parameters (see
Table 1-5 on page 1-37).
IPv6 Shelf eight groups of four IPv6 address to assign to shelf yes
Address hexadecimal digits
separated by colons, as
per RFC 4291
Prefix 128 The IPv6 prefix for the shelf IP address is yes
always 128.
Routing None, OSPFv3 specifies whether OSPFv3 is enabled on the
protocol interface
IISIS Router Provisioning (applies to IPv4 only) (see Table 1-4 on page 1-32)
COLAN Provisioning - IPv4 tab (Note 5 and Note 6) (See Table 1-4 on page 1-32 for complete list
of parameters)
Access COLAN-shelf-port COLAN port access identifier yes
Identifier (AID)
IP Address and standard dot notation COLAN IP address and subnet mask see Note 2
Subnet Mask and Note 7
Proxy ARP ON, OFF enables or disables the proxy ARP on the see Note 6
COLAN port and Note 8
Port Enabled YES, NO enables or disables the port no
See Note 17.
Routing NONE, OSPF, IISIS, / If OSPF, IISIS, or OSPF/IISIS is selected, see Note 2
Protocol OSPF/IISIS you must provision the corresponding circuit and Note 7
parameters (see Table 1-4 on page 1-32).
COLAN Provisioning - IPv6 tab (Note 5 and Note 6) (See Table 1-5 on page 1-37 for complete list
of OSPFv3 parameters.)
Aid (Access IPADDR-shelf-index, index-based AID for the COLAN IP address yes
Identifier) where Index is 1 to 254.
Circuit COLAN-shelf-port, COLAN circuit identifier yes
where port is X or A.
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
IP Address eight groups of four COLAN IPv6 address yes. See Note
hexadecimal digits 2 and Note 7
separated by colons, as
per RFC 4291
IP network 1 to 128 the IPv6 prefix associated with the IPv6 yes
prefix address of the COLAN interface
Port Enabled NO (default), YES enables or disables the port no
See Note 17.
Routing NONE, OSPFv3 If OSPFv3 is selected, you must provision the see Note 2
Protocol corresponding circuit parameters (see Table and Note 7
1-4 on page 1-32).
ARP/ND Proxy Provisioning - IPv4 tab
Start and End standard dot notation proxy ARP IP address(es) see Note 2
proxy ARP IP and Note 8
addresses
ARP/ND Proxy Provisioning - IPv6 tab
Aid (Access NDPROXY-shelf-index, index-based AID of the ND Proxy entry yes
Identifier) where Index is 1 to 150.
Circuit COLAN-shelf-X COLAN-X port yes
IPv6 Address eight groups of four IPv6 address to add to ND Proxy table yes. See Note
hexadecimal digits 2 and Note 7
separated by colons, as
per RFC 4291
Network address translation (NAT) Provisioning
DCN IP standard dot notation DCN IP address see Note 2
Address
Remote NE IP standard dot notation shelf IP address
Address
Prime YES indicates whether the shelf IP address is
used for mapping of incoming packets
Dynamic NAT Provisioning
NAT Starting 1024 to 65535 Sets the base UDP/TCP port value no
Port dynamically allocated for connections flows
managed by NAT services. It applies to
Redundant NAT and Private IP GNEs.
Note: If not specified, the current value is not
changed. If never configured, the default is
50000.
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
NAT Number 256 to 1024 Specifies the number of UDP/TCP port no
Of Entries values dynamically allocated for connections
flows managed by NAT services. It applies to
Redundant NAT and Private IP GNEs.
Note: If not specified, the current value is not
changed. If never configured, the default is
512.
Port Filtering Provisioning
Access COLAN-shelf-port COLAN port identifier yes
Identifier (AID)
Action PERMIT, BLOCK the action to be taken when IP packets match yes
the filter rule.
Location REMFORWARDOUT sets the location of the filter rule for the yes
INGRESS provisioned port.
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
Static Routes Provisioning - IPv4 tab
IP Address and standard dot notation IP address and subnet mask of the static yes
Subnet Mask route see Note 2
Next Hop standard dot notation IP address of the next hop and Note 12
Circuit COLAN, ILAN ports port used to get to the next hop
Cost 1 to 65535 cost of the link
Carrier Section/RS, sets the DCC/GCC channel used, section/ yes
line/MS, GCC0, GCC1 RS, line/MS, GCC0 or GCC1 (options
available depend on circuit pack type and
function)
Description 1 to 64 characters label for the static route no
Static Routes Provisioning - IPv6 tab
Aid STATICRT-shelf-index, index-based AID of the static route yes
where index is 1 to 80
IP Address eight groups of four IPv6 address of the static route yes
hexadecimal digits see Note 2
separated by colons, as and Note 12
per RFC 4291
IP network 0 to 128 the IPv6 prefix associated with the IPv6 yes
prefix address of the static route
Next Hop eight groups of four IPv6 address of the next hop no
hexadecimal digits
separated by colons, as
per RFC 4291
Circuit COLAN, ILAN ports port used to get to the next hop yes
Cost 1 to 65535 cost of the link yes
Carrier Section/RS, line/MS, sets the DCC/GCC channel used, section/ yes
GCC0, GCC1 RS, line/MS, GCC0 or GCC1 (options
available depend on circuit pack type and
function)
description 1 to 64 characters optional description of the static route no
redistribute OFF, OSPFV3 specifies whether to redistribute the static no
route into OSPFv3
rdtype INTERNAL, If redistributing into OSPFv3, specifies the no
EXTERNAL type of metric used. Internal uses Type-1
metric, External uses Type-2 metric.
OSPF - Routes Distribution / IISIS - Routes Distribution (applies to IPv4 only)—see Table 1-4 on
page 1-32
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
SNMP Provisioning (Note 5)
Agent state ENABLED, DISABLED enables or disables SNMP yes
Version alphanumeric indicates the version of the SNMP no
characters
Alarm Masking On, Off enables or disables alarm masking no
Proxy On, Off enables or disables SNMP proxy – option no
disabled for standalone NEs and member
shelves. Proxy can only be enabled when the
primary shelf is 6500.
If you are commissioning the Primary shelf of
a TIDc that will be managed by OneControl, it
is preferable to enable the SNMP proxy.
Request numeric value timeout value for SNMP requests – option no
Timeout disabled for standalone NEs and member
shelves
Destination alphanumeric indicates the trap destination no
characters
IP Address For IPv4, standard dot trap destination IP address no
notation.
For IPv6, eight groups
of four hexadecimal
digits separated by
colons, as per RFC
4291.
UDP port 1 to 65535 the user datagram protocol (UDP) port no
Version V1, V2C, V3 version of trap to be sent no
For V3, see Note 16.
UAP PUBLIC, SYSADMIN, user access privilege of the V2 user to be no
OBSERVER, used to send traps
CUSTOMER1,
CUSTOMER2,
OPERATOR
UID alphanumeric The SNMP V3 user if version is specified as no
characters a V3 trap. See Note 16.
the user information used to send traps
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
TRAP DISABLE, disables or enables TL-1 traps and/or SAOS no
Configuration ENABLE_ALL, traps on a per receiver basis
TL1_TRAPS_ONLY, For V1 or V2c version, only TL-1 traps are
SAOS_TRAPS_ONLY supported. Therefore, only
TL1_TRAPS_ONLY and DISABLE options
are valid.
For V3 version, both TL-1 and SAOS traps
are supported. Therefore, all options are
valid. Also see Note 16.
Security Provisioning
Password Standard, Complex, sets the password creating rules to standard, no
Rules Custom complex, or custom
ADMIN/ alphanumeric sets the password for Admin user or Surveil no
SURVEIL characters user
New Password
Confirm New
Password
SSH/TELNET and HTTP/HTTPS Server Provisioning
SSH Server ENABLED, DISABLED set the status of the SSH server no
Active State Note: An SSH server cannot be disabled
unless a telnet server is enabled.
Maximum SSH 1 to 18 (default 5) indicates the maximum number of concurrent no
Active SSH sessions that are allowed to the network
Sessions element.
SSH Idle 0 to 99 (default 30) sets the time (in minutes) before an idle SSH no
Timeout session is disconnected. A value of 0
(minutes) indicates infinite (no timeout).
Telnet Server ENABLED, DISABLED set the status of the Telnet server no
Active State Note: An SSH server cannot be disabled
unless a telnet server is enabled.
Maximum 1 to 18 (default 18) sets the maximum number of concurrent no
Telnet Active Telnet sessions that are allowed to the
Sessions network element
Note: If both SSH and telnet servers are
enabled, the total of maximum number of
SSH and telnet sessions must not exceed the
system maximum number of sessions (18).
Telnet Idle 0 to 99 (default 30) sets the time (in minutes) before an idle no
Timeout Telnet session is disconnected. A value of 0
(minutes) indicates infinite (no timeout).
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
HTTP Server ON, OFF sets the status of the HTTP server no
Active State
HTTPS Server ON, OFF sets the status of the HTTPS server no
Active State
Craft Access Provisioning—see Table 1-4 on page 1-32 for IPv4 and Table 1-5 on page 1-37 for
IPv6
Aid LAN-15/16/41/42 or as Craft Port AID yes
applicable for shelf
types
IP Address and standard dot notation Craft LAN port IP address and subnet mask no
Subnet Mask See Note 2
and Note 3.
IPV4 Server ON (default), OFF sets the IPV4 server on or off no
State
IPV6 Server ON, OFF (default) sets the IPV6 server on or off no
State
Host Only ON, OFF (default) sets the host only mode. When On, the no
Mode interface only accepts packets that terminate
at its IP address and routing updates and
packets to be forwarded through other
circuits are dropped.
Port Enabled YES, NO indicates if the port is enabled no
Craft OSPF/IISIS Provisioning—see Table 1-4 on page 1-32 for IPv4 and Table 1-5 on page 1-37
for IPv6
Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
Note 1: Various SAT panels also include other parameters, which are either read-only or not mandatory
to provision at the commissioning stage. For more information on parameters, see Part 1 of
Configuration - Provisioning and Operating, 323-1851-310.
Note 2: For more information about data communications engineering rules, refer to Data
Communications Planning and User Guide, 323-1851-101.
Note 3: Craft IP address is required only if you want the ability to access remote network elements using
the LAN-15 (or 41) port. Assign unique IP addresses to each LAN-15 (or 41) port in the system. Do not
use 10.0.0.1.
Note 4: OTM2 TR control applies only to NGM ports and is expected to be always ON (default) during
SLAT. 10G OTR Port 1, MOTR Port 1 and 2x10G OTR Ports 1 and 3 do not support TR Control.
Note 5: The number immediately following OTM2, COLAN, ILAN, and DEST indicates the shelf number.
Note 6: If you want ARP Proxy enabled on the COLAN port, you must select ARP Proxy ON in the
COLAN Provisioning step.
Note 7: COLAN provisioning is required only if COLAN is connected directly to the DCN (The COLAN
Provisioning step becomes highlighted only if in the COLAN & GNE Configuration step you have
selected an option where COLAN is connected to the DCN.).
Note 8: Proxy ARP and ND Proxy are only supported on the COLAN-X port.
Note 9: ILAN provisioning is required only if you intend to use ILAN. There are two ILAN ports defined
on a 6500 NE, namely ILAN-IN and ILAN-OUT.
Note 10: If you select the OSPF or OSPF/IISIS (IPv4 only) routing protocol and the Shelf IP address is
not defined on the NE, a warning message will be displayed to first define the Shelf IP address and the
operation will be aborted.
Note 11: The NSAP is up to 40 characters depending on the first 2 characters (AFI). For example, for
an AFI of 49, the range is 20 characters (6 characters for area address, 12 characters for system id, and
2 characters for network selector). The network selector (NSEL, last 2 bytes of NSAP) of the provisioned
NSAP destination address must be set to ‘00’ (6500 internally automatically sets the NSEL to support
the required transport service).
Note 12: Static routes provisioning is required only if the network element is connected directly to DCN
and OSPF is not configured on the COLAN interface.
Note 13: An OSC channel can be used instead of ILAN to connect shelves that are located at a distance
greater than 100 m. For engineering rules, refer to Data Communications Planning and User Guide,
323-1851-101.
Note 14: The default value for the air filter replacement timer is not displayed [the field displays empty]
as long as the NE is not commissioned. The field can be provisioned only after the shelf IP is defined.
Note 15: In this release. there can only be a single photonic OSRP instance within a TIDc. That is, for
each TIDc, there can only be a single SONET/SDH, OTN, or Photonic Control Plane OSRP instance.
L1 SONET/SDH or OTN Control Plane shelves can be either Primary or Member TIDc shelves. L0
Control Plane shelves must be Primary TIDc shelves only. Refer to the “TID consolidation (TIDc)” section
in the “Node information” chapter in Administration and Security, 323-1851-301, for details about Control
Plane considerations for TIDc.
Note 16: SNMPv3 on the current release of 6500 does not have any usable SNMPv3 USM users by
default. To access the node via SNMP v3, you must log into Site Manager via the Craft port after the
node is set up and create a USM user. For more information, see Fault Management - SNMP,
323-1851-740.
Note 17: If you are provisioning both IPv4 and IPv6 on the LAN ports (ILAN or COLAN), set the same
value for this parameter for both IPv4 and IPv6, that is, either YES (enabled) or NO (disabled).
Otherwise, the enabled/disabled provisioning of one protocol can overwrite the other.
Table 1-4
OSPF and IISIS parameters—SLAT Assistant Tool - IPv4
OSPF Router ID standard dot notation Sets the router ID for the OSPF.
It is recommended that the SHELF IP address (if
provisioned) is used as the OSPF router ID.
Link State external (default), Sets the type of link state announcement used.
Announcement router, summary This parameter is not used and can be left at the default
Type value (External).
Route On (default), Off Sets whether routes or route summaries (On) are
Summarization redistributed.
Autonomous On, Off (default) Sets the autonomous system border router (ASBR). ASBR
System Border identifies whether an OSPF router can accept input (route
Router redistribution) from another autonomous system such as
IISIS, or static routes.
Opaque Filter On, Off (default) Filters out OSPF Type-11 opaque LSAs (Address
Resolution [AR] and Topology Resolution [TR]) not required
by applications at a given site and within a given OSPF area,
in order to reduce memory consumption.
Shelf IP On, Off (default) Re-distributes a route to the local shelf IP into all OSPF
Re-distribution areas that the shelf participates in.
Router Level Level1 (default) Sets the IISIS router level. Since level 2 is not supported in
Level 1 and 2 this release, “Level 2” is always disabled.
Level 1 Priority 0 to 127 (default 64) Sets the level 1 (L1) router priority. The L1 router with the
highest priority becomes the L1 designated router for that
LAN segment.
Level 2 Priority 0 to 127 (default 64) Sets the level 2 router priority. The L2 router assigned the
highest priority becomes the L2 designated router for that
LAN segment.
Not supported in this release, option is disabled.
Route On (default), Off Sets whether routes (OFF) or route summaries (ON) are
Summarization redistributed.
Table 1-4
OSPF and IISIS parameters—SLAT Assistant Tool - IPv4 (continued)
IP Address and standard dot notation When adding an OSPF router, sets the IP subnet address,
Subnet Mask and the subnet mask, respectively, for redistribution. Do not
use the default route of 0.0.0.0 (IP subnet 0.0.0.0 and subnet
mask 0.0.0.0). This route must not be statically provisioned,
and must not be learned through OSPF.
Routing Protocol NONE, OSPF, IISIS Sets the routing defined for the network configuration.
or OSPF/IISIS
Network area standard dot notation Sets the area (defaults to backbone area of 0.0.0.0).
Cost 1 to 65534 Sets the cost of the route (reflects speed of interface)
Defaults are as follows:
• SHELF, LAN-shelf-15 (or 41), LAN-shelf-16 (or 42),
COLAN, ILAN: 10
• GCC0/1 on OTM1: 303
• GCC0/1 on OTM2: 75
• GCC0/1 on OTM3: 19
• GCC0/1 on /OTUTTP/ODUTTP/ODUCTP: 75
• section/RS DCC: 520
• line/MS DCC: 174
Table 1-4
OSPF and IISIS parameters—SLAT Assistant Tool - IPv4 (continued)
Dead interval 1 to 65535 Sets the interval (in seconds) at which hello packets must
(default 40) not be seen before neighbors declare the router down
Hello interval 1 to 65535 Sets the interval (in seconds) between the hello packets that
(default 10) the router sends on the interface
Retransmit interval 1 to 3600 (default 5) Sets the interval (in seconds) required between link state
advertisement retransmissions.
Note: It is not supported in this release
Transmit delay 1 to 3600 (default 1) Sets the estimated time (in seconds) to transmit a link state
update packet over this interface.
Note: It is not supported in this release
Priority 0 to 255 (default 1) Sets the router priority value used in multi-access networks
for the election of the designated router (0 indicates that
router is not eligible to become designated router)
Area Default Cost 1 to 16777215 Sets the cost of the route to the next area.
(default 1) Note: It is not supported in this release.
Area Virtual Link Standard dot Sets the IP address of the OSPF router id designated as a
notation virtual interface. Area Virtual Link is not supported in this
release
Area Off (default), NSSA, Sets whether the router is in a not so stubby area (NSSA) or
Stub stub area. NSSA and Stub are not supported in this release
Authentication Null, Simple Sets the type of password authentication performed on the
Type OSPF circuit.
Opaque Link State On, Off (default) Sets whether opaque link state advertisement performs on
Advertisement the OSPF circuit.
Table 1-4
OSPF and IISIS parameters—SLAT Assistant Tool - IPv4 (continued)
Carrier Section/RS (default), Displays the DCC channel used, section/RS, line/MS, GCC
line/MS, GCC0, used, GCC0 or GCC1 (options available depend on circuit
GCC1 pack type and function).
Circuit Metric 1 to 63 Sets the circuit default metric used to calculate the best
route. Default depends on type of interface as follows:
• SHELF, LAN-shelf-15 (or 41), LAN-shelf-16 (or 42),
COLAN, ILAN, GRE-IP: 4
• OC-n/STM-n/STM0J/STM1J/STM4J/OTMn ports with line/
MS DCC/GCC0/GCC1 provisioned: 5
• /OTUTTP/ODUTTP/ODUCTP: 5
• OC-n/EC1/STM-n/STM0J/STM1J/STM4J ports with
section/RS DCC provisioned: 6
Select a higher value for a slower circuit.
Level 2 Only On, Off (default) Sets the status of level 2 only routing on the IISIS circuit.
Not supported in this release, On option is always disabled
three way On, Off (default) Sets the status of 3-way handshaking on the IISIS circuit.
handshake Not supported in this release, On option is always disabled.
Table 1-4
OSPF and IISIS parameters—SLAT Assistant Tool - IPv4 (continued)
Neighbor Off (default), IP, OSI, Sets the protocols supported on neighbor routers (overrides
Protocols IP and OSI what the router advertises).
Supported (NPS) Must be set to OSI if the lower layer DCC Protocol parameter
Override is set to LAPD.
When provisioning an IISIS circuit:
• on an optical DCC port connected to OSI managed
network elements (for example, Optical Metro 3000 and
Optical Metro 4000), you must ensure that neighbour
protocol supported override parameter is set to OSI.
• on an optical port connected to another 6500 network
element, it is strongly recommended that the lower layer
DCC Protocol parameter be set to PPP and the neighbour
protocol supported override parameter be set to Off.
The “IP” and “IP and OSI” options are not supported.
OSPF—Routes Distribution
IP Address and standard dot notation When adding an OSPF router, sets the IP subnet address,
Subnet Mask and the subnet mask, respectively, for redistribution. Do not
use the default route of 0.0.0.0 (IP subnet 0.0.0.0 and subnet
mask 0.0.0.0). This route must not be statically provisioned,
and must not be learned through OSPF.
Metric 1 to 65535 When adding an OSPF router, sets the metric for
redistribution
Metric Type External (default), When adding an OSPF router, sets the metric type for
Internal redistribution
Distribution List Staticrdlist (default), When adding an OSPF router, sets the redistribution mode
Isisrdlist
Table 1-4
OSPF and IISIS parameters—SLAT Assistant Tool - IPv4 (continued)
IISIS—Routes Distribution
IP Address and standard dot notation Sets the IP subnet address and subnet mask, respectively,
Subnet Mask of the distribution list entry for the selected IISIS router. Do
not use the default route of 0.0.0.0 (IP subnet 0.0.0.0 and
subnet mask 0.0.0.0). This route must not be statically
provisioned, and must not be learned through OSPF.
Metric 1 to 63 Sets the metric (cost) of the distribution list entry for the
selected IISIS router.
Metric Type External (default), Sets the metric type of the distribution list entry for the
Internal selected IISIS router.
Distribution List Staticrdlist (default), Sets the IISIS router distribution list entries for the selected
Ospfrdlist IISIS router
Table 1-5
OSPFv3 parameters—SLAT Assistant Tool - IPv6
Router ID standard dot notation Sets the router ID for the OSPFv3 router.
The router ID must be unique within the OSPF network. If an
OSPFv2 router exists, the OSPFv3 defaults to the same
value as the OSPFv2 router ID.
Table 1-5
OSPFv3 parameters—SLAT Assistant Tool - IPv6 (continued)
Cost 1 to 65534 Sets the cost of the route (reflects speed of interface)
Defaults are as follows:
• SHELF: 0
• LAN-shelf-15 (or 41), LAN-shelf-16 (or 42), COLAN,
ILAN: 10
Dead interval 1 to 65535 Sets the interval (in seconds) at which hello packets must
(default 40) not be seen before neighbors declare the router down
Hello interval 1 to 65535 Sets the interval (in seconds) between the hello packets that
(default 10) the router sends on the interface
Retransmit interval 1 to 3600 (default 5) Sets the interval (in seconds) required between link state
advertisement retransmissions.
Note: It is not supported in this release
Transmit delay 1 to 3600 (default 1) Sets the estimated time (in seconds) to transmit a link state
update packet over this interface.
Note: It is not supported in this release
Priority 0 to 255 (default 1) Sets the router priority value used in multi-access networks
for the election of the designated router (0 indicates that
router is not eligible to become designated router)
Nodal SLAT procedures describe how to bring a newly installed 6500 network
element to an in-service state ready to carry traffic. Make sure the SLAT
prerequisites listed in Chapter 1, “SLAT process overview” are met before
starting the Nodal SLAT procedures.
CS Coherent Select
DISP dispersion
ID identifier
NE network element
PC personal computer
PM performance monitoring
Rx receive
SP shelf processor
Tx transmit
WT wavelength translator
ATTENTION
The Node Setup tool remembers the Advanced Parameter settings (NE
Configuration) and SNMP application settings. The tool automatically reuses
them when the next shelf is set up. The information is stored in the
slat_preferences.xml file at the following Site Manager installation location:
<user_home_dir>/.ciena_desktop/sitemanager/PREFERENCES/SM
The Node Setup application also uses the Single Public IP configuration. In
this configuration:
• The Shelf IP address must be DCN visible.
• The Shelf IP address and the COLAN-X IP address are normally the
same.
The Advanced SLAT Assistant Tool continues to be available for users that
require an expanded set of parameters when commissioning network
elements in more complex configurations.
ATTENTION
The Advanced SLAT Assistant Tool remembers the NE Configuration system
parameter settings and SNMP application settings. The tool automatically
reuses them when the next shelf is set up. The information is stored in the
slat_preferences.xml file at the following Site Manager installation location:
<user_home_dir>/.ciena_desktop/sitemanager/PREFERENCES/SM
After the initial setup is complete using either the Node Setup application or
Advanced SLAT, more parameter provisioning can be applied by using Site
Manager menus. All the parameters are editable via Site Manager.
For flowcharts of the quick-start Node Setup for each shelf type, see:
• Standalone shelf — Figure 2-2 on page 2-7
• Primary with Members shelf — Figure 2-3 on page 2-8
• Member shelf — Figure 2-4 on page 2-9
For examples of the solution provided by the Node Setup application for
network elements in various configurations, see “Appendix B: Quick-start
turning-up using the Node Setup application—examples” on page 11-1.
Figure 2-1
Selecting the turning-up solution for a newly installed system
Yes No
Is the DCN configuration one of the
following?
Direct Connect
DCN: 1.x.x.x
COLAN X
1.2.2.2 NE1
RJ45-Ethernet
or
Gateway Connect
DCN: 1.x.x.x
Dedicated DCN LAN drop per GNE
DCN routable IP address per shelf
GNE
COLAN X
Shelf 1 1.3.3.2
TID A (Primary)
Figure 2-2
Quick-start turning-up of a Standalone shelf using the Node Setup application (NE1 in Figure 2-1
on page 2-6)
Security Provisioning
(optional)
SNMP Provisioning
(optional)
To complete turning-up, seat required circuit packs and check for alarms.
(Procedure 2-4 “Quick-start turning-up using the Node Setup application” will instruct you
to use step 8 to step 22 in Procedure 2-2 “Checking the current software release”.)
Figure 2-3
Quick-start turning-up of a Primary with Members shelf using the Node Setup application
Quick-start turning-up of a Primary with Members shelf using Node Setup (Procedure 2-4)
COLAN Provisioning
Security Provisioning
(optional)
SNMP Provisioning
(optional)
To complete turning-up, seat required circuit packs and check for alarms.
(Procedure 2-4 “Quick-start turning-up using the Node Setup application” will instruct you
to use step 8 to step 22 in Procedure 2-2 “Checking the current software release”.)
Figure 2-4
Quick-start turning-up of a Member shelf using the Node Setup application
To complete turning-up, seat required circuit packs and check for alarms.
(Procedure 2-4 “Quick-start turning-up using the Node Setup application” will instruct you
to use step 8 to step 22 in Procedure 2-2 “Checking the current software release”.)
Procedures
Table 2-1
Procedures in this chapter
Procedure
Preparation tasks
Procedure 2-1, “Powering up a new network element and connecting a craft computer”
Table 2-1
Procedures in this chapter (continued)
Procedure
Optional tasks
—in Procedure 2-29, “Post SLAT commissioning”:
Procedure 2-1
Powering up a new network element and connecting a
craft computer
Use this procedure to power up the shelf and connect your craft computer to
the shelf processor.
Note: For multi-shelf nodes, commission the member shelves first and the
Primary shelf last.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
Prerequisites
To perform this procedure, you must directly connect your craft computer to
the shelf processor at the network element site, for each network element in
the system. For instructions, refer to the Installation technical publication
specific to the respective 6500 shelf type, the chapter on installing 6500
shelves.
Step Action
Step Action
CAUTION
Filler circuit packs required
Equip all empty slots with filler circuit packs to ensure
the correct air flow and cooling. Otherwise, equipment
damage can occur within 3 minutes.
9 Turn on the circuit breakers at the BIP corresponding to Power Input Cards A
and B or the redundant DC power supplies for a 2-slot shelf (for breakerless
Power Input Cards, turn on the power at the source).
Go to step 12.
10 Switch the power breakers on the Power Input Cards A and B to the “on”
position (indicated with a | sign on the panel).
Go to step 12.
11 Plug in the power cords corresponding to the redundant AC power supplies
for a 2-slot shelf.
Step Action
12 Upon circuit pack power up, the red Fail, the green Ready, and the blue In Use
status LEDs go through the following sequence:
• The red LED turns on momentarily.
• After a few seconds, the red, green and blue LEDs turn on.
• After a few seconds, the red and blue LEDs turn off and the green LED
flashes to indicate the software is initializing.
• When software initialization is complete, the green status LED turns on
(does not flash).
• If the circuit pack is in-service, the blue LED turns on after the green LED
while the circuit pack is in use.
Wait until the green and blue LEDs on the shelf processor turn steadily on.
Connecting the computer to the shelf processor
13 Connect the computer to the RJ-45 connector (LAN-15 or LAN-41 port) on
the shelf processor with a cross-over or straight Ethernet cable.
14 Configure your computer to obtain an IP address automatically (the shelf
processor is a DHCP server and can assign an IP address) or provision the
computer to have an IP address of 10.0.0.2 with a subnet mask of
255.255.255.252, and a default gateway of 10.0.0.1.
It can take up to three minutes for the Ethernet link to establish.
Note: If the SP has been previously commissioned or a Transport Data
Recovery Failed alarm is raised, delete all shelf provisioned data. Refer to the
“Deleting all shelf provisioning information for a standalone shelf or all
shelves of a consolidated node” procedure in Administration and Security,
323-1851-301.
15 Select your next step.
If Then go to
you have configured the computer to obtain an IP step 16
address automatically and you are using a PC
you have configured the computer to obtain an IP step 18
address automatically and you are using a MAC
you have provisioned the IP address manually step 23
Step Action
22 Use the drop-down menu to change the Configure IPv4 field to Using DHCP.
Then click Apply and close the window.
23 You have completed this procedure. Depending on your turning-up solution,
select the procedure to go to next from the following table.
To select your turning-up solution, see “Node setup solutions” on page 2-3
and “Selecting the turning-up solution for a newly installed system” on page
2-6.
If you will be using Then go to
the Node Setup application “Quick-start turning-up using the Node
Setup application” on page 2-26
a commissioning script file or “Checking the current software release” on
Advanced SLAT page 2-16
—end—
Procedure 2-2
Checking the current software release
Use this procedure to check the current software release on the network
element from the Node Information window in Site Manager or the NE
Identification window in Advanced SLAT/SLAT Assistant Tool.
Prerequisites
To perform this procedure you must
• have Site Manager Release 13.0software installed on your craft computer
• use an account with a UPC level of 4 or higher
Step Action
Step Action
7 Deliver the correct release to the shelf processor and then downgrade or
upgrade, as applicable, the software release on the shelf processor (Load,
first Invoke, second Invoke, Commit). Refer to release management and
upgrade management procedures in Administration and Security,
323-1851-301.
ATTENTION
Do not attempt to clear any alarms until the new shelf processor is upgraded.
ATTENTION
During the Invoke step, make sure the “Manually invoke circuit packs
requiring cold restart” check box is not selected.
ATTENTION
If you were directed to this procedure Procedure 2-2, “Checking the current
software release” from Procedure 2-4, “Quick-start turning-up using the
Node Setup application”, after you deliver the correct software release to the
SP, go back to Procedure 2-4, “Quick-start turning-up using the Node Setup
application”.
Step Action
13 Do not seat any circuit packs at this point. You will be instructed later during
Procedure 2-6, “Commissioning a network element using Advanced SLAT” to
seat the NTK615AA/BA or NTK616AA/BA PKT/OTN cross-connect [XC]
circuit pack and then the rest of the circuit packs after the NE Configuration
stage (which implicitly sets the date/time without user intervention).
Go to step 21 in this procedure.
14 Seat one PKT/OTN XC circuit pack (NTK615AA/BA or NTK616AA/BA) and
wait until the green and the blue LEDs on the XC turn steadily on
(approximately 25 minutes).
Alarms may be raised during the interval, which should clear automatically
Step Action
15 If there are other active alarms, determine if they are expected. Clear any
unexpected alarms by following the appropriate procedures in Part 1 and
Part 2 of Fault Management - Alarm Clearing, 323-1851-543.
CAUTION
Risk of damage to circuit packs
Ensure that any alarms associated with the fans are cleared
before proceeding (for example, fan failed, fan missing,
incompatible fan, or equipment configuration mismatch).
Installing the circuit packs with failed, missing, or wrong fans
may cause the circuit packs to be damaged by overheating.
16 Seat all remaining circuit packs that you must equip in the shelf.
17 Wait until the green LEDs on all circuit packs turn steadily on. For the
cross-connect circuit pack, the blue LED should also be on.
If any of the circuit packs do not power up properly, first try to unseat and
reseat the circuit pack to make sure the circuit pack is inserted into the
backplane correctly. If the red LED on the circuit pack is lit, replace the circuit
pack. Refer to Fault Management - Module Replacement, 323-1851-545, for
the appropriate procedures.
18 Select Active Alarms from the Faults drop-down menu.
19 Make sure there are no “Software Auto-upgrade in Progress” alarms or wait
until these alarms clear before going to the next step.
The “Software Auto-upgrade in Progress” alarm indicates that a circuit pack
is in the process of being auto-upgraded/downgraded to the active release of
the network element. This alarm will clear on its own once the process is
complete.
20 If there are other active alarms, determine if they are expected. Clear any
unexpected alarms by following the appropriate procedures in Part 1 and
Part 2 of Fault Management - Alarm Clearing, 323-1851-543.
21 Make sure you exit from the Site Manager session.
22 You have completed this procedure.
If your turning-up solution is Then
the Node Setup application The quick-start turning-up is complete.
Advanced SLAT Go to Procedure 2-5, “Launching Advanced
SLAT and logging in”.
—end—
Procedure 2-3
Commissioning the network element using scripts
Use this procedure to commission a new Release 12.3 network element by
using scripts.
Prerequisites
To perform this procedure
• make sure you have performed Procedure 2-1, “Powering up a new
network element and connecting a craft computer” and Procedure 2-2,
“Checking the current software release”
• make sure the active shelf processor (SP) is seated and all the other
circuit packs are unseated, and that the LAN cable is disconnected from
the FIM
• make sure the following cables are not connected:
— ILAN cables
— COLAN cables
• have the commissioning script file. The file type is .json.
Note: Refer to the Blue Planet MCP User Guide for procedures on
generating and exporting commissioning scripts.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
CAUTION
Risk of injury
Observe the safety guidelines in Installation - General
Information, 323-1851-201.0, and those recommended by
your company at all times.
Step Action
1 If you are logged into the network element, log out and exit Site Manager.
2 Make sure the craft computer is physically connected to the Craft port on the
faceplate of the shelf processor.
3 Launch Site Manager and choose Connection type as Craft Ethernet. Log
into the network element by using the default IP address, which is 10.0.0.1,
and the ADMIN/ADMIN credentials.
(For detailed login procedures, refer to Administration and Security,
323-1851-301.)
4 If the shelf is not commissioned, several warning dialogs may be displayed.
This behavior is expected and you must acknowledge to proceed.
If a dialog is displayed with the option of running a commissioning script or
continuing with Site Manager, click Run Commissioning Script.
If a dialog is not displayed with the option of running a commissioning script,
choose the option to continue with Site Manager. Once the dialog closes,
launch the TL1 Command Builder tool, Tools/TL1 Command Builder.
Note: The TL1 Command Builder main window opens. (The window
opens automatically only if you click Run Commissioning Script. To
open the TL1 Command Builder application manually, go to the Site
Manager Tools menu.)
5 In the TL1 Command Builder main window, verify that “Halt on error” (at the
bottom of the window) is checked.
6 Import the commissioning file as follows:
a. Go to File --> Open.
b. In the Open window, navigate to the folder where the commissioning file
is located. From the Files of type drop-down list select “Text Files
(.json)”, then select the commissioning script file from the file structure.
c. Click the Load button.
Note: The file is parsed in the background, which builds the set of TIDs,
shelves for each TID, and scripts for each shelf.
Step Action
7 After the file has been parsed successfully, a chooser dialog opens, which
allows the user to make the following selections:
a. Use the TID Name drop-down list to select the network element name
that you want to commission.
b. Use the Shelf drop-down list to select the shelf you want to commission.
c. Record the list of values in the Shelf drop-down.
d. Record whether the ALL value is listed in the Shelf drop-down list.
Note: Every new shelf has a shelf specific script that must be applied first
to commission that new shelf. The Shelf: ALL script in the drop-down list
will have to be applied to the Primary shelf after all of the shelf specific
scripts have been applied.
e. In the Script Number drop-down list, “1” will be the only option listed and
is selected by default.
f. Click OK.
8 In the TL1 Command Builder main window, click Run Script.
9 Verify the information in the confirmation dialog.
If the information is Then click
correct, that is, the correct node, shelf, OK
and Release are listed
not correct Cancel. Correct the selections and
verify the information in the new
confirmation dialog. Click OK.
If the following dialog is displayed before the ED-IP command is sent, click
OK and wait 30 seconds, then close TL1 Command Builder and Site
Manager:
“The remaining operation in script 1 is changing the craft port IP address.
The session to the craft port will likely drop due to the IP address change
before a response is received. After clicking “OK” please wait 30 seconds
for the ED-IP command to execute then close the TL1 Command Builder
application, If this is the last shelf specific script 1 for this TIDc, please
connect your computer to the craft port of the primary. Reset/renew the
IP address on your computer and log back into the primary and execute
the Shelf All script.”
Note: If the shelf-specific script execution fails, in the TL1 Command
Builder main window, click Save Results to save the log of the
commands sent and the responses received during the script execution.
Contact your next level of support.
Step Action
Step Action
Step Action
19 After script Shelf: ALL completes executing, select your next step.
If the script Shelf: ALL Then
execution
was successful A confirmation dialog is displayed. Click OK.
You have completed this procedure. Proceed to
Chapter 3, “Photonic layer provisioning
procedures”.
Note: It is recommended that the intra-site and
inter-site fibering be completed before the
craftsperson leaves the site to ensure any
fiber-related issues are resolved without requiring
subsequent visits to the site.
failed in the TL1 Command Builder main window, click
Save Results to save the log of the commands
sent and the responses received during the script
execution. Contact your next level of support.
—end—
Procedure 2-4
Quick-start turning-up using the Node Setup
application
If you have selected the Node Setup application as your turning-up solution
(see “Node setup solutions” on page 2-3 and “Selecting the turning-up
solution for a newly installed system” on page 2-6), use this procedure to
launch the application and perform the basic setup steps.
The Node Setup application steps are used to turn up the network element in
a simple way. After the basic setup is complete, more parameter provisioning
can be applied by using Site Manager menus. All the parameters are editable
via Site Manager.
Note: The Node Setup application must only be used locally during the
initial nodal SLAT process (when your craft computer is connected directly
to the LAN-15 port on the SP in a 6500-7 packet-optical, 2-slot, 14-slot or
7-slot shelf or LAN-41 port in a 32-slot shelf).
Note: The Last Refresh field at the bottom of the Node Setup application
screen displays the NE time in GMT.
Prerequisites
To perform this procedure you must:
• use an ADMIN account (ADMIN/ADMIN by default)
• have Site Manager installed. Alternatively, If you are using the web launch
of Site Manager off the shelf processor, Java 1.7 (or higher) must be
installed. Java Web Start (JWS) is not supported on SPAP processor
circuit packs (NTK503MAE5, NTK503NAE5, NTK555LA, NTK555NA or
NTK555NB).
• make sure that there are no other active login sessions to the NE (such as
monitoring from OneControl, open TL-1 sessions, open Site Manager
sessions)
Note: The SP and filler cards must be the only circuit packs seated in the
shelf. The active SP must be in slot 15 (for 6500-7 packet-optical, 2-slot,
7-slot, and 14-slot shelves) or slot 41 (for 32-slot shelves). Ensure fans,
power cards and access panels exist. Ensure that the maintenance
interface card (MIC) is present for MIC supported shelves.
Step Action
Step Action
ATTENTION
The Node Setup tool remembers the Advanced Parameter settings (NE
Configuration) and SNMP application settings. The tool automatically reuses
them when the next shelf is set up. The information is stored in the
slat_preferences.xml file at the following Site Manager installation location:
<user_home_dir>/.ciena_desktop/sitemanager/PREFERENCES/SM
Step Action
13 In the Proxy ARP GNE Configuration panel, enter the IP addresses of the
member shelves for this TIDc. Enter member shelf IP addresses as follows:
• Enter consecutive addresses by first address and last address of the
range.
• You can enter one non-consecutive address by setting the same address
in the Start IP Address and End IP Address. If you want to enter more
than one non-consecutive IP address, use Site Manager -> Configuration
->Comms Setting Management after you complete the basic setup.
If Member shelves already exist when this step is executed, you can display
their IP addresses, along with the Primary IP address, in the table by clicking
on the Refresh button.
14 Click Apply to apply the Proxy ARP GNE configuration changes to the
network element. Then go to step 15 to set up COLAN Provisioning.
15 In the COLAN Provisioning panel, the tool auto-populates the COLAN-X IP
address to match the Shelf IP address. You can change the address. Enter
the following mandatory parameters. Refer to COLAN Provisioning in Table
2-2 on page 2-31 for provisioning rules.
• IP Address
• Subnet Mask
16 Click Apply to apply the COLAN Provisioning changes to the network
element.
Step Action
17 The next Step, Security Provisioning, is optional. If you are using this Step,
enter the applicable parameters. To enable the Centralized Authentication
tab, select the Centralized Authentication Required checkbox. Refer to
Optional Step - Security Provisioning in Table 2-2 on page 2-31 for
provisioning rules.
18 Click Apply to apply the changes to the network element.
The application remembers all the changes made by the user and applies
them to the next shelf that is set up.
19 The next Step, SNMP Provisioning, is optional. If you are using this step,
enter the applicable parameters. Refer to Optional Step - SNMP Provisioning
in Table 2-2 on page 2-31 for provisioning rules.
20 Click Edit Trap Destination, enter the destination SNMP trap viewer
information, then click OK. Click Apply SNMP Data to apply the changes to
the network element.
The application remembers all changes made by the user and applies them
to the next shelf that is set up.
21 Click the Confirm Completion button.
22 You have completed the basic setup of the network element.
After the basic setup is complete, more parameter provisioning can be
applied by using Site Manager menus. All the parameters are editable via Site
Manager.
23 To complete the turning-up, go to Procedure 2-2, “Checking the current
software release” and perform step 8 to step 22 to insert the required circuit
packs and check for alarms.
—end—
Table 2-2
Node Setup application parameters
For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.
NE Identification
Table 2-2
Node Setup application parameters (continued)
For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.
NE Configuration
Shelf Type Standalone A shelf that does not belong to a consolidated yes
Primary with Members node is referred to as a Standalone shelf.
Shelf Number 1 to 254 shelf identifier of the shelf. Must be unique yes
within a site.
Photonic shelves (6500 and/or CPL) at a
given site (with the same Site ID) must have
unique logical shelf numbers (also referred to
as Shelf ID), regardless of node name (TID).
Note: A Photonic shelf refers to a shelf with
an OTS provisioned on it.
Shelf IP Address standard dot notation also known as circuitless IP address yes
Table 2-2
Node Setup application parameters (continued)
For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.
Site ID 0 to 65535 identifier of the site. Must be the same for all Site ID
NEs within a site. must be
In order for Visualization to work properly, the provisioned
Site ID on non-photonics shelves should be before the
set to match the Site ID of photonic shelves at photonic
the same site. layer is
defined.
For SPLI, alarm correlation, and OTS Can be
management to function, the Site ID must be provisioned
provisioned to a non-zero value. at this point
or after the
node setup
has
completed.
Table 2-2
Node Setup application parameters (continued)
For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.
Table 2-2
Node Setup application parameters (continued)
For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.
NE Configuration (continued)
Advanced Parameters
The Advanced Parameters are filled in automatically and can be edited as required. The tool remembers
the Advanced Parameter settings and automatically reuses them when the next shelf is set up.
Alarm Correlation ON, OFF (default) indicates whether the alarm correlation no
feature is enabled or disabled
Shelf Synch YES (default), NO enables or disables shelf synch between the no
primary shelf and the member shelves
Air Filter 1 to 1826 (default 731 sets the number of days before the “Filter no
Replacement or 730) Replacement Timer Expired” alarm is raised
Timer (in days)
Table 2-2
Node Setup application parameters (continued)
For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.
COLAN Provisioning
Passwords tab
Password Rules Standard, Complex sets the password creating rules to standard no
or complex
Table 2-2
Node Setup application parameters (continued)
For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.
Server State enable, disable sets the status of the Primary and Secondary no
RADIUS servers
IP Address standard dot notation sets the IP address of the Primary and no
Secondary RADIUS servers
Port Number numeric sets the port number of the Primary and no
Secondary RADIUS servers
Shared Secret alphanumeric sets the shared secret of the Primary and no
Confirm Shared characters Secondary RADIUS servers
Secret
Timeout (s) numeric sets the timeout value for the Primary and no
Secondary RADIUS servers
Table 2-2
Node Setup application parameters (continued)
For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.
Request Timeout numeric value timeout value for SNMP requests – option no
disabled for standalone NEs and member
shelves
Table 2-2
Node Setup application parameters (continued)
For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.
Note 1: OneControl supports the following special characters _+@-^~/.$%*#!()=[]{}’?|‘ in the TID for the
6500 Site Manager craft launch. Do not use special characters not supported in an NE TID if you want
to launch the 6500 Site Manager craft from OneControl.
Note 2: SNMPv3 on the current release of 6500 does not have any usable SNMPv3 USM users by
default. To access the node via SNMP v3, you must log into Site Manager via the Craft port after the
node is set up and create a USM user. For more information, see Fault Management - SNMP,
323-1851-740.
Procedure 2-5
Launching Advanced SLAT and logging in
If you have selected Advanced SLAT as your turning-up solution (see “Node
setup solutions” on page 2-3 and “Selecting the turning-up solution for a newly
installed system” on page 2-6), use this procedure to launch SAT and log into
the network element. You must have only one active SAT session for each
network element at a time.
Advanced SLAT contains the complete SLAT procedures that guide the user
through different SLAT steps. Advanced SLAT can be used remotely.
Note: SAT must only be used locally during the initial nodal SLAT process
(when your craft computer is connected directly to the LAN-15 port on the
SP in a 6500-7 packet-optical, 2-slot, 14-slot or 7-slot shelf or LAN-41 port
in a 32-slot shelf). Do not run SAT remotely over DCN.
Prerequisites
To perform this procedure you must:
• have Java 1.7 (or higher) software installed on your craft computer if you
are using a web browser to launch SAT. Java Web Start (JWS) is not
supported on SPAP processor circuit packs (NTK503MAE5,
NTK503NAE5, NTK555LA, NTK555NA or NTK555NB).
• If you are launching SAT from the installed version of Site Manager, you
do not have to install Java. (In this case, SAT uses the Java software
included in the Site Manager installation.)
• use an account with a UPC level of 4 or higher
• ensure that photonic circuit packs are seated in the shelf
• ensure that all External Inventory equipment (for example, CMDs and
DSCMs) is connected to the shelf access panel via CAT5 cables as
indicated in the EDP/IDP.
Step Action
Clearing the Java cache on your craft computer (to ensure the correct SAT load is executed)
Note 1: You only need to execute step 1 to step 7 once before the first time
you launch SAT.
Note 2: The following steps are based on Windows 7. Equivalent steps
should be performed is using Windows 10, Mac OS, or Linux. Refer to the
platform related or Java documentation for details.
1 In the Windows Start menu, select Control Panel.
Step Action
Step Action
17 Enter the IP address of the network element in the URL field, and press
Enter. The default IP address of an NE is 10.0.0.1.
18 In the web page, click the Launch Nodal SLAT Assistant Tool link.
19 On the next web page, click Launch Advanced SAT. If a security warning
dialog appears, click Continue. If any pop up dialogs appear, accept them if
you agree. You must accept them in order for the Advanced SLAT to run. Then
run the tool. If the required Java version is not installed, a warning dialog
appears, select Run with the latest version.
A Login screen appears.
Logging into the SLAT Assistant Tool
20 In the Login screen, leave the Domain at the Default domain.
21 Enter the username and password (ADMIN/ADMIN by default).
22 Click Login.
23 Click OK in the security banner.
The SLAT Assistant Tool window opens with the first Commissioning Step
highlighted.
If the shelf is already provisioned, a warning message is displayed. Follow the
detailed instructions provided in the message on how to proceed (depending
on whether the provisioning data is expected, or the shelf is being
re-commissioned with, or without physical cards present on the shelf).
24 Go to Procedure 2-6, “Commissioning a network element using Advanced
SLAT” if you are logging in for the first time or Procedure 2-26, “Provisioning
craft access” if you are logging back in after setting the shelf IP address. If the
Apply button is disabled and provisioning is entered, you can hover over the
Apply button and the tooltip will display the information over the error blocking
the Apply button.
After you complete a task, click Next to advance to the next task in the task
list. A green check mark will appear next to the task just completed, except
the “Craft Access Provisioning” task.
Click Previous to return to the previous task in the task list. Click Refresh to
refresh the current screen.
Note: The Last Refresh field at the bottom of the SAT screen displays the NE
time in GMT.
After an Advanced SLAT session is closed, the step tracking information
(check mark) is lost, but all applied provisioning is maintained.
Advanced SLAT tasks that follow the NE Configuration task are enabled only
after you complete the NE Configuration task.
—end—
Procedure 2-6
Commissioning a network element using Advanced
SLAT
Use this procedure to enter the NE identification, NE configuration, and GNE
configuration data for the network element in Advanced SLAT. See Table 1-3
on page 1-13 for detailed information.
ATTENTION
The Advanced SLAT Assistant Tool remembers the NE Configuration system
parameter settings and SNMP application settings. The tool automatically
reuses them when the next shelf is set up. The information is stored in the
slat_preferences.xml file at the following Site Manager installation location:
<user_home_dir>/.ciena_desktop/sitemanager/PREFERENCES/SM
Commissioning Steps that require shelf number for their execution will be
blocked by Advanced SLAT if the shelf number is not defined. The only two
Commissioning Steps that will be enabled by Advanced SLAT when the shelf
number is not defined are NE Identification and NE Configuration.
Note: Provisioned shelf current should be set after the shelf number has
been provisioned and prior to provisioning any other shelf parameters. To
determine the Provisioned shelf current value, refer to Administration and
Security, 323-1851-301 for the engineering rules.
Note: SuperMux, FLEX MOTR, and L2 MOTR circuit packs can be shelf
timed or self timed after the commissioning depending on whether the
circuit pack gets autoprovisioned before or after the XC. If you want all
SuperMux, FLEX MOTR, or L2 MOTR circuit packs to be shelf timed, you
can commission the shelf without these circuit packs equipped in the shelf
and equip them after the commissioning has been completed. If you want
all these circuit packs to be self timed, you can leave these circuit packs
equipped in the shelf during the commissioning procedure. After the
commissioning has been completed, you can use the “Provisioning an
independent timing group” procedure in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310, to change the timing to self
timed.
Prerequisites
To perform this procedure you must
• make sure that there are no other active login sessions to the NE (such as
monitoring from OneControl, open TL-1 sessions, open Site Manager
sessions)
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the NE Identification
Commissioning Step highlighted
Step Action
1 If Then go to
a message opens indicating that provisioning data has step 2
been detected on the shelf
otherwise step 3
Step Action
2 If provisioning data has been detected on the shelf, follow the detailed
instructions provided in the message on how to proceed (depending on
whether the provisioning data is expected, or the shelf is being
re-commissioned with, or without physical cards present on the shelf).
If you click the Delete Shelf button:
• If no physical cards are present in the shelf, the SLAT tool will start the
process to delete the existing provisioning.
• If physical cards are present in the shelf, a message opens indicating
that:
— Physical cards have been detected in the shelf.
— To remove the existing provisioning data, you must remove all the
physical cards from the shelf, except the active shelf processor and
the filler cards. (See Fault Management - Module Replacement,
323-1851-545 for the steps to unseat and remove the equipment.)
The active SP must be in slot 15 (for 2-slot, 7-slot, 6500-7
packet-optical, and 14-slot shelves) or slot 41 (for 32-slot shelves).
Then click the OK button in the physical cards detected message.
Then click the Delete Shelf button in the provisioning data detected
message to proceed with the delete operation.
• After you have clicked the Delete Shelf button:
a. The shelf restarts and the connection to the network element is dropped.
b. Exit the Advanced SLAT by clicking the X button in the top right corner of
the window.
c. Log back in with Advanced SLAT using Procedure 2-5, “Launching
Advanced SLAT and logging in”.
3 In the NE Identification panel, enter a network element name in the NE Name
field. Refer to Table 1-3 on page 1-13 for provisioning rules.
4 Enter the CLLI value in the CLLI field.
5 Optionally, enter the extended NE name in the Extended NE Name field.
Refer to Table 1-3 on page 1-13 for provisioning rules.
6 Click Apply to apply the changes to the network element.
This step can take up to 90 seconds to complete.
7 Click Next.
The next Commissioning Step panel appears.
Step Action
Step Action
14 Provision the parameters in the IPv6 panel (refer to Table 1-3 on page 1-13
and Table 1-5 on page 1-37). An asterisk (*) denotes mandatory parameters,
which must be entered, if enabled.
15 Click Apply to apply the changes to the network element.
16 For a SONET or SDH-J network element, verify that the blue LED on each
circuit pack is on.
This step can take a few minutes to complete.
For an SDH network element, the blue LED will not be on until auto-equipping
is enabled in Procedure 2-7, “Enabling or disabling auto-equipping”.
17 Click Confirm Completion, then click Next.
The next Commissioning Step panel appears.
18 Select your next step.
If your shelf Then go to
is equipped with NTK615AA/BA or NTK616AA/BA step 19
PKT/OTN cross-connect (XC) circuit packs
is not equipped with NTK615AA/BA or NTK616AA/BA step 26
PKT/OTN cross-connect (XC) circuit packs
Step Action
21 Seat all remaining circuit packs that you must equip in the shelf.
22 Wait until the green LEDs on all circuit packs turn steadily on. For the
cross-connect circuit pack, the blue LED should also be on.
Note: The blue LEDs will also be on for other circuit packs that have
auto-equipping enabled and are in-service.
If any of the circuit packs do not power up properly, first try to unseat and
reseat the circuit pack to make sure the circuit pack is inserted into the
backplane correctly. If the red LED on the circuit pack is lit, replace the circuit
pack. Refer to Fault Management - Module Replacement, 323-1851-545, for
the appropriate procedures.
23 Select Active Alarms from the Faults drop-down menu.
24 Review the active alarms and ensure that all “Software Auto-upgrade in
Progress” alarms have cleared before proceeding to the next step.
The “Software Auto-upgrade in Progress” alarm indicates that a circuit pack
is in the process of being auto-upgraded/downgraded to the active release of
the network element. This alarm will clear on its own once the process is
complete. See Part 2 of Fault Management - Alarm Clearing, 323-1851-543,
for details of the “Software Auto-upgrade in Progress” alarm.
25 If there are other active alarms, determine if they are expected. Clear any
unexpected alarms by following the appropriate procedures in Part 1 and
Part 2 of Fault Management - Alarm Clearing, 323-1851-543.
26 Select your next step. If you are using Dual Stack IPv4/IPv6, you must
provision the parameters in both the IPv4 tab and the IPv6 tab.
If you are provisioning the GNE Configuration panel for Then go to
IPv4 step 27
IPv6 step 32
27 If you select No in the GNE drop-down list, all GNE parameters are blocked.
28 If you select Yes in the GNE drop-down list, select the data communication
configuration from the displayed list. (Based on the selected comms
configuration, some GNE parameters are blocked.)
29 Enter the GNE parameters in the GNE Configuration panel (refer to Table 1-3
on page 1-13 for provisioning rules).
30 Click Confirm Completion to apply the changes to the network element.
Step Action
32 If you select No in the GNE drop-down list, all items in the displayed GNE list
are blocked.
33 If you select Yes in the GNE drop-down list, select the data communication
configuration from the displayed list. (Based on the selected comms
configuration, some GNE parameters are blocked.)
34 Click Confirm Selection to apply the changes to the network element.
35 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-7, “Enabling or disabling auto-equipping”.
—end—
Procedure 2-7
Enabling or disabling auto-equipping
Use this procedure to enable or disable the auto-equipping mode for each
individual slot or for all slots simultaneously.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
1 In the Auto Equipping panel, click on the Select All button or Deselect All
button to enable/disable auto-equipping for all slots. The following slots can
be provisioned:
• slot 1, 2, 15 and 25-27 for 2-slot shelf
• slot 1, 2, 15 and 83-85 for 2-slot optical Type 2 shelf with SPAP
• slot 1, 2, 15 and 83-90 for 2-slot optical Type 2 shelf with SPAP-2 w/
2xOSC
• slot 1 to 7, 15 and 83-86 for 7-slot shelf
• slot 1 to 7, 15 and 83-90 for 7-slot Optical Type 2 shelf
• slot 1 to 16, 83 to 90 for 14-slot shelf
• slot 1 to 18, 21 to 28, 31 to 38, 41, 42 and 51 to 62 for 32-slot shelf
• slot 1 to 8, 15, 16 and 83 to 86 for 6500-7 packet-optical shelf
2 Select individual check boxes to enable/disable auto-equipping for individual
slots.
You can cancel the changes by clicking Cancel.
Unselected slot indicates that when a circuit pack is inserted into the slot, it
does not automatically go in-service and generate alarms.
3 Click Apply to apply the changes to the network element.
4 For an SDH network element, verify that the blue LED on each circuit pack is
on. This step can take a few minutes to complete.
Step Action
5 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-8, “Performing a lamp test”.
—end—
Procedure 2-8
Performing a lamp test
Use this procedure to verify that all LEDs on the shelf are working properly.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
1 In the Lamp Test panel, click Apply to verify that all LEDs illuminate for
30 seconds.
If any of the LEDs does not illuminate, first check if there are any active
alarms against the unit the LED is located. Follow the appropriate procedures
in Part 1 and Part 2 of Fault Management - Alarm Clearing, 323-1851-543 to
clear the alarms. Otherwise, the LED is defective. Replace the unit by
following the appropriate procedures in Fault Management - Module
Replacement, 323-1851-545.
Note: NTK503MAE5/NAE5 2-slot shelf integrated Access Panel lamps on
the PWR OK A will not light during a lamp test if there is no power on feed A
and PWR OK B will not light during a lamp test if there is no power B on feed
B.
2 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-9, “Provisioning OSPF router parameters”.
—end—
Procedure 2-9
Provisioning OSPF router parameters
If OSPF routing is required, use this procedure to provision the OSPF router
ID (mandatory) and other OSPF router parameters.
Note: If the OSC SFP equipment is auto created before the shelf IP is
entered, OSPFv2 routers and circuits are not created. For OSC OSPFv2
auto provisioning, shelf IP must be provisioned before ED-SYS command
is applied.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
1 Select your next step. If you are using Dual Stack IPv4/IPv6, you must
provision the parameters in both the IPv4 tab and the IPv6 tab.
If you are provisioning the OSPF Router Provisioning Then go to
panel for
IPv4 step 2
IPv6 step 6
2 In the OSPF Router Provisioning panel, enter the shelf IPv4 address in the
Router ID field (mandatory).
Step Action
3 Enter the other parameters in the rest of the fields, as applicable. Refer to
Table 1-4 on page 1-32 for provisioning rules.
A Delete button is available if you want to delete the entry.
4 Click Apply to apply the changes to the network element.
5 Select your next step.
If Then go to
you must provision the IPv6 panel also step 6
otherwise step 8
6 Enter the OSPFv3 Router id in the Router ID field (mandatory). Follow the
recommendations displayed in the panel. Refer to Table 1-5 on page 1-37 for
provisioning rules.
If an OSPFv2 router ID has been provisioned, the SLAT tool will autopopulate
the OSPFv2 router id in the OSPFv3 Router id field. If the OSPFv3 id is
autopopulated, it is not provisioned until the user selects Apply.
7 Click Apply to apply the changes to the network element.
8 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-10, “Provisioning ILAN”.
—end—
Procedure 2-10
Provisioning ILAN
Use this procedure to provision the intershelf local area network (ILAN). This
procedure is required only if the network element must connect to other
network elements’ ILAN. Otherwise, click Confirm Completion. Then click
Next to go to the next procedure.
If you intend to use ILAN, make sure that the shelf IP address is also
provisioned.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
1 Select your next step. If you are using Dual Stack IPv4/IPv6, you must
provision the parameters in both the IPv4 tab and the IPv6 tab.
If you are provisioning for Then go to
IPv4 step 2
IPv6 step 7
Step Action
Step Action
8 Enter the required information in the Add ILAN port data dialog box:
• select an ILAN port
• enter the IPv6 address
If an IPv4 LAN interface address is unnumbered, the IPv6 LAN interface
address must be unnumbered, and vice versa. (If the rule is not met, you
will see an Operation failed error message.)
When you try to add or edit an IPv4 address on a LAN interface, the
system checks for the above rule only if IPv6 is supported by the NE or if
IPv6 is enabled on the NE. Otherwise, the system does not run the check.
• enter the subnet mask
• select YES or NO to enable or disable the port.
IPv4 and IPv6 use the same port. For example, if port enabled is set to
NO on the IPv6 ILAN-IN provisioning, then the IPv4 ILAN-IN provisioning
port will be disabled also.
Port enabled cannot be set to NO if an IPv4 or IPv6 OPSF circuit exists
on that interface.
• select the routing protocol (NONE or OSPF)
• provision the circuit parameters (see Table 1-5 on page 1-37)
• click OK
9 Repeat step 7 and step 8 for the other ILAN port, if applicable.
You can select one of the rows in the table and click Delete or Edit to delete
or edit that entry.
10 In the IPv6 panel, click Confirm Completion.
11 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-11, “Provisioning Shelf IP address”.
—end—
Procedure 2-11
Provisioning Shelf IP address
Use this procedure to provision the shelf IP address for the shelf. You can also
define the OSPF circuit parameters for the Shelf port.
All shelves require either an IPv4 shelf address, an IPv6 shelf address, or
both.
Note: When reprovisioning a member shelf, the 6500 can lose TL-1
access and you cannot recover TIDc member following a SLAT. You can
restart the primary shelf so the new member will properly auto-enroll or
use a different shelf IP for the member when re-provisioning it.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have SLAT Assistant Tool open with the Commissioning Step highlighted
• ensure that the shelf IP address is not defined
Step Action
1 Select your next step. If you are using Dual Stack IPv4/IPv6, you must
provision the parameters in both the IPv4 tab and the IPv6 tab.
If you are provisioning the Shelf IP Provisioning panel for Then go to
IPv4 step 2
IPv6 step 8
2 In the Shelf IP Provisioning panel, select the IPv4 tab and enter the shelf IPv4
address.
3 Select the routing protocol for the port.
Step Action
Procedure 2-12
Provisioning IISIS router parameters
If IISIS routing is required, use this procedure to provision IISIS router
parameters. This procedure applies to IPv4 only.
If you will be provisioning IISIS router parameters during the Shelf IP, COLAN,
or DCC Provisioning steps, you do not have to provision the router at the IISIS
Router Provisioning step. The IISIS router provisioning during the Shelf IP,
COLAN, or DCC Provisioning steps overwrites the router provisioning
performed at the IISIS Router Provisioning step.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
1 In the IISIS Router Provisioning panel, enter the parameters in the fields, as
applicable. See Table 1-4 on page 1-32 for parameter details.
A Delete button is available if you want to delete the entry.
2 Click Apply to apply the changes to the network element.
3 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-13, “Provisioning COLAN”.
—end—
Procedure 2-13
Provisioning COLAN
Use this procedure to provision the central office local area network (COLAN).
This procedure is required only if the network element is connected directly to
the data communications network (DCN). Otherwise, skip this procedure.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
1 Select your next step. If you are using Dual Stack IPv4/IPv6, you must
provision the parameters in both the IPv4 tab and the IPv6 tab.
If you are provisioning for Then go to
IPv4 step 2
IPv6 step 7
Step Action
Procedure 2-14
Provisioning proxy ARP (IPv4)/ND Proxy Provisioning
(IPv6)
Use this procedure to provision proxy ARP for IPv4 and perform ND Proxy
provisioning for IPv6. Proxy ARP and ND Proxy are supported on the COLAN
X port only.
Proxy ARP provisioning is required for IPv4 only if you require proxy ARP to
reply to ARP requests directed at other NEs. Otherwise, skip this procedure
for IPv4.
ND Proxy provisioning is required for IPv6 if you require this shelf to respond
to Neighbor Solicitation requests on behalf of subtending shelves.
To enable proxy ARP, the network element must be a GNE and have proxy
ARP enabled.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
1 Select your next step. If you are using Dual Stack IPv4/IPv6, you must
provision the parameters in both the IPv4 tab and the IPv6 tab.
If you are provisioning for Then go to
IPv4 step 2
IPv6 step 7
Step Action
Procedure 2-15
Provisioning NAT
Use this procedure to provision the network address translation (NAT) table.
This table allows a GNE to map an allocated DCN IP address to the NE IP
address provisioned on the NE. This procedure applies to IPv4 only.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
Procedure 2-16
Provisioning Dynamic NAT
Use this procedure to provision the Dynamic network address translation
(NAT). This procedure applies to IPv4 only.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
1 In the Dynamic NAT Provisioning panel, enter the value for NAT Starting Port.
This value should be between 1024 and 65535.
2 Enter a value for Number of NAT Entries. This value should between 256 and
1024.
3 Click Apply.
The next Commissioning Step panel appears.
Go to Procedure 2-17, “Provisioning Port Filtering”.
—end—
Procedure 2-17
Provisioning Port Filtering
Use this procedure to provision the Port filtering parameters.
Use the Add button to provision a new entry and the Delete button to delete
an existing entry.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
1 In the Port Filtering Provisioning panel, click on the Add button and enter the
parameters in the fields, as applicable. Refer to “Port Filtering Provisioning”
section in Table 1-3 on page 1-13 for provisioning values.
2 Click OK in the Add dialog box.
A new row, with the entered values, is added to the table.
A Delete button is available if you want to delete the entry.
3 Click on the Confirm Completion button.
4 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-18, “Provisioning Reverse Port NAT”.
—end—
Procedure 2-18
Provisioning Reverse Port NAT
Use this procedure to provision the Reverse Port NAT parameters. This
procedure applies to IPv4 only.
Reverse Port NAT displays the information about mapping the TCP/UDP port
of external requests to other internal port numbers and use a single external
IP address to access service in the internal network.
The Reverse Port NAT entries can be added only in Standalone Private IP and
Redundant Private IP GNE configuration modes.
Use the Add button to provision a new entry and the Delete button to delete
an existing entry. The Add button is disabled when Static NAT entries exist.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
1 In the Reverse Port NAT Provisioning panel, click on the Add button and enter
the parameters in the fields, as applicable. Refer to “Reverse Port NAT
provisioning” section in Table 1-3 on page 1-13 for provisioning values.
2 Click OK in the Add dialog box.
A new row, with the entered values, is added to the table.
A Delete button is available if you want to delete the entry.
3 Click on the Confirm Completion button.
4 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-19, “Provisioning Neighbor Discovery Protocol”.
—end—
Procedure 2-19
Provisioning Neighbor Discovery Protocol
Use this procedure to enable or disable the NDP (Neighbor Discovery
Protocol) feature on the shelf.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the Advanced Nodal SLAT Assistant Tool open with the NDP
Provisioning Step highlighted
Step Action
1 In the NDP Provisioning panel, select Enabled or Disabled from the Admin
State drop-down list. Click Apply.
2 If no change is required, click Confirm Completion.
3 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-20, “Provisioning static routes”.
—end—
Procedure 2-20
Provisioning static routes
Use this procedure to provision static routes. One or more static routes are
required on non-OSPF GNE shelves, usually against the COLAN, to provide
reachability to external destinations. In most cases, these static routes must
be redistributed into the internal routing domain (OSPF or iISIS). For IPv4,
redistribution is done as a separate step. For IPv6, redistribution is specified
as part of the static route provisioning itself.
Depending on the specific requirements of the network, static routes may also
be required on other interfaces and shelves.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
1 Select your next step. If you are using Dual Stack IPv4/IPv6, you must
provision the parameters in both the IPv4 tab and the IPv6 tab.
If you are provisioning for Then go to
IPv4 step 2
IPv6 step 8
Step Action
8 In the IPv6 Static Routes Provisioning panel, click Add. See Table 1-3 on
page 1-13 for parameter details.
9 In the Add dialog box, enter the parameters for the static route in the fields,
as applicable. Then, click OK. Note that redistribution of the static route into
OSPFv3 can be enabled in this step by setting Redistribute to OSPFv3, and
setting the RDTYPE (metric type) as either Internal (Type 1) or External
(Type 2).
A new row, with the entered values, is added to the table.
You can select one of the rows in the table and click Delete or Edit button to
delete or edit an entry.
10 Repeat step 8 and step 9 for the other static routes, if applicable.
11 Click Confirm Completion to apply the changes to the network element.
12 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-21, “Provisioning OSPF routes distribution”.
—end—
Procedure 2-21
Provisioning OSPF routes distribution
Use this procedure to provision route redistribution on the OSPF router.
Routes can be distributed into OSPFv2 from the following two sources:
• iISIS (ISISRDLIST)
• static routes (STATICRDLIST)
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
Step Action
5 In the OSPF - Routes Distribution panel, verify the route distribution data.
Then click Confirm Completion.
6 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-22, “Provisioning IISIS routes distribution”.
—end—
Procedure 2-22
Provisioning IISIS routes distribution
Use this procedure to provision routes distribution on the IISIS router. This
procedure applies to IPv4 only. Routes can be distributed into iISIS from the
following two sources:
• OSPF (OSPFRDLIST)
• static routes (STATICRDLIST)
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
Procedure 2-23
Provisioning SNMP
Use this procedure to provision the SNMP for the network element.
ATTENTION
The Advanced SLAT Assistant Tool remembers the NE Configuration system
parameter settings and SNMP application settings. The tool automatically
reuses them when the next shelf is set up. The information is stored in the
slat_preferences.xml file at the following Site Manager installation location:
<user_home_dir>/.ciena_desktop/sitemanager/PREFERENCES/SM
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
1 In the SNMP Provisioning panel, set the SNMP state to Enabled or Disabled.
To set the SNMP State to Enabled, select Enabled and click Apply SNMP
Data.
2 In the SNMP provisioning panel, select the SNMP Version.
3 Enable or disable alarm masking.
4 Enable or disable SNMP proxy. If SNMP proxy is enabled, enter a proxy
timeout value.
5 Click Apply SNMP Data.
6 Select a destination ID from the SNMP Trap Destinations table and click Edit
Trap Destination.
7 In the Edit SNMP Trap Destinations dialog box, edit the IP address and UDP
port and the TRAP Configuration for that destination and click OK.
Step Action
8 Repeat step 6 and step 7 for the remaining destination IDs, if applicable.
9 In the SNMP provisioning panel, click Confirm Completion.
10 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-24, “Provisioning security”.
—end—
Procedure 2-24
Provisioning security
Use this procedure to provision the security attributes for the network element.
On a member shelf, only Intrusion detection status is provisionable. You can
leave the default settings, and change them at a later time.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
Procedure 2-25
Provisioning SSH/TELNET and HTTP/HTTPS Server
Use this procedure to provision the Secure Shell (SSH), Telnet, and HTTP/
HTTPS server for the network element.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
Procedure 2-26
Provisioning craft access
Use this procedure to provision the craft LAN-15 (or 41) and LAN-16 (or 42)
port IPv4 address. To access the IPv6 craft port IP, IPv6 must be turned on
through Site Manager access through IPv4, because IPv6 is disabled by
default.
This procedure is required only if you want the ability to access remote
network elements using the LAN-15 (or 41) or LAN-16 (or 42) port. Otherwise,
skip this procedure.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
Step Action
If you are connected through the craft port, the connection to the network
element is dropped. An “Operation Failed” error message appears because
the software is unable to refresh the screen. This is expected.
CAUTION
Loss of step tracking information
This step (step 7) causes a logout. You must log back
into the network element. The step tracking
information (check mark) is lost, but all applied
provisioning is maintained.
8 Exit the Advanced SLAT by clicking the X button in the top right corner of the
window.
9 Select your next step.
If you are using a Then go to
PC step 10
MAC step 11
Step Action
13 Log back in with Advanced SLAT using Procedure 2-5, “Launching Advanced
SLAT and logging in”. Use the new LAN port IP address you just entered,
instead of the default IP address.
A message appears indicating that you are reconnecting after setting the craft
IP address.
14 Click OK to close the message.
15 If you have finished editing the craft access, click Confirm Completion.
Go to Procedure 2-27, “Provisioning craft OSPF/IISIS”.
—end—
Procedure 2-27
Provisioning craft OSPF/IISIS
Use this procedure to provision Craft OSPF/IISIS circuits. This step is
optional. The data should be filled only if you require craft reach through
capability.
This procedure is required only if you want the ability to access remote
network elements using the LAN-15 (or 41) or LAN-16 (or 42) port. Otherwise,
skip this procedure.
Craft OSPF data can only be provisioned if the craft IP address does not have
the default (IPv4) value (10.0.0.1 or 10.0.0.5).
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
Procedure 2-28
Checking, clearing, and provisioning alarms
Use this procedure to check and clear the active alarms on the network
element, and to provision alarm points. You must clear any unexpected
alarms.
Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
Step Action
1 Make sure that there are no equipment class alarms. Certain facility class
alarms are expected until the network SLAT is complete.
2 Clear any unexpected alarms according to Part 1 and Part 2 of Fault
Management - Alarm Clearing, 323-1851-543.
3 If you want to change the alarm severity for any alarm points, in the Site
Manager Alarm Profiles application under Configuration->Alarms & Controls:
a. Select a user alarm profile (User 1, for example) for the appropriate alarm
class.
b. Edit the user alarm profile name if you want. Refer to the “Editing an
alarm profile” procedure in Part 1 of Fault Management - Alarm Clearing,
323-1851-543.
c. Edit the severity for each alarm point you want to change. Refer to the
“Editing an alarm profile” procedure in Part 1 of Fault Management -
Alarm Clearing, 323-1851-543.
d. Set the modified alarm profile as the default. Refer to the “Setting a
default profile” procedure in Part 1 of Fault Management - Alarm
Clearing, 323-1851-543.
e. Set the modified alarm profile as active for all instances of facilities or
equipment which are already provisioned. Refer to the “Setting a profile
as active” procedure in Part 1 of Fault Management - Alarm Clearing,
323-1851-543.
All existing alarms that have a different severity in the modified profile will
be cleared and raised with the new severity.
You have completed this procedure.
For more (optional) initial provisioning, go to Procedure 2-29, “Post SLAT
commissioning”.
—end—
Procedure 2-29
Post SLAT commissioning
Use this procedure to perform the following optional tasks, as applicable to
your system:
• enabling the DHCP server on the craft IPv6 port
• connecting the network element (NE) to the DCN
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
• saving the golden database to a remote host. Perform this task if you want
to clone a provisioning golden database onto a number of newly
commissioned NEs that are physical clones.
• cloning a provisioning golden database onto a number of newly
commissioned NEs that are physical clones
Prerequisites
• To enable the DHCP server on the craft IPv6 port, you must:
— use an account with a UPC level of 4 or higher.
— be logged into the network element
• To set up a golden database, you must
— use an account with a UPC level of 3 or higher
— have the user identifier and password you want to set for the golden
user profile
— have the URL of the remote host where you will back up the golden
database
— be logged into the golden NE
— make sure you have provisioned the golden NE with the provisioning
database that will serve as the golden database
— make sure that you have provisioned communications on the golden
NE to perform the file transfer of the golden database to the remote
host
Step Action
• To restore the golden database onto newly commissioned NEs that are
physical clones, you must
— use an account with a UPC level of 3 or higher
— make sure that you have provisioned communications on the newly
commissioned NEs to perform the file transfer of the golden database
from the remote host
— make sure the newly commissioned NEs are physical clones of the
golden NE
CAUTION
Risk of DCC/GCC communications loss
If the newly commissioned NE is not a physical clone of the
golden NE, the DCC/GCC communications may not be
preserved. Perform a local restore on the newly commissioned
network element to restore the DCC/GCC communications.
Step Action
Step Action
Step Action
Step Action
CS Coherent Select
NE network element
Rx receive
SP shelf processor
TR transmit/receive
Tx transmit
Procedures
The following table lists the procedures in this chapter. Perform the
procedures as applicable.
Procedures in this chapter do not cover the provisioning of the passive OTS
network. For the provisioning of the passive OTS network, see “Passive OTS
network procedures” on page 5-1.
Table 3-1
Procedures in this chapter
Procedure
Procedure 3-1
Provisioning photonic parameters
Use this procedure to provision:
• photonic parameters for line facing amplifiers, XLA amplifiers, RLA
amplifiers, DIA amplifier, cascaded amplifiers, DSCMs and pads at a
network element
• the fiber type for SRA circuit packs
• RAMAN parameters (SRA circuit packs)
• the excess loss parameter on the OSC (2xOSC or SPAP-2 [with OSC
SFP] circuit packs, SRA/ESAM/SAM circuit packs)
The target peak power and the target gain tilt must be provisioned for each line
facing and cascaded amplifier in the system. The target peak power and the
target gain tilt values, and the XLA/RLA gain mode and top offset are
provisioned as per the OnePlanner amplifier report. For Drop LIM, nothing
needs to be provisioned. For DIA amplifier, the target gain must be
provisioned as per the OnePlanner amplifier report.
DSCM/Pad placed at the input or output port of a line facing amplifier must be
associated with an OTS, the position of DSCM/Pad is specified in the
equipment slot sequence.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage electrostatic-
sensitive devices. Always connect yourself to ground before
you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
For any patch panel losses or remote distance losses between the WSS
switch port and a filter Common/NTWK/EXPR port, refer to 6500
Packet-Optical Platform Photonic Layer Guide, NTRN15DA.
Prerequisites
• Ensure that the commissioning procedures (using Node Setup or
Advanced SLAT) have been completed.
• Ensure that photonic circuit packs (such as SCMD4, 2xOSC, SPAP-2 w/
2xOSC, SLA, MLA, MLA2, MLA2 w/VOA, MLA3, LIM, XLA, SRA, ESAM,
SAM, WSS, RLA, 2-port OPM), pluggables, and/or modules (such as
CMD44, CMD64, BMD2, or DSCM) have been provisioned. Refer to the
“Retrieving equipment and facility details” procedure in Part 1 of
Configuration - Provisioning and Operating, 323-1851-310.
• Use an account with a UPC level of 3 or higher.
Step Action
1 Log into the network element using Site Manager and launch the Equipment
& Facility Provisioning application from the Configuration menu.
Step Action
Step Action
Step Action
Step Action
For pads at DIA OTS WSS and backbone WSS Switch port 8/9 Output port
(port 18/20), no provisioning is required.
Provisioning DSCM/Pad/excess loss on OSC
Note: If the DSCM is connected by CAT5 cable to the External Inventory
Access Panel port of the shelf, it will auto-provision. Otherwise, you need to
provision the DSCM manually. The Pad must be provisioned as DSCM
manually if it is not connected to a CMD Tx or Rx. Channel pads that connect
to a CMD Tx and/or Rx must be provisioned as Pad Loss in the ADJ-FIBER
facility of the CMD Tx and/or Rx port.
43 If Then go to
you are provisioning a channel pad step 48
you are provisioning a DSCM or non-channel pad step 44
you are provisioning the excess loss on OSC step 50
(insertion of pad)
you have completed DSCM, pad, or excess loss you have completed
provisioning this procedure
Step Action
Procedure 3-2
Provisioning adjacencies
For OTS instances created using the Photonic Configuration Management
application, once the slot sequences are defined, all intra-OTS adjacencies
are system derived. Use this procedure to provision the inter-OTS WSS-WSS
(or RLA-RLA) adjacencies and line adjacencies. For configurations using
FIMs, all adjacencies are automatically system derived.
See Photonic Layer Guide, NTRN15DA, for details of the intra and inter
adjacencies.
For TOADM and DIA, inter-OTS adjacencies are provisioned after TOADM
and DIA are tested in Procedure 4-9, “Testing TOADM channel access
continuity” and Procedure 4-10, “Testing a DIA configuration”.
The 2-port OPM is not part of an OTS. For adjacencies to the 2-port OPM,
see:
• “CMD44-OPM adjacencies” on page 3-23 for the CMD-OPM adjacencies,
• “LIM-OPM adjacencies” on page 3-24 and “LIM-OPM adjacencies in XLA
case” on page 3-24 for the LIM-OPM adjacencies.
A single OPM can be fibered to two different LIM (or XLA, if present) circuit
packs that are in different OTSs. The OPM and LIM (or XLA, if present) circuit
packs must reside in the same shelf.
When one 2-port OPM circuit pack is equipped in the shelf where a line
amplifier OTS is provisioned, the following LIM to OPM adjacencies are auto-
provisioned:
• port 1 (Line B MON) of the LIM in lower numbered OTS points to OPM port
1
• port 1 (Line B MON) of the LIM in higher numbered OTS points to OPM
port 2
When two 2-port OPM circuit packs are equipped in the shelf where a line
amplifier OTS is provisioned, the following LIM to OPM adjacencies are auto-
provisioned:
• port 1 (Line B MON) of the LIM in lower numbered OTS points to port 1 of
the 2-port OPM in higher numbered slot
• port 1 (Line B MON) of the LIM in higher numbered OTS points to port 2
of the 2-port OPM in higher numbered slot
When a 2-port OPM circuit pack is equipped in the shelf where a line amplifier
OTS is provisioned, the following XLA to OPM adjacencies (LIM type) are
auto-provisioned:
• port 1 (Line B MON) of the XLA points to OPM port 1
• port 2 (Line A MON) of the XLA points to OPM port 2
When two 2-port OPM circuit packs are equipped in the shelf where a line
amplifier OTS is provisioned, the following XLA to OPM adjacencies (LIM
type) are auto-provisioned:
• port 1 (Line B MON) of the XLA points to OPM port 1 in higher numbered
slot
• port 2 (Line A MON) of the XLA points to OPM port 2 in higher numbered
slot
When two or more 2-port OPMs are provisioned in the shelf, the adjacencies
will be derived only for the 2-port OPM that was provisioned first.
Prerequisites
• Ensure that the commissioning procedures (using Node Setup or
Advanced SLAT) have been completed.
• Use an account with a UPC level of 3 or higher.
• Log into the network element using Site Manager and launch the
Equipment & Facility Provisioning application from the Configuration
menu.
Step Action
Step Action
Provision adjacencies between the 2-port OPM and the LIM or XLA if applicable
Note 1: For ROADM, when the LIM (or XLA if present) and WSSOPM are
provisioned in the OTS, the LIM monitor port adjacencies point to the OPM
monitor ports of the WSSOPM by default. If required, you can override the
default adjacencies to point to the 2-port OPM by performing step 2 to step 6.
Then the far end address of the WSSOPM monitor port adjacencies will be
cleared.
Note 2: Perform step 2 to step 6 at a line amplifier site if you want to override
the auto-provisioned LIM (or XLA if present) to OPM adjacencies.
Note 3: The RLA has an internal OCM and does not need to be connected
to an OPM. RLA ports 1 and 2 can be used to connect an external customer
OPM if required.
2 In the Equipment table, select the LIM equipment, XLA, or RLA equipment
that is connected to the 2-port OPM.
3 Select ADJ in the Facility Type drop down list.
4 Select the LIM monitor port (port 1 or port 2) or XLA monitor port (port 1 or 2).
5 Click Edit in the Facility area.
6 In the Edit facility dialog box:
• select OPM in the Adjacency type drop down list
• select the Expected far end address format (TID-SH-SL-PRT) and the
Expected far end address as indicated in the EDP/IDP. This address
should point to the 2-port OPM monitor port (port 1 or port 2).
• click OK
The corresponding adjacency at the OPM port will be auto-derived.
7 Repeat step 2 to step 6 for the other LIM monitor port or XLA monitor port that
is connected to the 2-port OPM.
8 Repeat step 2 to step 7 for all LIM equipment or XLA equipment monitor port.
Provision Line adjacencies
9 In the Equipment table, select the LIM, RLA, SRA, ESAM, SAM, or DSCM
equipment that connects to the line fiber in the transmit direction.
10 Select ADJ-LINE (for LIM, RLA, SRA, ESAM, SAM) or ADJ (for DSCM) from
the Facility Type drop down list.
11 Select the Line adjacency that corresponds to ADJ-<shelf>-<slot>-5 (Line B
Out) or ADJ-<shelf>-<slot>-1 (for DSCM Out) as indicated in the EDP/IDP.
12 Click Edit in the Facility area.
13 In the Edit facility dialog box, modify the Fiber Type as indicated in the EDP/
IDP.
Step Action
14 Select the Expected far end address format (TID-SH-SL-PRT) and enter the
Expected far end address as indicated in the EDP/IDP.
The Expected far end address identifies the receive port of the line facing
module that is connected to the other end of the line, it should point to port 8
of LIM, RLA, SRA, ESAM, SAM, or port 2 of DSCM on the remote NE.
15 Enter the minimum span loss, span loss margin and target span loss as
indicated in the EDP/IDP.
16 Click OK in the Edit facility dialog box.
17 Repeat step 9 to step 16 for all line adjacencies. If this is a DGFF site, go to
step 24.
Provision adjacencies between the 2-port OPM and the enhanced CMD44 or CMD64 if applicable
18 In the Equipment table, select the enhanced CMD44 or CMD64 equipment
that is connected to the 2-port OPM.
19 Select ADJ in the Facility Type drop down list.
20 Select the CMD44 monitor port (port 92) or CMD64 monitor port (port 129 or
port 130).
21 Click Edit in the Facility area.
22 In the Edit facility dialog box:
• select OPM in the Adjacency type drop down list
• select the Expected far end address format (TID-SH-SL-PRT) and the
Expected far end address as indicated in the EDP/IDP. This address
should point to the 2-port OPM monitor port (port 1 or port 2).
• click OK
The corresponding adjacency at the OPM port will be auto-derived.
23 Repeat step 18 to step 22 if there is another CMD44 or CMD64 connected to
the 2-port OPM (or if you want to connect the other monitor port of a CMD64).
Step Action
25 In the Equipment table, select the WSSOPM or RLA equipment for one end
of the WSS-WSS link.
26 Select ADJ in the Facility Type drop down list.
27 Select the adjacency corresponding to the WSS or RLA output port.
28 Click Edit in the Facility area.
29 In the Edit facility dialog box:
• select WSS or RLA in the Adjacency type drop down list
• select the Expected far end address format (TID-SH-SL-PRT) and the
Expected far end address as indicated in the EDP/IDP. This address
should point to the connecting WSS’s or RLA’s input port AID.
• click OK
30 In the Equipment table, select the WSSOPM or RLA equipment for the other
end of the WSS-WSS or RLA-RLA link.
31 Select ADJ in the Facility Type drop down list.
32 Select the adjacency corresponding to the WSS or RLA output port.
33 Click Edit in the Facility area.
34 In the Edit facility dialog box:
• select WSS or RLA in the Adjacency type drop down list
• select the Expected far end address format (TID-SH-SL-PRT) and the
Expected far end address as indicated in the EDP/IDP. This address
should point to the connecting WSS or RLA circuit pack’s input port AID.
• click OK
If this is a DGFF site, you have completed this procedure.
Step Action
Step Action
Step Action
62 For the OTS2/path2 CMD Channel In port, provision the ADJ-TX Expected
Far End Address to point to OPS SW2 Out port.
Note: For OPS in colored configurations, if the wavelengths corresponding
to the Expected Far End Addresses of SW1 and SW2 differ, this fault is
reported via an “Adjacency Mismatch” alarm.
Provisioning OPM adjacencies when using standalone OPM monitoring
63 In the Equipment table, select the equipment that is connected to the 2-port
OPM.
64 Select ADJ in the Facility Type drop down list.
65 Select the equipment monitor port (port 1 or port 2).
66 Click Edit in the Facility area.
67 In the Edit facility dialog box:
• select OPM in the Adjacency type drop down list
• select the Expected far end address format (TID-SH-SL-PRT) and enter
the Expected far end address as indicated in the EDP/IDP. This address
should point to the connecting OPM port.
• click OK
Provisioning the Excess Loss parameter
68 To scale the measured power from the tap point to the actual line power,
provision the Excess Loss parameter:
• select ADJ-FIBER in the Facility Type drop down list
• select the facility that is the tap point
• click Edit in the Facility area
• in the Edit facility dialog box, provision the Excess Loss parameter as
indicated in the EDP/IDP
• click OK
—end—
Figure 3-1
CMD44-OPM adjacencies
2-port OPM
Figure 3-2
LIM-OPM adjacencies
Figure 3-3
LIM-OPM adjacencies in XLA case
Procedure 3-3
Changing amplifier provisioning targets and
differential provisioning settings on an existing
network
Use this procedure to change amplifier peak power and gain tilt targets, as
well as differential provisioning settings, on an already deployed photonic
layer network. This procedure does not apply to the passive OTS network.
Prerequisites
• Before you perform this procedure, contact Ciena to perform a link budget
analysis of the system to determine the amplifier peak power and gain tilt
targets, as well as differential provisioning settings, that must be applied.
• All active channels on the network must have an End-to-End Condition of
“Optimized”.
• The network must be alarm-free.
• Peak power and gain tilt targets must be available for all amplifiers in the
network.
• Differential provisioning targets must be available for all modulation types
for all domains.
Step Action
Step Action
Step Action
Step Action
14 Adjust the baselines (by using Reset TCA baselines) in the domains located
downstream from the domain just re-optimized.
15 Re-optimize the downstream domains for which you have adjusted the
baselines.
16 Repeat step 7 to step 15 to change the provisioning by no more than 1 dB
steps until the final targets have been achieved.
17 After you change the amplifier provisioning values in all domains and all
active channels on the network have an End-to-End Condition of “Optimized”,
log into the network elements identified as Domain Optical Controllers (DOC)
in step 1 and change the Automation mode back to its original setting
recorded in step 4.
18 Perform step 17 on both DOC NEs in each optical domain in the network.
Branched networks and networks with spurs contain more than one optical
domain.
Step Action
19 After you change the amplifier provisioning values in all domains and all
active channels on the network have an End-to-End Condition of “Optimized”,
enable the DOC gain clamp mode you disabled in step 2.
a. At the TL-1 command prompt, enter:
ED-DOC::DOC-<shelf>-<instance>:CTAG:::
DOCGAINCLAMP=ENABLE;
b. Log out of the TL-1 interface.
CANC-USER::ADMIN:1;
20 Perform step 19 on both DOC NEs in each optical domain in the network.
Branched networks and networks with spurs contain more than one optical
domain.
—end—
Procedure 3-4
Updating SPLI entries
Use this procedure to update Service and Photonic Layer Interoperability
(SPLI) entries on an already deployed photonic layer network.
Prerequisites
• Use an account with a UPC level of 3 or higher.
• Log into the network element using Site Manager and launch the
Equipment & Facility Provisioning application from the Configuration
menu.
Step Action
Photonic layer site testing procedures describe how to test the photonic layer
in 6500 network element. Make sure the SLAT prerequisites listed in Chapter
1, “SLAT process overview” are met and Nodal SLAT procedures are
completed before starting the photonic layer site testing procedures.
Procedures in this chapter do not apply to the passive OTS network. For the
passive OTS network procedures, see “Passive OTS network procedures” on
page 5-1.
Table 4-1
Procedures in this chapter
Procedure
Procedure 4-1, “Connecting intra-site fibers for TOADM/ROADM/DGFF/DIA/Colorless OADM sites”
Procedure 4-2, “Adding a new CMD44, CMD64, or BMD2”
Procedure 4-3, “Adding a new OMD4 or OMX”
Procedure 4-4, “Adding a new SCMD4”
Procedure 4-5, “Adding a new CCMD12”
Procedure 4-6, “Adding a new CCMD8x16 or a CXM C-Band Type 1”
Procedure 4-7, “Testing ROADM channel access continuity”
Procedure 4-8, “Testing a CDC ROADM configuration”
Procedure 4-9, “Testing TOADM channel access continuity”
Procedure 4-10, “Testing a DIA configuration”
Procedure 4-11, “Testing a low channel count DIA configuration”
Procedure 4-12, “Testing a Colorless OADM configuration”
Procedure 4-13, “Connecting intra-site fibers and testing a Colorless Direct Attach configuration
(COADM OTS connected to 1x9 or 1x2 WSS)”
Procedure 4-14, “Connecting intra-site fibers for a Colorless Direct Attach configuration
(CCMD12/CMD44/CMD64 connected to 1x20 WSS)”
Procedure 4-15, “Testing Colorless Direct Attach configurations (CCMD12/CMD44/CMD64
connected to 1x20 WSS)”
Procedure 4-16, “Testing a line amplifier node”
Table 4-1
Procedures in this chapter (continued)
Procedure
Procedure 4-17, “Testing DGFF nodes”
Procedure 4-18, “Connecting intra-site fibers for Coherent Select sites”
Procedure 4-19, “Testing a Coherent Select line amplifier node”
Procedure 4-20, “Testing a Coherent Select Terminal - Colored node”
Procedure 4-21, “Testing Coherent Select Directionless or Directional nodes”
Procedure 4-22, “Connecting inter-NE fibers and testing the photonic layer”
Procedure 4-23, “Configuring a single span 100 GHz CMD44 point-to-point terminal”
Procedure 4-24, “Configuring a single span OMD4/CMD44 or OMX point-to-point terminal”
Procedure 4-25, “Equalizing a thin terminal system”
Procedure 4-26, “Configuring a remote CMD44 terminal”
Procedure 4-1
Connecting intra-site fibers for
TOADM/ROADM/DGFF/DIA/Colorless OADM sites
Use this procedure to perform intra-site fiber connections at a line amplifier
site or a TOADM/ROADM/DGFF/DIA/Colorless OADM site. In this procedure,
CMD44 refers to both the regular CMD44, the enhanced 100GHz CMD44 with
isolator (eCMD44), and the enhanced 50GHz CMD44 unless specified
otherwise.
The configurations shown in the following figures are also known as MuxAmp
configurations:
• “Intra-NE fiber connections at a ROADM site (CMD44 only)” on page 4-39
• “Intra-NE fiber connections at a ROADM site with interior SLA” on page
4-40
• “Intra-NE fiber connections at a ROADM site with single 2xOSC circuit
pack” on page 4-41
• “Intra-NE fiber connections at a ROADM site (example shows XLA and
SRA)” on page 4-42
• “Intra-NE fiber connections at a ROADM site (CMD44 and CMD64)” on
page 4-43
• “Intra-NE fiber connections at a ROADM site using RLA/CMD64” on page
4-44
• “Intra-NE fiber connections at a ROADM site using RLA/CMD44” on page
4-45
• “Intra-NE fiber connections at a ROADM site using RLA/CMD64 with
ESAM/SAM/SRA (SAM shown)” on page 4-46
• “Intra-NE fiber connections at a ROADM site using RLA/CMD44 with
ESAM/SAM/SRA (SRA shown)” on page 4-47
• “Intra-NE fiber connections between a low channel count DIA and
backbone OTS” on page 4-48
• “Intra-NE fiber connections at a ROADM site with XLA and SRA - DSCM
placement” on page 4-49
• “Intra-NE fiber connections at a ROADM site with ESAM-MLAx (example
shows MLA)” on page 4-49
• “Intra-NE fiber connections (CMD44 to BMD2 to WSS)” on page 4-50
• “Intra-NE fiber connections (CMD44 to BMD2 to SLA to WSS)” on page
4-51
• “Intra-NE fiber connections (CMD44 to Drop LIM to WSS)” on page 4-52
• “Intra-NE fiber connections between a 100 GHz DIA and backbone OTS”
on page 4-53
• “Intra-NE fiber connections between a 50 GHz DIA and backbone OTS”
on page 4-54
• “Intra-NE fiber connections at a Colorless OADM site” on page 4-55
• “Intra-NE fiber connections at a Colorless OADM site with CMD44 50GHz”
on page 4-56
• “Intra-NE fiber connections at a low channel count DIA site (non-OTS
equipment)” on page 4-57
• “Intra-NE fiber connections at a CDC ROADM site (CCMD8x16)” on page
4-58
• “Intra-NE fiber connections at a CDC ROADM site (CCMD8x16 and
CMD44 50 GHz)” on page 4-59
• “Intra-NE fiber connections at a CDC ROADM site (CCMD8x16 and
CMD44 100 GHz)” on page 4-60
The configurations shown in the following figures are also known as dynamic
gain flattening filter (DGFF) configurations:
• “Intra-NE fiber connections at a DGFF site” on page 4-61
• “Intra-NE fiber connections at a DGFF site (RLA)” on page 4-62
• “Intra-NE fiber connections at a DGFF site (RLA with SAM/ESAM/SRA)”
on page 4-63
This procedure does not cover a ROADM site using OMD4, OMDF4, OMDF8,
and/or BS. You must connect the intra-site fibers of such ROADM sites based
on the specific network configurations.
For a thin OADM site, fiber connections between the two OTSs are done after
the TOADM site is tested in Procedure 4-9, “Testing TOADM channel access
continuity”.
Prerequisites
• Ensure that commissioning information has been entered.
• Ensure that cables are connected between the access panel and
subtending modules (CMD, BMD2, and DSCM).
• Use optical terminators on unused input faceplate connectors of installed
WSS circuit packs. If dust caps are used instead of optical terminators,
PMs can be reported against the port and the port may appear in-service.
• Ensure that the fibers have been cleaned and verified to be in working
condition, and the loss between fibers is not greater than 0.5 dB. The
fibers that are used in the following steps must be verified to be in good
working order prior to use. It is very important that fibers are cleaned and
scoped prior to being connected. Refer to the cleaning instructions in
Installation - General Information, 323-1851-201.0.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
Step Action
Step Action
Connecting OSC to SLA, MLA, LIM, MLA2, MLA2 w/VOA, MLA3, or RLA
Note: For the maximum number and slot equipping rules regarding 2xOSC
circuit packs, see the section on shelf equipping rules in the configuration
rules chapter of Planning - Ordering Information, 323-1851-151. The OSC
ports in this section (step 2 to step 8) could alternatively be on the SPAP-2
w/2xOSC circuit pack if applicable.
2 Connect the 2xOSC OSC-1 Out port to the OSC In (port 3) of the appropriate
line facing circuit pack (SLA, MLA, LIM, MLA2, MLA2 w/VOA, MLA3, or RLA).
Ensure that the OSC-1 is connected to the line facing circuit pack as indicated
in the EDP/IDP (in the correct slot).
3 Connect the 2xOSC OSC-1 In port to the OSC Out (port 4) of the appropriate
line facing circuit pack. Ensure that the OSC-1 is connected to the line facing
circuit pack as indicated in the EDP/IDP (in the correct slot).
4 Select your next step.
If you need to fiber another OSC and are using a Then go to
single 2xOSC circuit pack configuration step 5
dual 2xOSC circuit packs configuration step 7
5 Connect the 2xOSC OSC-2 Out port to the OSC In (port 3) of the appropriate
line facing circuit pack. Ensure that the OSC-2 is connected to the line facing
circuit pack as indicated in the EDP/IDP (in the correct slot).
6 Connect the 2xOSC OSC-2 In port to the OSC Out (port 4) of the appropriate
line facing circuit pack. Ensure that the OSC-2 is connected to the line facing
circuit pack as indicated in the EDP/IDP (in the correct slot).
Go to step 16.
7 Connect the 2xOSC OSC-1 Out port of the second 2xOSC circuit pack to the
OSC In (port 3) of the appropriate line facing circuit pack. Ensure that the
OSC-1 is connected to the line facing circuit pack as indicated in the EDP/IDP
(in the correct slot).
Step Action
8 Connect the 2xOSC OSC-1 In port of the second 2xOSC circuit pack to the
OSC Out (port 4) of the appropriate line facing circuit pack. Ensure that the
OSC-1 is connected to the line facing circuit pack as indicated in the EDP/IDP
(in the correct slot).
Then go to step 1.
Making OSC connections on SRA/ESAM/SAM
9 Make sure to read and observe the following CAUTION and Attention.
CAUTION
Risk of not detecting OSC Optical Line Failure alarms
Make sure to connect the OSC fibers as indicated in the
EDP/IDP. Otherwise, Optical Line Failure alarms may
not be detected correctly in single fiber cut scenarios.
(Double fiber cuts are not affected.)
Step Action
10 On the SRA/ESAM/SAM circuit pack, connect the OSC SFP Tx port to the
OSC In port (Port 3).
11 Select your next step.
If Then go to
you are connecting an NTK504BA OSC Filter module step 13
you are not using and OSC Filter module and are step 12
completing the OSC connections on SRA/ESAM/SAM
Step Action
Performing intra-NE fibering at a line amplifier site equipped with SRA/ESAM/SAM line facing circuit
packs and XLA circuit packs
18 See Figure 4-3 on page 4-34 for an example of intra-NE fibering at a line
amplifier site with XLA circuit packs. (The line facing circuit pack can be
ESAM, SAM, or SRA.)
The line amplifier site contains two OTSs. One OTS contains one of the line
facing circuit packs and the XLA (OTS 1 in Figure 4-3 on page 4-34). The
other OTS contains the second line facing circuit pack (OTS2 in Figure 4-3 on
page 4-34).
Make sure to fiber correctly. The system derives the adjacencies based on the
OTS slot sequence provisioning.
19 Connect the Line A Out (port 7) of the line facing circuit pack that is in the
same OTS as the XLA either to a DSCM In port or to the Line A In (port 8) of
the XLA circuit pack. When connecting to a DSCM, ensure that the
connection is made as indicated in the EDP/IDP (DSCM in the correct slot).
Ensure the correct fixed pad is inserted in the connection as indicated in the
EDP/IDP.
20 If applicable, connect the first DSCM to the second DSCM in the Line A
direction towards the XLA.
21 If not connected in step 19, connect the Line A In (port 8) of the XLA circuit
pack to the DSCM Out port. If only one DSCM, the DSCM you are connecting
to is the same as in step 19. If two DSCMs, you are connecting to the second
DSCM. Ensure the correct fixed pad is inserted in the connection as indicated
in the EDP/IDP.
22 Connect the Line A Out (port 7) of the XLA either to a DSCM In port or to the
Line B In (port 6) of the line facing circuit pack that is in the other OTS than
the XLA (OTS2 in Figure 4-3). When connecting to a DSCM, ensure that the
connection is made as indicated in the EDP/IDP (DSCM in the correct slot).
Ensure the correct fixed pad is inserted in the connection as indicated in the
EDP/IDP.
23 If applicable, connect the first DSCM to the second DSCM in the Line A
direction towards the next line facing circuit pack.
24 If not connected in step 22, connect the Line B In (port 6) of the line facing
circuit pack to the DSCM Out port. If only one DSCM, the DSCM you are
connecting to is the same as in step 22. If two DSCMs, you are connecting to
the second DSCM. Ensure the correct fixed pad is inserted in the connection
as indicated in the EDP/IDP.
Step Action
25 Perform step 19 to step 24 in the opposite direction. The port numbers are as
follows:
• OTS2 line facing circuit pack Line A Out - port 7
• XLA Line B In - port 6
• XLA Line B Out - port 5
• line facing circuit pack that is in the same OTS as the XLA (OTS1) -
Line B In port 6
Go to step 51.
Performing intra-NE fibering at a line amplifier site equipped with ESAM +MLAx+ESAM
26 See Figure 4-4 on page 4-35 for an example of intra-NE fibering at a line
amplifier site with ESAM-MLAx-ESAM circuit pack configuration.
The line amplifier site contains two OTSs. One OTS contains one of the
ESAMs and the MLAx (OTS 1 in Figure 4-4 on page 4-35). The other OTS
contains the second ESAM (OTS2 in Figure 4-4 on page 4-35).
Make sure to fiber correctly. The system derives the adjacencies based on the
OTS slot sequence provisioning.
27 Connect the Line A Out (port 7) of the ESAM that is in the same OTS as the
MLAx either to a DSCM In port or to the Line A In (port 8) of the MLAx circuit
pack. When connecting to a DSCM, ensure that the connection is made as
indicated in the EDP/IDP (DSCM in the correct slot). Ensure the correct fixed
pad is inserted in the connection as indicated in the EDP/IDP.
28 If not connected in step 27, connect the Line A In (port 8) of the MLAx circuit
pack to the DSCM Out port. Ensure the correct fixed pad is inserted in the
connection as indicated in the EDP/IDP.
29 Connect the Line A Out (port 7) of the MLAx either to a DSCM In port or to
the Line B In (port 6) of the ESAM circuit pack that is in the other OTS than
the MLAx (OTS2 in Figure 4-4 on page 4-35). When connecting to a DSCM,
ensure that the connection is made as indicated in the EDP/IDP (DSCM in
the correct slot). Ensure the correct fixed pad is inserted in the connection as
indicated in the EDP/IDP.
30 If not connected in step 29, connect the Line B In (port 6) of the ESAM to the
DSCM Out port. Ensure the correct fixed pad is inserted in the connection as
indicated in the EDP/IDP.
Step Action
31 Perform step 27 to step 30 for the opposite direction. The port numbers are
as follows:
• OTS2 ESAM circuit pack Line A Out - port 7
• MLAx Line B In - port 6
• MLAx Line B Out - port 5
• ESAM circuit pack that is in the same OTS as the MLAx (OTS1) -
Line B In port 6
Go to step 51.
Performing intra-NE fibering at a line amplifier site equipped with ESAM -MLAx-MLAx-ESAM
32 See Figure 4-5 on page 4-36 for an example of intra-NE fibering at a line
amplifier site with ESAM-MLAx-MLAx-ESAM circuit pack configuration.
The line amplifier site contains two OTSs. One OTS contains one of the
ESAMs and one MLAx (OTS 1 in Figure 4-5 on page 4-36). The other OTS
contains the second MLAx and the second ESAM (OTS2 in Figure 4-5 on
page 4-36).
Make sure to fiber correctly. The system derives the adjacencies based on the
OTS slot sequence provisioning.
33 Connect the Line A Out (port 7) of the first ESAM either to a DSCM In port or
to the Line A In (port 8) of the MLAx circuit pack that is in the same OTS as
the first ESAM. When connecting to a DSCM, ensure that the connection is
made as indicated in the EDP/IDP (DSCM in the correct slot). Ensure the
correct fixed pad is inserted in the connection as indicated in the EDP/IDP.
34 If not connected in step 33, connect the Line A In (port 8) of the MLAx circuit
pack to the DSCM Out port. Ensure the correct fixed pad is inserted in the
connection as indicated in the EDP/IDP.
35 Connect the Line A Out (port 7) of the MLAx from OTS 1 either to a DSCM In
port or to the Line B In (port 6) of the MLAx circuit pack that is in the other
OTS (OTS2 in Figure 4-5 on page 4-36). When connecting to a DSCM,
ensure that the connection is made as indicated in the EDP/IDP (DSCM in
the correct slot). Ensure the correct fixed pad is inserted in the connection as
indicated in the EDP/IDP.
36 If not connected in step 35, connect the Line B In (port 6) of the OTS2 MLAx
circuit pack to the DSCM Out port. Ensure the correct fixed pad is inserted in
the connection as indicated in the EDP/IDP.
Step Action
37 Connect the Line B Out (port 5) of the OTS2 MLAx either to a DSCM In port
or to the Line B In (port 6) of the ESAM circuit pack that is in the same OTS
(OTS2 in Figure 4-5 on page 4-36). When connecting to a DSCM, ensure that
the connection is made as indicated in the EDP/IDP (DSCM in the correct
slot). Ensure the correct fixed pad is inserted in the connection as indicated
in the EDP/IDP.
38 If not connected in step 37, connect the Line B In (port 6) of the OTS2 ESAM
circuit pack to the DSCM Out port. Ensure the correct fixed pad is inserted in
the connection as indicated in the EDP/IDP.
39 Perform step 33 to step 38 for the opposite direction. The port numbers are
as follows:
• OTS2 ESAM Line A Out - port 7
• OTS2 MLAx Line A In - port 8
• OTS2 MLAx Line A Out - port 7
• OTS1 MLAx Line B In - port 6
• OTS1 MLAx Line B Out - port 5
• OTS1 ESAM Line B In - port 6
Go to step 51.
Performing intra-NE fibering at a line amplifier site equipped with ESAM-MLAx-MLAx
40 See Figure 4-6 on page 4-37 for an example of intra-NE fibering at a line
amplifier site with ESAM-MLAx-MLAx circuit pack configuration.
The line amplifier site contains two OTSs. One OTS contains the ESAM and
one of the MLAx (OTS 1 in Figure 4-6 on page 4-37). The other OTS contains
the second MLAx (OTS2 in Figure 4-6 on page 4-37).
Make sure to fiber correctly. The system derives the adjacencies based on the
OTS slot sequence provisioning.
41 Connect the Line A Out (port 7) of the ESAM either to a DSCM In port or to
the Line A In (port 8) of the MLAx circuit pack that is in the same OTS as the
ESAM. When connecting to a DSCM, ensure that the connection is made as
indicated in the EDP/IDP (DSCM in the correct slot). Ensure the correct fixed
pad is inserted in the connection as indicated in the EDP/IDP.
42 If not connected in step 41, connect the Line A In (port 8) of the MLAx circuit
pack to the DSCM Out port. Ensure the correct fixed pad is inserted in the
connection as indicated in the EDP/IDP.
Step Action
43 Connect the Line A Out (port 7) of the MLAx from OTS 1 either to a DSCM In
port or to the Line B In (port 6) of the MLAx circuit pack that is in the other
OTS than the ESAM (OTS2 in Figure 4-6 on page 4-37). When connecting to
a DSCM, ensure that the connection is made as indicated in the EDP/IDP
(DSCM in the correct slot). Ensure the correct fixed pad is inserted in the
connection as indicated in the EDP/IDP.
44 If not connected in step 43, connect the Line B In (port 6) of the MLAx from
OTS2 to the DSCM Out port. Ensure the correct fixed pad is inserted in the
connection as indicated in the EDP/IDP.
45 Perform step 41 to step 44 for the opposite direction. The port numbers are
as follows:
• OTS2 MLAx circuit pack Line A Out - port 7
• OTS1 MLAx Line B In - port 6
• OTS1 MLAx Line B Out - port 5
• ESAM circuit pack Line B In - port 6
Go to step 51.
46 See Figure 4-1 on page 4-32 or Figure 4-2 on page 4-33 for an example of
intra-NE fibering at a line amplifier site.
47 Connect the Line A Out (port 7) of the first line facing circuit pack either to a
DSCM IN port or to the Line B In (port 6) of the next adjacent line facing circuit
pack. When connecting to a DSCM, ensure that the connection is made as
indicated in the EDP/IDP (DSCM in the correct slot). Ensure the correct fixed
pad is inserted in the connection as indicated in the EDP/IDP.
48 If not connected in step 47, connect the Line B In (port 6) of the next adjacent
line facing circuit pack to the DSCM Out port. The DSCM you are connecting
to is the same as in step 47. Ensure the correct fixed pad is inserted in the
connection as indicated in the EDP/IDP.
49 Connect the Line A Out (port 7) of the adjacent line facing circuit pack either
to a DSCM IN port or to the Line B In (port 6) of the first line facing circuit pack.
When connecting to a DSCM, ensure that the connection is made as
indicated in the EDP/IDP (DSCM in the correct slot). Make sure the correct
fixed pad is inserted in the connection as indicated in the EDP/IDP.
50 If not connected in step 49, connect the Line B In (port 6) of the first line facing
circuit pack to the DSCM Out port. The DSCM you are connecting to is the
same as in step 49. Ensure that the correct fixed pad is inserted in the
connection as indicated in the EDP/IDP.
Step Action
Step Action
61 If you are using the SCMD4, provision the SCMD4 cascade order according
to the EDP/IDP. Under Configuration -> Photonic Services -> SCMD
Cascading Order, select the line facing circuit pack and identify the SCMD4
in each position (position 1 is the one closest to the line facing circuit pack).
Select your next step.
If Then go to
you want to connect the line facing circuit pack to a step 62
2-port OPM
otherwise You have completed
this procedure.
64 See the following for examples of intra-NE fibering at a CDC ROADM site.
• Figure 4-28 on page 4-58
• Figure 4-29 on page 4-59
• Figure 4-30 on page 4-60
Step Action
CAUTION
Risk of affecting performance
You must inspect and clean the MPO connectors after
removing the MPO cable from its original packaging or
if the MPO cable has been removed from the faceplate
for any reason.
Step Action
Step Action
69 Connect the FIM to the WSSOPM for all applicable ROADM degrees as
indicated in the EDP/IDP.
This equipment uses MPO connectors. See step 66 for instructions on how
to handle MPO cables and connectors.
Then go to step 71.
70 See:
• the following figures for examples of intra-NE fibering at ROADM sites:
— Figure 4-8 on page 4-39 - CMD44, WSS 1x5, MLA, dual 2xOSC
— Figure 4-9 on page 4-40 - CMD44, WSS 1x5, MLA, interior SLA, dual
2xOSC
— Figure 4-10 on page 4-41 - CMD44, WSS 1x5, MLA, interior SLA,
single 2xOSC
— Figure 4-11 on page 4-42 - CMD44, WSS 1x9, XLA, SRA
— Figure 4-12 on page 4-43 - CMD44, CMD64/XLA or MLA3, WSS 1x9,
amp
— Figure 4-13 on page 4-44 - CMD64, RLA
— Figure 4-14 on page 4-45 - CMD44, RLA
— Figure 4-15 on page 4-46 - CMD64, RLA, SAM
— Figure 4-16 on page 4-47 - CMD64, RLA, SRA
— Figure 4-17 on page 4-48 - low channel count DIA (WSS/CCMD12)
and backbone OTS (WSS and MLA3)
• the following figures for examples for examples of intra-NE fibering at a
DGFF site
— Figure 4-31 on page 4-61 - WSS 1x5, MLA, dual 2xOSC
— Figure 4-32 on page 4-62 - RLA, dual 2xOSC
— Figure 4-33 on page 4-63 - RLA, SAM
At sites equipped with XLA, the line facing circuit pack can be ESAM, SAM,
or SRA.
71 Select your next step.
If Then go to
the site uses SRA/ESAM/SAM and XLA/RLA circuit step 72
packs
otherwise step 81
Step Action
73 Connect the Line A Out (port 7) of the SRA/ESAM/SAM circuit pack to the
DSCM In port. Ensure that the connection is made as indicated in the
EDP/IDP (DSCM in the correct slot). Ensure the correct fixed pad is inserted
in the connection as indicated in the EDP/IDP.
74 If applicable, connect the first DSCM to the second DSCM.
75 Connect the DSCM Out port to the Line A In (port 8) of the XLA/RLA. If only
one DSCM, the DSCM you are connecting is the same as in step 73. If two
DSCMs, you are connecting the second DSCM. Ensure the correct fixed pad
is inserted in the connection as indicated in the EDP/IDP.
76 Connect Line B In (port 6) of the line facing circuit pack to the DSCM Out port.
Ensure that the connection is made as indicated in the EDP/IDP (DSCM in
the correct slot). Ensure the correct fixed pad is inserted in the connection as
indicated in the EDP/IDP.
77 If applicable, connect the first DSCM to the second DSCM.
78 Connect Line B Out (port 5) of the XLA/RLA to the DSCM In port. If only one
DSCM, the DSCM you are connecting is the same as in step 76. If two
DSCMs, you are connecting the second DSCM. Ensure the correct fixed pad
is inserted in the connection as indicated in the EDP/IDP.
Go to step 81.
79 Connect Line A Out (port 7) of the line facing circuit pack to the Line A In (port
8) of the XLA/RLA.
80 Connect the Line B In (port 6) of the line facing circuit pack to the Line B Out
(port 5) of the XLA/RLA.
81 Select your next step.
If a DSCM module is Then go to
present step 82
not present step 87
Step Action
83 Connect the Line A Out (port 7) of the line facing circuit pack, or XLA if
present, to the DSCM In port. Ensure that the connection is made as
indicated in the EDP/IDP (DSCM in the correct slot). Ensure the correct fixed
pad is inserted in the connection as indicated in the EDP/IDP.
84 Connect the DSCM Out port to the Line A In (port 8) of the line circuit pack
(cascaded SLA). The DSCM you are connecting to is the same as in step 83.
85 Connect the Line A Out (port 7) of the line circuit pack (cascaded SLA) to the
Common IN port of the WSS. Ensure the correct fixed pad is inserted in the
connection as indicated in the EDP/IDP.
Go to step 88.
86 Connect the Line A In (port 8) of the line circuit pack (pre-amplifier) or RLA to
the DSCM Out port. Ensure that the connection is made as indicated in the
EDP/IDP (DSCM in the correct slot). Ensure the correct fixed pad is inserted
in the connection as indicated in the EDP/IDP.
87 Connect the Common In (port number depends on the WSS) of the WSS or
RLA (port 8) to the Line A Out (port 7) of the line facing circuit pack.
88 Connect the Common Out (port number depends on the WSS) of the WSS
or RLA (port 5) to the Line B In (port 6) of the line facing circuit pack.
Go to step 101.
89 See Figure 4-19 on page 4-49 for an example of intra-NE fibering at a
ROADM site with MLAx-ESAM configuration.
90 Select your next step.
If a DSCM module is Then go to
present between the ESAM and the MLAx step 91
not present step 97
91 Connect the Line A Out (port 7) of the ESAM circuit pack to the DSCM In port.
Ensure that the connection is made as indicated in the EDP/IDP (DSCM in
the correct slot). Ensure the correct fixed pad is inserted in the connection as
indicated in the EDP/IDP.
92 If applicable, connect the first DSCM to the second DSCM.
93 Connect the DSCM Out port to the Line A In (port 8) of the MLAx. If only one
DSCM, the DSCM you are connecting is the same as in step 91. If two
DSCMs, you are connecting the second DSCM. Ensure the correct fixed pad
is inserted in the connection as indicated in the EDP/IDP.
94 Connect Line B In (port 6) of the ESAM to the DSCM Out port. Ensure that
the connection is made as indicated in the EDP/IDP (DSCM in the correct
slot). Ensure the correct fixed pad is inserted in the connection as indicated
in the EDP/IDP.
Step Action
102 Connect the Line B MON and Line A MON ports of:
• the line facing circuit pack, or
• the XLA if present, or
• the MLAx in ESAM-MLAx ROADM configurations
To avoid misfibering, ensure that the patch cords are correctly labeled.
Go to step 104.
Step Action
to the monitor ports of the 2-port OPM (port 1 and port 2) as indicated in the
EDP/IDP.
To avoid misfibering, ensure that the patch cords are correctly labeled.
104 Repeat step 71 to step 103 for all ROADM/DGFF OTSs at the site.
Connecting WSS to WSS
105 Connect the Switch In port of the WSS or RLA at one end of the fiber
connection for the pass-through channel to the Switch Out port of the WSS
or Demux Out port of the RLA at the other end of the fiber connection, as
indicated in the EDP/IDP.
106 Connect the Switch Out port of the WSS or Demux Out port of the RLA at one
end of the fiber connection for the pass-through channel to the Switch In port
of the WSS or RLA at the other end of the fiber connection, as indicated in
the EDP/IDP.
107 Repeat step 105 and step 106 for all the fiber connections required for
pass-through channels at the same site.
108 Select your next step.
If the site Then
has no channel access (DGFF site) you have completed
this procedure
is a ROADM site with CMD44 access go to step 109
is a ROADM site with CCMD12 access go to step 144
is a ROADM with a low channel count DIA go to step 157
Step Action
Step Action
Connecting CMD44 to BMD2 to WSS (WSS 50 GHz w/OPM 9x1/WSS Flex C-Band w/OPM 9x1 not
supported with BMD2) or RLA
112 Connect the common Out (port 90) of the CMD44 to input port of BMD2
(either 3 or 5) as indicated in the EDP/IDP. If another CMD44 is present,
connect that to the other input port of BMD2. See Figure 4-20 on page 4-50.
113 Connect the common In (port 89) of the CMD44 to corresponding Output port
of BMD2 (either 4 or 6) as indicated in the EDP/IDP.
114 Connect the common Out of BMD2 (port 2) to Switch In port (or Add In port
for NTK553KA) of WSS or RLA as indicated in the EDP/IDP. For RLA, SW5
(Switch 5 In, port 29) is recommended.
115 Connect the common In of BMD2 (port 1) to Switch Out port (or Drop Out port
for NTK553KA) of WSS or RLA as indicated in the EDP/IDP. For RLA, SW5
(Switch 5 Out, port 30) is recommended.
Go to step 134.
Connecting CMD44 to BMD2 to SLA (Drop LIM) to WSS (WSS 50 GHz w/OPM 9x1/WSS Flex C-Band
w/OPM 9x1 not supported with Drop LIM or BMD2)
116 Connect the common Out (port 90) of the CMD44 to input port of BMD2
(either 3 or 5) as indicated in the EDP/IDP. If another CMD44 is present,
connect that to the other input port of BMD2. See Figure 4-21 on page 4-51.
117 Connect the common In (port 89) of the CMD44 to corresponding Output port
of BMD2 (either 4 or 6) as indicated in the EDP/IDP.
118 Connect the common Out of BMD2 (port 2) to the Line B In (port 6) of the SLA
circuit pack.
119 Connect the common In of BMD2 (port 1) to the Line A Out (port 7) of the SLA
circuit pack.
120 Connect the Line B Out (port 5) of the SLA circuit pack to the Switch In port
(or Add In port for NTK553KA) of WSS as indicated in the EDP/IDP.
121 Connect the Line A In (port 8) of the SLA circuit pack to the Switch Out port
(or Drop Out port for NTK553KA) of WSS as indicated in the EDP/IDP.
Go to step 134.
Connecting CMD44 to WSS or RLA
122 Connect the Common Out (port 90) of the CMD44 to the Switch In port (or
Add In port for NTK553KA) of the WSS or RLA as indicated in the EDP/IDP.
See Figure 4-8 on page 4-39. For RLA, SW5 (Switch 5 In, port 29) is
recommended.
Step Action
123 Connect the Common In (port 89) of the CMD44 to the Switch Out port (or
Drop Out port for NTK553KA) of the WSS or RLA as indicated in the
EDP/IDP. For RLA, SW5 (Switch 5 Out, port 30) is recommended.
Note: The internal fibering between a 50 GHz CMD44 and WSS 50 GHz
w/OPM 9x1/WSS Flex C-Band w/OPM 9x1 can be done in the following
manner. The common In and Out of the 50 GHz CMD44 card can be
connected to the switch port 8 or switch port 9, that is, port numbers 17,18 or
port numbers 19, 20. Specifically for 50 GHz CMD44, the intra fibering from
50 GHz CMD44 to WSS 50 GHz w/OPM 9x1/WSS Flex C-Band w/OPM 9x1
is done on the corresponding ports. Pass through configuration is not allowed
on the switch ports 8 and 9 (that is, port numbers 17,18,19 and 20 for a WSS
50 GHz w/OPM 9x1/WSS Flex C-Band w/OPM 9x1).
Go to step 134.
Connecting CMD44 to SLA (Drop LIM) to WSS (WSS 50 GHz w/OPM 9x1/WSS Flex C-Band w/OPM
9x1 not supported with Drop LIM)
124 Connect the Common Out (port 90) of the CMD44 to the Line B In (port 6) of
the SLA circuit pack. See Figure 4-22 on page 4-52 for an example.
125 Connect the Common In (port 89) of the CMD44 to the Line A Out (port 7) of
the SLA circuit pack.
126 Connect the Line B Out (port 5) of the SLA circuit pack to the Switch In port
(or Add In port for NTK553KA) of the WSS as indicated in the EDP/IDP.
127 Connect the Line A In (port 8) of the SLA circuit pack to the Switch Out port
(or Drop Out port for NTK553KA) of the WSS as indicated in the EDP/IDP.
Go to step 134.
Connecting CMD44 to BMD2 to amplifier in DIA configuration
128 Connect the Common Out (port 90) of the CMD44 50 GHz to the Input of
BMD2 (either 3 or 5) as indicated in the EDP/IDP. If a second CMD44 50 GHz
is present, connect the second CMD44 50 GHz to the other input port of
BMD2. See Figure 4-24 on page 4-54 for an example.
129 Connect the Common In (port 89) of the CMD44 50 GHz module(s) to the
corresponding Output of BMD2 (either 4 or 6) as indicated in the EDP/IDP.
130 Connect the Common Out (port 2) of the BMD2 to Line A In (port 8) of the
amplifier circuit pack.
131 Connect the Common In (port 1) of BMD2 to Line B Out (port 5) of the
amplifier circuit pack.
Go to step 134.
Step Action
Step Action
Step Action
153 Repeat step 150 and step 152 for each connected CCMD12.
154 Connect the Common Out (port 10) of the SMD to Line A In (port 8) of the
amplifier circuit pack in the DIA OTS.
155 Connect the Common In (port 9) of the SMD to Line B Out (port 5) of the
amplifier circuit pack in the DIA OTS.
156 Repeat step 150 to step 155 for all COADM OTSs at the site.
Connecting intra-NE fibers for a low channel count DIA
157 See Figure 4-27 on page 4-57 to perform the steps for intra-NE fibering for a
low channel count DIA.
158 Connect the Common Out (port 26) of the CCMD12 to the Common In (port
21) of the WSS as indicated in the EDP/IDP.
159 Connect the Common In (port 25) of the CCMD12 to the Common Out (port
22) of the WSS as indicated in the EDP/IDP.
160 Connect the Monitor Out (port 27) of the CCMD12 to the Monitor 1 (port 1) of
the WSS as indicated in the EDP/IDP.
161 Repeat step 157 to step 160 for all low channel count DIA at the site
(maximum of two low channel count DIAs per site).
—end—
Figure 4-1
Intra-NE fiber connections at a Line amplifier site (single 2xOSC configuration)
WSC WSC
OSC OSC
2 1
OSC2 Out
OSC1 Out
OSC2 In
OSC1 In
2
2
1
1
MLA MLA
PEC: NTK552BA PEC: NTK552BA
Line B Mon Line B Mon
1 1
Line A Mon Line A Mon
2 2
OSC B In OSC B In
3 3
4 4
OSC A Out OSC A Out
Line A In Line A Out Line B In Line B Out
8 A 7 6 B 5
5 B Line B In
6 7 A 8
Line B Out Line A Out Line A In
Legend
= DSCM
= Attenuator
Figure 4-2
Intra-NE fiber connections at a Line amplifier site (dual 2xOSC configuration)
2 x OSC
2 x OSC
2 1 2 1
PEC: NTK554BA
PEC: NTK554BA
OSC OSC OSC OSC
2 1 2 1
OSC2 Out
OSC1 Out
OSC2 Out
OSC1 Out
OSC2 In
OSC1 In
OSC2 In
OSC1 In
2
2
1
1
2
2
1
1
SLA SLA
PEC: NTK552AA PEC: NTK552AA
Line B Mon Line B Mon
1 1
Line A Mon Line A Mon
2 2
OSC B In OSC B In
3 3
4 4
OSC A Out OSC A Out
Line A In Line A Out Line B In Line B Out
8 A 7 6 5
5
Line B In
6 7 A 8
Line B Out Line A Out Line A In
Legend
= DSCM
= Attenuator
Figure 4-3
Intra-NE fiber connections at a line amplifier site—example shows SRA – XLA – SRA (with and
without DSCMs)
Can be SRA/ESAM/SAM
Note: A 2-port OPM can be connected at the Mon 1 and Mon 2 ports of the XLA.
circuit pack
OTS2
With DSCMs
OTS1
Can be SRA/ESAM/SAM
circuit pack
Figure 4-4
Intra-NE fiber connections at a line amplifier site—ESAM - MLAx - ESAM (example shows MLA2)
Figure 4-5
Intra-NE fiber connections at a line amplifier site—ESAM - MLAx - MLAx - ESAM (example shows
MLA)
Figure 4-6
Intra-NE fiber connections at a line amplifier site—ESAM - MLAx - MLAx (example shows MLA)
Figure 4-7
Intra-NE fiber connections at a TOADM site
8
Line B Out
Line A In
MLA
Slot 13
A
B
Mon2(A Out)
Mon1(B Out)
OSC A Out
Line A Out
OSC B In
Line B In
Note 3: A 2-port OPM can be connected at the Mon 1 and Mon 2 ports of the line facing circuit pack.
4
6
B
3
7
2
1
2x OSC
OSC1 Out
WSC
1
OSC
3
1
OSC1 In SCMD4 Ch1 Out
4
OSC2 Out 3
2
WSC
OSC
Ch1 In
2
4
MUX / DEMUX
Ch2 Out
Note 2: Dual 2xOSC configuration shown. Single 2xOSC configuration is also supported.
OSC2 In
6
Common In
Slot 14 1 Ch2 In
5
2 Ch3 Out
Common Out 8
11
Upg In Ch3 In 7
12
Slot 12
Upg Out Ch4 Out
10
9
Ch4 In
Ch1 Out
SCMD4 4
3
Ch1 In
Note 1: The diagram within the dotted square represents a thin terminal.
MUX / DEMUX
Ch2 Out
6
Common In
5
1 Ch2 In
2 Ch3 Out
Common Out 8
11 7
Upg In Ch3 In
Slot 11
12
Upg Out Ch4 Out
10
9
Ch4 In
OTS
2
Ch4 Out
Slot 4
10
Upg In 9
Ch4 In
11
Upg Out Ch3 Out
12 8
Common In 7
1 Ch3 In
2 Ch2 Out
Common Out 6
5
Ch2 In
Ch1 Out
4
SCMD4 3
Ch1 In
Ch4 Out
Slot 3
10
Upg In 9
Ch4 In
11
Upg Out
MUX / DEMUX
Ch3 Out
12 8
Common In 7
1 Ch3 In
2 Ch2 Out
Common Out 6
5
2x OSC Ch2 In
Ch1 Out
OSC1 Out 4
1 SCMD4
WSC
OSC
3
3
1 Ch1 In
OSC1 In
OSC2 Out
2
WSC
OSC
4
2
OSC2 In
Slot 1
7
2
6
3
4
1
Mon1(B Out)
Mon2(A Out)
OSC A Out
OSC B In
Line A Out
Line B In
B
Slot 2
A
Line B Out
Line A In
MLA
OTS
1
5
8
2 1 2 1
Release 13.0
OSC OSC OSC OSC
2 1 2 1
OSC1 In
OSC1 In
OSC2 Out
OSC2 Out
OSC1 Out
OSC1 Out
OSC2 In
OSC2 In
2
2
1
1
2
2
1
1
Switch 7 In
Common Out Switch 8 In Common Out
12
13 Switch 8 In
Switch 9 In
13
Switch 9 In
LC LC
Ch 1 In CMD44 CMD44 Ch 1 In
PEC: NTT862AA PEC: NTT862AA
Ch 1 Out Ch 1 Out
LC LC
Ch 2 In LC LC Ch 2 In
Common Out 90 90 Common Out
Ch 2 Out Ch 2 Out
89 89
Common In Common In
LC LC
Ch 43 In Ch 43 In
Legend
Ch 43 Out Ch 43 Out
44 Channel MUX/DEMUX
44 Channel MUX/DEMUX
LC LC
= DSCM Ch 44 In Ch 44 In
June 2019
Commissioning and Testing
Photonic layer site testing procedures 4-39
Release 13.0
WSC WSC WSC WSC
2 1 2 1
OSC1 In
OSC1 In
OSC2 Out
OSC2 Out
OSC1 Out
OSC1 Out
OSC2 In
OSC2 In
3 3
4 4 4
OSC A Out OSC A Out 4 4 OSC A Out
Common In
Common In Switch 1 Out Switch 1 Out
Line A In Line A Out Line A In Line A Out 17
A 7 7 17 Switch 2 In Switch 2 In Line B In Line B Out
8 8 A 6 B 5
5 5
6 6
5 B 6 5 6 Switch 2 Out Switch 2 Out 7 A 8
Line B Out Line B In Line B Out Line B In Line A Out Line A In
Switch 3 In Switch 3 In
7 7 9:1
9:1
8 8
Switch 3 Out Switch 3 Out
Switch 4 In Switch 4 In
9 9
10 10
Switch 4 Out Switch 4 Out
1:5 1:5
Σ Switch 5 In Switch 5 In Σ
11 11
12 12
18 Switch 5 Out Switch 5 Out 18
Common Out Common Out
13 13
Switch 6 In Switch 6 In
14 14
Intra-NE fiber connections at a ROADM site with interior SLA
Switch 7 In Switch 7 In
15 15
Switch 8 In Switch 8 In
16 16
Switch 9 In Switch 9 In
LC LC
Ch 1 In CMD44 CMD44 Ch 1 In
PEC: NTT862AA PEC: NTT862AA
Ch 1 Out Ch 1 Out
LC LC
Ch 2 In LC LC Ch 2 In
Common Out 90 90 Common Out
Ch 2 Out Ch 2 Out
89 89
Common In Common In
LC LC
Ch 43 In Ch 43 In
Legend Ch 43 Out Ch 43 Out
44 Channel MUX/DEMUX
44 Channel MUX/DEMUX
LC LC
= DSCM Ch 44 In Ch 44 In
Ch 44 Out Ch 44 Out
= Attenuator
June 2019
Commissioning and Testing
323-1851-221 Standard Issue 3
Figure 4-10
Release 13.0
WSC WSC
4 3
OSC OSC
2 1
OSC1 In
OSC2 Out
OSC1 Out
OSC2 In
LC LC
Ch 1 In CMD44 CMD44 Ch 1 In
PEC: NTT862AA PEC: NTT862AA
Ch 1 Out Ch 1 Out
LC LC
Ch 2 In LC LC Ch 2 In
Common Out 90 90 Common Out
Ch 2 Out Ch 2 Out
89 89
Common In Common In
Intra-NE fiber connections at a ROADM site with single 2xOSC circuit pack
LC LC
Ch 43 In Ch 43 In
Legend Ch 43 Out Ch 43 Out
44 Channel MUX/DEMUX
44 Channel MUX/DEMUX
LC LC
= DSCM Ch 44 In Ch 44 In
Ch 44 Out Ch 44 Out
= Attenuator
June 2019
Commissioning and Testing
Photonic layer site testing procedures 4-41
Figure 4-11
Intra-NE fiber connections at a ROADM site (example shows XLA and SRA)
Note : An interior SLA is supported between the WSS and the XLA.
Figure 4-12
Intra-NE fiber connections at a ROADM site (CMD44 and CMD64)
Figure 4-13
Intra-NE fiber connections at a ROADM site using RLA/CMD64
Figure 4-14
Intra-NE fiber connections at a ROADM site using RLA/CMD44
Figure 4-15
Intra-NE fiber connections at a ROADM site using RLA/CMD64 with ESAM/SAM/SRA (SAM shown)
Figure 4-16
Intra-NE fiber connections at a ROADM site using RLA/CMD44 with ESAM/SAM/SRA (SRA shown)
Figure 4-17
Intra-NE fiber connections between a low channel count DIA and backbone OTS
Figure 4-18
Intra-NE fiber connections at a ROADM site with XLA and SRA - DSCM placement
Figure 4-19
Intra-NE fiber connections at a ROADM site with ESAM-MLAx (example shows MLA)
Figure 4-20
Intra-NE fiber connections (CMD44 to BMD2 to WSS)
1 Ch1 In
2
1530.33nm
LC
2xOSC PEC: NTK554BAE5
LC
Ch1 Out OSC1 Out OSC2 Out
Ch2 In 1 OSC OSC 2
44 Channel MUX / DEMUX
3
4
1530.72nm 1 1 2 2
Ch2 Out OSC1 In OSC2 In
Loc: Shelf: Slot:
Common Out
90
Common In 89
WSS 50 GHz
PEC: NTK553KC
85 Ch43 In
1546.92nm
MLA
86
Ch43 Out
PEC: NTK552BA
Ch44 In Monitor 1 Line B Mon
87 1 1
1547.32nm OPM
88
Ch44 Out BMD2 Monitor 2
2 2
Line A Mon
PEC: NTT862DA
3
Switch1 In Σ 1:2 Common Out
8
3
4
OSC B In
3 In
1548.11nm Output 2
4 6
Ch2 Out
Common Out
90
Note: NTK553KC shown. For NTK553KA,
ports 3 and 4 are Switch In/Demux Out, and
Common In 89 ports 5 and 6 are Add In/Drop Out.
85 Ch43 In
1564.68nm
86
Ch43 Out
87 Ch44 In
1565.09nm
88
Ch44 Out
Figure 4-21
Intra-NE fiber connections (CMD44 to BMD2 to SLA to WSS)
Release 13.0
1 OSC1 In 1 2 OSC2 In 2 MLA
Line B Mon
1
2
WSS 100 GHz 5x1 Line A Mon
OSC B In
Monitor 1 3
1
OPM Monitor 2 4
2 OSC A Out
4 Switch1 Out
Mon 2 (A Out)
OSC B In
3
Switch5 In 4
11 5:1 OSC A Out
Common In
12 Switch5 Out 17 Line B In Line B Out
6 5
7 8
Intra-NE fiber connections (CMD44 to Drop LIM to WSS)
A
Line A Out Line A In
Ch44 In 87
5 6
Line B Out Line B In
Ch44 Out 88
June 2019
Commissioning and Testing
323-1851-221 Standard Issue 3
Figure 4-23
Release 13.0
Backbone OTS 1 Backbone OTS 2
WSC WSC
WSC WSC 4 3
4 3
2x OSC
2x OSC
OSC OSC
OSC OSC 2 1
2 1
OSC2 In
OSC1 In
OSC2 Out
OSC1 Out
PEC: NTK554BA
OSC2 In
OSC1 In
OSC2 Out
OSC1 Out
1
1
2
2
1
1
2
2
WSS 100 GHz WSS 100 GHz
PEC: NTK553JA
PEC: NTK553JA
MLA
PEC: NTK552BA 6500 Monitor 1 MLA
Monitor 1 1
Mon 1 (B Out) 1 OPM Monitor 2 6500 PEC: NTK552BA
DIA OTS
Common In
LC Ch 43 In Switch2 Out 6
85 5 B 6 Common Out
Line B Out Line B In 18 Switch2 In
2:1 5
86
June 2019
Commissioning and Testing
Photonic layer site testing procedures 4-53
2x OSC
Figure 4-24
2x OSC
Release 13.0
OSC OSC OSC OSC
2 1 2 1
PEC: NTK554BA
PEC: NTK554BA
OSC2 In
OSC1 In
OSC2 In
OSC1 In
OSC2 Out
OSC1 Out
OSC2 Out
OSC1 Out
1
1
2
2
WSS 50 GHz
1
1
2
2
WSS 50 GHz
PEC: NTK553FA/FC/LA PEC: NTK553FA/FC/LA
MLA MLA
6500 Monitor 1 Monitor 1 6500
PEC: NTK552BA 1 1 PEC: NTK552BA
Mon 1 (B Out) Monitor 2 OPM OPM Monitor 2 Mon 1 (B Out)
1 2 2 1
2 2
Mon 2 (A Out) Switch1 Out 4 Switch1 In Mon 2 (A Out)
3
OSC B In Switch1 In 3 Switch1 Out OSC B In
3 4 3
4 Switch2 Out 6 Switch2 In 4
Common In 5 Common Out OSC A Out
OSC A Out 21 Switch2 In Switch2 Out 22
5 6
Line A In Line A Out Line B In Line B Out
8 A 7 6 B 5
9x1
9x1
Switch3 In 7 Switch3 Out
8
5 B 6 7 A 8
Line B Out Line B In Switch4 Out Switch4 In Line A Out Line A In
10 9
WSS 50 GHz
WSS 50 GHz
Switch4 In 9 Switch4 Out
10
Switch5 Out 12 Switch5 In
11
Switch5 In 11 Switch5 Out
12
Switch6 Out 14 Switch6 In
13
1: 9 Switch6 In 13 14 Switch6 Out 1: 9
Common Out Switch7 Out 16 Switch7 In Common In
22 15
21
Switch7 In 15 Switch7 Out
16
9:1 9:1
DIA OTS
CMD44 50GHz Blue Can also be NTK553KC
PEC: NTT862BA
Slot: 84
1 Ch1 In
1530.33nm
2
Ch1 Out WSS 50 GHz
3 Ch2 In
1530.72nm
PEC: NTK553FA/FC/LA
4
Ch2 Out
MLA Monitor 1
Common Out 90 1
PEC: NTK552BA 6500 Monitor 2 OPM
Intra-NE fiber connections between a 50 GHz DIA and backbone OTS
2
Mon 1 (B Out)
Common In 89 1
BMD2 Switch1 Out 4
2
PEC: NTT862DA Mon 2 (A Out) Switch1 In 3
85 Ch43 In OSC B In
1546.92nm 3 Switch2 Out
Common In 6
86 3 Input 1
21
Switch3 In 7
5
Input 2
Common 5 B 6 Switch4 Out 10
WSS 50 GHz
June 2019
Commissioning and Testing
323-1851-221 Standard Issue 3
Figure 4-25
Release 13.0
6500
Ch 01 Out
2
Ch 01 In
1
Ch 02 Out
4
Ch 02 In
Σ 12:1
3
COADM OTS
Ch 03 Out
6 Monitor Out
Ch 03 In 27
5
DIA OADM OTS
Ch 04 Out
8
Ch 04 In
7
CCMD12
13 Ch 07 In
Monitor 1
Ch 08 Out 1
16 Monitor 2 OPM
Ch 08 In 2
15 MLA
Ch 09 Out Switch1 Out
18 PEC: NTK552BA 4
Switch1 In
CCMD12
Ch 09 In Mon 1 (B Out) 3
17
LB In
Ch 10 Out 2 Common In 6
20
25
Switch8 In Mon 2 (A Out) 21 Switch2 In
Ch 10 In 5
PEC: NTK508FA
19
26
OSC B In
3
Switch8 Out
Ch 11 Out Switch3 Out
50 GHz SMD
8
2:8
23
22 4
9x1
Switch7 In
OSC A Out Switch3 In
Common In
7
LB Out
Ch 11 In 24
21
PEC: NTK553GA
Switch7 Out 9 Line A In Line A Out
Ch 12 Out 8 A 7 Switch4 Out
10
WSS 50 GHz
24
21
Switch6 In
Switch4 In
Σ 1:12
Ch 12 In 9
23
22 10
OPM
14
Common Out
17
Intra-NE fiber connections at a Colorless OADM site
Switch4 In
Switch6 In
18 13
Dual-WSS
Switch4 Out Σ 1:9
50 GHz 1x8
Common Out Switch7 Out
8 16
22
Up to 8 CCMD12s
15 Monitor 8
Switch7 In
Switch3 In
Ch 01 Out 15
2 16 7
Switch3 Out Monitor 7
Ch 01 In
1
6
13 Monitor 6
Ch 02 Out
Switch2 In 5 9:1
4 Monitor 5
14 Switch8 Out (Drop1)
Ch 02 In
Switch2 Out 18
Σ 12:1
4
3 Monitor 4
8:2
Switch8 In (Add1)
17
11
Ch 03 Out Switch1 In 3
6 Monitor Out 12
Monitor 3
Ch 03 In 27 Switch1 Out 2 Switch9 Out (Drop2)
5
Monitor 2 20
Ch 04 Out
1 Switch9 In (Add2)
Monitor 1 19
8
Ch 04 In
7
Ch 05 Out
10
Ch 05 In
9
Ch 06 Out
12 Common In
Ch 06 In 25
11
Ch 07 Out Common Out
14 26
CCMD12
13 Ch 07 In
Ch 08 Out
16
Ch 08 In
15
Ch 09 Out
18
CCMD12
Ch 09 In
17
Ch 10 Out
20
Ch 10 In
PEC: NTK508FA
19
Ch 11 Out
22
Ch 11 In
21
Ch 12 Out
24
Σ 1:12
Ch 12 In
23
Colorless Channel Mux Demux
June 2019
Commissioning and Testing
Photonic layer site testing procedures 4-55
Figure 4-26
Intra-NE fiber connections at a Colorless OADM site with CMD44 50GHz
Figure 4-27
Intra-NE fiber connections at a low channel count DIA site (non-OTS equipment)
Figure 4-28
Intra-NE fiber connections at a CDC ROADM site (CCMD8x16)
Figure 4-29
Intra-NE fiber connections at a CDC ROADM site (CCMD8x16 and CMD44 50 GHz)
Figure 4-30
Intra-NE fiber connections at a CDC ROADM site (CCMD8x16 and CMD44 100 GHz)
Release 13.0
OSC OSC OSC OSC
2 1 2 1
OSC1 In
OSC1 In
OSC2 Out
OSC2 Out
OSC1 Out
OSC1 Out
OSC2 In
OSC2 In
2
2
1
1
2
2
1
1
5 5
6 6
5 B 6 Switch 2 Out Switch 2 Out 7 A 8
Line B Out Line B In Line A Out Line A In
7 7 9:1
Switch 3 In Switch 3 In
8
Switch 4 In 8
9 Switch 4 In
Switch 5 In 9
10 Switch 5 In
1:5 Switch 6 In
1:5
10
Σ 11
Σ
Switch 6 In
Switch 7 In
11
18 12 18
Switch 7 In
Common Out Switch 8 In Common Out
12
13 Switch 8 In
Switch 9 In
13
Switch 9 In
Legend
= DSCM
= Attenuator
June 2019
Commissioning and Testing
Photonic layer site testing procedures 4-61
Figure 4-32
Intra-NE fiber connections at a DGFF site (RLA)
Figure 4-33
Intra-NE fiber connections at a DGFF site (RLA with SAM/ESAM/SRA)
Procedure 4-2
Adding a new CMD44, CMD64, or BMD2
Use this procedure to add a new 100GHz CMD44/eCMD44, 50GHz CMD44,
CMD64, or Broadband Mux/Demux (BMD2). For more information about the
CMD44 and BMD2 modules, refer to Common Equipment, 323-1851-102.1.
If a shelf is equipped with an access panel that supports external slots and a
shelf processor that supports interfacing with external slots, a CMD44,
CMD64, or BMD2 module is automatically provisioned to the external slot
when physically connected to the access panel. The external slot numbers
depend on the shelf type and SP type. Refer to Common Equipment,
323-1851-102.1. Otherwise, you must manually provision the CMD44,
CMD64, or BMD2 module to one of the virtual slots. The virtual slots are: slots
29 to 32 on a 2-slot shelf (NTK503MAE5/NAE5 variants), slots 91 to 99 on a
2-slot (NTK503LA variant), 6500-7 packet-optical, 7-slot, or 14-slot shelf, and
slots 63 to 82 on a 32-slot shelf. The virtual slots are always available whether
the access panel supports external slots or not.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Prerequisites
• You require an optical power meter.
• You require an LC to LC patch cord.
• You require RJ-45 straight-through cables NTTC09BME6 (to connect
CMD44, CMD64, or BMD2 modules to the access panel)
• You require a user account with a UPC level of 3 or higher.
• Make sure that the power and wavelength have been provisioned on the
transmitter that you are testing with.
Step Action
Step Action
13 Use a power meter and measure the power level at the Common Out port of
the BMD2 (port 2).
Record this value.
Step Action
14 Calculate the loss between the Channel In port and the Common Out port of
the BMD2 using the values recorded in step 7, step 10 and in step 13. If the
loss is greater than 10.8 dB (with 50GHz CMD44), clean and verify all optical
patch fibers and connectors. If you are unable to increase the power, contact
your next level of support to determine if any components require
replacement.
15 Place a loopback between the:
• Common Out (port 90) and the Common In (port 89) of the CMD44
or
• Common Out (port 130) and the Common In (port 129) of the CMD64
or
• if a BMD2 is present, place a loopback between Common Out (port 2)
and the Common In (port 1) of the BMD2 using an LC to LC patch cord.
16 Using a power meter, measure the power present on the CMD44, CMD64, or
BMD2 output port that corresponds to the wavelength being tested.
17 Select your next step.
If Then go to
BMD2 present step 18
otherwise step 20
18 Calculate the loss between the BMD2 common input and the BMD2 output
port.
19 If the measured loss is higher than 3.8 dB, try to fix the problem by cleaning
and inspecting the optical connectors. If this is not sufficient, replace the
BMD2. Refer to the appropriate procedure in Fault Management - Module
Replacement, 323-1851-545.
20 Calculate the loss between the common input and the CMD44 or CMD64
channel output port.
21 If the loss is greater than 6 dB (for 100GHz CMD44 only), or 6.6 dB (for
100GHz eCMD44), 7 dB (for 50GHz CMD44 only), 7.5 dB (for 50GHz
eCMD44 only), 7.1 dB (for CMD64 only), 10.5dB (for 50GHz CMD44 and
BMD2), or 11 dB (for 50GHz eCMD44 and BMD2), try to fix the problem by
cleaning and inspecting the optical connectors. If this is not sufficient, replace
the module. Refer to the appropriate procedure in Fault Management -
Module Replacement, 323-1851-545.
22 Remove the optical patch cord between the Common Out and the Common
In ports.
23 Disconnect the transmitter from the CMD44 or CMD64 port.
—end—
Procedure 4-3
Adding a new OMD4 or OMX
Use this procedure to add a new OMD4 or OMX. For more information about
the OMD4 and OMX modules, refer to Common Equipment, 323-1851-102.1.
If a shelf is equipped with an access panel that supports external slots and a
shelf processor that supports interfacing with external slots, an OMD4 or OMX
module is automatically provisioned to the external slot when physically
connected to the access panel. The external slot numbers depend on the shelf
type and SP type. Refer to Common Equipment, 323-1851-102.1. Otherwise,
you must manually provision the OMD4 or OMX module to one of the virtual
slots. The virtual slots are: slots 29 to 32 on a 2-slot shelf
(NTK503MAE5/NAE5 variants), slots 91 to 99 on a 2-slot (NTK503LA variant),
6500-7 packet-optical, 7-slot, or 14-slot shelf, and slots 63 to 82 on a 32-slot
shelf. The virtual slots are always available whether the access panel supports
external slots or not.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Prerequisites
• You require an optical power meter.
• You require an LC to LC patch cord for OMD4, or an SC to SC or LC to SC
patch cord for OMX.
• You require a user account with a UPC level of 3 or higher.
Step Action
Step Action
11 Calculate the loss between the Channel In port and the Common Out/OTS
Out port using the values recorded in step 7 and in step 10. If the loss is
greater than 2.5 dB for OMD4 or the Max Mux loss in Table 4-2 on page 4-71
for OMX, clean and verify all optical patch fibers and connectors. If you are
unable to increase the power, contact your next level of support to determine
if any components require replacement.
12 Place a loopback between the Common Out/OTS Out (port 2) and the
Common In/OTS In (port 1) of the OMD4/OMX using an LC to LC patch cord
for OMD4 or an SC to SC patch cord for OMX.
13 Using a power meter, measure the power present on the OMD4/OMX output
port that corresponds to the wavelength being tested.
14 Calculate the loss between the common input and the OMD4/OMX channel
output port.
15 If the loss is greater than 2.5 dB for OMD4 or the Max Demux loss in Table
4-2 on page 4-71 for OMX, try to fix the problem by cleaning and inspecting
the optical connectors. If this is not sufficient, replace the module. Refer to the
appropriate procedure in Fault Management - Module Replacement,
323-1851-545.
16 Remove the optical patch cord between port 2 and port 1.
17 Disconnect the transmitter from the OMD4/OMX.
18 Select one of the transmitters to be connected to the Upgrade/THRU port of
the OMD4/OMX. Use a power meter or the power monitoring function (if
available) on the subtending transmitting equipment to determine the
transmitter power (record the transmitter power).
19 Connect the transmitter to the Upgrade/THRU In port of the OMD4/OMX
(port 11 on OMD4 and 4-channel OMX, port 35 on 16-channel OMX).
20 Ensure that this is the only transmitter connected to the OMD4/OMX. All other
transmitters must be disconnected from the OMD4/OMX.
21 Use a power meter and measure the power level at the Common Out/OTS
Out (port 2) of the OMD4/OMX. Record this value.
22 Calculate the loss between the Upgrade/THRU In port and the Common Out
port using the values recorded in step 18 and in step 21. If the loss is greater
than 1.1 dB for OMD4 or the Max Pass-through/upgrade loss in Table 4-2 on
page 4-71 for OMX, clean and verify all optical patch fibers and connectors.
If you are unable to increase the power, contact your next level of support to
determine if any components require replacement.
23 Place a loopback between the Common Out/OTS Out (port 2) and the
Common In/OTS In (port 1) of the OMD4/OMX using an LC to LC patch cord
for OMD4 or an SC to SC patch cord for OMX.
Step Action
Table 4-2
OMX maximum dB loss
Procedure 4-4
Adding a new SCMD4
Use this procedure to add and test a new SCMD4 to an existing 6500
Packet-Optical Platform network.
CAUTION
Risk of service interruption
When a new SCMD4 is added to a thin OADM site, traffic
passing through the thin OADM site will be lost when the
upgrade ports are rerouted.
Prerequisites
• You require an optical power meter.
• You require an LC to LC patch cord.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Step Action
1 Insert the new SCMD4 into the shelf. Equipment and facilities will
auto-provision if auto-equipping is enabled.
Step Action
Step Action
16 Calculate the loss between the common input and the SCMD4 channel
output port.
17 If the measured loss is higher than 5.4 dB, try to fix the problem by cleaning
and inspecting the optical connectors and optical patch fibers. If this is not
sufficient, replace the SCMD4. Refer to the appropriate procedure in Fault
Management - Module Replacement, 323-1851-545.
18 Remove the optical patch cord between the Common Out and the Common
In ports.
19 Disconnect the transmitter from the SCMD4 port.
20 Reset the Target Loss of the ingress VOA of the tested wavelength to 15 dB.
21 Reset the Target Loss of the demux VOA back to 15 dB. The demux VOA is
located on port 1.
Connecting the new SCMD4 to other equipment
22 Optically connect the SCMD4 to other equipment as indicated in the
EDP/IDP.
CAUTION
Risk of service interruption
If the SCMD4 is being added at a Thin OADM node,
traffic passing through the node will be lost when the
upgrade ports are rerouted. If the SCMD4 is being
added at a Thin Terminal or a Thin OADM node, traffic
dropping at the node may be lost when the upgrade
ports are rerouted.
23 Edit the OTS to include the new SCMD4. Refer to the “Editing an OTS
instance” procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310. For a Thin OADM node, edit both OTSs.
24 Provision the SCMD4 Cascading Order according to the EDP/IDP. For
details, see the “Provisioning the SCMD cascading order” procedure in Part 2
of Configuration - Provisioning and Operating, 323-1851-310.
Step Action
25 For a thin OADM node, edit the inter-OTS adjacencies for the pass-through
traffic if the configuration has changed.
• Select Configuration -> Equipment & Facility Provisioning.
• In the Equipment table, select the innermost SCMD4 (the one furthest
from the line facing circuit pack), or the line-facing circuit pack if the
SCMD4 cascade is empty (no SCMD4).
• Select ADJ in the Facility Type drop down list.
• Select the adjacency that corresponds to the port where the
pass-through traffic is handed off to the other OTS.
This port is the Upgrade Out (port 12) of the innermost SCMD4 or Line A
OUT (port 7) of the line-facing circuit pack if the SCMD4 cascade is
empty (no SCMD4).
Note: Adjacency format = ADJ-<shelf>-<slot>-<port>
• Click Edit in the Facility area.
• Set the Adjacency type to CMD (if the other OTS SCMD4 cascade is not
empty) or LIM (if the other OTS SCMD4 cascade is empty).
• Enter the Expected Far End Address and the Expected Far End Address
Format as described in the EDP/IDP.
The Expected Far End Address must point to the input port of the
innermost SCMD4 of the other OTS (port 11) or to the Line B In (port 6)
of the line-facing circuit pack of the other OTS if its SCMD4 cascade is
empty (no SCMD4).
• Click OK.
• Repeat the above substeps for the other OTS.
26 At each of the 2 DOC nodes controlling the channels passing through or
add/drop at the node where the SCMD4 was added, perform a DOC
re-optimization followed by a DOC reset TCA baseline operation. Refer to the
“Re-optimizing channels” and “Resetting TCA baselines” procedures in
Part 2 of Configuration - Provisioning and Operating, 323-1851-310.
—end—
Procedure 4-5
Adding a new CCMD12
Use this procedure to add and test a new CCMD12 to an existing 6500
Packet-Optical Platform network.
Note: This procedure does not apply to low channel count DIA ROADM
configurations (only one CCMD12 is supported per DIA).
Prerequisites
• You require an optical power meter.
• You require an LC to LC patch cord.
• You must know how to retrieve performance monitoring data. Refer to the
“Retrieving performance monitoring data” procedure in Fault Management
- Performance Monitoring, 323-1851-520.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Step Action
1 Insert the new CCMD12 into the shelf. Equipment and facilities will
auto-provision if auto-equipping is enabled.
Testing the new CCMD12
2 Select one of the transmitters to be connected to the new CCMD12. Edit the
OTMn facility of the transmitter to set the Tx power to maximum and Tx
wavelength to 1550.12 nm.
Step Action
Step Action
13 Connect the CCMD12 Common In port to the corresponding Switch Out port
of the SMD as indicated in the EDP/IDP.
14 Connect the CCMD12 Monitor Out port to the corresponding Monitor port of
the SMD as indicated in the EDP/IDP.
15 Edit the OTS to include the new CCMD12. Refer to the “Editing an OTS
instance” procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310.
16 Disconnect the transmitter and receiver from the CCMD12 Ch In and Ch Out
ports.
17 Edit the OTMn facility of the transmitter to set the Tx power to its default value
and Tx wavelength to 0 nm.
—end—
Procedure 4-6
Adding a new CCMD8x16 or a CXM C-Band Type 1
Use this procedure to add and test a new CCMD8x16 or a CXM to an existing
6500 Packet-Optical Platform network. For more information about the
CCMD8x16 and the CXM C-Band Type 1, refer to Photonics Equipment,
323-1851-102.6.
The CCMD8x16 and the CXM are connected to Fiber Interconnect Modules
(FIM). Keep in mind the following information regarding the FIMs. For more
information, see the Photonic passive modules table in Planning - Ordering
Information, 323-1851-151.
• FIM Type 1 is shipped with the following equipment pre-installed:
— dust caps on MPO ports 1 to 4 (WSS1)
— MPO Loopback (APC, SM, 12 Fiber) modules in all the other MPO port
positions
— Duplex LC Loopback (SM) modules in each of the duplex LC
connector positions
Prerequisites
If you are adding a CXM C-Band Type 1 and want to test the MPO cable
between the CCMD8x16 UPG CXM port and the CXM C-Band Type 1 UPG
CCMD port, you must use a transponder.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Step Action
1 Make sure there are no Cable Trace Compromised alarms, Adjacency Far
End Not Discovered alarms or Adjacency Mismatch alarms in the TID where
you are installing the new CCMD8x16 or the CXM C-Band Type 1. See Fault
Management - Alarm Clearing, 323-1851-543 for the procedures on how to
clear the respective alarms.
2 Insert the new equipment:
• CCMD8x16 into the shelf (see the procedure on inserting or removing
circuit packs in the Installation technical publication specific to the
respective 6500 shelf type)
• CXM C-Band Type 1 into the host CCMD8x16 circuit pack (see the
procedure on installing and removing pluggable modules in the
Installation technical publication specific to the respective 6500 shelf
type)
Step Action
The CDC equipment uses MPO cables and connectors. For steps to:
• connect MPO cables, see the Installation technical publication specific to
the respective 6500 shelf type (in the procedure on routing fiber-optic
cables and electrical cables to circuit packs in the 6500 shelf)
• inspect and clean MPO connectors, see Installation - General
Information, 323-1851-201.0
CAUTION
Risk of affecting performance
You must inspect and clean the MPO connectors after
removing the MPO cable from its original packaging or
if the MPO cable has been removed from the faceplate
for any reason.
5 If you are adding a CXM C-Band Type 1, connect the jumper cable between
the UPG CXM port on the CCMD8x16 and the UPG CCMD port on the CXM.
6 Make sure there are no Adjacency Far End Not Discovered alarms or
Adjacency Mismatch alarms. See Fault Management - Alarm Clearing,
323-1851-543 for the procedures on how to clear the respective alarms.
7 After the last fibering has been completed and the TID slot sequence has
been completed, if the Dark Fiber Loss Management system parameter is
enabled in the Node Information tab of Site Manager, the network element
starts verifying all the subfibers within the MPO ports automatically. (For
details on setting the parameter, see the procedure on editing the nodal
system parameters in Administration and Security, 323-1851-301.)
Make sure that you wait for approximately 5 minutes after the last fibering was
completed.
8 In Site Manager, display the connection validation results under the Validation
Summary tab.
Step Action
9 If any of the subfibers within the MPO cables is dirty or bent, a High Fiber
Loss error is displayed. Disconnect the cable, clean and inspect the
connectors, then reconnect the cable. Replace the cable, if necessary. Note
that the root cause of the High Fiber Loss alarm on a given adjacency port
can include the near end fiber, far end fiber, loopback connector, or the FIM.
For details, see Fault Management - Alarm Clearing, 323-1851-543.
10 If there is a problem with a loopback connector, in Site Manager select
Configuration, then Shelf Level View, then right-click on the MPO port and
select Show Fiber Topology to determine which loopback connector.
Disconnect the loopback, clean and inspect the connectors, then reconnect
the loopback.
11 Select your next step.
If you have added Then
a new CCMD8x16 you have completed this
procedure
a CXM C-Band Type 1 and you want to go to step 12
test the jumper MPO subfibers between
ports 34 and 35 of the CCMD8x16
12 If the configuration is set up with ROADM OTSs and you want to test the
jumper MPO subfibers between ports 34 and 35 of the CCMD8x16, you will
use a transponder. Select one of the transponders to be connected to the new
CCMD8x16.
13 Connect the transmitter to the appropriate CCMD8x16 In port per the
EDP/IDP and connect the receiver to the appropriate CCMD8x16 Out port
per the EDP/IDP.
Ensure that this is the only transmitter and receiver pair connected to the
CCMD8x16. All other transmitters and receivers must be disconnected from
the CCMD8x16.
14 Perform a manual loopback test to exercise the jumper subfibers. See the
procedure on performing optical loopback testing in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310. If the test fails, disconnect the
cable, clean and inspect the connectors, then reconnect the cable. Replace
the cable, if necessary.
—end—
Procedure 4-7
Testing ROADM channel access continuity
Use this procedure to test channel access continuity on a WSS based node
where light from transmitting subtending equipment is available. This test
verifies the optical continuity and checks for reflection-related problems. This
procedure does not optimize the channels for traffic.
See “Testing a CDC ROADM configuration” on page 4-111 for CDC ROADM
sites and “Testing DGFF nodes” on page 4-247 for DGFF site testing.
Prerequisites
• This procedure allows you to perform optical continuity testing through all
the equipment associated with one ROADM OTS. Full traffic continuity
testing can proceed only after the system is complete. It is recommended
that you perform the continuity test with at least one service layer source
for each installed CMD.
Note: The ROADM OTS must be defined before performing this
procedure.
Step Action
• The fibers that are used in the following steps to connect to subtending
client equipment must be verified to be in good working order prior to use.
It is very important that client fibers are cleaned and scoped prior to being
connected. See Installation - General Information, 323-1851-201.0, for the
cleaning and inspection procedures.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Figure 4-34
Overview of ROADM channel access continuity testing and fibering steps (configuration uses
LIM)
Dir. 1
OPM connections
17 20
24
B 28 A
12
A 32 B
18
2 Dir. 2
39
36
BMD2 OR BS5 DIA OR DIA
COADM
Power 10 35
meter
Tx Rx Tx Rx
Tx Rx
Figure 4-35
Overview of ROADM channel access continuity testing and fibering steps (configuration uses
SRA/ESAM/SAM+XLA)
Dir. 1
OPM connections
19 20
24
B B 28 A B
12
A A 32 A
B
19
2
29
BMD2 OR BS5 DIA OR DIA
36 Dir. 2
COADM
Power 10 35
meter
Tx Rx Tx Rx
Tx Rx
Figure 4-36
Overview of ROADM channel access continuity testing and fibering steps (configuration uses
ESAM+MLAx)
Figure 4-37
Overview of ROADM channel access continuity testing and fibering steps (configuration uses
RLA)
Dir. 1
20
OPM
connections
19 24
B 38 A
12
A 32 B
19
2
29
Dir. 2
36
Power 10 35
meter
Tx Rx
Figure 4-38
Overview of ROADM channel access continuity testing and fibering steps (configuration uses
RLA and ESAM/SAM/SRA)
Dir. 1
19
B B 28 A B
12
A A 33 A
B
19
2
29
37 Dir. 2
Power 10 36
meter
Tx Rx
Step Action
Step Action
5 Calculate the coupler loss for the line facing circuit pack:
Coupler loss = <OSC output power (dBm) read in step 3> - <OSC Out power
(dBm) read in step 4>
The calculated coupler loss should be less than 5 dB (SRA) or 3.5 dB (other
line facing circuit packs).
If the OSC or loopback fibers are dirty, crossed or pinched, the calculated
coupler loss will be much greater than 5 dB (SRA) or 3.5 dB (other line facing
circuit packs). You must rectify the situation before you continue.
6 Using an optical power meter, measure the power going to the OSC In port
from the OSC Out (port 4). This value should be roughly the same as the
power read in step 4.
7 Remove the loopback you put in step 2.
8 Repeat step 2 to step 7 for the other OSC-1 (dual 2xOSC configuration) or
the OSC-2 (single 2xOSC configuration).
Setting up for the testing
9 See the following figures for examples of ROADM node testing. Labeled
numbers in these figures identify the steps to follow.
• Figure 4-34 on page 4-85 - configuration uses LIM
• Figure 4-35 on page 4-85 - configuration uses SRA/ESAM/SAM+XLA
• Figure 4-36 on page 4-86 - configuration uses ESAM+MLAx
• Figure 4-37 on page 4-86 - configuration uses RLA
• Figure 4-38 on page 4-87 - configuration uses RLA + SRA/ESAM/SAM
Step Action
Step Action
Step Action
17 If the line facing circuit pack is an MLA, MLA2, MLA2 w/VOA, or MLA3,
perform this step on the line facing circuit pack.
If your configuration uses ESAM-MLAx, perform this step on the MLAx.
a. Edit the Line B AMP facility (AMP-<shelf>-<slot>-6) to set the target gain
to 17 dB:
— In the Equipment & Facility Provisioning application, select the
appropriate photonic shelf from the Shelf drop-down list and select
the LIM in the equipment table.
— Select AMP from the Facility Type drop-down list and select
AMP-<shelf>-<slot>-6 in the facility table.
— Click Edit.
— In the Edit AMP facility dialog, enter 17.00 in the Target Gain field
then click OK.
b. Verify the ORL at Line B output:
— In the Performance Monitoring application, select the appropriate
photonic shelf from the Shelf drop-down list.
— For non-MLA2 w/VOA, select the AMP Type and the facility
AMP-<shelf>-<slot>-6 from the Facility drop down list.
— For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-5 from the Facility drop down list.
— Click Start Monitoring.
— In the PM table, read the Untimed ORL-OTS value.
— If the value is lower than 28 dB, clean all the optical connections from
the Line B output port to the input of the pad. When DSCMs are used
and the DSCM location is at the head end of the span (collocated with
the amplifier being commissioned), the minimum ORL threshold to
meet or exceed is 24 dB.
Step Action
18 If the line facing circuit pack is an MLA, MLA2, MLA2 w/VOA, MLA3, or an
SLA, perform this step on the line facing circuit pack.
If your configuration uses ESAM-MLAx, perform this step on the MLAx.
a. Edit the Line A AMP facility (AMP-<shelf>-<slot>-8) to set the target gain
to 20 dB:
— In the Equipment & Facility Provisioning application, select the
appropriate photonic shelf from the Shelf drop-down list and select
the LIM in the equipment table.
— Select AMP from the Facility Type drop-down list and select
AMP-<shelf>-<slot>-8 in the facility table.
— Click Edit.
— In the Edit AMP facility dialog, enter 20.00 in the Target Gain field
then click OK.
b. Verify the ORL at Line A output:
— In the Performance Monitoring application, select the appropriate
photonic shelf from the Shelf drop-down list.
— For non-MLA2 w/VOA, select the AMP Type and the facility
AMP-<shelf>-<slot>-8 from the Facility drop down list.
— For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-7 from the Facility drop down list.
— Click Start Monitoring.
— In the PM table, read the Untimed ORL-OTS value.
— If the value is lower than 28 dB (24 dB when a DSCM is placed after
the amplifier output), clean all the optical connections from the Line
A output port to the input of the CMD.
Step Action
Step Action
Step Action
24 Read the total power going to the WSS OPM Monitor 2 port (port 2) by
retrieving the untimed OPR-OTS PM value for the WSSOPM OPTMON
facility:
a. Select Performance -> Performance Monitoring -> New.
b. Select the WSSOPM type and the facility OPTMON-<shelf>-<WSS
slot>-2. Click Start Monitoring. Read the Untimed OPR-OTS value.
Step Action
25 Use the PM feature as follows to verify that the power going to the OPM is
approximately 17 dB (for an SLA, MLA, MLA2, MLA2 w/VOA, MLA3, XLA, or
RLA) or 10 dB (for a LIM) lower than the power at the Line A Out (port 7).
If Then use the PM feature on the
an XLA is present XLA
an RLA is present RLA
your configuration uses ESAM+MLAx MLAx
otherwise line facing circuit pack
c. Select the AMP type and the facility AMP-<shelf>-<AMP slot>-8. Click
Start Monitoring. Read the Untimed OPOUT-OTS value.
d. Calculate the difference of the power read in substep c and the power
recorded in step 24. The difference should be approximately 17 dB.
Go to substep g.
e. Select the OPTMON type and the facility OPTMON-<shelf>-<AMP
slot>-8. Click Start Monitoring. Read the Untimed OPR-OTS value.
f. Calculate the difference of the power read in substep e and the power
recorded in step 24. The difference should be approximately 10 dB.
g. If the power difference is 19 dB or higher (for an SLA, MLA, MLA2, MLA2
w/VOA, MLA3, XLA, or RLA) or 12 dB or higher (for a LIM), clean and
verify the patch cord and the connectors between the Line A Mon (port 2)
and the OPM Monitor 2 port.
h. If you cannot correct the loss, contact your next level of support.
Step Action
26 To verify that the fiber connections are correct and the power from the correct
port is being measured, temporarily disconnect the fiber between AMP
monitor port 2 to WSS OPM monitor port 2.
If the reading on the WSSOPM Then the fibers are
OPTMON facility indicates
no power connected correctly. Reconnect
the removed fiber and go to the
next step.
there is still power connected incorrectly. Swap the
fiber connections and repeat
from step 24.
27 Ensure that all LOS alarms on the WSS OPM are cleared.
Step Action
If Then go to
the line facing circuit pack is MLA, MLA2, MLA2 w/VOA, substep a
or MLA3
the line facing circuit pack is SLA or LIM substep c
an XLA is present substep a
an RLA is present substep a
your configuration uses ESAM+MLAx substep a
Step Action
The following list is provided as a job aid to calculate the expected loss.
• Identify the equipment present in your configuration and enter the values
for the associated loss or gain, as applicable, after the = (equal sign) on
the respective equipment line.
• Add the values preceded by + (plus sign).
• Subtract the values preceded by - (minus sign).
• The result is the maximum expected loss for your configuration.
Step Action
31 If the measured loss (calculated in step 29) is higher than the maximum
expected loss (calculated in step 30), identify the source of the excessive loss
and to make the appropriate corrections:
• Starting with the transmitter and going toward the line facing circuit pack,
measure the input and the output of each component with a power meter.
Always clean both male connectors before closing a connection.
• Compare the loss through each component and patch cord with the
maximum expected loss as indicated in Table 4-3 on page 4-107 to Table
4-5 on page 4-109.
• When the source of the excessive loss is identified, clean and inspect the
optical connectors. If the problem persists, replace the faulty component.
Refer to the appropriate procedure in Fault Management - Module
Replacement, 323-1851-545.
Step Action
If Then go to
the line facing circuit pack is SLA, MLA, MLA2, or MLA3 substep a
the line facing circuit pack is MLA2 w/VOA substep c
the line facing circuit pack is LIM substep e
an XLA is present substep a
an RLA is present substep a
your configuration uses ESAM+MLAx substep a
a. Select the AMP type and the facility AMP-<shelf>-<AMP slot>-8. Click
Start Monitoring.
b. Read the Untimed OPOUT-OTS value.
Go to step 33.
c. Select the VOA type and the facility VOA-<shelf>-<AMP slot>-7. Click
Start Monitoring.
d. Read the Untimed OPOUT-OTS value.
Go to step 33.
e. Select the OPTMON type and the facility
OPTMON-<shelf>-<AMP slot>-8. Click Start Monitoring.
f. Read the Untimed OPR-OTS value.
33 Disable the Forced Shutoff on the DropLIM or WSS 50 GHz w/OPM 9x1 or
WSS Flex C-Band w/OPM 9x1:
a. In the Equipment & Facility Provisioning application, select the
appropriate photonic shelf from the Shelf drop-down list and select the
LIM or WSSOPM in the equipment table.
b. Select AMP from the Facility Type drop-down list and select
AMP-<shelf>-<slot>-8 for LIM or AMP-<shelf>-<slot>-21 for WSSOPM in
the facility table.
Step Action
c. Click Edit.
d. In the Edit AMP facility dialog, select Disabled in the Forced Shutoff
dropdown list then click OK.
34 If you are testing with DIA and COADM, select the SMD in the equipment
table.
• Select the required CHC facility in the demux direction and for the
wavelength that you are testing
— Set the Primary state to “OOS”
— Set the Opaque state to “No”
— Set the Switch selector to the port to which the CCMD12 Common In
is connected
• Select the NMCC in the Facility drop down list.
— Set the Target Loss to 0 dB.
35 With a power meter, measure the power present on the CMD output port that
corresponds to the wavelength being tested.
36 Calculate the loss between the line facing circuit pack Line A out and the CMD
channel output port:
<power measured in step 32 (dBm)> - <power measured in step 35 (dBm)>
37 Considering all the components present (including fixed pads and DSCM),
calculate the maximum expected loss between the Line A output and the
CMD channel output (use the data provided in Table 4-3 on page 4-107 to
Table 4-5 on page 4-109). Gain values can be retrieved by querying the
appropriate AMP facilities.
The following list is provided as a job aid to calculate the expected loss.
• Identify the equipment present in your configuration and enter the values
for the associated loss or gain, as applicable, after the = (equal sign) on
the respective equipment line.
• Add the values preceded by + (plus sign).
• Subtract the values preceded by - (minus sign).
• The result is the maximum expected loss for your configuration.
Step Action
Step Action
39 On the WSSOPM, select the required CHC facility and for the wavelength that
you are testing:
— Set the Opaque state to “Yes”.
— Set the Switch selector to the default (usually the first switch on the
WSS).
• Select the NMCC in the Facility drop down list.
— Set the Target Loss to its default value (18 dB).
40 If you are testing with DIA, select the DIA WSSOPM in the equipment table.
• Select the CHC in the Facility drop down list.
— Select the wavelength of the transmitter chosen in step 10.
— Set the Opaque state to “Yes”.
— Set the Switch selector to the default (usually the first switch on the
WSS).
• Select the NMCC in the Facility drop down list.
— Set the Target Loss to its default value (18 dB).
41 If you are testing with DIA and COADM, select the SMD in the equipment
table.
• Select the required CHC facility in the mux direction and for the
wavelength that you are testing
— Set the Primary state to “IS”.
— Set the Opaque state to “Yes”.
— Set the Switch selector to the default mux port (port 11).
• Select the NMCC in the Facility drop down list.
— Set the Target Loss to 28 dB.
42 If you are testing with DIA and COADM, select the SMD in the equipment
table.
• Select the required CHC facility in the demux direction and for the
wavelength that you are testing.
— Set the Primary state to “IS”.
— Set the Opaque state to “Yes”.
— Set the Switch selector to the default demux port (port 12).
• Select the NMCC in the Facility drop down list.
— Set the Target Loss to 28 dB.
Step Action
43 Enable the Forced Shutoff on the DropLIM or WSS 50 GHz w/OPM 9x1 or
WSS Flex C-Band w/OPM 9x1:
a. In the Equipment & Facility Provisioning application, select the
appropriate photonic shelf from the Shelf drop-down list and select the
LIM or WSSOPM in the equipment table.
b. Select AMP from the Facility Type drop-down list and select
AMP-<shelf>-<slot>-8 for LIM or AMP-<shelf>-<slot>-21 for WSSOPM in
the facility table.
c. Click Edit.
d. In the Edit AMP facility dialog, select Enabled in the Forced Shutoff
dropdown list then click OK.
44 Remove the loopback put in step 12.
45 Repeat from step 9 on the other OTS if the node is not a terminal.
Testing express port cabling for all channels
46 Select the WSSOPM or RLA you want to test. Start with one direction. Ensure
that Line A In (port 8) port on the circuit pack associated with the WSS or the
Line A In (port 8) port on the RLA is disconnected as follows.
If Then you are ensuring that the
Line A In (port 8) is disconnected
on the following circuit pack
associated with the WSS or on
the RLA
an XLA is present XLA
an RLA is present RLA
your configuration uses ESAM+MLAx MLAx
otherwise line facing circuit pack
Step Action
Table 4-3
CCMD12, SMD, CMD44, CMD64, BMD2, OMD4, and WSS maximum dB loss
Unit PEC Max Mux loss (dB) Max Demux loss (dB)
100 GHz CMD44 NTT862AA 6.0 6.0
100 GHz CMD44 with isolator NTT862FA 6.0 6.6
50 GHz CMD44 Blue NTT862BA 7.0 7.0
50 GHz CMD44 Red NTT862BB 7.0 7.0
50 GHz enhanced CMD44 Blue NTT862BC 7.5 7.5
50 GHz enhanced CMD44 Red NTT862BD 7.5 7.5
75 GHz CMD64 NTT862JA 6.5 7.1
SCMD4 100 GHz NTK508AxE5 4.6 Ch In to Common 5.4 Common In to Ch
Out Out
1.1 Upgrade In to 0.75 Common In to
Common Out Upgrade Out
WSS 100 GHz w/OPM 5x1 NTK553EA 7.0 8.7
WSS 100 GHz w/OPM 4x1 NTK553HA 11.4 8.5
WSS 100 GHz w/OPM 2x1 (2-slot) NTK553JA 7.0 4.4
WSS 100 GHz w/OPM 2x1 (1-slot) NTK553JB 8.8 5.3
WSS 50 GHz w/OPM 2x1 (3-slot) NTK553KC 7.0 4.4
WSS 50 GHz w/OPM 2x1 (1-slot) NTK553KA 8.4 12.4 Common In to
Demux Out
2.0 Common In to Drop
Out
WSS 50 GHz w/OPM 9x1 NTK553FA 7.0 11.2
NTK553FC 6.8 11.7
WSS Flex C-Band w/OPM 9x1 NTK553LA 6.8 11.7
RLA 5x1 NTK553RA 6.5 8.0
BMD2 NTT862DA 3.8 3.8
CCMD12 NTK508FA 13.4 13.4
SMD NTK553GA 7.3 7.3
Table 4-3
CCMD12, SMD, CMD44, CMD64, BMD2, OMD4, and WSS maximum dB loss (continued)
Unit PEC Max Mux loss (dB) Max Demux loss (dB)
SMD NTK553GB 7.1 7.1
OMD4 NTK504Ax 2.5 Ch In to Common 3.3 Common In to Ch
Out Out
1.1 Upgrade In to 0.75 Common In to
Common Out Upgrade Out
Table 4-4
OMDF4, OMDF8, and BS5 maximum dB loss
Table 4-5
Dispersion Slope Compensation Modules (DSCM) maximum dB loss
Table 4-5
Dispersion Slope Compensation Modules (DSCM) maximum dB loss (continued)
Procedure 4-8
Testing a CDC ROADM configuration
Use this procedure to test channel access continuity on a CDC ROADM where
light from transmitting subtending equipment is available. This test verifies the
optical continuity and checks for reflection-related problems. This procedure
does not optimize the channels for traffic.
Prerequisites
• This procedure allows you to perform optical continuity testing through all
the equipment associated with CDC ROADM equipment at the site. Full
traffic continuity testing can proceed only after the system is complete. It
is recommended (while not mandatory) that you perform an Optical
Loopback test with at least one service layer source for each installed
CCMD8x16. See the procedure on performing optical loopback testing in
Part 2 of Configuration - Provisioning and Operating, 323-1851-310.
• If no transmitter is available, you cannot perform this procedure.
• Perform this procedure only after you have completed Procedure 2-1,
“Powering up a new network element and connecting a craft computer”
through Procedure 4-1, “Connecting intra-site fibers for
TOADM/ROADM/DGFF/DIA/Colorless OADM sites”. You must first
complete the NE commissioning, photonic layer provisioning including TID
slot sequence provisioning (see “Photonic layer provisioning procedures”
on page 3-3), and fibering before performing this procedure.
• The fibers and the MPO cables that are used in the following steps to
connect the equipment must be verified to be in good working order prior
to use. It is very important that fibers are cleaned and scoped prior to
being connected. See Installation - General Information, 323-1851-201.0,
for the cleaning and inspection procedure.
• Use optical terminators on applicable unused input faceplate connectors
of installed WSS circuit packs. If dust caps are used instead of optical
terminators, PMs can be reported against the port and the port may
appear in-service.
This requirement does not apply to the WSS Flex C-Band w/OPM 20x1
circuit packs.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Step Action
Step Action
5 Calculate the coupler loss for the line facing circuit pack:
Coupler loss = <OSC output power (dBm) read in step 3> - <OSC Out power
(dBm) read in step 4>
The calculated coupler loss should be less than 5 dB (SRA) or 3.5 dB (other
line facing circuit packs).
If the OSC or loopback fibers are dirty, crossed or pinched, the calculated
coupler loss will be much greater than5 dB (SRA) or 3.5 dB (other line facing
circuit packs). You must rectify the situation before you continue.
6 Using an optical power meter, measure the power going to the OSC In port
from the OSC Out (port 4). This value should be roughly the same as the
power read in step 4.
7 Remove the loopback you put in step 2.
8 Repeat step 2 to step 7 for all other ROADM OTSs at the site.
Testing the interconnects using the Connection Validation application: WSSOPM-to-WSSOPM,
WSSOPM-to-MPO loopback module, WSSOPM-to-LC loopback module, WSSOPM-to-CCMD8x16,
CCMD8x16-to-MPO loopback module
9 See the following figures for examples of the interconnects tested by the
Connection Validation application:
• Figure 4-39 on page 4-116—testing the WSSOPM-to-WSSOPM
interconnect
• Figure 4-40 on page 4-117—testing the WSSOPM-to-MPO loopback
module interconnect
• Figure 4-41 on page 4-118—testing the WSSOPM-to-LC loopback
module interconnect
• Figure 4-42 on page 4-119—testing the WSSOPM-to-CCMD8x16
interconnect
• Figure 4-43 on page 4-120—testing the CCMD8x16-to-MPO loopback
module interconnect
10 Make sure there are no Cable Trace Compromised alarms, Adjacency Far
End Not Discovered alarms or Adjacency Mismatch alarms. If alarms are
raised, see Fault Management - Alarm Clearing, 323-1851-543 for the
procedures on how to clear the respective alarms.
11 Make sure that the Dark Fiber Loss Management system parameter is
enabled in the Node Information tab of Site Manager. (For details, see the
procedure on editing the nodal system parameters in Administration and
Security, 323-1851-301.)
12 Make sure that you wait for approximately 5 minutes after the last fibering was
completed.
Step Action
CAUTION
Risk of affecting performance
You must inspect and clean the MPO connectors after
removing the MPO cable from its original packaging or
if the MPO cable has been removed from the faceplate
for any reason.
Figure 4-39
CDC ROADM—testing the WSSOPM-to-WSSOPM interconnect
Figure 4-40
CDC ROADM—testing the WSSOPM-to-MPO loopback module interconnect
Figure 4-41
CDC ROADM—testing the WSSOPM-to-LC loopback module interconnect
Figure 4-42
CDC ROADM—testing the WSSOPM-to-CCMD8x16 interconnect
Figure 4-43
CDC ROADM—testing the CCMD8x16-to-MPO loopback module interconnect
Step Action
CAUTION
Risk of affecting performance
You must inspect and clean the MPO connectors after
removing the MPO cable from its original packaging or
if the MPO cable has been removed from the faceplate
for any reason.
Figure 4-44
CDC ROADM—testing with transponder loopback
Figure 4-45
CDC ROADM—testing the jumper cable interconnect on CCMD8x16 using transponder loopback
Step Action
20 If excessive losses are detected, clean and inspect the optical connectors.
(See Table 4-6 on page 4-124 for maximum CCMD8x16 and WSS Flex
C-Band w/OPM 20x1 loss values and Table 4-7 on page 4-124 for maximum
FIM loss values.)
Table 4-6
CCMD8x16 and WSS Flex C-Band w/OPM 20x1 maximum loss
Unit PEC Max Mux loss (dB) Max Demux loss (dB)
WSS Flex C-Band w/OPM 20x1 NTK553MA 8.2 8.2
CCMD8x16 NTK508HA 17 17
Table 4-7
Fiber Interconnect Modules (FIM) maximum loss
21 If the problem persists, replace the faulty component. Refer to the appropriate
procedure in Fault Management - Module Replacement, 323-1851-545.
22 If alarms are raised, see Fault Management - Alarm Clearing, 323-1851-543
for the procedures on how to clear the respective alarms.
Validating CMD44 to WSS connectivity
23 Ensure that the CMD44/BMD2 and MLA3/XLA are added to the slot
sequence. See the procedure on editing a slot sequence in Part 2 of
Configuration - Provisioning and Operating, 323-1851-310.
24 For the CMD you are testing:
a. Select one of the transmitters to be connected to the selected CMD.
b. For the ADJ-TX facility of the CMD port to be connected, set the
transmitter type to match the transmitter you are turning up.
c. If you can adjust the output power of the transmitter, set it to correct power
level.
Step Action
Step Action
Step Action
35 If the line facing circuit pack is an MLA3, perform this step on the line facing
circuit pack (MLA3).
a. Edit the Line B AMP facility (AMP-<shelf>-<slot>-6) to set the target gain
to 17 dB:
— In the Equipment & Facility Provisioning application, select the
appropriate photonic shelf from the Shelf drop-down list and select
the LIM in the equipment table.
— Select AMP from the Facility Type drop-down list and select
AMP-<shelf>-<slot>-6 in the facility table.
— Click Edit.
— Record the current Target Gain value. (You will revert to it at the end
of this procedure.)
— In the Edit AMP facility dialog, enter 17.00 in the Target Gain field
then click OK.
b. Verify the ORL at Line B output:
— In the Performance Monitoring application, select the appropriate
photonic shelf from the Shelf drop-down list.
— For non-MLA2 w/VOA, select the AMP Type and the facility
AMP-<shelf>-<slot>-6 from the Facility drop down list.
— For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-5 from the Facility drop down list.
— Click Start Monitoring.
— In the PM table, read the Untimed ORL-OTS value.
— If the value is lower than 28 dB, clean all the optical connections from
the Line B output port to the input of the pad. When DSCMs are used
and the DSCM location is at the head end of the span (collocated with
the amplifier being commissioned), the minimum ORL threshold to
meet or exceed is 24 dB.
Step Action
36 If the line facing circuit pack is an MLA3, perform this step on the line facing
circuit pack (MLA3).
a. Edit the Line A AMP facility (AMP-<shelf>-<slot>-8) to set the target gain
to 20 dB:
— In the Equipment & Facility Provisioning application, select the
appropriate photonic shelf from the Shelf drop-down list and select
the LIM in the equipment table.
— Select AMP from the Facility Type drop-down list and select
AMP-<shelf>-<slot>-8 in the facility table.
— Click Edit.
— Record the current Target Gain value. (You will revert to it later in this
procedure.)
— In the Edit AMP facility dialog, enter 20.00 in the Target Gain field
then click OK.
b. Verify the ORL at Line A output:
— In the Performance Monitoring application, select the appropriate
photonic shelf from the Shelf drop-down list.
— For non-MLA2 w/VOA, select the AMP Type and the facility
AMP-<shelf>-<slot>-8 from the Facility drop down list.
— For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-7 from the Facility drop down list.
— Click Start Monitoring.
— In the PM table, read the Untimed ORL-OTS value.
— If the value is lower than 28 dB (24 dB when a DSCM is placed after
the amplifier output), clean all the optical connections from the Line
A output port to the input of the CCMD8x16/CMD44.
Go to step 38.
Step Action
Step Action
Step Action
40 To verify that the fiber connections are correct and the power from the correct
port is being measured, temporarily disconnect the fiber between AMP
monitor port 2 to WSS OPM monitor port 2.
If the reading on the WSSOPM Then the fibers are
OPTMON facility indicates
no power connected correctly. Reconnect
the removed fiber and go to the
next step.
there is still power connected incorrectly. Swap the
fiber connections and repeat
from step 38.
41 Read the total power going to the WSS OPM Monitor 1 port (port 1) by
retrieving the untimed OPR-OTS PM value the WSSOPM OPTMON facility:
a. Select Performance -> Performance Monitoring -> New.
b. Select the WSSOPM type and the facility OPTMON-<shelf>-<WSS
slot>-1. Click Start Monitoring. Read the Untimed OPR-OTS value.
42 Use the PM feature as follows to verify that the power going to the OPM is
approximately 17 dB (for an MLA3 or XLA) lower than the power at the Line
B out (port 5).
If Then use the PM feature on the
an XLA is present XLA
otherwise line facing circuit pack
Step Action
43 To verify that the fiber connections are correct and the power from the correct
port is being measured, temporarily disconnect the fiber between AMP
monitor port 1 to WSS OPM monitor port 1.
If the reading on the WSSOPM Then the fibers are
OPTMON facility indicates
no power connected correctly. Reconnect
the removed fiber and go to the
next step.
there is still power connected incorrectly. Swap the
fiber connections and repeat
from step 41.
44 Ensure that all LOS alarms on the WSS OPM are cleared.
Restoring the settings on the degree after testing
45 Select your step.
If Then
the line facing circuit set the respective MLA3 Target Gain values back to
pack is an MLA3 the values you recorded in step 35 (MLA3 Line B) and
step 36 (MLA3 Line A)
an XLA is present set the XLA AMP facilities to OOS, then set the XLA
Gain Mode and Target Gain back to the values you
recorded in step 37 for the XLA Line B and Line A,
respectively. Set the facilities back to IS.
46 On the WSSOPM:
• Select CHC in the Facility drop down list and select the CHC facility with
the index associated with the wavelength in the Mux direction of the
transmitter chosen in step 30, that is ‘CHC-<shelf>-<slot>-10-<index>’.
— Set the Opaque state to “Yes”.
• Select the NMCC in the Facility drop down list.
— Set the Target Loss to its default value (18 dB).
47 Delete the photonic connection you provisioned in step 30.
48 Remove the far-end adjacency provisioning if it was added in step 17 for the
purpose of this testing only.
49 Remove the loopback you added in step 31.
50 Remove the padding you added in step 32.
51 Repeat step 29 to step 50 for each of the remaining degrees.
—end—
Procedure 4-9
Testing TOADM channel access continuity
Use this procedure to test channel access continuity at TOADM sites where
light from transmitting subtending equipment is available. This test verifies the
optical continuity and checks for reflection-related problems. This procedure
does not optimize the channels for traffic.
See Figure 4-46 on page 4-134 for an example of TOADM node testing.
Labeled numbers in this figure identify the steps in this procedure.
You can use Table 4-9 on page 4-140 to record information and test results.
Prerequisites
• Have an optical power meter.
• Make sure that you have a copy of the EDP/IDP.
• This procedure allows you to perform optical continuity testing through the
OTS. Full traffic continuity testing can proceed only after the system is
complete. It is recommended that you perform the continuity test with at
least one service layer source for each installed SCMD4.
• If no transmitter is available, you cannot perform this procedure.
• Perform this procedure only after you have completed all procedures
through Procedure 4-1, “Connecting intra-site fibers for
TOADM/ROADM/DGFF/DIA/Colorless OADM sites”. You must first
complete the NE commissioning and fibering before performing this
procedure.
• The fibers that are used in the following steps to connect to subtending
client equipment must be verified to be in good working order prior to use.
It is very important that client fibers are cleaned and inspected prior to
being connected. See Installation - General Information, 323-1851-201.0
for the cleaning and inspection procedures.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Figure 4-46
Overview of TOADM channel access continuity testing
10
16 17
A
B
12 18
19
11
Power 9 20
meter
Tx Rx
Step Action
Step Action
4 In the Performance Monitoring window, select the OPTMON type and the
facility for OSC Out (port 4) on the line facing circuit pack connected to the
OSC-1 you are testing (OPTMON-<shelf>-<slot>-4). Record the OPR-OTS
Untimed parameter.
5 Calculate the coupler loss for the line facing circuit pack:
Coupler loss = <OSC output power (dBm) read in step 3> - <OSC Out power
(dBm) read in step 4>
The calculated coupler loss should be less than 3.5 dB.
If the OSC or loopback fibers are dirty, crossed or pinched, the calculated
coupler loss will be much greater than 3.5 dB. You must rectify the situation
before you continue.
6 Using an optical power meter, measure the power going to the OSC In port
from the OSC Out (port 4). This value should be roughly the same as the
power read in step 4.
7 Remove the loopback you put in step 2.
8 Repeat step 2 to step 7 for the other OSC-1 (dual 2xOSC configuration) or
the OSC-2 (single 2xOSC configuration).
Setting up for the testing
9 Select the SCMD4 you want to test:
• Choose the SCMD4 that is the furthest from the line-facing circuit pack.
• Choose one of the transmitters to be connected to the selected SCMD4.
Make sure the wavelength of the transmitter matches the wavelength of
the SCMD4 port it is connected to.
• If you can adjust the output power of transmitter, set it to maximum.
• Using a power meter set correctly for the wavelength, measure the
transmitter output power and connect the transmitter to the appropriate
SCMD4 port.
Step Action
The amount of padding depends on the type of the line-facing circuit pack.
Circuit pack Padding
LIM 0 dB
SLA 10 dB
11 On the SCMD4 where the transmitter is connected, set the target loss of the
corresponding ingress VOA facility to 0 dB by editing the Target Loss
parameter of the VOA facility in the Equipment and Facility Provisioning
application.
12 Using the PM features, measure the power present at the Line B input of the
line-facing circuit pack:
If the line-facing circuit Then select
pack is
MLA, MLA2, or MLA3 Line B AMP facility (port 6) and record the
OPIN-OTS Untimed value
SLA and LIM OPTMON facility (port 6) and record the
OPR-OTS Untimed value
13 Calculate the loss between the SCMD4 input and the Line B input port:
<power measured in step 9 (dBm)> - <power measured in step 12 (dBm)>
14 Considering all the components present (including fixed pads and DSCM),
calculate the maximum expected loss between the SCMD4 input channel
port and the Line B input port (use the information in Table 4-8 on page 4-140
and Table 4-5 on page 4-109).
Step Action
15 If the measured loss is higher than the maximum expected loss, identify the
source of the excessive loss and make the appropriate corrections:
• Starting with the transmitter and going toward the line-facing circuit pack,
measure the input and the output of each component with a power meter.
Always clean both male connectors before closing a connection.
• Compare the loss through each component and patch cord to the
maximum expected loss as indicated in Table 4-8 on page 4-140 and
Table 4-5 on page 4-109.
• When the source of the excessive loss is identified, clean and inspect the
optical connectors. If the problem persists, replace the faulty component.
Refer to the appropriate procedure in Fault Management - Module
Replacement, 323-1851-545.
16 If the line-facing circuit pack is an MLA, MLA2, or MLA3:
• Adjust the target gain of the Line B amplifier facility to 17 dB.
• Verify the ORL at the Line B output. If the value is lower than 28 dB, clean
all the optical connections from the Line B output port to the input of the
pad. When DSCMs are used and the DSCM location is at the head end
of the span (collocated with the amplifier being commissioned), the
minimum ORL threshold to meet or exceed is 24 dB.
17 If the line-facing circuit pack is an MLA, MLA2, MLA3, or an SLA:
• Adjust the target gain of the Line A amplifier facility to 20 dB.
• Verify the ORL at the Line A output. If the value is lower than 28 dB (24 dB
when a DSCM is placed after the amplifier output), clean all the optical
connections from the Line A output port to the input of the SCMD4.
18 Using the PM features, measure the power present at the Line A output of the
line facing circuit pack:
If the line-facing circuit pack Then use the Line A facility (port 8)
is
MLA, MLA2, MLA3, or SLA AMP facility OPOUT-OTS Untimed value
LIM OPTMON facility OPR-OTS Untimed value
19 Set the target loss of the demux VOA facility on the SCMD4 Common In
(port 1) to 0 dB.
20 With a power meter, measure the power present on the SCMD4 output port
that corresponds to the wavelength you are testing.
21 Calculate the loss between the line-facing circuit pack Line A Out and the
SCMD4 channel output port.
Step Action
22 Considering all the components present (including fixed pads and DSCM),
compute the maximum expected loss between the Line A output and the
SCMD4 channel output (use the information in Table 4-8 on page 4-140 and
Table 4-5 on page 4-109).
24 When you have completed all testing, return the SCMD4 VOAs to 15 dB of
attenuation and disconnect the test transmitter.
25 Remove the loopback at the amplifier and reconnect the fibers as per
EDP/IDP.
26 Select the next step.
If this is a Then
thin OADM site repeat from step 9 on the other line-facing OTS. Then
go to step 27.
thin terminal site you have completed this procedure
Step Action
27 Using fibers that are known to be in good condition, complete the connection
between the two innermost SCMD4 in each direction for the pass-through
traffic. See Figure 4-7 on page 4-38 for an example.
a. Connect the Upgrade Out (port 12) of the innermost SCMD4 (or Line A
Out [port 7] of the line-facing circuit pack if SCMD4 cascade is empty) in
OTS1 to the Upgrade In (port 11) of the innermost SCMD4 (or Line B In
[port 6] of the line-facing circuit pack if SCMD4 cascade is empty) in
OTS2.
b. Connect the Upgrade In (port 11) of the innermost SCMD4 (or Line B In
[port 6] of the line-facing circuit pack if SCMD4 cascade is empty) in
OTS1 to the Upgrade Out (port 12) of the innermost SCMD4 (or Line A
Out [port 7] of the line-facing circuit pack if SCMD4 cascade is empty) in
OTS2.
Note: The innermost SCMD4 is the one that is the furthest from the
line-facing circuit pack in each OTS.
28 Provision the inter-OTS adjacency for the pass-through traffic.
• Select Configuration -> Equipment & Facility Provisioning.
• In the Equipment table, select the innermost SCMD4 (the one furthest
from the line facing circuit pack), or the line-facing circuit pack if the
SCMD4 cascade is empty (no SCMD4).
• Select ADJ in the Facility Type drop down list.
• Select the adjacency that corresponds to the port where the
pass-through traffic is handed off to the other OTS.
This port is the Upgrade Out (port 12) of the innermost SCMD4 or Line A
OUT (port 7) of the line-facing circuit pack if the SCMD4 cascade is
empty (no SCMD4).
Note: Adjacency format = ADJ-<shelf>-<slot>-<port>
• Click Edit in the Facility area.
• Set the Adjacency type to CMD (if the other OTS SCMD4 cascade is not
empty) or LIM (if the other OTS SCMD4 cascade is empty).
• Enter the Expected Far End Address and the Expected Far End Address
Format as described in the EDP/IDP.
The Expected Far End Address must point to the input port of the
innermost SCMD4 of the other OTS (Port 11) or to the Line B In (port 6)
of the line-facing circuit pack of the other OTS if its SCMD4 cascade is
empty (no SCMD4).
Step Action
• Click OK.
• Repeat the above substeps for the other OTS.
—end—
Table 4-8
SCMD4 Maximum dB loss
Circuit PEC Max Mux loss (dB) Max Demux loss (dB)
pack
Table 4-9
Worksheet: Testing Thin OADM channel access continuity
Procedure Site Name:________________ Grp Grp Grp Grp Grp Grp Grp Grp Grp
step Site ID:___________________ Ch Ch Ch Ch Ch Ch Ch Ch Ch
Shelf:____________________
Procedure 4-10
Testing a DIA configuration
Use this procedure to test a direction independent access (DIA) configuration
that is not part of a Colorless COADM configuration. Figure 4-47 on page
4-142 illustrates an example of DIA configuration.
To test a low channel count DIA configuration, see Procedure 4-11, “Testing a
low channel count DIA configuration”.
Prerequisites
• Have a power meter.
• Make sure that you have a copy of the EDP/IDP.
• This procedure allows you to perform optical continuity testing through the
network element. Full traffic continuity testing can proceed only after the
system is complete. It is recommended that you perform the continuity test
with at least one service layer source for each installed CMD44.
• Perform this procedure only after you have completed all procedures
through Procedure 4-1, “Connecting intra-site fibers for
TOADM/ROADM/DGFF/DIA/Colorless OADM sites”. Connect all optical
fibers within the DIA configuration. You must first complete the NE
commissioning and fibering before performing this procedure.
• Use optical terminators on unused input faceplate connectors of installed
WSS circuit packs. If dust caps are used instead of optical terminators,
PMs can be reported against the port and the port may appear in-service.
• The fibers that are used in the following steps to connect to subtending
client equipment must be verified to be in good working order before use.
It is very important that client fibers are cleaned and inspected before
being connected. See Installation - General Information, 323-1851-201.0
for the cleaning and inspection procedures.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Figure 4-47
DIA configuration testing overview
27
26 29
OPM
36 25
16
13 33 20 30
MON
B
A
10 41
8 46
BMD2
7 47
4 48
Power 3 49
meter
Tx Rx Rx Tx
Step Action
Step Action
7 If your configuration includes a BMD2 module, check power into the BMD2
Mux port (port 3 or port 5, depending on which BMD2 port you have
connected the CMD44 50 GHz to) with a power meter.
The measured power into the BMD2 must be within 1 dB of the CMD44
Common Out.
8 Measure the power at the Common Out (port2) of the BMD2. If the loss is
higher than 4 dB, clean and inspect the optical connectors. Repeat the
measurement and if the loss is still higher than 4 dB, replace the BMD2
module. Refer to the appropriate procedure in Fault Management - Module
Replacement, 323-1851-545.
9 Reconnect the fiber of BMD2 Common Out as per EDP/IDP.
10 Using the PM features, measure the power present at the Line A Input (port 8)
of the amplifier circuit pack. Check that the input power is within 2 dB of the
power measured at the output of the CMD44 or BMD2 if applicable.
11 Set the target gain for AMP-<shelf>-<AMP slot>-8 facility to 7 dB.
12 Verify the ORL at Line A Out (port 7) on the amplifier. If the value is lower than
28 dB, clean all the optical connections from the Line A Out port.
Step Action
16 Ensure that all LOS alarms on the WSS OPM are cleared.
Step Action
Step Action
Step Action
28 If your configuration includes a BMD2 module, check power into the BMD2
Common In (port 1) with a power meter. The measured power into the BMD2
Common In must be within 1 dB of the amplifier output power. Reconnect the
fiber as per EDP/IDP.
29 Measure the power at the BMD2 Demux Out (port 4 or 6). If the measured
loss is higher than 4.5 dB, clean and inspect the optical connectors. Repeat
the measurement and if the loss is still higher than 4.5 dB, replace the BMD2
module. Refer to the appropriate procedure in Fault Management - Module
Replacement, 323-1851-545.
30 Check power into the CMD44 Common In (port 89) with a power meter. The
measured power into the CMD44 Common In must be within 1 dB of the
amplifier or BMD2 output power.
31 Check power out of the CMD44 Demux port of the test wavelength with a
power meter. If the measured loss is higher than:
• 8 dB for a CMD44 50 GHz
• 8.5 dB for an eCMD44 50GHz
• 7.6 dB for an eCMD44 100 GHz
clean and inspect the optical connectors. Repeat the measurement and if the
loss is still higher than the values above, replace the CMD44 module. Refer
to the appropriate procedure in Fault Management - Module Replacement,
323-1661-545.
32 On the WSSOPM, for the wavelength that you are testing:
• Select the required CHC facility:
— Set the Opaque state to “Yes”
— Set the Switch selector to the default (usually the first switch on the
WSS)
• Select the NMCC facility:
— Set the Target Loss to its default value (15 dB for WSS 50GHz 2x1 or
18 dB for all other WSS)
33 Remove the loopback on the WSS and delete the CHC and NMCC facilities
created in step 20.
34 Fiber the DIA WSS circuit pack to the other WSS circuit packs at the site in
accordance with the EDP/IDP. See Figure 4-23 on page 4-53 and Figure 4-23
on page 4-53 for examples.
35 Provision the inter-OTS WSS-WSS adjacencies to indicate to the 6500
software how the WSSs in the node are physically connected to one another.
Provision an adjacency on each WSS output port that is connected to another
WSS. To do so, log into each shelf and perform step 36 to step 42.
Step Action
Procedure 4-11
Testing a low channel count DIA configuration
Use this procedure to test a low channel count direction independent access
(DIA) configuration.
Figure 4-48 on page 4-150 illustrates an example of a low channel count DIA
configuration.
Prerequisites
• Have an optical power meter.
• Make sure that you have a copy of the EDP/IDP.
• This procedure allows you to perform optical continuity testing through the
network element. Full traffic continuity testing can proceed only after the
system is complete. It is recommended that you perform the continuity test
with at least one service layer source for the CCMD12.
• Perform this procedure only after you have completed all procedures
through Procedure 4-1, “Connecting intra-site fibers for
TOADM/ROADM/DGFF/DIA/Colorless OADM sites”. Connect all optical
fibers within the low channel count DIA configuration. You must first
complete the NE commissioning and fibering before performing this
procedure.
• Use optical terminators on unused input faceplate connectors of installed
WSS circuit packs. If dust caps are used instead of optical terminators,
PMs can be reported against the port and the port may appear in-service.
• The fibers that are used in the following steps to connect to subtending
client equipment must be verified to be in good working order before use.
It is very important that client fibers are cleaned and inspected before
being connected. See Installation - General Information, 323-1851-201.0
for the cleaning and inspection procedures.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Figure 4-48
Low channel count DIA configuration testing overview
Step Action
Step Action
Procedure 4-12
Testing a Colorless OADM configuration
Use this procedure to test a Colorless OADM configuration. A Colorless
OADM configuration is made up of the DIA OTS and the COADM OTS.
See the following figures for examples of the Colorless OADM configuration:
• “Intra-NE fiber connections at a Colorless OADM site” on page 4-55
• “Intra-NE fiber connections at a Colorless OADM site with CMD44 50GHz”
on page 4-56
Prerequisites
• You must know how to retrieve performance monitoring data. Refer to the
“Retrieving performance monitoring data” procedure in Fault Management
- Performance Monitoring, 323-1851-520.
• You require a user account with a UPC level of 3 or higher.
• You require an optical power meter.
• You require an LC to LC patch cord (for testing steps that use a fiber
loopback).
• Make sure that you have a copy of the EDP/IDP.
• This procedure allows you to perform optical continuity testing through the
network element. Full traffic continuity testing can proceed only after the
system is complete. It is recommended that you perform the continuity test
with at least one service layer source for each installed CCMD12.
• You must first complete the NE commissioning and fibering before
performing this procedure. Perform this procedure only after you have
completed the intra-site fibers as detailed in Procedure 4-1, “Connecting
intra-site fibers for TOADM/ROADM/DGFF/DIA/Colorless OADM sites”.
Connect all optical fibers within the Colorless OADM configuration.
Specifically:
— The COADM OTS and the DIA OTS must be provisioned. See Chapter
3, “Photonic layer provisioning procedures”.
— The High Fiber Loss Detection Alarm parameter in the Site Manager
Node Information application (System tab) must be set to Enabled for
the shelf containing a COADM OTS.
— The DIA MLA-SMD adjacencies for the Colorless OADM are
provisioned. See Procedure 3-2, “Provisioning adjacencies”.
• The fibers that are used in the following steps to connect to subtending
client equipment must be verified to be in good working order before use.
It is very important that client fibers are cleaned and inspected before
being connected. See Installation - General Information, 323-1851-201.0
for the cleaning and inspection procedures.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage electrostatic-sensi-
tive devices. Always connect yourself to ground before you
handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in Installation - General
Information, 323-1851-201.0, and those recommended by
your company at all times.
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can se-
verely damage your eyes.
Step Action
Table 4-10
CCMD12 and SMD maximum loss
Equipment PEC Max Mux loss (dB) Max Demux loss (dB)
Note: For the demux path of the WSS Flex C-Band w/OPM 9x1 circuit packs NTK553LB, there is an
embedded EDFA between the Common In and Switch Out ports 8-9. This amplifier provides between
6 and 13 dB gain to compensate for the maximum total passive loss of 11.7 dB in those paths.
6 If the problem persists, replace the faulty component. Refer to the appropriate
procedure in Fault Management - Module Replacement, 323-1851-545.
Step Action
Step Action
12 Verify the loss between the SMD and the DIA amplifier:
• Select the ADJ-FIBER facility for SMD port 10 (Common Out).
• If the loss is more than 2 dB, check the fibering.
13 Retrieve the untimed ORL-OTS PM value for the AMP facility of the DIA
amplifier Line A Output (AMP-<shelf>-<slot>-8).
ORL value must be greater than 28 dB. If the value is lower than 28 dB, clean
all the optical connections from the Line A Out port.
14 Use the PM application to check that power is present at DIA WSSOPM port
2.
15 Put the AMP facility of DIA amplifier Line A Out (port 7) OOS and check that
there is no power at DIA WSSOPM port 2. If otherwise, check the fibering
from the DIA amplifier Monitor port 2 to the DIA WSSOPM port 2.
16 Put DIA amplifier Line A back IS.
17 Verify the loss between DIA amplifier Monitor port 2 and DIA WSSOPM port
2:
a. On the DIA amplifier, select port 2 (Monitor 2 [A]), then select the
ADJ-FIBER facility and check the fiber loss that is reported.
b. If the loss is more than 1 dB, check the fibering.
18 Select the CHMON type, the facility CHMON-<shelf>-<DIA AMP slot>-7, and
the wavelength you are testing. Click Start Monitoring. Read the Untimed
OPT-OCH value.
19 Select the AMP type and the facility AMP-<shelf>-<DIA AMP slot>-8. Click
Start Monitoring. Read the Untimed OPOUT-OTS value.
20 Calculate the difference of the power read in step 18 and the power read in
step 19. The difference should be within ± 2dB.
21 Check ADJ-FIBER on port 7 of the DIA amplifier.
22 Retrieve the untimed OPR-OTS PM value for the OPTMON facility of the DIA
WSS Monitor port 2.
The loss = step 21 value - step 22 value, which must be less than 20 dB. If it
is not, make sure the fiber is connected to the correct ports. Clean the
connectors and verify the optical patch fiber between the DIA amplifier Mon
2 (port 2) and the DIA WSS Monitor port 2. If you are unable to reduce the
loss, contact your next level of support to determine if any components
require replacement.
Step Action
23 Retrieve the untimed OPR-OTS PM value for the OPTMON facility of the DIA
WSS Switch1 In (port 3).
The loss = step 22 value - step 23 value, which must be less than 12 dB. If it
is not, clean the connectors and verify the loopback patch cord. If you are
unable to reduce the loss, contact your next level of support to determine if
any components require replacement.
24 On the DIA WSSOPM, open pixel for the CHC-shelf-slot-index:
a. Select the CHC in the Facility drop-down list and select the CHC with the
index associated with the wavelength being tested.
b. Set the Opaque state to “No”.
c. Set the Switch selector to the port which has the fiber loopback.
d. Select the NMCC facility in the Facility drop-down list.
e. Set the Target Loss to 0 dB.
25 Retrieve the untimed OPIN-OTS PM value for the AMP facility of the DIA
amplifier Line B In (port 6).
The loss = step 23 value - step 25 value, which must be less than 8 dB. If it is
not, clean the connectors and verify the optical patch fiber between the DIA
WSS Common Out and the DIA amplifier Line B In. If you are unable to
reduce the loss, contact your next level of support to determine if any
components require replacement.
26 Retrieve the untimed OPOUT-OTS PM value for the AMP facility of the DIA
amplifier Line B Output (AMP-<shelf>-<slot>-6).
27 Retrieve the untimed OPR-OTS PM value for the OPTMON facility of the DIA
WSS Monitor port 1.
The loss = step 26 value - step 27 value, which must be less than 20 dB. If it
is not, make sure the fiber is connected to the correct ports. Clean the
connectors and verify the optical patch fiber between the DIA amplifier
Mon 1 (port 1) and the DIA WSS Monitor port 1. If you are unable to reduce
the loss, contact your next level of support to determine if any components
require replacement.
28 Retrieve the untimed ORL-OTS PM value for the AMP facility of the DIA
amplifier Line B Output (AMP-<shelf>-<slot>-6).
ORL value must be greater than 28 dB. If the value is lower than 28 dB, clean
all the optical connections from the Line B Out port.
29 Retrieve the untimed OPR-OTS PM value for the OPTMON facility of the
SMD Common In (port 9).
The fiber loss = step 26 value - step 29 value, which must be less than 1 dB.
If it is not, clean the connectors and verify the optical patch fiber between the
DIA amplifier Line B Out and the SMD Common In.
Step Action
Procedure 4-13
Connecting intra-site fibers and testing a Colorless
Direct Attach configuration (COADM OTS connected
to 1x9 or 1x2 WSS)
Use this procedure to connect intra-site fibers for a Colorless Direct Attach
configuration (COADM OTS connected to 1x9 or 1x2 50 GHz WSS) and to
test the configuration. Figure 4-49 on page 4-165 illustrates a configuration
example with a 1x9 WSS. Figure 4-50 on page 4-166 illustrates a
configuration example with a 1x2 50 GHz WSS. Figure 4-51 on page 4-167
illustrates a configuration example with a 1x9 WSS and an OPS. Figure 4-52
on page 4-168 illustrates a configuration example with a 1x9 WSS and an
CMD44 50 GHz.
Note that:
• The Colorless OADM Direct Attach configuration:
— is connected to:
– NTK553LA or NTK553LB (1x9 WSSOPM). These units can be
used in fixed-grid 50 GHz configurations or flexible grid.
– NTK553FA or NTK553FC (1x9 WSSOPM) in fixed-grid 50 GHz
configurations
– NTK553KA (1x2 WSSOPM) in fixed-grid 50 GHz configurations
— works with the following units for 96 channels:
– XLA and MLA3
– NTK553LA/LB
Note: This procedure assumes that the CCMDs are connected and
tested before any colored CMD44s are connected and tested. If the
colored CMD44s are connected first in a greenfield scenario, use
Procedure 4-7, “Testing ROADM channel access continuity” to test the
colored CMD44s.
Prerequisites
• Make sure that you have a copy of the EDP/IDP.
• You must know how to retrieve performance monitoring data. Refer to the
procedure on retrieving performance monitoring data in Fault
Management - Performance Monitoring, 323-1851-520.
• Use an account with a UPC level of 3 or higher.
• You require an optical power meter.
• You require an LC to LC patch cord.
• You must first complete the NE commissioning before performing this
procedure. Perform this procedure only after you have completed all
applicable procedures in this document up to, but not including, Procedure
4-1, “Connecting intra-site fibers for
TOADM/ROADM/DGFF/DIA/Colorless OADM sites”. Specifically:
— Ensure that commissioning information has been entered.
— The COADM OTS and the ROADM OTS must be provisioned.
Note: The COADM amplifier must be explicitly provisioned as part of the
COADM OTS.
— The High Fiber Loss Detection Alarm parameter in the Site Manager
Node Information application (System tab) must be set to Enabled for
the shelf containing a COADM OTS.
— The MLA-SMD adjacencies for the Colorless OADM Direct Attach are
provisioned. See Procedure 3-2, “Provisioning adjacencies”.
• This procedure allows you to perform optical continuity testing through the
network element. Full traffic continuity testing can proceed only after the
system is complete. It is recommended that you perform the continuity test
with at least one service layer source for each installed CCMD12.
• The fibers that are used in the following steps to connect to subtending
client equipment must be verified to be in good working order before use.
It is very important that client fibers are cleaned and inspected before
being connected. See Installation - General Information, 323-1851-201.0
for the cleaning and inspection procedures.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Figure 4-49
Colorless Direct Attach configuration (COADM OTS with 1x9 WSS) example
ROADM
COADM
Figure 4-50
Colorless Direct Attach configuration (COADM OTS connected to 1x2 50 GHz WSS) example—
testing with transponder loopback
Figure 4-51
Colorless Direct Attach configuration (COADM OTS connected to 1x9 WSS and using OPS)
example
Figure 4-52
Colorless Direct Attach configuration (COADM OTS connected to 1x9 WSS with CMD44) example
Figure 4-53
Colorless Direct Attach configuration (COADM OTS connected to 1x9 WSS with unamplified and
amplified CMD44s) example
Step Action
Step Action
6 In Site Manager, using the Protection Status screen, select the appropriate
Shelf and OPTMON OPS Facility and then operate a Lockout on the
protection member to make the OPS SW1 active.
This allows the optical manual loopback test to be performed between the
transmitter/receiver, through the OPS, to the CCMD12 connected on the OPS
SW1 path.
7 Perform step 10 to step 12, then release the Lockout on the Protection path.
8 In Site Manager, using the Protection Status screen, select the appropriate
Shelf and OPTMON OPS Facility, then operate a Forced switch on the
working member to make the OPS SW2 active.
This allows the optical manual loopback test to be performed between the
transmitter/receiver, through the OPS, to the CCMD12 connected on the OPS
SW2 path.
9 Perform step 10 to step 12, then release the Forced switch on the Working
path. Then go to step 13.
10 Perform optical loopback testing through CCMD12 ADJ-TX. See the
procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310.
11 Select the Validation Summary tab to display the connection validation
results. If the test has failed, disconnect the cable, clean and inspect the
connectors and reconnect.
For steps to inspect and clean connectors, see Installation - General
Information, 323-1851-201.0.
For High Fiber Loss alarms, see the procedure in Fault Management - Alarm
Clearing, 323-1851-543.
12 If there are Loss of Signal alarms present, clear the alarms by changing the
secondary state of the affected facilities to AINS.
Step Action
Step Action
Step Action
Step Action
Step Action
26 Retrieve the transmitter power (OPT-OCH from the OTM/PTP facility) and the
power into amplifier Line B input port (AMP OPIN-OTS).
The typical delta in measured power levels should be less than:
• CMD44/BMD2: 9 dB +/- 1 dB
• eCMD44/BMD2: 9 dB +/- 1 dB
• CMD44: 6 dB +/- 1 dB
• eCMD44: 6 dB +/- 1 dB
27 Retrieve the amplifier Line B output port (AMP OPUT-OTS) and the power
into WSS switch port input (WSS OPTMON PM).
The expected fiber loss should be less than the high fiber loss threshold
(default 1.5 dB).
Go to step 29.
28 Retrieve the transmitter power (OPT-OCH from the OTM/PTP facility) and the
power into WSS switch port input (WSS OPTMON PM).
The expected fiber loss should be less than the high fiber loss threshold
(default 1.5 dB).
29 Repeat step 23 to step 28 for each CMD44.
Step Action
Procedure 4-14
Connecting intra-site fibers for a Colorless Direct
Attach configuration (CCMD12/CMD44/CMD64
connected to 1x20 WSS)
Use this procedure to perform intra-site fiber connections for a Colorless
Direct Attach configuration (CCMD12/CMD44/CMD64 connected to 1x20
WSS, with or without an OPS).
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
• These configurations use MPO cables and connectors. For steps to:
— connect MPO cables, see the Installation technical publication specific
to the respective 6500 shelf type (in the procedure on routing
fiber-optic cables and electrical cables to circuit packs in the 6500
shelf)
— inspect and clean MPO connectors, see Installation - General
Information, 323-1851-201.0
CAUTION
Risk of affecting performance
You must inspect and clean the MPO connectors after
removing the MPO cable from its original packaging or
if the MPO cable has been removed from the faceplate
for any reason.
DANGER
Risk of injury
For a FIM Type 4 module and to respect the 1M laser
safety limit on the aggregate MPO output, the individual
input powers to the LC ports must be <=13 dBm.
Step Action
1 Identify your configuration type and connect the equipment as indicated in the
EDP/IDP.
For port numbers on FIMs, refer to the procedure on connecting fiber-optic
cables to circuit packs in the Installation technical publication specific to the
respective 6500 shelf type.
• Basic ROADM configuration with possible expansion—see:
— Figure 4-54 on page 4-183 (CCMD12s only)
— Figure 4-54 on page 4-183 (CMD64 and CCMD12s)
— Figure 4-56 on page 4-185 (CMD44s and CCMD12s)
and note the following:
— ROADM OTS contains WSS 1x20, MLA3/XLA-SRA/ESAM/SAM.
— CMDs (CCMD12s, CMD64/XLA/MLA3, or
CMD44/BMD2/XLA/MLA3) are not part of an OTS.
— CMDs (CCMD12s, CMD64/XLA/MLA3, or
CMD44/BMD2/XLA/MLA3) are connected via FIM Type 4.
— On the Twin 1x20 WSS, MPO ports C and D must be dedicated for
local add/drop channels only.
— Each add/drop port can accommodate up to 5x CCMD12s (5x12
channels) and 1 x CMD64 (64 channels) or 2xCMD44 (2x44
channels) up to 128 channels (120 channels for CCMD12 only).
— Use FIM Type 5 only if the degree expands to more than one.
— Figure 4-61 on page 4-190Use FIM Type 6 only if the degree expands
to more than five.
• Two-degree ROADM configuration—see Figure 4-57 on page 4-186 and
note the following:
— A single FIM Type 4 can be used for 2x degrees to have fulfill
add/drop channels per degree
— Use FIM Type 5 to interconnect degree 1 and 2.
— Figure 4-57 on page 4-186 shows configuration using CCMD12s
only. Configurations using CMD64s or CMD44s use same FIM
configurations.
Step Action
Figure 4-54
Configuration example—basic ROADM configuration with possible expansion (CCMD12)
SR A
COPM Raman
OSC OSC
OTDR
Line OTS-1
L A
X
S S
W
Common Common
0
-2
Out In
Twin 1x20 WSS
FIM Type 6
FIM Type 5
MPO MPO MPO MPO MPO
60 Ch’s 60 Ch’s
FIM Type 4
CCMD12
#1
Σ Σ
CCMD12
#10
Σ Σ
Figure 4-55
Configuration example—basic ROADM configuration with possible expansion (CCMD12 and
CMD64 75 GHz)
Figure 4-56
Configuration example—basic ROADM configuration with possible expansion (CCMD12 and
CMD44)
Figure 4-57
Configuration example—two-degree ROADM
Figure 4-58
Configuration example—two-degree ROADM with possible future expansion
SR A
SR A
COPM Raman COPM Raman
OSC OSC OSC OSC
OTDR OTDR
Line OTS-1
Line OTS-2
L A
L A
X
X
S S
S S
W
W
Common Common Common Common
0
-2
0
-2
Out In Out In
Twin 1x20 WSS Twin 1x20 WSS
FIM Type 6
FIM Type 5
MPO MPO MPO MPO MPO
60 Ch’s 60 Ch’s
60 Ch’s
MPO MPO MPO MPO
60 Ch’s Deg # 6 to Deg # 7 to Deg # 8 to Deg # 9 to Deg # 10 to
Deg 1-5 Deg 1-5 Deg 1-5 Deg 1-5 Deg 1-5
FIM Type 4
CCMD12 CCMD12
#1 #1
Σ Σ Σ Σ
CCMD12 CCMD12
#10 #10
Σ Σ Σ Σ
Release 13.0
SR A
SR A
SR A
SR A
COPM Raman COPM Raman COPM Raman COPM Raman
OSC OSC OSC OSC OSC OSC OSC OSC
OTDR OTDR OTDR OTDR
L A
X
L A
X
L A
X
L A
X
S S
W
-0
2
S S
W
0
-2
S S
W
0
-2
S S
W
Out In Out In Out In
0
-2 Out In
Twin 1x20 WSS Twin 1x20 WSS Twin 1x20 WSS Twin 1x20 WSS
To Degree 1-5
To Degree 1-5
To Degree 1-5
MPO
P MPO MPO
P MPO MPO
FIM Type 5
60 Ch’s 60 Ch’s 60 Ch’s
60 Ch’s 60 Ch’s
MPO MPO MPO MPO
60 Ch’s MPO MPO MPO MPO
60 Ch’s
Σ Σ Σ Σ Σ Σ Σ Σ
Σ Σ Σ Σ Σ Σ Σ Σ
Configuration example—four-degree ROADM with full-fill per degree with two FIM Type 4 and one
June 2019
Commissioning and Testing
323-1851-221 Standard Issue 3
Photonic layer site testing procedures 4-189
Figure 4-60
Configuration example—five to ten-degree expansion
Line OTS-1
S S
W X
L A SR A
-2
MPO
OSC
Out
Common
MPO
COPM
MPO
5
FI M
Raman
OTDR
OSC
MPO
In
Common
MPO
MPO
MPO
Line OTS-5
MPO
S S
W X
L A SR A
-2
Twin 1x20 WSS
0
MPO
MPO
OSC
Out
Common
MPO
COPM
FIM 6
MPO
x5
5
FI M
Raman
OTDR
MPO
MPO
OSC
In
Common
MPO
MPO
MPO
Line OTS-6
MPO
MPO
S S
W X
L A SR A
-2
Twin 1x20 WSS
0
MPO
MPO
MPO
OSC
Out
Common
MPO
MPO
MPO
COPM
MPO
Raman
OTDR
OSC
In
Common
5
FI M
MPO
MPO
MPO
Line OTS-10
MPO
S S
W X
L A SR A
-2
Twin 1x20 WSS
0
MPO
MPO
OSC
Out
Common
MPO
MPO
COPM
MPO
Raman
OTDR
OSC
In
Common
MPO
June 2019
Configuration example—full-filled ten-degree ROADM (supported up to 8-way in this release)
SR A
SR A
SR A
SR A
Line OTS-10
Line OTS-6
Line OTS-1
Line OTS-5
L A
L A
L A
L A
X
X
S S
S S
S S
S S
W
W
0
-2
0
-2
0
-2
0
-2
Release 13.0
Figure 4-61
Photonic layer site testing procedures 4-191
Figure 4-62
Configuration example—CCMD12 connected to 1x20 WSS and using OPS
Procedure 4-15
Testing Colorless Direct Attach configurations
(CCMD12/CMD44/CMD64 connected to 1x20 WSS)
Use this procedure to test Colorless Direct Attach configurations
(CCMD12/CMD44/CMD64 connected to 1x20 WSS, with or without OPS),
where light from transmitting subtending equipment is available. This test
verifies the optical continuity and checks for reflection-related problems. This
procedure does not optimize the channels for traffic.
To test:
• Colorless OADM configurations (made up of a DIA OTS and a COADM
OTS), see Procedure 4-12, “Testing a Colorless OADM configuration”
• Colorless Direct Attach configurations (COADM OTS connected to 1x9 or
1x2 WSS), see Procedure 4-13, “Connecting intra-site fibers and testing a
Colorless Direct Attach configuration (COADM OTS connected to 1x9 or
1x2 WSS)”
These configurations use MPO cables and connectors. For steps to:
• connect MPO cables, see the Installation technical publication specific to
the respective 6500 shelf type (in the procedure on routing fiber-optic
cables and electrical cables to circuit packs in the 6500 shelf)
• inspect and clean MPO connectors, see Installation - General Information,
323-1851-201.0
CAUTION
Risk of affecting performance
You must inspect and clean the MPO connectors after
removing the MPO cable from its original packaging or if the
MPO cable has been removed from the faceplate for any
reason.
Prerequisites
• This procedure allows you to perform optical continuity testing through all
the equipment associated with one OTS. Full traffic continuity testing can
proceed only after the system is complete. It is recommended that you
perform the continuity test with at least one service layer source for each
installed CMD.
• If no transmitter is available, you cannot perform this procedure.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
DANGER
Risk of injury
For a FIM Type 4 module and to respect the 1M laser safety
limit on the aggregate MPO output, the individual input
powers to the LC ports must be <=13 dBm.
Step Action
Step Action
Step Action
CAUTION
Risk of affecting performance
You must inspect and clean the MPO connectors after
removing the MPO cable from its original packaging or
if the MPO cable has been removed from the faceplate
for any reason.
Step Action
18 In Site Manager, using the Protection Status screen, select the appropriate
Shelf and OPTMON OPS Facility and then operate a Lockout on the
protection member to make the OPS SW1 active.
This allows the optical manual loopback test to be performed between the
transmitter/receiver, through the OPS, to the CCMD12 connected on the OPS
SW1 path.
19 Perform step 22 to step 26, then release the Lockout on the Protection path.
20 In Site Manager, using the Protection Status screen, select the appropriate
Shelf and OPTMON OPS Facility, then operate a Forced switch on the
working member to make the OPS SW2 active.
This allows the optical manual loopback test to be performed between the
transmitter/receiver, through the OPS, to the CCMD12 connected on the OPS
SW2 path.
21 Perform step 22 to step 26, then release the Forced switch on the Working
path. Then go to step 32.
Figure 4-63
CDA—testing with transponder loopback (example not using OPS)
Step Action
CAUTION
Risk of affecting performance
You must inspect and clean the MPO connectors after
removing the MPO cable from its original packaging or
if the MPO cable has been removed from the faceplate
for any reason.
24 If excessive losses are detected, clean and inspect the optical connectors.
(See Table 4-11 on page 4-199 for maximum CCMD12 and WSS Flex
C-Band w/OPM 20x1 loss values and Table 4-12 on page 4-200 for maximum
FIM loss values.)
25 If the problem persists, replace the faulty component. Refer to the appropriate
procedure in Fault Management - Module Replacement, 323-1851-545.
26 If alarms are raised, see Fault Management - Alarm Clearing, 323-1851-543
for the procedures on how to clear the respective alarms.
Table 4-11
CCMD12 and WSS Flex C-Band w/OPM 20x1 maximum loss
Unit PEC Max Mux loss (dB) Max Demux loss (dB)
WSS Flex C-Band w/OPM 20x1 NTK553MA 8.2 8.2
CCMD12 NTK508FAE5 17 17
Step Action
Table 4-12
Fiber Interconnect Modules (FIM) maximum loss
Module PEC Maximum insertion loss Maximum insertion loss
Add or Drop: Add or Drop:
MPO-MPO connections MPO-LC connections
FIM Type 4 NTK504CD not applicable 1.1 dB
FIM Type 5 NTK504CE 1.4 dB 1.1 dB
FIM Type 6 NTK504CF 1.4 dB not applicable
Step Action
29 Retrieve the transmitter power (OPT-OCH from the OTM/PTP facility) and the
power into amplifier Line B input port (AMP OPIN-OTS).
The typical delta in measured power levels should be less than:
• CMD64: 5 dB +/- 1 dB
• CMD44/BMD2: 9 dB +/- 1 dB
• eCMD44/BMD2: 9 dB +/- 1 dB
• CMD44: 6 dB +/- 1 dB
• eCMD44: 6 dB +/- 1 dB
30 Retrieve the amplifier Line B output port (AMP OPUT-OTS) and the power
into WSS switch port input (WSS OPTMON PM). The expected fiber loss
should be less than 1.1 dB (as in Table 4-12 for FIM4).
31 Repeat step 27 to step 30 for each CMD44/CMD64.
Validating the fibering to the output of the line facing circuit pack
32 Select one degree for the following sequence of testing steps. (You will repeat
the steps for each degree.)
33 On the transponder connected to the CCMD12/CMD44/CMD64 with which
you are testing:
• If you can adjust the output power of the transmitter, set it to maximum.
• Set a power meter to measure the transmitter output power and connect
the transmitter to the appropriate CCMD12/CMD44/CMD64 port.
34 Provision a photonic connection (you can select any wavelength for CCMD12
or the appropriate wavelength for CMD44/CMD64) from the
CCMD12/CMD44/CMD64 input port where the transponder is connected to
the output port of the line facing circuit pack. See the procedure on adding a
photonic connection in Part 1 of Configuration - Bandwidth and Data
Services, 323-1851-320.
35 Using patch cords that are known to be in good condition, put an optical
loopback with the appropriate padding between the line facing circuit pack
Line B Out (port 5) and the line facing circuit pack Line A In (port 8).
36 Select the amount of padding based on circuit pack type.
If the line facing circuit pack is Then use
MLA3 20 dB
SRA/ESAM/SAM 20 dB
Step Action
39 If the line facing circuit pack is an MLA3, perform this step on the line facing
circuit pack (MLA3).
a. Edit the Line B AMP facility (AMP-<shelf>-<slot>-6) to set the target gain
to 17 dB:
— In the Equipment & Facility Provisioning application, select the
appropriate photonic shelf from the Shelf drop-down list and select
the LIM in the equipment table.
— Select AMP from the Facility Type drop-down list and select
AMP-<shelf>-<slot>-6 in the facility table.
— Click Edit.
— Record the current Target Gain value. (You will revert to it at the end
of this procedure.)
— In the Edit AMP facility dialog, enter 17.00 in the Target Gain field
then click OK.
b. Verify the ORL at Line B output:
— In the Performance Monitoring application, select the appropriate
photonic shelf from the Shelf drop-down list.
— For non-MLA2 w/VOA, select the AMP Type and the facility
AMP-<shelf>-<slot>-6 from the Facility drop down list.
— For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-5 from the Facility drop down list.
— Click Start Monitoring.
— In the PM table, read the Untimed ORL-OTS value.
Step Action
— If the value is lower than 28 dB, clean all the optical connections from
the Line B output port to the input of the pad. When DSCMs are used
and the DSCM location is at the head end of the span (collocated with
the amplifier being commissioned), the minimum ORL threshold to
meet or exceed is 24 dB.
40 If the line facing circuit pack is an MLA3, perform this step on the line facing
circuit pack (MLA3).
a. Edit the Line A AMP facility (AMP-<shelf>-<slot>-8) to set the target gain
to 20 dB:
— In the Equipment & Facility Provisioning application, select the
appropriate photonic shelf from the Shelf drop-down list and select
the LIM in the equipment table.
— Select AMP from the Facility Type drop-down list and select
AMP-<shelf>-<slot>-8 in the facility table.
— Click Edit.
— Record the current Target Gain value. (You will revert to it later in this
procedure.)
— In the Edit AMP facility dialog, enter 20.00 in the Target Gain field
then click OK.
b. Verify the ORL at Line A output:
— In the Performance Monitoring application, select the appropriate
photonic shelf from the Shelf drop-down list.
— For non-MLA2 w/VOA, select the AMP Type and the facility
AMP-<shelf>-<slot>-8 from the Facility drop down list.
— For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-7 from the Facility drop down list.
— Click Start Monitoring.
— In the PM table, read the Untimed ORL-OTS value.
— If the value is lower than 28 dB (24 dB when a DSCM is placed after
the amplifier output), clean all the optical connections from the Line A
output port to the input of the CCMD12/CMD44/CMD64.
Go to step 43.
41 If an XLA is present, perform the following on the XLA:
a. Edit the Line B AMP facility (AMP-<shelf>-<slot>-6) to set the target gain
to 20 dB and the Gain Mode to HIGH (You will be instructed to set the XLA
AMP facility OOS to modify the Gain Mode.):
— In the Equipment & Facility Provisioning application, select the
appropriate photonic shelf from the Shelf drop-down list and select
the XLA in the equipment table.
— Select AMP from the Facility Type drop-down list and select
AMP-<shelf>-<slot>-6 in the facility table.
Step Action
— Click Edit.
— Record the Line B AMP facility Gain Mode value and the Target Gain
value. (You will revert to them at the end of this procedure.)
— In the Edit AMP facility dialog:
•Set the primary state to out of service (OOS).
•Set the Gain Mode to HIGH.
•Enter 20.00 in the Target Gain field.
•Click Apply.
— In the Edit AMP facility dialog:
•Set the primary state back to in service (IS).
•Click OK.
b. Verify the ORL at Line B output:
— In the Performance Monitoring application, select the appropriate
photonic shelf from the Shelf drop-down list.
— Select the AMP Type and the facility AMP-<shelf>-<slot>-6 from the
Facility drop down list.
— Click Start Monitoring.
— In the PM table, read the Untimed ORL-OTS value.
— If the value is lower than 28 dB, clean all the optical connections from
the Line B output port to the input of the pad. When DSCMs are used
and the DSCM location is at the head end of the span (collocated with
the amplifier being commissioned), the minimum ORL threshold to
meet or exceed is 24 dB.
c. Edit the Line A AMP facility (AMP-<shelf>-<slot>-8) to set the target gain
to 20 dB and the Gain Mode to HIGH:
— In the Equipment & Facility Provisioning application, select the
appropriate photonic shelf from the Shelf drop-down list and select
the XLA in the equipment table.
— Select AMP from the Facility Type drop-down list and select
AMP-<shelf>-<slot>-8 in the facility table.
— Click Edit.
— Record the Line A AMP facility Gain Mode value and the Target Gain
value. (You will revert to them at the end of this procedure.)
— In the Edit AMP facility dialog:
•Set the primary state to out of service (OOS).
•Set the Gain Mode to HIGH.
•Enter 20.00 in the Target Gain field.
•Click Apply.
Step Action
Step Action
c. Calculate the difference of the power read in substep b and the power
recorded in step 42. The difference should be approximately 17 dB.
d. If the power difference is 19 dB or higher (for an MLA3 or XLA), clean and
verify the patch cord and the connectors between the Line A Mon (port 2)
and the OPM Monitor 2 port.
e. If you cannot correct the loss, contact your next level of support.
44 To verify that the fiber connections are correct and the power from the correct
port is being measured, temporarily disconnect the fiber between AMP
monitor port 2 to WSS OPM monitor port 2.
If the reading on the WSSOPM Then the fibers are
OPTMON facility indicates
no power connected correctly. Reconnect
the removed fiber and go to the
next step.
there is still power connected incorrectly. Swap the
fiber connections and repeat
from step 43.
45 Read the total power going to the WSS OPM Monitor 1 port (port 1) by
retrieving the untimed OPR-OTS PM value the WSSOPM OPTMON facility:
a. Select Performance -> Performance Monitoring -> New.
b. Select the WSSOPM type and the facility OPTMON-<shelf>-<WSS
slot>-1. Click Start Monitoring. Read the Untimed OPR-OTS value.
46 Use the PM feature as follows to verify that the power going to the OPM is
approximately 17 dB (for an MLA3 or XLA) lower than the power at the Line
B out (port 5).
If Then use the PM feature on the
an XLA is present XLA
otherwise line facing circuit pack
Step Action
e. If you cannot correct the loss, contact your next level of support.
47 To verify that the fiber connections are correct and the power from the correct
port is being measured, temporarily disconnect the fiber between AMP
monitor port 1 to WSS OPM monitor port 1.
If the reading on the WSSOPM Then the fibers are
OPTMON facility indicates
no power connected correctly. Reconnect
the removed fiber and go to the
next step.
there is still power connected incorrectly. Swap the
fiber connections and repeat
from step 43.
48 Ensure that all LOS alarms on the WSS OPM are cleared.
Restoring the settings on the degree after testing
49 Select your step.
If Then
the line facing circuit set the respective MLA3 Target Gain values back to
pack is an MLA3 the values you recorded in step 39 (MLA3 Line B) and
step 40 (MLA3 Line A)
an XLA is present set the XLA AMP facilities to OOS, then set the XLA
Gain Mode and Target Gain back to the values you
recorded in step 41 for the XLA Line B and Line A,
respectively. Set the facilities back to IS.
Procedure 4-16
Testing a line amplifier node
Use this procedure to test a Line Amplifier node.
With no input connected, the pre-amplifier is set to the no shutoff mode (by
setting the ALSO Disabled parameter to True). In the no shutoff mode the
amplifier transmits an amplified spontaneous emission (ASE) broadband
noise that can be used to measure the reflectance and the loss of the
mid-stage connections.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Prerequisites
There should be no line fibers connected. The only fibers connected are the
intra-NE fibers.
Figure 4-64
Overview of Line Amplifier node testing for configurations using SLA/MLAx and LIM circuit packs
Figure 4-65
Overview of Line Amplifier node testing for configurations using
SRA/ESAM/SAM+XLA+SRA/ESAM/SAM circuit packs
Dir. 2
B B A
SRA/ SRA/
ESAM/ ESAM/
XLA
SAM SAM
1 2
A A B
Dir. 1
Legend
= Attenuator
= DSCM
Figure 4-66
Overview of Line Amplifier node testing for configurations using ESAM+MLAx+ESAM circuit
packs
Figure 4-67
Overview of Line Amplifier node testing for configurations using ESAM+MLAx+MLAx+ESAM
circuit packs
Figure 4-68
Overview of Line Amplifier node testing for configurations using ESAM+MLAx+MLAx circuit
packs
Step Action
Step Action
Step Action
13 Using PM, observe the ORL at the output of the Line A amplifier facility of line
facing circuit pack 1.
• Select Performance->Performance Monitoring-> New to open the PM
screen.
• For non-MLA2 w/VOA, select the AMP Type and the facility
AMP-<shelf>-<slot>-8 from the Facility drop down list.
• For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-7 from the Facility drop down list.
• Click Start Monitoring.
• Review the ORL-OTS Untimed parameter. The measurement in the
Untimed bin should be greater than 28 dB. When DSCMs are placed after
the amplifier output, the ORL value should be greater than 24 dB.
If the reading is less than the minimum ORL required, clean all fiber
connections at the amplifier output (including connections to a DSCM)
and verify that the patch fiber and attenuator are clean and in good
working order.
• If cleaning fiber connections does not correct reflectance problems,
contact your next level of support.
14 In the Performance Monitoring window:
• For non-MLA2 w/VOA, select the AMP Type and the facility
AMP-<shelf>-<slot>-8 from the Facility drop down list.
• For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-7 from the Facility drop down list.
• Record the OPOUT-OTS Untimed parameter.
15 Select your next step.
If line facing circuit pack 2 is Then go to
MLA, MLA2, MLA2 w/VOA, or MLA3 step 16
SLA or LIM step 17
Step Action
16 In Site Manager, select the appropriate LIM from the Equipment and Facilities
Provisioning window.
• Ensure the Primary State of the Line B amplifier of line facing circuit pack
2 is not OOS-AUMA.
• Select Performance -> Performance Monitoring ->New.
• Select the MLA/MLA2/MLA2 w/VOA/MLA3 Line B AMP facility of line
facing circuit pack 2 (AMP-<shelf>-<slot>-6) from the Facility drop down
list.
• Click Start Monitoring.
• Record the OPIN-OTS Untimed parameter.
• Calculate the mid-stage loss:
Mid-stage loss = <Line A output power (dBm) read in step 14> - <adjacent
Line B input power (dBm) read in this step>
• Compare the mid-stage loss with the expected range by adding up the
pad and DSCM loss as indicated in Table 4-5 on page 4-109. If the loss
falls below this range, increase the pad attenuation. If the loss exceeds
this range, clean and inspect all connectors and patch cords in the
mid-stage access, then go to step 23.
17 In the Performance Monitoring window,
• Select the OPTMON facility associated with port 6 of line facing circuit
pack 2 (OPTMON-<shelf>-<slot>-6).
• Click Start Monitoring.
• Record the OPR-OTS Untimed parameter.
• Calculate the mid-stage loss:
Mid-stage loss = <Line A output power (dBm) read in step 14> - <adjacent
Line B input power (dBm) read in this step>.
• Compare the mid-stage loss with the expected range by adding up the
pad and DSCM loss as indicated in Table 4-5 on page 4-109. If the loss
falls below this range, increase the pad attenuation. If the loss exceeds
this range, clean and inspect all connectors and patch cords in the
mid-stage access.
18 Select your next step.
If line facing circuit pack 2 is Then go to
SLA, MLA, MLA2, MLA2 w/VOA, or MLA3 step 23
LIM step 19
Step Action
Testing mid-stage loss in direction 2 if line facing circuit pack 2 is a LIM circuit pack
19 In the Performance Monitoring window, select the OPTMON Type and the
facility for the LIM of line facing circuit pack 2 (OPTMON-<shelf>-<slot>-8)
from the Facility drop down list. Record the OPR-OTS Untimed parameter.
20 Select your next step.
If line facing circuit pack 1 is Then go to
MLA, MLA2, MLA2 w/VOA, or MLA3 step 21
SLA step 22
21 In Site Manager, select the appropriate LIM from the Equipment and Facilities
Provisioning window.
• Ensure the Primary State of the Line B amplifier of line facing circuit pack
1 is not OOS-AUMA.
• Select Performance -> Performance Monitoring ->New.
• Select the MLA/MLA2/MLA2 w/VOA/MLA3 Line B AMP facility of line
facing circuit pack 1 (AMP-<shelf>-<slot>-6) from the Facility drop down
list.
• Click Start Monitoring.
• Record the OPIN-OTS Untimed parameter.
• Calculate the mid-stage loss:
Mid-stage loss = <Line A output power (dBm) read in step 19> - <adjacent
Line B input power (dBm) read in this step>.
• Compare the mid-stage loss with the expected range by adding up the
pad and DSCM loss as indicated in Table 4-5 on page 4-109. If the loss
falls below this range, increase the pad attenuation. If the loss exceeds
this range, clean and inspect all connectors and patch cords in the
mid-stage access, then go to step 23.
Step Action
Testing mid-stage loss in direction 2 if line facing circuit pack 2 is not a LIM circuit pack
26 If line facing circuit pack 1 is an SLA, put an optical loopback with 10-dB
padding between Line B Out (port 5) and Line A In (port 8) of line facing circuit
pack 1. If line facing circuit pack 1 is an MLA/MLA2/MLA2 w/VOA/MLA3, no
loopback is required.
Step Action
27 Put the Line A amplifier facility of line facing circuit pack 2 in no shutoff mode
as follows:
• In the Equipment & Facility Provisioning application, retrieve the facility
information of the Line A AMP facility (port 8).
• Ensure the primary state of the Line A AMP facility (port 8) is not
OOS-AUMA.
• Set the AMP facility parameter ALSO Disabled to True.
The “Automatic Shutoff Disabled” alarm is raised. If alarm correlation is
enabled, this alarm could be masked. Check the active disabled alarms.
In the no shutoff mode, the amplifier will produce broadband noise. In this
mode, the amplifier output power may be different from 9.5 dBm.
28 Using PM, observe the ORL at the output of the Line A amplifier facility of line
facing circuit pack 2.
• Select Performance->Performance Monitoring-> New to open the PM
screen.
• For non-MLA2 w/VOA, select the AMP Type and the facility
AMP-<shelf>-<slot>-8 from the Facility drop down list.
• For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-7 from the Facility drop down list.
• Click Start Monitoring.
• Review the ORL-OTS Untimed parameter. The measurement in the
Untimed bin should be greater than 28 dB. When DSCMs are placed after
the amplifier output, the ORL value should be greater than 24 dB.
If the reading is less than the minimum ORL required, clean all fiber
connections at the amplifier output (including connections to a DSCM)
and verify that the patch fiber and attenuator are clean and in good
working order.
• If cleaning fiber connections does not correct reflectance problems,
contact your next level of support.
29 In the Performance Monitoring window:
• For non-MLA2 w/VOA, select the AMP Type and the facility
AMP-<shelf>-<slot>-8 from the Facility drop down list.
• For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-7 from the Facility drop down list.
• Record the OPOUT-OTS Untimed parameter.
Step Action
31 In Site Manager, select the appropriate LIM from the Equipment and Facilities
Provisioning window.
• Ensure the Primary State of the Line B amplifier of line facing circuit pack
1 is not OOS-AUMA.
• Select Performance -> Performance Monitoring ->New.
• Select the MLA/MLA2/MLA2 w/VOA/MLA3 Line B AMP facility of line
facing circuit pack 1 (AMP-<shelf>-<slot>-6) from the Facility drop down
list.
• Click Start Monitoring.
• Record the OPIN-OTS Untimed parameter.
• Calculate the mid-stage loss:
Mid-stage loss = <Line A output power (dBm) read in step 29> - <adjacent
Line B input power (dBm) read in this step>
• Compare the mid-stage loss with the expected range by adding up the
pad and DSCM loss as indicated in Table 4-5 on page 4-109. If the loss
falls below this range, increase the pad attenuation. If the loss exceeds
this range, clean and inspect all connectors and patch cords in the
mid-stage access, then go to step 33.
32 In the Performance Monitoring window,
• Select the OPTMON facility associated with port 6 of line facing circuit
pack 1 (OPTMON-<shelf>-<slot>-6).
• Click Start Monitoring.
• Record the OPR-OTS Untimed parameter.
• Calculate the mid-stage loss:
Mid-stage loss = <Line A output power (dBm) read in step 29> - <adjacent
Line B input power (dBm) read in this step>.
• Compare the mid-stage loss with the expected range by adding up the
pad and DSCM loss as indicated in Table 4-5 on page 4-109. If the loss
falls below this range, increase the pad attenuation. If the loss exceeds
this range, clean and inspect all connectors and patch cords in the
mid-stage access.
33 Put the Line A amplifier of line facing circuit pack 2 back in normal mode by
setting the AMP facility parameter ALSO Disabled to False.
The “Automatic Shutoff Disabled” alarm clears.
Step Action
34 If line facing circuit pack 1 is an SLA, remove the loopback between Line B
Out (port 5) and the Line A In (port 8) of line facing circuit pack 1.
35 Connect all the line fibers as per EDP/IDP.
You have completed this procedure.
Testing a line amplifier node equipped with SRA/ESAM/SAM and XLA circuit packs
See Figure 4-65 on page 4-210 for an example of node testing of this
configuration. Testing starts with direction 1 by putting a loopback on
SRA/ESAM/SAM 2 and putting the XLA Line A amplifier in the no shutoff
mode. Testing completes with direction 2 by putting a loopback on
SRA/ESAM/SAM 1 and putting the XLA Line B amplifier in the no shutoff
mode.
Note: DSCMs are not supported when using SRA line facing circuit packs.
Direction 1 (Loopback on SRA/ESAM/SAM 2)
36 Put an optical loopback with 20 dB padding between Line B Out (port 5) and
Line A In (port 8) of SRA/ESAM/SAM 2.
37 Put the Line A amplifier facility of the XLA in no shutoff mode as follows:
• In the Equipment & Facility Provisioning application, retrieve the facility
information of the Line A AMP facility (port 8).
• Ensure the primary state of the Line A AMP facility (port 8) is not
OOS-AUMA.
• Set the AMP facility parameter ALSO Disabled to True.
The “Automatic Shutoff Disabled” alarm is raised. If alarm correlation is
enabled, this alarm could be masked. Check the active disabled alarms.
In the case of SRA and ESAM, the following alarms are raised:
- “Line A Input OTDR Trace High Reflection Detected”
- “Line A Input OTDR Trace High Loss Detected”
- “OTDR Trace In Progress”
This is expected behavior when the SRA/ESAM line fibers are not connected.
For detailed information on Optical Time Domain Reflectometry (OTDR),
refer to:
- the 6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA
- the chapter on OTDR trace in Configuration - Provisioning and Operating,
Part 2 of 2, 323-1851-310
- the procedures on OTDR alarms in Fault Management - Alarm Clearing,
Part 2 of 2, 323-1851-543
Step Action
Note that OTDR requires at least 20 km of optical fiber to verify the fiber for
reflection or loss. An OTDR trace run on short fiber may fail due to loss or
reflection.
The following steps require readings on the XLA. Note that the XLA power is
squelched when the OTDR trace is running. The OTDR trace must complete
before you can get a reading on the XLA.
38 Record the following XLA AMP facility parameters (you will be instructed in
step 46 to put them back to the values you are recording in this step):
• AMP Mode
• Target Power
39 After the OTDR trace has completed:
a. Put the XLA AMP facility out-of-service.
b. Set the XLA AMP facility AMP Mode to Power.
c. Set the Target Power to 9.5 dBm. (In the no shutoff mode, the amplifier
will produce broadband noise. In this mode, the amplifier output power
may be different from 9.5 dBm.)
d. Put the XLA AMP facility back in-service.
40 Using PM, observe the ORL at the output of the Line A amplifier facility of the
XLA:
• Select Performance->Performance Monitoring-> New to open the PM
screen.
• Select the AMP Type and the facility AMP-<shelf>-<slot>-8 from the
Facility drop down list.
• Click Start Monitoring.
• Review the ORL-OTS Untimed parameter. The measurement in the
Untimed bin should be greater than 28 dB. When DSCMs are placed after
the amplifier output, the ORL value should be greater than 24 dB.
If the reading is less than the minimum ORL required, clean all fiber
connections at the amplifier output (including connections to a DSCM)
and verify that the patch fiber and attenuator are clean and in good
working order.
• If cleaning fiber connections does not correct reflectance problems,
contact your next level of support.
41 In the Performance Monitoring window:
• Select the AMP Type and the facility AMP-<shelf>-<slot>-8 from the
Facility drop down list.
• Record the OPOUT-OTS Untimed parameter.
Step Action
Step Action
47 Remove the loopback between Line B Out (port 5) and the Line A In (port 8)
of SRA/ESAM/SAM 2.
48 Connect all the line fibers as per EDP/IDP.
In the case of SRA and ESAM, the following alarms clear:
- “Line A Input OTDR Trace High Reflection Detected”
- “Line A Input OTDR Trace High Loss Detected”
- “OTDR Trace In Progress”
Direction 2 (Loopback on SRA/ESAM/SAM 1)
49 Put an optical loopback with 20 dB padding between Line B Out (port 5) and
Line A In (port 8) of SRA/ESAM/SAM 1.
50 Put the Line B amplifier facility of the XLA in no shutoff mode as follows.
• In the Equipment & Facility Provisioning application, retrieve the facility
information of the Line B AMP facility (port 6).
• Ensure the primary state of the Line B AMP facility (port 6) is not
OOS-AUMA.
• Set the AMP facility parameter ALSO Disabled to True.
The “Automatic Shutoff Disabled” alarm is raised. If alarm correlation is
enabled, this alarm could be masked. Check the active disabled alarms.
In the case of SRA and ESAM, the following alarms are raised:
- “Line A Input OTDR Trace High Reflection Detected”
- “Line A Input OTDR Trace High Loss Detected”
- “OTDR Trace In Progress”
This is expected behavior when the SRA/ESAM line fibers are not connected.
For detailed information on Optical Time Domain Reflectometry (OTDR),
refer to:
- the 6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA
- the chapter on OTDR trace in Configuration - Provisioning and Operating,
Part 2 of 2, 323-1851-310
- the procedures on OTDR alarms in Fault Management - Alarm Clearing,
Part 2 of 2, 323-1851-543
Step Action
Note that OTDR requires at least 20 km of optical fiber to verify the fiber for
reflection or loss. An OTDR trace run on short fiber may fail due to loss or
reflection.
The following steps require readings on the XLA. Note that the XLA power is
squelched when the OTDR trace is running. The OTDR trace must complete
before you can get a reading on the XLA.
51 Record the following XLA AMP facility parameters (you will be instructed in
step 59 to put them back to the values you are recording in this step):
• AMP Mode
• Target Power
52 After the OTDR trace has completed:
a. Put the XLA AMP facility out-of-service.
b. Set the XLA AMP facility AMP Mode to Power.
c. Set the Target Power to 9.5 dBm. (In the no shutoff mode, the amplifier
will produce broadband noise. In this mode, the amplifier output power
may be different from 9.5 dBm.)
d. Put the XLA AMP facility back in-service.
53 Using PM, observe the ORL at the output of the Line B amplifier facility of the
XLA:
• Select Performance->Performance Monitoring-> New to open the PM
screen.
• Select the AMP Type and the facility AMP-<shelf>-<slot>-6 from the
Facility drop down list.
• Click Start Monitoring.
• Review the ORL-OTS Untimed parameter. The measurement in the
Untimed bin should be greater than 28 dB. When DSCMs are placed after
the amplifier output, the ORL value should be greater than 24 dB.
If the reading is less than the minimum ORL required, clean all fiber
connections at the amplifier output (including connections to a DSCM)
and verify that the patch fiber and attenuator are clean and in good
working order.
• If cleaning fiber connections does not correct reflectance problems,
contact your next level of support.
54 In the Performance Monitoring window:
• Select the AMP Type and the facility AMP-<shelf>-<slot>-6 from the
Facility drop down list.
• Record the OPOUT-OTS Untimed parameter.
Step Action
Step Action
60 Remove the loopback between Line B Out (port 5) and the Line A In (port 8)
of SRA/ESAM/SAM 1.
61 Connect all the line fibers as per EDP/IDP.
In the case of SRA and ESAM, the following alarms clear:
- “Line A Input OTDR Trace High Reflection Detected”
- “Line A Input OTDR Trace High Loss Detected”
- “OTDR Trace In Progress”
You have completed this procedure.
Testing a line amplifier node equipped with ESAM+MLAx+ESAM circuit packs
See Figure 4-66 on page 4-210 for an example of node testing of this
configuration. Testing starts with direction 1 by putting a loopback on ESAM 2
and putting the MLAx Line A amplifier in the no shutoff mode. Testing
completes with direction 2 by putting a loopback on ESAM 1 and putting the
MLAx Line B amplifier in the no shutoff mode.
Direction 1 (Loopback on ESAM 2)
62 Put an optical loopback with 20 dB padding between Line B Out (port 5) and
Line A In (port 8) of ESAM 2.
63 Put the Line A amplifier facility of MLAx in no shutoff mode as follows:
• In the Equipment & Facility Provisioning application, retrieve the facility
information of the Line A AMP facility (port 8).
• Ensure the primary state of the Line A AMP facility (port 8) is not
OOS-AUMA.
• Set the AMP facility parameter ALSO Disabled to True.
The “Automatic Shutoff Disabled” alarm is raised. If alarm correlation is
enabled, this alarm could be masked. Check the active disabled alarms.
For ESAM, the following alarms are raised:
- “Line A Input OTDR Trace High Reflection Detected”
- “Line A Input OTDR Trace High Loss Detected”
- “OTDR Trace In Progress”
This is expected behavior when the ESAM line fibers are not connected. For
detailed information on Optical Time Domain Reflectometer (OTDR), refer to:
- the 6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA
- the chapter on OTDR trace in Configuration - Provisioning and Operating,
Part 2 of 2, 323-1851-310
- the procedures on OTDR alarms in Fault Management - Alarm Clearing,
Part 2 of 2, 323-1851-543
Step Action
Note that OTDR requires at least 20 km of optical fiber to verify the fiber for
reflection or loss. An OTDR trace run on short fiber may fail due to loss or
reflection.
The following steps require readings on the MLAx. Note that the MLAx power
is squelched when the OTDR trace is running. The OTDR trace must
complete before you can get a reading on the MLAx.
64 Record the following MLAx Line A AMP facility parameters (you will be
instructed in step 72 to put them back to the values you are recording in this
step):
• AMP Mode
• Target Power
65 After the OTDR trace has completed:
a. Put the MLAx AMP facility out-of-service.
b. Set the MLAx AMP facility AMP Mode to Power.
c. Set the Target Power to 9.5 dBm. (In the no shutoff mode, the amplifier
will produce broadband noise. In this mode, the amplifier output power
may be different from 9.5 dBm.)
d. Put the MLAx AMP facility back in-service.
66 Using PM, observe the ORL at the output of the Line A amplifier facility of the
MLAx:
• Select Performance->Performance Monitoring-> New to open the PM
screen.
• Select the AMP Type and the facility AMP<shelf>-<slot>-8 from the
Facility drop down list.
• Click Start Monitoring.
• Review the ORL-OTS Untimed parameter. The measurement in the
Untimed bin should be greater than 28 dB. When DSCMs are placed after
the amplifier output, the ORL value should be greater than 24 dB.
If the reading is less than the minimum ORL required, clean all fiber
connections at the amplifier output (including connections to a DSCM)
and verify that the patch fiber and attenuator are clean and in good
working order.
• If cleaning fiber connections does not correct reflectance problems,
contact your next level of support.
67 In the Performance Monitoring window:
• Select the AMP Type and the facility AMP<shelf>-<slot>-8 from the
Facility drop down list.
• Record the OPOUT-OTS Untimed parameter.
Step Action
Step Action
72 Put the MLAx AMP facility parameters back to the values you recorded in step
64, as follows:
a. Put the facility out-of-service.
b. Put the AMP Mode and the Target Power of the facility back to the values
you recorded in step 64.
c. Put the facility back in-service.
73 Remove the loopback between Line B Out (port 5) and the Line A In (port 8)
of ESAM 2.
74 Connect all the line fibers as per EDP/IDP.
For ESAM, the following alarms clear:
- “Line A Input OTDR Trace High Reflection Detected”
- “Line A Input OTDR Trace High Loss Detected”
- “OTDR Trace In Progress”
Direction 2 (Loopback on ESAM 1)
75 Put an optical loopback with 20 dB padding between Line B Out (port 5) and
Line A In (port 8) of ESAM 1.
76 Put the Line B amplifier facility of MLAx in no shutoff mode as follows:
• In the Equipment & Facility Provisioning application, retrieve the facility
information of the Line A AMP facility (port 6).
• Ensure the primary state of the Line A AMP facility (port 6) is not
OOS-AUMA.
• Set the AMP facility parameter ALSO Disabled to True.
The “Automatic Shutoff Disabled” alarm is raised. If alarm correlation is
enabled, this alarm could be masked. Check the active disabled alarms.
For ESAM, the following alarms are raised:
- “Line A Input OTDR Trace High Reflection Detected”
- “Line A Input OTDR Trace High Loss Detected”
- “OTDR Trace In Progress”
This is expected behavior when the ESAM line fibers are not connected. For
detailed information on Optical Time Domain Reflectometer (OTDR), refer to:
- the 6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA
- the chapter on OTDR trace in Configuration - Provisioning and Operating,
Part 2 of 2, 323-1851-310
- the procedures on OTDR alarms in Fault Management - Alarm Clearing,
Part 2 of 2, 323-1851-543
Step Action
Note that OTDR requires at least 20 km of optical fiber to verify the fiber for
reflection or loss. An OTDR trace run on short fiber may fail due to loss or
reflection.
The following steps require readings on the MLAx. Note that the MLAx power
is squelched when the OTDR trace is running. The OTDR trace must
complete before you can get a reading on the MLAx.
77 Record the following MLAx Line A AMP facility parameters (you will be
instructed in step 85 to put them back to the values you are recording in this
step):
• AMP Mode
• Target Power
78 After the OTDR trace has completed:
a. Put the MLAx AMP facility out-of-service.
b. Set the MLAx AMP facility AMP Mode to Power.
c. Set the Target Power to 9.5 dBm. (In the no shutoff mode, the amplifier
will produce broadband noise. In this mode, the amplifier output power
may be different from 9.5 dBm.)
d. Put the MLAx AMP facility back in-service.
79 Using PM, observe the ORL at the output of the Line B amplifier facility of the
MLAx:
• Select Performance->Performance Monitoring-> New to open the PM
screen.
• Select the AMP Type and the facility AMP<shelf>-<slot>-6 from the
Facility drop down list.
• Click Start Monitoring.
• Review the ORL-OTS Untimed parameter. The measurement in the
Untimed bin should be greater than 28 dB. When DSCMs are placed after
the amplifier output, the ORL value should be greater than 24 dB.
If the reading is less than the minimum ORL required, clean all fiber
connections at the amplifier output (including connections to a DSCM)
and verify that the patch fiber and attenuator are clean and in good
working order.
• If cleaning fiber connections does not correct reflectance problems,
contact your next level of support.
80 In the Performance Monitoring window:
• Select the AMP Type and the facility AMP<shelf>-<slot>-6 from the
Facility drop down list.
• Record the OPOUT-OTS Untimed parameter.
Step Action
Step Action
85 Put the MLAx AMP facility parameters back to the values you recorded in step
77, as follows:
a. Put the facility out-of-service.
b. Put the AMP Mode and the Target Power of the facility back to the values
you recorded in step 77.
c. Put the facility back in-service.
86 Remove the loopback between Line B Out (port 5) and the Line A In (port 8)
of ESAM 1.
87 Connect all the line fibers as per EDP/IDP.
For ESAM, the following alarms clear:
- “Line A Input OTDR Trace High Reflection Detected”
- “Line A Input OTDR Trace High Loss Detected”
- “OTDR Trace In Progress”
You have completed this procedure.
Testing a line amplifier node equipped with ESAM+MLAx+MLAx+ESAM circuit packs
See Figure 4-67 on page 4-211 for an example of node testing of this
configuration. Testing starts with direction 1 by putting a loopback on ESAM 2
and putting the MLAx 1 Line A and MLAx 2 Line B amplifiers in the no shutoff
mode. Testing completes with direction 2 by putting a loopback on ESAM 1
and putting the MLAx 2 Line A and MLAx 1 Line B amplifiers in the no shutoff
mode.
Direction 1 (Loopback on ESAM 2)
88 Put an optical loopback with 20 dB padding between Line B Out (port 5) and
Line A In (port 8) of the line facing circuit pack 2 (ESAM 2).
Step Action
89 Put the Line A amplifier facility of MLAx 1 and the Line B amplifier facility of
MLAx 2 in no shutoff mode as follows:
a. In the Equipment & Facility Provisioning application, retrieve the facility
information of the Line A AMP facility (port 8).
b. Ensure the primary state of the Line A AMP facility (port 8) is not
OOS-AUMA.
c. Set the AMP facility parameter ALSO Disabled to True for the Line A
amplifier facility of MLA 1.
d. Repeat substep a to substep c for the Line B amplifier facility of MLAx 2
(port 6).
This is expected behavior when the ESAM line fibers are not connected. For
detailed information on Optical Time Domain Reflectometer (OTDR), refer to:
- the 6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA
- the chapter on OTDR trace in Configuration - Provisioning and Operating,
Part 2 of 2, 323-1851-310
- the procedures on OTDR alarms in Fault Management - Alarm Clearing,
Part 2 of 2, 323-1851-543
Note that OTDR requires at least 20 km of optical fiber to verify the fiber for
reflection or loss. An OTDR trace run on short fiber may fail due to loss or
reflection.
The following steps require readings on the MLAx. Note that the MLAx power
is squelched when the OTDR trace is running. The OTDR trace must
complete before you can get a reading on the MLAx.
Step Action
90 Record the following MLAx Line A AMP facility parameters (you will be
instructed in step 99 to put them back to the values you are recording in this
step):
• AMP Mode
• Target Power
91 After the OTDR trace has completed:
a. Put the MLAx AMP facility out-of-service.
b. Set the MLAx AMP facility AMP Mode to Power.
c. Set the Target Power to 9.5 dBm. (In the no shutoff mode, the amplifier
will produce broadband noise. In this mode, the amplifier output power
may be different from 9.5 dBm.)
d. Put the MLAx AMP facility back in-service.
92 Using PM, observe the ORL at the output of the Line A amplifier facility of
MLA 1:
• Select Performance->Performance Monitoring-> New to open the PM
screen.
• Select the AMP Type and the facility AMP<shelf>-<slot>-8 from the
Facility drop down list.
• Click Start Monitoring.
• Review the ORL-OTS Untimed parameter. The measurement in the
Untimed bin should be greater than 28 dB. When DSCMs are placed after
the amplifier output, the ORL value should be greater than 24 dB.
If the reading is less than the minimum ORL required, clean all fiber
connections at the amplifier output (including connections to a DSCM)
and verify that the patch fiber and attenuator are clean and in good
working order.
• If cleaning fiber connections does not correct reflectance problems,
contact your next level of support.
Step Action
93 Using PM, observe the ORL at the output of the Line B amplifier facility of
MLA 2:
• Select Performance->Performance Monitoring-> New to open the PM
screen.
• Select the AMP Type and the facility AMP<shelf>-<slot>-5 from the
Facility drop down list.
• Click Start Monitoring.
• Review the ORL-OTS Untimed parameter. The measurement in the
Untimed bin should be greater than 28 dB. When DSCMs are used and
the DSCM location is at the head end of the span (collocated with the
amplifier being commissioned), the minimum ORL threshold to meet or
exceed is 24 dB.
If the reading is less than the minimum ORL required, clean all fiber
connections at the amplifier output (including connections to a DSCM)
and verify that the patch fiber and attenuator are clean and in good
working order.
• If cleaning fiber connections does not correct reflectance problems,
contact your next level of support.
94 In the Performance Monitoring window:
• Select the AMP Type and the facility AMP<shelf>-<slot>-8 from the
Facility drop down list.
• Record the OPOUT-OTS Untimed parameter.
95 In the Performance Monitoring window,
• Select the OPTMON facility associated with port 6 of ESAM 2
(OPTMON<shelf>-<slot>-6).
• Click Start Monitoring.
• Record the OPR-OTS Untimed parameter.
• Calculate the loss:
Loss = <Line A output power (dBm) read in step 94> - <adjacent Line B input
power (dBm) read in this step>.
• Compare the loss with the expected range by adding up the pad and
DSCM loss as indicated in Table 4-5 on page 4-109. If the loss falls below
this range, increase the pad attenuation. If the loss exceeds this range,
clean and inspect all connectors and patch cords in the mid-stage
access.
96 In the Performance Monitoring window, select the OPTMON Type and the
facility for ESAM 2 (OPTMON<shelf>-<slot>-8) from the Facility drop down
list. Record the OPR-OTS Untimed parameter.
Step Action
Step Action
103 Put the Line A amplifier facility of MLAx 2 and the Line B amplifier facility of
MLAx 1 in no shutoff mode as follows:
a. In the Equipment & Facility Provisioning application, retrieve the facility
information of the Line A AMP facility (port 8).
b. Ensure the primary state of the Line A AMP facility (port 8) is not
OOS-AUMA.
c. Set the AMP facility parameter ALSO Disabled to True for Line A amplifier
facility of MLAx 2.
d. Repeat substep a to substep c for the Line B amplifier facility of MLAx 1
(port 6).
This is expected behavior when the ESAM line fibers are not connected. For
detailed information on Optical Time Domain Reflectometer (OTDR), refer to:
- the 6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA
- the chapter on OTDR trace in Configuration - Provisioning and Operating,
Part 2 of 2, 323-1851-310
- the procedures on OTDR alarms in Fault Management - Alarm Clearing,
Part 2 of 2, 323-1851-543
Note that OTDR requires at least 20 km of optical fiber to verify the fiber for
reflection or loss. An OTDR trace run on short fiber may fail due to loss or
reflection.
The following steps require readings on the MLAx. Note that the MLAx power
is squelched when the OTDR trace is running. The OTDR trace must
complete before you can get a reading on the MLAx.
Step Action
104 Record the following MLAx Line A AMP facility parameters (you will be
instructed in step 113 to put them back to the values you are recording in this
step):
• AMP Mode
• Target Power
105 After the OTDR trace has completed:
a. Put the MLAx AMP facility out-of-service.
b. Set the MLAx AMP facility AMP Mode to Power.
c. Set the Target Power to 9.5 dBm. (In the no shutoff mode, the amplifier
will produce broadband noise. In this mode, the amplifier output power
may be different from 9.5 dBm.)
d. Put the MLAx AMP facility back in-service.
106 Using PM, observe the ORL at the output of the Line A amplifier facility of
MLA 2:
• Select Performance->Performance Monitoring-> New to open the PM
screen.
• Select the AMP Type and the facility AMP<shelf>-<slot>-8 from the
Facility drop down list.
• Click Start Monitoring.
• Review the ORL-OTS Untimed parameter. The measurement in the
Untimed bin should be greater than 28 dB. When DSCMs are placed after
the amplifier output, the ORL value should be greater than 24 dB.
If the reading is less than the minimum ORL required, clean all fiber
connections at the amplifier output (including connections to a DSCM)
and verify that the patch fiber and attenuator are clean and in good
working order.
• If cleaning fiber connections does not correct reflectance problems,
contact your next level of support.
Step Action
107 Using PM, observe the ORL at the output of the Line B amplifier facility of
MLA 1:
• Select Performance->Performance Monitoring-> New to open the PM
screen.
• Select the AMP Type and the facility AMP<shelf>-<slot>-5 from the
Facility drop down list.
• Click Start Monitoring.
• Review the ORL-OTS Untimed parameter. The measurement in the
Untimed bin should be greater than 28 dB. When DSCMs are used and
the DSCM location is at the head end of the span (collocated with the
amplifier being commissioned), the minimum ORL threshold to meet or
exceed is 24 dB.
If the reading is less than the minimum ORL required, clean all fiber
connections at the amplifier output (including connections to a DSCM)
and verify that the patch fiber and attenuator are clean and in good
working order.
• If cleaning fiber connections does not correct reflectance problems,
contact your next level of support.
108 In the Performance Monitoring window:
• Select the AMP Type and the facility AMP<shelf>-<slot>-8 from the
Facility drop down list.
• Record the OPOUT-OTS Untimed parameter.
109 In the Performance Monitoring window,
• Select the OPTMON facility associated with port 6 of ESAM 1
(OPTMON<shelf>-<slot>-6).
• Click Start Monitoring.
• Record the OPR-OTS Untimed parameter.
• Calculate the loss:
Loss = <Line A output power (dBm) read in step 108> - <adjacent Line B input
power (dBm) read in this step>.
• Compare the loss with the expected range by adding up the pad and
DSCM loss as indicated in Table 4-5 on page 4-109. If the loss falls below
this range, increase the pad attenuation. If the loss exceeds this range,
clean and inspect all connectors and patch cords in the mid-stage
access.
110 In the Performance Monitoring window, select the OPTMON Type and the
facility for ESAM 1 (OPTMON<shelf>-<slot>-8) from the Facility drop down
list. Record the OPR-OTS Untimed parameter.
Step Action
Step Action
This is expected behavior when the ESAM line fibers are not connected. For
detailed information on Optical Time Domain Reflectometer (OTDR), refer to:
- the 6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA
- the chapter on OTDR trace in Configuration - Provisioning and Operating,
Part 2 of 2, 323-1851-310
- the procedures on OTDR alarms in Fault Management - Alarm Clearing,
Part 2 of 2, 323-1851-543
Note that OTDR requires at least 20 km of optical fiber to verify the fiber for
reflection or loss. An OTDR trace run on short fiber may fail due to loss or
reflection.
The following steps require readings on the MLAx. Note that the MLAx power
is squelched when the OTDR trace is running. The OTDR trace must
complete before you can get a reading on the MLAx.
118 Put the Line A amplifier facility of MLAx 2 in no shutoff mode.
119 Record the following MLAx 2 Line A AMP facility parameters and the MLAx 1
Line B AMP facility parameters (you will be instructed in step 127 to put them
back to the values you are recording in this step):
• AMP Mode
• Target Power
Step Action
Step Action
123 In the Performance Monitoring window, record the input power of the Line B
amplifier facility of MLAx 1 and calculate the loss at this stage.
• Select the MLAx 1 Line B AMP facility AMP-<shelf>-<slot>-6 from the
Facility drop down list.
• Click Start Monitoring.
• Record the OPIN-OTS Untimed parameter.
• Calculate the loss:
Loss = <MLAx 2 Line A output power (dBm) read in step 122> - <MLAx 1
Line B input power (dBm) read in this step>
• Compare the loss with the expected range by adding up the pad and
DSCM loss as indicated in Table 4-5 on page 4-109. If the loss falls below
this range, increase the pad attenuation. If the loss exceeds this range,
clean and inspect all connectors and patch cords in the mid-stage
access, then go to step 124.
124 Using PM, observe the ORL at the output of the Line B amplifier facility of
MLAx 1.
• Select Performance->Performance Monitoring-> New to open the PM
screen.
• Select the AMP Type and the facility AMP-<shelf>-<slot>-5 from the
Facility drop down list.
• Click Start Monitoring.
• Review the ORL-OTS Untimed parameter. The measurement in the
Untimed bin should be greater than 28 dB. When DSCMs are used and
the DSCM location is at the head end of the span (collocated with the
amplifier being commissioned), the minimum ORL threshold to meet or
exceed is 24 dB.
If the reading is less than the minimum ORL required, clean all fiber
connections at the amplifier output (including connections to a DSCM)
and verify that the patch fiber and attenuator are clean and in good
working order.
• If cleaning fiber connections does not correct reflectance problems,
contact your next level of support.
125 In the Performance Monitoring window, record the output power of the Line B
amplifier facility of MLAx 1:
• Select the MLAx 1 Line B AMP facility AMP-<shelf>-<slot>-5 from the
Facility drop down list.
• Record the OPOUT-OTS Untimed parameter.
Step Action
126 In the Performance Monitoring window, record the input power of the Line B
ESAM facility and calculate the loss at this stage.
• Select the OPTMON facility associated with port 6 of the ESAM circuit
pack (OPTMON-<shelf>-<slot>-6).
• Click Start Monitoring.
• Record the OPR-OTS Untimed parameter.
• Calculate the loss:
Loss = <Line A output power (dBm) read in step 125> - <adjacent Line B input
power (dBm) read in this step>.
• Compare the loss with the expected range by adding up the pad and
DSCM loss as indicated in Table 4-5 on page 4-109. If the loss falls below
this range, increase the pad attenuation. If the loss exceeds this range,
clean and inspect all connectors and patch cords in the mid-stage
access.
127 For each of the MLAx AMP facilities from step 119, put the facility parameters
back to the values you recorded in step 119, as follows:
a. Put the facility out-of-service.
b. Put the AMP Mode and the Target Power of the facility back to the values
you recorded in step 119.
c. Put the facility back in-service.
128 Remove the loopback fiber you placed (in step 116) between Line B Out
(port 5) and Line A In (port 8) of the ESAM circuit pack.
129 On the MLAx 1 Line B AMP facility:
• Put the facility back in normal mode by setting the facility parameter
ALSO Disabled to False (was set to True in step 117).
The “Automatic Shutoff Disabled” alarm clears.
• Set the AMP Mode to Gain.
130 On the MLAx 2 Line A AMP facility:
• Put the facility back in normal mode by setting the facility parameter
ALSO Disabled to False (was set to True in step 118).
The “Automatic Shutoff Disabled” alarm clears.
• Set the AMP Mode to Gain.
Step Action
Step Action
134 Using PM, observe the output power of the Line A amplifier facility of line
facing circuit pack 1:
• Select the AMP Type and the facility AMP-<shelf>-<slot>-8 from the
Facility drop down list.
• Record the OPOUT-OTS Untimed parameter.
135 In Site Manager, select the appropriate AMP from the Equipment and
Facilities Provisioning window.
• Ensure the Primary State of the Line B amplifier of line facing circuit pack
2 is not OOS-AUMA.
• Select Performance -> Performance Monitoring ->New.
• Select the MLAx Line B AMP facility of line facing circuit pack 2
(AMP-<shelf>-<slot>-6) from the Facility drop down list.
• Click Start Monitoring.
• Record the OPIN-OTS Untimed parameter.
• Calculate the mid-stage loss:
Mid-stage loss = <Line A output power (dBm) read in step 134> - <adjacent
Line B input power (dBm) read in this step>
• Compare the mid-stage loss with the expected range by adding up the
pad and DSCM loss as indicated in Table 4-5 on page 4-109. If the loss
falls below this range, increase the pad attenuation. If the loss exceeds
this range, clean and inspect all connectors and patch cords in the
mid-stage access.
136 Put the Line A amplifier of line facing circuit pack 1 back in normal mode by
setting the AMP facility parameter ALSO Disabled to False.
The “Automatic Shutoff Disabled” alarm is cleared.
You have completed this procedure.
—end—
Procedure 4-17
Testing DGFF nodes
Use this procedure to test a DGFF node. DGFF nodes contain two ROADM
OTS subtypes without local add/drop channels. A DGFF node can be:
• at a DOC domain boundary, or
• not at a DOC domain boundary. In this case, the DGFF node demarcates
two sections within a single DOC domain.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Prerequisites
• There should be no line fibers connected. The only fibers connected are
the intra-NE fibers.
Figure 4-69
Test setup example—OSC connectivity
Loopback Loopback
Figure 4-70
Test setup example—node continuity
Direction 1
Line B Out
fiber
Line B Out
fiber Direction 2
Step Action
Step Action
Step Action
12 Put the Line A AMP facility (port 8) of the first amplifier (amplifier 1 in Figure
4-70 on page 4-249) in no shutoff mode as follows:
a. In the Equipment & Facility Provisioning application, retrieve the facility
information.
b. Ensure the primary state of the facility is not OOS-AUMA.
c. Put the Line A AMP facility in no shutoff mode by setting the AMP facility
parameter ALSO Disabled to True.
The “Automatic Shutoff Disabled” alarm is raised. If alarm correlation is
enabled, this alarm could be masked. Check the active disabled alarms.
In the no shutoff mode, the amplifier will produce broadband noise.
13 On the Line A AMP (port 8) facility of amplifier 1:
a. Set the AMP Target Power value at its default maximum.
b. Change the AMP Mode to Power.
Step Action
19 Select the OPTMON Type and the facility for the WSS OPM Port 2 from the
Facility drop down list. Record the OPR-OTS Untimed parameter (optical
power received).
The difference between the power values recorded in step 17 and step 19
should be less than 18 dB.
20 Select Performance->PM Graphing. From the Graph Type drop down list,
select the Channel powers per port option. Select
CHMON-<sh>-<ampSlot>-7 from the Facility drop down list.
Channel powers should be visible in the PM Graphing window if the OPM is
connected correctly to the amplifier monitor port and if the OPM device is
capable of monitoring the channel optical powers.
21 On the next WSS in Direction 1:
a. Select the OPTMON Type and the facility for the WSS Switch In (Mux In)
port from the Facility drop down list (for example, select port 3 if ports 3
and 4 are connected to set up the DGFF site, as in Figure 4-70 on page
4-249).
b. Record the OPR-OTS Untimed parameter. The difference between the
power values recorded in this step (step 21) and step 18 should be less
than 12 dB.
22 Check for High Fiber Loss (HFL) alarms reported against ADJ-FIBER
facilities at the following interconnections:
• amplifier 1 port 7 to WSS 1 Common In
• WSS 1 to WSS 2
Step Action
25 Make sure all alarms against the AMP facility on port 6 or AMPMON on port 5
have cleared on amplifier 2 (for example, Input Loss of Signal, Shutoff
Threshold Crossed, Automatic Power Reduction). If the alarms have not
cleared, see the respective alarm clearing procedures in Fault Management
- Alarm Clearing, 323-1851-543.
26 Select Performance->PM Graphing. From the Graph Type drop down list,
select the Channel powers per port option. Select
CHMON-<sh>-<ampSlot>-5 from the Facility drop down list.
Channel powers should be visible in the PM Graphing window if the OPM is
connected correctly to the amplifier monitor port and if the OPM device is
capable of monitoring the channel optical powers.
Restoring settings after testing
27 On the Line B AMP facility of amplifier 2, make sure the Target Gain is set
back to minimum gain.
28 Close down the pixel you opened in step 24:
a. Select the CHC facility and click Edit.
b. In the Edit Facility CHC window, set the Opaque parameter to Yes.
c. Set the Switch Selector to 3.
d. Set the Target Loss to 18.
29 Put amplifier 1 back in auto shutoff mode by setting the Line A AMP facility
parameter ALSO Disabled to False.
The “Automatic Shutoff Disabled” alarm clears.
30 On the Line A AMP facility of amplifier 1, change the AMP Mode to Gain.
31 Repeat step 12 to step 30 for the other direction (see Figure 4-70 on page
4-249—Direction 2, amplifiers 3 and 4, respectively).
—end—
Procedure 4-18
Connecting intra-site fibers for Coherent Select sites
Use this procedure to perform intra-site fiber connections for Coherent Select
(CS) sites. In this procedure, CMD44 refers to both the regular CMD44, the
enhanced 100GHz CMD44 with isolator (eCMD44), and the enhanced
50 GHz CMD44 unless specified otherwise.
To connect intra-site fibers for configurations other than Coherent Select, see
“Connecting intra-site fibers for TOADM/ROADM/DGFF/DIA/Colorless OADM
sites” on page 4-5.
Prerequisites
• Ensure that commissioning information has been entered.
• Ensure that cables are connected between the access panel and
subtending modules (CMD, BMD2, OBB, OBMD).
• Ensure that the fibers have been cleaned and verified to be in working
condition, and the loss between fibers is not greater than 0.5 dB. The
fibers that are used in the following steps must be verified to be in good
working order prior to use. It is very important that fibers are cleaned and
scoped prior to being connected. Refer to the cleaning instructions in
Installation - General Information, 323-1851-201.0.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
Step Action
3 Connect the 2xOSC OSC-1 Out port to the OSC In (port 3) of the appropriate
line facing circuit pack (LIM [line-amp only], MLA2, MLA2 w/VOA, or MLA3).
Ensure that the OSC-1 is connected to the line facing circuit pack as indicated
in the EDP/IDP (in the correct slot).
Step Action
4 Connect the 2xOSC OSC-1 In port to the OSC Out (port 4) of the appropriate
line facing circuit pack. Ensure that the OSC-1 is connected to the line facing
circuit pack as indicated in the EDP/IDP (in the correct slot).
5 Select your next step.
If you need to fiber another OSC and are using a Then go to
single 2xOSC circuit pack configuration step 6
dual 2xOSC circuit packs configuration step 8
6 Connect the 2xOSC OSC-2 Out port to the OSC In (port 3) of the appropriate
line facing circuit pack. Ensure that the OSC-2 is connected to the line facing
circuit pack as indicated in the EDP/IDP (in the correct slot).
7 Connect the 2xOSC OSC-2 In port to the OSC Out (port 4) of the appropriate
line facing circuit pack. Ensure that the OSC-2 is connected to the line facing
circuit pack as indicated in the EDP/IDP (in the correct slot).
Go to step 10.
8 Connect the 2xOSC OSC-1 Out port of the second 2xOSC circuit pack to the
OSC In (port 3) of the appropriate line facing circuit pack. Ensure that the
OSC-1 is connected to the line facing circuit pack as indicated in the EDP/IDP
(in the correct slot).
9 Connect the 2xOSC OSC-1 In port of the second 2xOSC circuit pack to the
OSC Out (port 4) of the appropriate line facing circuit pack. Ensure that the
OSC-1 is connected to the line facing circuit pack as indicated in the EDP/IDP
(in the correct slot).
10 Select your next step.
If you are performing intra-NE fibering at a Then go to
CS line amplifier site step 11
CS Terminal - Colored site (also known as Terminal with step 14
88-channel colored Mux/Demux)
CS Terminal - Directionless site (also known as step 23
single-ended OADM 16-channel colorless and
directionless Mux/Demux)
CS OADM - Directionless site (also known as OADM step 23
16-channel colorless and directionless Mux/Demux)
CS Terminal - Directional (also known as single-ended step 32
OADM, 16+16 channel colorless and directional
Mux/Demux)
CS OADM - Directional site (also known as OADM 16+16 step 32
channel colorless and directional Mux/Demux)
Step Action
Step Action
30 Connect the Line 1 Out port (port 6) of the OBB to Line B In port (port 6) of
the amplifier.
31 Connect the Line 1 In port (port 5) of the OBB to Line A Out port (port 7) of
the amplifier.
You have completed this procedure.
Step Action
Step Action
Connecting OBB to amplifier (CS Terminal - Directional site or CS OADM - Directional site)
41 Connect the Line 2 Out port (port 12) of the OBB to Line B In port (port 6) of
the amplifier.
42 Connect the Line 2 In port (port 11) of the OBB to Line A Out port (port 7) of
the amplifier.
If this is a Then
CS Terminal - Directional site You have completed this procedure.
CS OADM - Directional site Go to step 43 to connect the other
amplifier.
43 Connect the Line 1 Out port (port 9) of the OBB to Line B In port (port 6) of
the amplifier.
44 Connect the Line 1 In port (port 10) of the OBB to Line A Out port (port 7) of
the amplifier.
You have completed this procedure.
—end—
Figure 4-71
Intra-NE fiber connections—Coherent Select line amplifier site (example shows MLA2)
Figure 4-72
Intra-NE fiber connections—Coherent Select Terminal - Colored site (example shows MLA2)
Release 13.0
2xOSC PEC: NTK554BA
OSC1 Out OSC2 Out
OSC 1 OSC 2
OSC1 In OSC2 In
COMBINER 4
OSC A Out
6 7
Line B In Line B Out
Line 1 Out Line 2 In 6 B 5
SPLITTER/COMBINER
Loc:AA Shelf:X Slot:Y
CMD1 In
CMD2 In
CMD1 Out
CMD2 Out
1 2 3 4
1
8
1
7
1
8
1
7
n
n
Common In
Common In
Common Out
Common Out
SPLITTER/COMBINER SPLITTER/COMBINER
1 In
2 In
3 In
4 In
5 In
6 In
7 In
8 In
1 In
2 In
3 In
4 In
5 In
6 In
7 In
8 In
1 Out
2 Out
3 Out
4 Out
5 Out
6 Out
7 Out
8 Out
1 Out
2 Out
3 Out
4 Out
5 Out
6 Out
7 Out
8 Out
Optical Broadband
Mux/Demux
PEC: 174-0104-900
Optical Broadband
Mux/Demux
PEC: 174-0104-900
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Intra-NE fiber connections—Coherent Select Terminal - Directionless (example shows MLA2)
June 2019
Commissioning and Testing
Photonic layer site testing procedures 4-263
Figure 4-74
Intra-NE fiber connections—Coherent Select OADM - Directionless site (example shows MLA2)
Release 13.0
OSC1 Out OSC2 Out
OSC 1 OSC 2
OSC1 In OSC2 In
SPLITTER/COMBINER SPLITTER/COMBINER 7 A 8
CMD1 In
CMD2 In
CMD3 In
CMD4 In
CMD1 Out
CMD2 Out
CMD3 Out
CMD4 Out
1 2 3 4 5 6 7 8
1
8
1
1
8
1
7
7 n
n
Common In
Common In
Common Out
Common Out
SPLITTER/COMBINER SPLITTER/COMBINER
1 In
2 In
3 In
4 In
5 In
6 In
7 In
8 In
1 In
2 In
3 In
4 In
5 In
6 In
7 In
8 In
1 Out
2 Out
3 Out
4 Out
5 Out
6 Out
7 Out
8 Out
1 Out
2 Out
3 Out
4 Out
5 Out
6 Out
7 Out
8 Out
Optical Broadband
Mux/Demux
PEC: 174-0104-900
Optical Broadband
Mux/Demux
PEC: 174-0104-900
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Intra-NE fiber connections—Coherent Select Terminal - Directional (example shows MLA2)
June 2019
Commissioning and Testing
Photonic layer site testing procedures 4-265
OSC1 In OSC2 In
Release 13.0
OSC1 In OSC2 In
5 B 6 SPLITTER/COMBINER SPLITTER/COMBINER 7 A 8
Line B Out Line B In Line A Out Line A In
CMD1 Out
CMD2 Out
CMD3 Out
CMD4 Out
4-266 Photonic layer site testing procedures
1 2 3 4 5 6 7 8
1
8
7
8
1
7
n
n
Common In
Common In
Common Out
Common Out
SPLITTER/COMBINER SPLITTER/COMBINER
1 In
2 In
3 In
4 In
5 In
6 In
7 In
8 In
1 In
2 In
3 In
4 In
5 In
6 In
7 In
8 In
1 Out
2 Out
3 Out
4 Out
5 Out
6 Out
7 Out
8 Out
1 Out
2 Out
3 Out
4 Out
5 Out
6 Out
7 Out
8 Out
Mux/Demux
PEC: 174-0104-900
Mux/Demux
PEC: 174-0104-900
Optical Broadband
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Optical Broadband 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
8
7
1
1
1
8
7
n
n
Common In
Common Out
Common In
Common Out
SPLITTER/COMBINER SPLITTER/COMBINER
1 In
2 In
3 In
4 In
5 In
6 In
7 In
8 In
1 Out
2 Out
3 Out
4 Out
5 Out
6 Out
7 Out
8 Out
1 In
2 In
3 In
4 In
5 In
6 In
7 In
8 In
Mux/Demux
PEC: 174-0104-900
Optical Broadband
1 Out
2 Out
3 Out
4 Out
5 Out
6 Out
7 Out
8 Out
Mux/Demux
PEC: 174-0104-900
Optical Broadband
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Intra-NE fiber connections—Coherent Select OADM - Directional site (example shows MLA2)
June 2019
Commissioning and Testing
323-1851-221 Standard Issue 3
Photonic layer site testing procedures 4-267
Procedure 4-19
Testing a Coherent Select line amplifier node
Use this procedure to test a Coherent Select (CS) line amplifier node. Figure
4-77 on page 4-268 illustrates an example of testing.
With no input connected, the pre-amplifier is set to the no shutoff mode. In the
no shutoff mode the amplifier transmits an amplified spontaneous emission
(ASE) broadband noise that can be used to measure the reflectance and the
loss of the mid-stage connections.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Prerequisites
There should be no line fibers connected. The only fibers connected are the
intra-NE fibers.
Figure 4-77
Overview of Coherent Select Amplifier node testing
Step Action
1 See Figure 4-77 on page 4-268 for an example of CS line amplifier node
testing. For convenience, in this procedure the circuit packs are called as
follows:
• The line facing circuit pack with the Line A amplifier (MLA2,
MLA2 w/VOA, or MLA3) is called line facing circuit pack 1.
• The LIM is called line facing circuit pack 2.
2 Launch Site Manager and log in as an admin level user.
Step Action
Step Action
11 Put the Line A amplifier facility of line facing circuit pack 1 in no shutoff mode.
• In the Equipment & Facility Provisioning application, retrieve the facility
information of the Line A AMP facility (port 8).
• Ensure the primary state of the Line A AMP facility (port 8) is not
OOS-AUMA.
• Put the Line A amplifier facility of line facing circuit pack 1 in no shutoff
mode by setting the AMP facility parameter ALSO Disabled to True.
The “Automatic Shutoff Disabled” alarm is raised. If alarm correlation is
enabled, this alarm could be masked. Check the active disabled alarms.
In the no shutoff mode, the amplifier will produce broadband noise. In this
mode, the amplifier output power may be different from 9.5 dBm.
12 Using PM, observe the ORL at the output of the Line A amplifier facility of line
facing circuit pack 1.
• Select Performance->Performance Monitoring-> New to open the PM
screen.
• For MLA2/MLA3, select the AMP Type and the facility
AMP-<shelf>-<slot>-8 from the Facility drop down list.
• For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-7 from the Facility drop down list.
• Click Start Monitoring.
• Review the ORL-OTS Untimed parameter. The measurement in the
Untimed bin should be greater than 28 dB. When DSCMs are placed after
the amplifier output, the ORL value should be greater than 24 dB.
If the reading is less than the minimum ORL required, clean all fiber
connections at the amplifier output (including connections to a DSCM)
and verify that the patch fiber and attenuator are clean and in good
working order.
• If cleaning fiber connections does not correct reflectance problems,
contact your next level of support.
13 In the Performance Monitoring window:
• For MLA2/MLA3, select the AMP Type and the facility
AMP-<shelf>-<slot>-8 from the Facility drop down list.
• For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-7 from the Facility drop down list.
• Record the OPOUT-OTS Untimed parameter.
Step Action
Step Action
17 Put the Line A amplifier of line facing circuit pack 1 back in normal mode by
setting the AMP facility parameter ALSO Disabled to False.
The “Automatic Shutoff Disabled” alarm is cleared.
18 Remove the loopback between Line B Out (port 5) and the Line A In (port 8)
of line facing circuit pack 2.
19 Connect all the line fibers as per EDP/IDP.
You have completed this procedure.
—end—
Procedure 4-20
Testing a Coherent Select Terminal - Colored node
Use this procedure to test a Coherent Select Terminal - Colored node (see
Figure 4-72 on page 4-262), where light from transmitting subtending
equipment is available. This test verifies the optical continuity and checks for
reflection-related problems. This procedure does not optimize the channels
for traffic.
Prerequisites
• This procedure allows you to perform optical continuity testing through all
the equipment associated with one OTS. Full traffic continuity testing can
proceed only after the system is complete. It is recommended that you
perform the continuity test with at least one service layer source for each
installed CMD.
• If no transmitter is available, you cannot perform this procedure.
• You must first complete the NE commissioning and fibering before
performing this procedure. Refer to:
– Chapter 2, “Nodal SLAT procedures”
– Chapter 3, “Photonic layer provisioning procedures”
– Procedure 4-18, “Connecting intra-site fibers for Coherent Select
sites”
• The fibers that are used in the following steps to connect to subtending
client equipment must be verified to be in good working order prior to use.
It is very important that client fibers are cleaned and scoped prior to being
connected. See Installation - General Information, 323-1851-201.0, for the
cleaning and inspection procedures.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Step Action
Step Action
4 In the Performance Monitoring window, select the OPTMON type and the
facility for OSC Out (port 4) on the line facing circuit pack connected to the
OSC-1 you are testing (OPTMON-<shelf>-<slot>-4). Record the OPR-OTS
Untimed parameter.
5 Calculate the coupler loss for the line facing circuit pack:
Coupler loss = <OSC output power (dBm) read in step 3> - <OSC Out power
(dBm) read in step 4>
The calculated coupler loss should be less than 3.5 dB.
If the OSC or loopback fibers are dirty, crossed or pinched, the calculated
coupler loss will be much greater than 3.5 dB. You must rectify the situation
before you continue.
6 Using an optical power meter, measure the power going to the OSC In port
from the OSC Out (port 4). This value should be roughly the same as the
power read in step 4.
7 Remove the loopback you put in step 2.
Setting up for the testing
8 Start with the Blue CMD44:
a. Choose one of the transmitters to be connected to the selected Blue
CMD44. Make sure the wavelength of the transmitter matches the
wavelength of the CMD44 port it is connected to.
b. If you can adjust the output power of transmitter, set it to maximum.
c. Using a power meter set correctly for the wavelength, measure the
transmitter output power and connect the transmitter to the appropriate
CMD44 port.
Note: No other transmitter should be connected to the network element at
this point. Make sure the receiver of the testing wavelength is not connected
to the circuit pack so as not to overload receiver port while testing.
9 Using patch cords that are known to be in good condition, put an optical
loopback with the appropriate padding between the line facing circuit pack
Line B Out port and the line facing circuit pack Line A In port. The amount of
padding shall be 20 dB (MLA2/MLA3/MLA2 w/ VOA).
10 Using the PM features, measure the power present at the Line B input of the
line facing circuit pack:
11 Calculate the loss between the CMD44 input and the Line B input port:
<power measured in step 8 (dBm)> - <power measured in step 10 (dBm)>
Step Action
12 Considering all the components present (including fixed pads and BMD2),
calculate the maximum expected loss between the CMD44 input channel port
and the Line B input port. Select the LINE B AMP facility (port 6) and record
the OPIN-OTS Untimed value.
max CMD44 mux loss (Ch<x>-In to Common Out) (see Table 4-3 on page
4-107)
+ max BMD2 mux loss (see Table 4-3 on page 4-107)
+ Fixed pad loss (if present)
+ N x 0.5 dB for each patch cord
= max expected loss =
13 If the measured loss is higher than the maximum expected loss, identify the
source of the excessive loss and make the appropriate corrections:
a. Starting with the transmitter and going toward the line facing circuit pack,
measure the input and the output of each component with a power meter.
Always clean both male connectors before closing a connection.
b. Compare the loss through each component and patch cord to the
maximum expected loss
c. When the source of the excessive loss is identified, clean and inspect the
optical connectors. If the problem persists, replace the faulty component.
Refer to the appropriate procedure in Fault Management – Module
Replacement, 323-1851-545.
14 Adjust the target gain of the Line B amplifier facility to 17 dB. Verify the ORL
at the Line B output. If the value is lower than 28 dB, clean all the optical
connections from the Line B output port to the input of the pad.
15 Adjust the target gain of the Line A amplifier facility to 20 dB. Verify the ORL
at the Line A output. If the value is lower than 28 dB, clean all the optical
connections from the Line A output port to the input of the CMD44.
16 Using the PM features, measure the power present at the Line A output of the
line facing circuit pack:
17 With a power meter, measure the power present on the CMD44 output port
that corresponds to the wavelength you are testing.
18 Calculate the loss between the line facing circuit pack Line A Out and the
CMD44 channel output port. Line A facility (port 8) AMP facility OPOUT-OTS
Untimed value:
<power measured in step 16 (dBm)> - <power measured in step 17 (dBm)>
19 Considering all the components present (including fixed pads), compute the
maximum expected loss between the Line A output and the CMD44 channel
output.
Step Action
20 If the measured loss is higher than the maximum expected loss, identify the
source of the excessive loss and make the appropriate corrections:
a. Starting with the Line A output and going toward the CMD44, measure
the input and the output of each component with a power meter. Always
clean both male connectors before closing a connection.
b. Compare the loss through each component and patch cord with the
maximum expected loss for each component.
c. When the source of the excessive loss is identified, clean and inspect the
optical connectors. If the problem persists, replace the faulty component.
Refer to the appropriate procedure in Fault Management – Module
Replacement, 323-1851-545.
21 When you have completed all testing, disconnect the test transmitter.
22 Repeat step 8 to step 21 with the Red CMD44.
23 Remove the loopback at the amplifier and reconnect the fibers as per the
EDP/IDP.
—end—
Procedure 4-21
Testing Coherent Select Directionless or Directional
nodes
Use this procedure to test the following types of Coherent Select (CS) nodes:
• Terminal - Directionless node (see Figure 4-73 on page 4-263)
• OADM - Directionless node (see Figure 4-74 on page 4-264)
• Terminal - Directional node (see Figure 4-75 on page 4-265)
• OADM - Directional node (see Figure 4-76 on page 4-266)
This test verifies the optical continuity and checks for reflection-related
problems. This procedure does not optimize the channels for traffic.
Prerequisites
• This procedure allows you to perform optical continuity testing through all
the equipment associated with one OTS. Full traffic continuity testing can
proceed only after the system is complete. It is recommended that you
perform the continuity test with at least one service layer source for each
installed Optical Broadband Mux/Demux (OBMD).
• If no transmitter is available, you cannot perform this procedure.
• You must first complete the NE commissioning and fibering before
performing this procedure. Refer to:
– Chapter 2, “Nodal SLAT procedures”
– Chapter 3, “Photonic layer provisioning procedures”
– Procedure 4-18, “Connecting intra-site fibers for Coherent Select
sites”
Step Action
• The fibers that are used in the following steps to connect to subtending
client equipment must be verified to be in good working order prior to use.
It is very important that client fibers are cleaned and scoped prior to being
connected. See Installation - General Information, 323-1851-201.0, for the
cleaning and inspection procedures.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Step Action
Step Action
4 In the Performance Monitoring window, select the OPTMON type and the
facility for OSC Out (port 4) on the line facing circuit pack connected to the
OSC-1 you are testing (OPTMON-<shelf>-<slot>-4). Record the OPR-OTS
Untimed parameter.
5 Calculate the coupler loss for the line facing circuit pack:
Coupler loss = <OSC output power (dBm) read in step 3> - <OSC Out power
(dBm) read in step 4>
The calculated coupler loss should be less than 3.5 dB.
If the OSC or loopback fibers are dirty, crossed or pinched, the calculated
coupler loss will be much greater than 3.5 dB. You must rectify the situation
before you continue.
6 Using an optical power meter, measure the power going to the OSC In port
from the OSC Out (port 4). This value should be roughly the same as the
power read in step 4.
7 Remove the loopback you put in step 2.
Setting up for the testing
8 Select the OBMD8 you want to test:
a. Start with the leftmost OBMD8.
b. Select one of the transmitters to be connected to the selected OBMD8.
Provision the transmitter to a valid wavelength.
c. If you can adjust the output power of the transmitter, set it to maximum.
d. Using a power meter set correctly for the wavelength, measure the
transmitter output power, and connect the transmitter to the appropriate
OBMD8 port.
Note 1: For Terminal - Directional or OADM - Directional nodes, perform the
following testing steps with OBB CMD1 and CMD2 ports for Line 1 and OBB
CMD3 and CMD4 ports for Line 2.
Note 2: If you are testing an OADM node, from this step on select one of the
line facing circuit packs and perform the steps using that circuit pack.
Step Action
9 Using patch cords that are known to be in good condition, put an optical
loopback with the appropriate padding between the line facing circuit pack
Line B Out port and the line facing circuit pack Line A In port.
The amount of padding must be 20 dB (MLA2/MLA3/MLA2 w/VOA).
10 Using the PM features, measure the power present at the Line B input of the
line facing circuit pack.
11 Calculate the loss between the OBMD8 input and the Line B input port:
<power measured in step 8 (dBm)> - <power measured in step 10 (dBm)>
12 Considering all the components present (including fixed pads), calculate the
maximum expected loss between the OBMD8 input channel port and the Line
B input port. Select the LINE B AMP facility (port 6) and record the OPIN-OTS
Untimed value.
max OBMD8 mux loss (Ch<x>-In to Common Out) (see Table 4-13 on
page 4-284)
+ max OBB mux loss (see Table 4-14 on page 4-284 or Table 4-15 on page
4-284, as applicable)
+ N x 0.5 dB for each patch cord
= max expected loss =
13 If the measured loss is higher than the maximum expected loss, identify the
source of the excessive loss and make the appropriate corrections:
• Starting with the transmitter and going toward the line facing circuit pack,
measure the input and the output of each component with a power meter.
Always clean both male connectors before closing a connection.
• Compare the loss through each component and patch cord to the
maximum expected loss
• When the source of the excessive loss is identified, clean and inspect the
optical connectors. If the problem persists, replace the faulty component.
Refer to the appropriate procedure in Fault Management – Module
Replacement, 323-1851-545.
14 Adjust the target gain of the Line B amplifier facility to 17 dB. Verify the ORL
at the Line B output. If the value is lower than 28 dB, clean all the optical
connections from the Line B output port to the input of the pad.
15 Adjust the target gain of the Line A amplifier facility to 20 dB. Verify the ORL
at the Line A output. If the value is lower than 28 dB, clean all the optical
connections from the Line A output port to the input of the OBMD8.
Step Action
16 Using the PM features, measure the power present at the Line A output of the
line facing circuit pack:
17 With a power meter, measure the power present on the OBMD8 output port
that corresponds to the wavelength you are testing.
18 Calculate the loss between the line facing circuit pack Line A Out and the
OBMD8 channel output port. Line A facility (port 8) AMP facility OPOUT-OTS
Untimed value:
<power measured in step 16 (dBm)> - <power measured in step 17 (dBm)>
19 Considering all the components present (including fixed pads), compute the
maximum expected loss between the Line A output and the OBMD8 channel
output.
20 If the measured loss is higher than the maximum expected loss, identify the
source of the excessive loss and make the appropriate corrections:
a. Starting with the Line A output and going toward the OBMD8, measure
the input and the output of each component with a power meter. Always
clean both male connectors before closing a connection.
b. Compare the loss through each component and patch cord with the
maximum expected loss for each component.
c. When the source of the excessive loss is identified, clean and inspect the
optical connectors. If the problem persists, replace the faulty component.
Refer to the appropriate procedure in Fault Management – Module
Replacement, 323-1851-545.
21 When you have completed all testing, disconnect the test transmitter.
22 Repeat step 8 to step 21 with the other OBMD module(s).
23 Remove the loopback at the amplifier and reconnect the fibers as per the
EDP/IDP.
24 Select your next step.
If you are testing Then
a Terminal node return the transmitter power to its
default value if you have adjusted the
output power in step 8 (substep c).
You have completed this procedure.
an OADM node (non-Terminal) go to step 25
Step Action
25 Repeat step 8 to step 23 for the second OTS. Then go to step 26.
26 In the Equipment & Facility Provisioning application:
a. Display the facility information of the Line A AMP facility (port 8) of MLA
west.
b. Place the west side MLA in no shutoff mode by setting the AMP facility
parameter ALSO Disabled to True.
The “Automatic Shutoff Disabled” alarm is raised. If alarm correlation is
enabled, this alarm could be masked. Check the active disabled alarms.
In the no shutoff mode, the amplifier will produce broadband noise. In this
mode, the amplifier output power may be different from 9.5 dBm.
c. Set the Output power to 10 dBm.
27 Use the PM function to verify the OPOUT-OTS at the Line A output by
performing the following:
a. Select Performance->Performance Monitoring-> New to open the PM
screen.
b. For non-MLA2 w/VOA, select the AMP Type and the facility
AMP-<shelf>-<slot>-8 from the Facility drop down list.
For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-7 from the Facility drop down list.
c. Click Start Monitoring.
d. Record the OPOUT-OTS Untimed parameter.
28 Read the OPIN-OTS value at Line B In of the east side MLA2 and compare
with the value read in step 27.
Delta = Line A Out – OBB Insertion Loss (see Table 4-14 on page 4-284 or
Table 4-15 on page 4-284, as applicable) – 2x 0.5 dB (patch cord)
29 If the delta calculated in step 28 is higher than 2 dB, clean fibers and check
power at each component, starting with Line A Out connection until Line B In
of the east side MLA.
30 Place the amplifier back to shutoff mode by setting the AMP facility parameter
ALSO Disabled to False.
The “Automatic Shutoff Disabled” alarm is cleared.
31 Repeat step 26 to step 30 for the other direction.
32 Return the transmitter power to its default value if you have adjusted the
output power in step 8 (substep c).
—end—
Table 4-13
Optical Broadband Mux/Demux (OBMD 1x8 C-Band) module insertion loss
optical specifications
Table 4-14
Optical Bridge and Broadcast (OBB 2x2x2 C-Band) module insertion loss
optical specifications
Table 4-15
Optical Bridge and Broadcast (OBB 2x4x1 C-Band) module insertion loss
optical specifications
Procedure 4-22
Connecting inter-NE fibers and testing the photonic
layer
Use this procedure to connect the OTS to the optical line and to perform
photonic layer testing.
To log on to remote nodes from an amplifier node, shelf IP of the remote nodes
are needed.
The fibers used in the following steps to make optical connections to the line
must be verified to be in good working order prior to use. It is very important
that the optical connectors be cleaned and scoped prior to being connected.
See Installation - General Information, 323-1851-201.0 for instructions on
inspecting and cleaning fibers.
If you need to provision the amplifiers manually to test the optical continuity
and ORL, the default gain could be too low. If the default gain is too low, set
the Pre Amp Gain Target to 20 dB. If the span loss is significantly less than
20 dB, then the Pre Amp Gain Target can be provisioned to the span loss.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Step Action
Step Action
• Verify that the fiber type is correct for the line adjacency as specified in
the EDP/IDP.
• Verify that the ADJ status is “RELIABLE”.
Note: An “Adjacency Mismatch” alarm is raised in case of a mismatch
between the Actual far end address and the Expected far end address.
8 Repeat step 7 for all NEs in the network, then go to step 9.
Checking for unexpected alarms
9 In the Active Alarms application, verify that there are no unexpected alarms
raised against the remote authentication dial in user service (RADIUS) server
visibility, if applicable.
10 If applicable, verify the status of both network timing protocol (NTP) servers,
and verify that there are no unexpected alarms raised against the NTP server
visibility.
11 Ensure that the Primary State of every AMP facility is IS (in the Edit Facility
dialog). However, when there is no light, the primary state displayed in the
facility table should be OOS-AU.
12 Verify that there are no unexpected communication, Optical Line Fail, OSC
related or Adjacency Mismatch alarms.
The system can have amplifier shutoff alarms until you add the first optical
channel.
13 Verify that there are no alarms that indicate incorrect provisioning of domain
optical control (DOC) OTSs.
The DOC Invalid Photonic Domain alarm should be cleared at this point.
14 Clear any unexpected alarms by referring to Fault Management - Alarm
Clearing, 323-1851-543 for troubleshooting.
15 Repeat step 9 to step 14 for all the NEs in the network.
Step Action
The span loss represents the loss of the OSC/TG signal from the far end Line
B output port to the near end Line A input port. The loss is measured in the
receive direction and includes the loss from the transmitter on the other side
of the line to the drop port on the local line facing circuit pack.
• The OSC/TG span loss is measured at the low wavelength edge of the
C band. The expected span loss is typically quoted at the middle of the
C band. To account for the wavelength dependent loss (WDL), subtract
0.01 dB/km (for example, for a 100 km span, subtract 1 dB) from the
reported span loss before comparing with the expected loss.
— Compare the reported loss after correcting for WDL against the
expected value from the EDP/IDP.
— Clean the fibers for the Line A input port under the following
conditions:
— If the span loss source from “OSC” is 3 dB higher than expected.
— If the span loss source from “TG” is 2 dB higher than expected.
• If the span loss measurement from either source is lower than the
expected span loss, then no further action is required.
• If the loss is still greater than expected, you may need to verify the
connections on the next network element at the other end of the line or
test the optical line to find the source of the additional attenuation.
The Rx path loss is a provisionable value that corresponds to the total loss
from the Tx to the span input and the loss from the span output to the drop
port. The relation between the actual measurement and the displayed span
loss is:
Displayed span loss = Measured loss - Rx path loss
Step Action
Step Action
20 If the line facing circuit pack is an ESAM, MLA, MLA2, MLA2 w/VOA, or
MLA3, or if an XLA is present, use the PM function to measure the optical
return loss (ORL) at the post-amplifier output by performing the following.
• Select Performance->Performance Monitoring->New to open the PM
window.
• Review the untimed ORL-OTS reading in the Performance Count(s) list.
For the post-amplifier (AMP-<shelf>-<slot>-6 for non-MLA2 w/VOA or
VOA-<shelf>-<slot>-5 for MLA2 w/VOA), the measurement in the
Untimed bin should be stable and greater than 28 dB. When DSCMs are
used and the DSCM location is at the head end of the span (collocated
with the amplifier being commissioned), the minimum ORL threshold to
meet or exceed is 24 dB.
• If the reading is stable, but less than the required threshold, clean all fiber
connections at the amplifier output and verify that any patch fibers used
are clean and have no pinches or bends.
• If the ORL reading is OOR, check if the amplifier is provisioned to IS.
21 If the line facing circuit pack is an ESAM, MLA, MLA2, MLA2 w/VOA, or
MLA3, or if an XLA is present, put the post-amplifier back to shutoff mode:
• Set the AMP facility parameter ALSO Disabled to False.
• If present, also set the ESAM/SAM OPTMON facility parameter ALSO
Disabled to False.
The “Automatic Shutoff Disabled” alarm is cleared.
Running OTDR trace (if required)
Note: OTDR traces are supported on the ESAM and SRA circuit packs.
22 Run a manual short OTDR trace, see ‘OTDR trace’ chapter in Part 2 of
Configuration - Provisioning and Operating, 323-1851-310, for details.
23 Check that the single/total losses for any events are below the thresholds.
Refer to Photonic Layer Guide, NTRN15DA, for details on the types of events
and how to interpret the OTDR traces.
Note: If the single/total losses for any events are above the thresholds, if
necessary clean the optical interface connector sleeve inside the circuit pack
and the connectors and adapters on the patch cords. Refer to the ‘Cleaning
connectors’ section in Installation - General Information, 323-1851-201.0, for
detailed cleaning procedures.
Repeat for line facing directions
24 If necessary, repeat this procedure from step 3 onwards for the other line
facing directions.
—end—
Procedure 4-23
Configuring a single span 100 GHz CMD44
point-to-point terminal
Use this procedure to configure a single span CMD44 Terminal or in an
amplified or unamplified configuration. See Figure 4-78 on page 4-293 and
Figure 4-79 on page 4-294.
Step Action
1 Add the CMD44 module. See Procedure 4-2, “Adding a new CMD44,
CMD64, or BMD2”.
2 If you are configuring Then
an amplified configuration go to step 3
otherwise go to step 10
Step Action
Release 13.0
6500 Packet-Optical Platform
LC
LC
TX LC Ch 1 In 100GHz CMD44 100GHz CMD44 LC TX
Unprotected Ch 1 In
1 1
2 2
Ch 1 Out Ch 1 Out
RX LC Ch 2 In Ch 2 In LC RX
LC 3 3 LC
4 4
Ch 2 Out LC Ch 2 Out
Common Out LC Common In
44 Channel MUX/DEMUX
44 Channel MUX/DEMUX
86 86
Ch 43 Out Ch 43 Out
LC Ch 44 In LC
Ch 44 In
87 87
88 88
Ch 44 Out Ch 44 Out
Legend
CMD44 single span point-to-point unamplified configuration
= DSCM (optional)
= Pad (optional)
June 2019
Commissioning and Testing
Photonic layer site testing procedures 4-293
Release 13.0
2x OSC NTK554BA 2x OSC NTK554BA
OSC1 Out OSC1 Out
LC LC
OSC OSC Ch1 In
44 Channel MUX/DEMUX
Ch43 Out 7 A 8 5 6 Ch43 Out
LC Line A Out Line A In Line B Out Line B In LC
Ch44 In Ch44 In
87 87
CMD44 single span point-to-point amplified configuration
88 88
Ch44 Out Ch44 Out
Legend
= DSCM (optional)
= Attenuator (optional)
June 2019
Commissioning and Testing
323-1851-221 Standard Issue 3
Photonic layer site testing procedures 4-295
Procedure 4-24
Configuring a single span OMD4/CMD44 or OMX
point-to-point terminal
Use this procedure to configure a single span OMD4/CMD44 terminal in an
amplified or unamplified configuration, or to configure a single span OMX
terminal in an unamplified configuration. See Figure 4-80 on page 4-298 to
Figure 4-82 on page 4-300.
Step Action
Step Action
Step Action
Figure 4-80
OMD4/CMD44 single span point-to-point unamplified configuration
Figure 4-81
OMD4/CMD44 single span point-to-point amplified configuration
Figure 4-82
OMX single span point-to-point unamplified configuration (4 CH OMX shown)
Procedure 4-25
Equalizing a thin terminal system
The thin terminal refers to any cascades of OMDF4/CMD44, OMDF8/BS, or
CMD44 connected to any LIM variants (LIM, SLA, and MLAx). MLAx means
MLA, MLA2, MLA2 w/VOA, or MLA3. The thin terminal is defined using the
TOADM OTS type in the new OTS provisioning model. The TOADM OTS is
used to enable a topology view of channels whose Tx/Rx adjacencies are
subsequently provisioned on channel In/Out ports.
The thin terminals are used in a standalone point to point system. Up to two
line amplifier sites are supported depending on the link budget.
CAUTION
Risk of traffic loss
The OTS provisioning for a thin terminal system includes
setting DOC to TRUE for the OTS. However, the DOC must be
put OOS and channels must be equalized manually. Refer to
6500 Packet-Optical Platform Photonic Layer Guide,
NTRN15DA, for detailed information on photonic concepts,
applications, and engineering rules.
Use this procedure to equalize a thin terminal point to point system. Typical
thin terminal systems are shown in Figure 4-83 on page 4-302. The target
power into line fiber is 0 dBm/ch.
Figure 4-83
Typical thin terminal systems
You must provision the amplifier target gain (AMP A and AMP B) to their
design flat gain (DFG) values as indicated in Table 4-16. The target gain tilt
should be left at the default value of 0 dB.
Table 4-16
Amplifier design flat gains
SLA 20 dB N/A
MLA 20 dB 17 dB
For MLA2 w/VOA, set the VOA reset required parameter of the VOA facility to
False and set the Target Loss parameter based on the calculated value for:
• downstream Z (SPAN) at Terminal and Line amplifier
• downstream Z (MID) at Line amplifier
The following is a description of the pad placement at a thin terminal site (see
Figure 4-84):
• Channel Add Pads Z(add,n) – Placed at the channel input of a channel
Mux/Demux module to provide target output power at Line B OUT. See
Table 4-17 on page 4-304 for the Line B target output power.
• SPAN Pads Z(SPAN) – Sized to set the loss between upstream Line B
OUT and local Line A In equal to the local AMP A design flat gain. See
Table 4-16 on page 4-302.
• Channel Drop Pads Z(drop,n) – Placed before the receive port of a
transponder's DWDM interface to set the channel RX power below its
overload threshold. Refer to the Technical specifications section in Part 3
of Planning, NTRN10EG, for overload threshold values of each OTR,
OCLD or pluggable module.
• 3 dB pad between Line A Out and CMD Common In – This pad is to
prevent the pre-amplifier from being triggered into APR due to back
reflections from unterminated CMD ports. The 3 dB pad is not required
with LIM circuit pack (NTK552DAE5) or if the CMD connecting to
SLA/MLAx is eCMD44 (NTT862FAE5).
Figure 4-84
Pad placement at a thin terminal site
Table 4-17
Terminal line B target output power (up to 40 channels)
Channel Count Output Power (dBm) Channel Count Output Power (dBm)
1 0.1 21 13.2
2 3.1 22 13.4
3 4.8 23 13.6
4 6.1 24 13.8
5 7.0 25 14.0
6 7.8 26 14.2
7 8.5 27 14.3
8 9.0 28 14.5
9 9.6 29 14.6
10 10 30 14.8
11 10.4 31 14.9
12 10.8 32 15.1
13 11.2 33 15.2
14 11.5 34 15.3
15 11.8 35 15.4
16 12.1 36 15.6
17 12.3 37 15.7
18 12.6 38 15.8
19 12.8 39 15.9
20 13.0 40 16.0
The following is a description of the pad placement at a line amplifier site (see
Figure 4-85 on page 4-305):
• SPAN Pads Z(SPAN) – Sized to set the loss between upstream Line B
OUT and local Line A In equal to the local AMP A design flat gain. See
Table 4-16 on page 4-302. If there is no local AMP A (LIM circuit pack),
Z(SPAN) = 0 dB (no pad).
• Midstage Pads Z(MID) – Sized to set the loss between local Line A OUT
and local Line B In equal the local AMP B design flat gain. See Table 4-16
on page 4-302.
— If there is no local AMP B (LIM or SLA circuit pack), Z(MID) = 0 dB (no
pad) with no DSCM1 or Z(MID) = 8 dB with DSCM1
— If there is no local AMP A (LIM circuit pack), Z(MID) is sized to set the
loss between the upstream Line B Out and local Line B In equal to the
local AMP B design flat gain.
Figure 4-85
Pad placement at a line amplifier site
Figure 4-86 shows a simplified thin terminal network. Only key elements
involved in the equalization process are shown.
Figure 4-86
Simplified thin terminal network for equalization purposes
Prerequisites
All actions contained in this procedure are to be executed on an OTS that was
previously created and defined.
All the equipment that are part of the OTS being worked on have all been
installed and provisioned properly.
All fibers connecting the equipment that are part of the OTS being worked on
have all been installed properly (labeled, routed, cleaned, inspected and
connected).
Fibers between the DWDM transmitters and the appropriate MUX ports have
all been labeled, routed, cleaned, inspected and connected at both ends.
Fibers that are to connect the DWDM receivers to the DEMUX port have been
labeled, routed, cleaned, inspected and connected to the DEMUX ports but
not to the receivers. Instead the ends that are to be connected to the DWDM
receivers should be protected by dust caps.
All transponder line interfaces in the design must be present with transmit
ports enabled and outputting proper optical power levels.
This procedure provides high level steps with respect to using the Site
Manager Equipment & Facility Provisioning application and the Performance
Monitoring application. Refer to Part 1 of Configuration - Provisioning and
Operating, 323-1851-310 and Fault Management - Performance Monitoring,
323-1851-520 for detailed procedures.
Step Action
Step Action
Step Action
10 At the line amplifier site, calculate the Z(SPAN) pad connected to the first line
facing amplifier.
• measure the upstream Line B OUT output power, that is, the untimed
OPOUT-OTS value for the upstream AMP-<shelf>-<slot>-6 (with AMP B)
or the untimed OPR-OTS value for the upstream
OPTMON-<shelf>-<slot>-6 (no AMP B) in the PM application
• measure the power at the local Line A In, that is, the untimed OPIN-OTS
value for the local AMP-<shelf>-<slot>-8 (with AMP A) or the untimed
OPR-OTS value for the local OPTMON-<shelf>-<slot>-8 (no AMP A) in
the PM application
• upstream span loss (dB) = upstream Line B OUT power (dBm) - local
Line A In power (dBm)
• Z(SPAN) (dB) = DFG of the first line facing amplifier (from Table 4-16 on
page 4-302) - upstream span loss (dB)
11 If the upstream amplifier is an MLA2 w/VOA, set the VOA-<shelf>-<slot>-5
facility Target Loss to Z(SPAN). Otherwise, place a fixed attenuator with a
value of Z(SPAN) at the Line A In (port 8) of the first line facing amplifier.
12 In the Equipment & Facility Provisioning application, select the LIM
equipment for the first line facing amplifier.
13 Provision the AMP-<shelf>-<slot>-8 facility.
• set the target gain to the design flat gain of the AMP as indicated in Table
4-16 on page 4-302
• set target gain tilt to 0 dB
14 If the first line facing amplifier is an MLA2 w/VOA, set the
VOA-<shelf>-<slot>-7 facility VOA Reset Required to False. Otherwise, go to
step 15.
Step Action
15 Calculate the Z(MID) pad from the first line facing amplifier to the second line
facing amplifier.
• measure the Line A OUT power, that is, the untimed OPOUT-OTS value
for the local AMP-<shelf>-<slot>-8 (with AMP A) in the PM application
If there is no local AMP A, use the upstream Line B OUT power, that is,
the untimed OPOUT-OTS value for the upstream AMP-<shelf>-<slot>-6
(with AMP B) or the untimed OPR-OTS value for the upstream
OPTMON-<shelf>-<slot>-6 (no AMP B) in the PM application.
• measure the power at the Line B In of the second line facing amplifier,
that is, the untimed OPIN-OTS value for the local AMP-<shelf>-<slot>-6
(with AMP B) in the PM application
• Midstage loss (dB) = Line A OUT power (dBm) - Line B In power (dBm)
(with local AMP A)
or
Midstage loss (dB) = upstream Line B OUT power (dBm) - local Line B In
power (dBm) (no local AMP A)
• Z(MID) (dB) = DFG of the second line facing amplifier (from Table 4-16
on page 4-302) - Midstage loss (dB)
If there is no local AMP B, Z(MID) = 0 dB (no pad) with no DSCM1 or Z(MID)
= 8 dB with DSCM1.
16 If the first line facing amplifier is an MLA2 w/VOA, provision the
VOA-<shelf>-<slot>-7 facility Target Loss to Z(MID). Otherwise, place a fixed
attenuator with a value of Z(MID) at the Line B In (port 6) of the second line
facing amplifier.
17 If the second line facing amplifier is a LIM or SLA circuit pack, go to step 21.
18 In the Equipment & Facility Provisioning application, select the LIM
equipment for the second line facing amplifier.
19 Provision the AMP-<shelf>-<slot>-6 facility.
• set the target gain to the design flat gain of the AMP as indicated in Table
4-16 on page 4-302
• set target gain tilt to 0 dB
20 If the second line facing amplifier is an MLA2 w/VOA, provision the
VOA-<shelf>-<slot>-5 facility VOA Reset Required to False. Otherwise, go to
step 21.
21 If the downstream site is another line amplifier site, repeat from step 9 for the
next line amplifier site.
22 At the far end thin terminal, if the line facing amplifier is a LIM circuit pack, go
to step 28.
Step Action
23 At the far end thin terminal site, calculate the Z(SPAN) pad.
• measure the upstream Line B OUT output power, that is, the untimed
OPOUT-OTS value for the upstream AMP-<shelf>-<slot>-6 (with AMP B)
or the untimed OPR-OTS value for the upstream
OPTMON-<shelf>-<slot>-6 (no AMP B) in the PM application
• measure the power at the local Line A In, that is, the untimed OPIN-OTS
value for the local AMP-<shelf>-<slot>-8 (with AMP A) or the untimed
OPR-OTS value for the local OPTMON-<shelf>-<slot>-8 (no AMP A) in
the PM application
• upstream span loss (dB) = upstream Line B OUT power (dBm) - local
Line A In power (dBm)
• Z(SPAN) (dB) = DFG of the line facing amplifier (from Table 4-16 on page
4-302) - upstream span loss (dB)
24 If the upstream amplifier is an MLA2 w/VOA, set the VOA-<shelf>-<slot>-5
facility Target Loss to Z(SPAN). Otherwise, place a fixed attenuator with a
value of Z(SPAN) at the Line A In (port 8) of the line facing amplifier.
25 In the Equipment & Facility Provisioning application, select the LIM
equipment for the line facing amplifier.
26 Provision the AMP-<shelf>-<slot>-8 facility.
• set the target gain to the design flat gain of the AMP as indicated in Table
4-16 on page 4-302
• set target gain tilt to 0 dB
27 If the CMD module connecting to the line facing amplifier is not an eCMD44
(NTT862FAE5), connect a 3 dB pad between Line A Out and CMD Common
In.
28 Select the appropriate pad to place at the input of each receiver. This is
Z(drop,n).
• for each channel being dropped, connect an OPM on the CMD channel
output port and measure the dropped channel power
• determine the pad required to set the power below the receiver overload
level
• repeat this step until all Z(drop, n) pads are selected
29 Repeat from step 2 for the opposite direction.
Step Action
Step Action
Table 4-18
OMDF4, OMDF8, BS5, and CMD44 typical insertion loss in the Mux direction
OMDF4
OMDF8
BS5
CMD44
Procedure 4-26
Configuring a remote CMD44 terminal
Use this procedure to configure a remote CMD44 terminal. For supported
configurations, refer to 6500 Packet-Optical Platform Photonic Layer Guide,
NTRN15DA.
Step Action
This chapter contains all the necessary procedures to turn up a passive OTS
network.
Before performing the procedures in this chapter, it is assumed that the proper
planning and engineering work has been completed. OnePlanner is a network
design and link engineering tools that support the passive OTS networks. Use
either one of these tools to complete the engineering of such network.
OnePlanner can generate reports and Visio schematics that will be used in
the execution of these procedures.
Table 5-1
Procedures in this chapter
Procedure
Table 5-1
Procedures in this chapter (continued)
Procedure
Procedure 5-13, “Turning up channels over a Passive Bridge to ROADM—one passive tail
configuration”
Procedure 5-1
Adding passive components
Use this procedure to provision passive components that are involved in the
passive OTS.
The DSCM modules that are not part of Ciena’s portfolio or have no I2C
external Ethernet connectors and the 2150 (6-slot) and 2150 (3-slot) chassis
should be provisioned to one of the virtual slots. The virtual slots are: slots 29
to 32 on a 2-slot shelf (NTK503MAE5/NAE5 variants), slots 91 to 99 on a
2-slot (NTK503LA variant), 6500-7 packet-optical, 7-slot, or 14-slot shelf, and
slots 63 to 82 on a 32-slot shelf.
In the passive OTS network, pads are not provisioned using the DSCM
equipment type (and hence not part of an OTS). Pads are provisioned using
the pad loss parameter value within the ADJ-FIBER facility of a given port as
indicated in step 42 of this procedure.
Note that in this procedure, the 2xOSC circuit pack could be the SPAP-2
w/2xOSC circuit pack if applicable.
Prerequisites
To perform this procedure you must:
• use an account with a UPC level of 3 or higher
• be logged into the network element and have the Site Manager interface
open
Step Action
Step Action
6 First, add the 2150 (6-slot) chassis, 2150 (3-slot) chassis or 6-slot passive
photonics chassis (PPC6) needed to house the passive components. The
2150 (6-slot) chassis, 2150 (3-slot) chassis or 6-slot passive photonics
chassis (PPC6) is required only if the passive configuration contains the
OSCF, OMDF4, OMDF8, or BS modules. Click Add in the Equipment area to
open the Add Equipment dialog box. In the Add Equipment dialog box, enter
the required information (as per EDPs):
• select PPC6 in the Type drop-down menu
• select the chassis type in the Provisioned PEC drop-down menu
• select the required slot number
• the State is IS by default
• click OK
7 Verify that the 2150 (6-slot) chassis, 2150 (3-slot) chassis or 6-slot passive
photonics chassis (PPC6) appears in the Equipment list.
8 Repeat from step 6 to add all the necessary 2150 (6-slot) chassis, 2150
(3-slot) chassis or 6-slot passive photonics chassis (PPC6).
Go to step 11.
9 Connect the 6-slot passive photonics chassis (PPC6) to the external slots on
the access panel using straight-through RJ-45 cables. The 6-slot passive
photonics chassis (PPC6) auto-provision.
10 Verify that the 6-slot passive photonics chassis (PPC6) appear in the
Equipment list.
Step Action
12 Add the OSC filters, the optical mux/demux filters and the band splitters
needed in your configuration (as per EDPs). Click Add in the Equipment area
to open the Add Equipment dialog box. In the Add Equipment dialog box,
enter the required information (as per EDPs):
• select in the Type drop-down menu
— OSCF for an OSC filter
— OMDF4 for a 4-channel optical mux/demux filter
— OMDF8 for an 8-channel optical mux/demux filter
— BS for a band splitter
• select the proper module in the Provisioned PEC drop-down menu
• select the required slot-subslot in the Slot drop-down menu
• the State is IS by default
• click OK
13 Verify that the filter module appears in the Equipment list.
14 Repeat from step 12 to add all the necessary filter modules.
15 Insert the filter modules in the appropriate slots of the 2150 (6-slot) chassis
or 2150 (3-slot) chassis or the 6-slot passive photonics chassis (PPC6) (as
per EDPs).
Go to step 18.
16 Insert the OSC filters, the optical mux/demux filters and the band splitters in
the appropriate slots of the 6-slot passive photonics chassis (PPC6) (as per
EDP). The passive filters auto-provision.
17 Verify that the filter modules appear in the Equipment list.
Step Action
19 Add the DSCM needed in your configuration (as per EDPs). Click Add in the
Equipment area to open the Add Equipment dialog box. In the Add Equipment
dialog box, enter the required information (as per EDPs):
• select DSCM in the Type drop-down menu
• select the proper DSCM in the Provisioned PEC drop-down menu
• select the required slot number
• the State is IS by default
• click OK
20 Verify that the DSCM appears in the Equipment list.
21 Repeat from step 19 to add all the necessary DSCMs.
Go to step 24.
22 Connect the 6500 DSCM modules to the external slots on the access panel
using straight-through RJ-45 cables. The 6500 DSCM modules
auto-provision.
23 Verify that the 6500 DSCM modules appear in the Equipment list.
24 Select your next step.
If your configuration requires Then go to
L-band MLA/LIM, FGA, and/or 2xOSC circuit packs in a step 25
shelf with auto-equipping enabled
L-band MLA/LIM, FGA, and/or 2xOSC circuit packs in a step 28
shelf with auto-equipping disabled
no L-band MLA/LIM, FGA, or 2xOSC circuit packs step 36
25 Insert the L-band MLA/LIM, FGA, and/or 2xOSC circuit packs in the
appropriate slots (as per EDP). The L-band MLA/LIM, FGA, and/or 2xOSC
circuit packs auto-provision.
26 Once the blue LED and green LED on the L-band MLA/LIM, FGA, and/or
2xOSC circuit packs turn steadily on, verify that the L-band MLA/LIM, FGA,
and/or 2xOSC circuit packs appear in the Equipment list.
Step Action
27 For the 2xOSC circuit packs, insert the required SFP modules in the
appropriate ports (as per EDP). The SFP modules auto-provision. Verify that
the SFP modules appear in the Equipment list.
Go to step 36.
28 Add the L-band MLA/LIM, FGA, and/or 2xOSC circuit packs needed in your
configuration (as per EDPs). Click Add in the Equipment area to open the
Add Equipment dialog box. In the Add Equipment dialog box, enter the
required information (as per EDPs):
• select in the Type drop-down menu
— LIM for an L-band MLA or LIM circuit pack
— FGA for an FGA circuit pack
— 2xOSC for a 2xOSC circuit pack
— SP for an SPAP-2 w/2xOSC circuit pack
• select the required slot in the Slot drop-down menu
• the State is IS by default
• click OK
29 Verify that the L-band MLA/LIM, FGA, or 2xOSC circuit pack appears in the
Equipment list.
30 Repeat from step 28 to add all the necessary L-band MLA/LIM, FGA, and/or
2xOSC circuit packs.
31 Insert the L-band MLA/LIM, FGA, and/or 2xOSC circuit packs in the
appropriate slots (as per EDP).
32 For the 2xOSC circuit packs, add the required SFP modules (as per EDPs).
Click Add in the Equipment area to open the Add Equipment dialog box. In
the Add Equipment dialog box, enter the required information (as per EDPs):
• select P155M in the Type drop-down menu
• select the proper PEC in the Provisioned PEC drop-down menu
• select the required slot-port in the Slot drop-down menu
• the State is IS by default
• click OK
33 Verify that the SFP module appears in the Equipment list.
34 Repeat from step 32 to add all the necessary SFP modules.
35 Insert the required SFP modules in the appropriate ports (as per EDP).
Step Action
37 Connect the OMX or CMD44 modules to the external slots on the access
panel using straight-through RJ-45 cables. The OMX or CMD44 modules
auto-provision.
38 Verify that the OMX or CMD44 modules appear in the Equipment list.
Go to step 42.
39 Add the OMX or CMD44 modules needed in your configuration (as per
EDPs). Click Add in the Equipment area to open the Add Equipment dialog
box. In the Add Equipment dialog box, enter the required information (as per
EDPs):
• select OMX or CMD44 in the Type drop-down menu
• select the proper OMX or CMD44 in the Provisioned PEC drop-down
menu
• select the required slot number
• the State is IS by default
• click OK
40 Verify that the OMX or CMD44 module appears in the Equipment list.
41 Repeat from step 39 to add all the necessary OMX or CMD44 modules.
42 Provision the required pad.
• Select the equipment that the pad is connected to in the Equipment list.
For a pad at the line port of a transponder, select the channel port of the
channel mux/demux that the line port is connected to.
• Select the ADJ-FIBER in the Facility Type drop-down menu.
• Select the ADJ-FIBER facility corresponds to the port where the pad is
connected in the Facility list and click Edit.
• Enter the pad value in the Pad Loss field.
• Click OK.
43 Repeat step 42 for all the required pads.
—end—
Procedure 5-2
Creating a passive OTS and defining its configuration
Use this procedure to create a passive OTS and define the position of each
component within the OTS.
Prerequisites
To perform this procedure you must:
• use an account with a UPC level of 3 or higher
• be logged into the network element and have the Site Manager interface
open
• make sure the passive components have been provisioned according to
Procedure 5-1, “Adding passive components”
• review the new OTS provisioning model concept in the overview section of
the “OTS Slot Sequencing” chapter in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310
Step Action
Procedure 5-3
Provisioning line adjacencies
Use this procedure to provision the line adjacencies for each passive OTS or
passive configuration site. The Actual Far End Address field will not be
populated.
Note: The line in and line out adjacencies must be provisioned in order
for links to be populated in OneControl.
Prerequisites
To perform this procedure you must:
• use an account with a UPC level of 3 or higher
• have the Site Manager interface open
• be logged into each network element
• make sure the passive OTS or configuration has been defined according
to Procedure 5-2, “Creating a passive OTS and defining its configuration”
Step Action
Procedure 5-4
Equalizing a passive layer network
This procedure provides an example for equalizing (or pad tuning) a passive
layer network, using the example network shown in Figure 5-1 on page 5-22.
Before deploying and turning-up any 6500 passive layer network, the output
from either the Ciena Network Designer (CND) or the OnePlanner tool must
be used to design and build the network. The Ciena account team uses the
tool to generate the equipment requirement for the network based on the
customer network requirements (that is, facility, wavelength, capacity, and
service requirements). A graphical output (in Visio format) from the tool is
used to build the network.
The tool output provides the following information that is necessary to turn-up
a 6500 passive layer network:
• Network View diagram (CND) / screen capture of the OnePlanner tool
view or Visio report (OnePlanner) – indicates the number of nodes and the
fiber type/loss specifications for the optical network interconnections
between the nodes. Figure 5-1 on page 5-22 is an example of the CND
network view for a 5-node network. OnePlanner provides a similar network
view.
• Node View diagrams (CND) / NE OTS diagrams and Fiber Run List Report
(OnePlanner) – indicate the optical interconnections for each node. The
diagrams and the report identify the fiber interconnections and potential
pad placements at each node and between nodes. These diagrams and
reports indicate all connections between the interface module ports and
the network fiber plant. Figure 5-2 on page 5-23 is an example of the CND
node view diagram for an OTS of a node. Figure 5-3 on page 5-24 is a
OnePlanner example of the NE OTS diagram. Figure 5-4 and Figure 5-5
on page 5-25 illustrate an excerpt from the OnePlanner Fiber Run List
Report for the example in Figure 5-3 on page 5-24.
• Power Level reports (CND) / Passive Provisioning grid and DWDM
Adjacencies grid (OnePlanner) – indicate the optical channel power
values for the DWDM ports within each node. This tool output identifies the
channel and/or network power levels that should be achieved. The power
levels are achieved in a passive layer network by manual pad placement.
Figure 5-6 on page 5-26 is an example of the tabular power report for a
node. In OnePlanner, the information can be exported from the Passive
Provisioning and DWDM Adjacencies grids (see Passive Provisioning
example in Figure 5-7 and Figure 5-8 on page 5-27, and DWDM
Adjacencies example in Figure 5-9 on page 5-28, Figure 5-10 on page
5-29, Figure 5-11 on page 5-29, and Figure 5-12 on page 5-30).
• Rack View diagrams (CND only) – indicate how the 2150 (6-slot), 2150
(3-slot) or PPC6 shelves and other ancillary equipment (filters, DSCMs,
and so on) are populated at each node. These diagrams also identify the
SFP/XFP requirements for each node.
The CND and OnePlanner Visio output examples provided in Figure 5-1 on
page 5-22, Figure 5-2 on page 5-23, and Figure 5-3 on page 5-24 are for
network-level turn-up and test explanation purposes only. The example
network is intended to capture some of the standard network configuration
concepts present in actual deployments. Understanding the concepts
contained in these network-level diagrams and in the subsequent
network-level turn-up description allows this information to be adapted for any
network configuration. For special network-level configurations not described
in this section, contact the Ciena account team for additional information.
In Figure 5-1 on page 5-22 (CND) (the OnePlanner network view is similar),
five 6500 nodes are connected in an end-to-end configuration. Included in this
diagram are the span fiber characteristics and the open or closed type of
node, where an open (or Zero Pass Through, ZPT) node contains all add/drop
traffic with no pass-through (express) traffic, and a closed node may contain
add/drop traffic but always contains pass-through (express) traffic. The step
number marked up in the diagram refers to the step number in this procedure.
The OTS TX and OTS RX terminology is explained in Figure 5-13 on page
5-31.
The Node View diagram, provided by CND as shown in Figure 5-2 on page
5-23, indicates the optical connections that are made between the different
chassis, ancillary equipment (that is, the FGAs, DSCMs, filters, and band
splitters), and span fiber at each node. The connection detail is provided to the
port level. The suggested need and recommended location of optical
attenuators is also shown on the diagram, if applicable. This information is
provided by OnePlanner as shown in Figure 5-3 on page 5-24, Figure 5-4 on
page 5-25, and Figure 5-5 on page 5-25.
The CND Power Level report, as shown in Figure 5-6 on page 5-26, contains
target channel power levels (average, maximum and minimum) for the
following points within a 6500 passive layer node:
• FGA input
• Network Fiber Launch output
• Transponder Receiver input
Transponder Receiver Input targets and suggested starting pad values are
provided in the OnePlanner DWDM Adjacencies grid.
The target channel power levels called out in the CND Power Level report or
the OnePlanner grids are realized at installation time by the channel
equalization procedure (this procedure as an example), which is a process for
installing pads and manual adjustment (that is, “tuning”) of the pad values with
appropriate test equipment and test points. Therefore, equalizing sometimes
is also called pad tuning.
6500 passive layer networks use generic pad placements for the channel
equalization procedure. The following is a description of these pad
placements (refer to Figure 5-14 on page 5-32):
• FGA Overload Pads Z(FGA) – Placed at a FGA-RX (pre-amplifier) input to
ensure the FGA output does not saturate before full channel count
loading. When a DSCM precedes the FGA, then the pad is placed before
the DSCM.
Within a node, pad values are installed and “tuned” starting upstream and
progressing downstream in the signal direction. Each pad value is chosen so
that all channel powers measurements at the reference point indicated in
Table 5-2 on page 5-17 are as close to the average design value as possible,
while ensuring that they are within the maximum and minimum thresholds
defined in the CND Power Level report or the OnePlanner grids.
The 6500 OTS and topology software allows almost any placement of the
different components (for example, DSCM, pads, etc.) in a passive photonic
system. However, the CND and OnePlanner design tools determine the
placement of the different components (for example, DSCM, pads, etc.) in a
passive photonic system that is a smaller subset of what the 6500 software
allows. See Figure 5-14 on page 5-32 for CND or OnePlanner tool possible
component placement. This equalization procedure is designed to support the
configurations defined by the CND or OnePlanner tool, not all possible
configurations supported by the 6500 software. Therefore, to use this
procedure, the 6500 passive layer network must be modeled using CND or
OnePlanner. If the system was not modeled using CND or OnePlanner, this
procedure may not be used.
Table 5-2
Summary of external pad IDs, placement rules, test points and verification criteria
Z(FGA) FGA FGA Line FGA Line Out OSA Pad that sets all Pch as close to
Input (see PFGA,avg as possible, while
Note) guaranteeing that
PFGA,min<Pch<PFGA,max
Z(FGA Tx) Node FGA Tx Node egress OSA Pad that sets all Pch as close to
egress PLAUNCH,avg as possible, while
guaranteeing that
PLAUNCH,min<Pch<PLAUNCH,max
Z(LAUNCH) Node Varies with Node egress OSA Pad that sets all Pch as close to
egress configuration PLAUNCH,avg as possible, while
guaranteeing that
PLAUNCH,min<Pch<PLAUNCH,max
Z(drop,n) Channel RX Channel Rx Channel OPM Pad that sets Pdrop,in as close to
Input Demux Out Pdrop,n,avg as possible, while
guaranteeing that
Pdrop,n,min<Pch<Pdrop,n,max
OnePlanner considerations: The DWDM Adjacencies grid provides a threshold value (Max
Rx Power Required) and the Rx Nominal Level value. If the measured power is above the
threshold, you must install a pad to bring the power level between the threshold and Rx
Nominal Level. The power level should be as close to the Rx Nominal Level as possible.
Z(add,n) Channel Channel Mux At installation: OSA Pad that sets Padd,n as close to
Mux Input Node egress PLAUNCH,avg as possible, while
guaranteeing that
PLAUNCH,min<Padd,n<PLAUNCH,max
Note: When a DSCM precedes the FGA, then the pad is placed before the DSCM.
OSA: Optical Spectrum Analyzer
OPM: Optical Power Meter
Prerequisites
All actions contained in this procedure are to be executed on an OTS that was
previously created and defined as per the previous procedures.
All the passive components that are part of the OTS being worked on have all
been installed and provisioned properly.
All fibers connecting the passive components that are part of the OTS being
worked on have all been installed properly (labeled, routed, cleaned,
inspected and connected).
Fibers between the DWDM transmitters and the appropriate MUX ports have
all been labeled, routed, cleaned, inspected and connected at both ends. The
pads that are present in this connection should be as specified in the EDPs
(as per the CND or OnePlanner tool).
Fibers that are to connect the DWDM receivers to the DEMUX port have been
labeled, routed, cleaned, inspected and connected to the DEMUX ports but
not to the receivers. Instead the ends that are to be connected to the DWDM
receivers should be protected by dust caps.
All transponder line interfaces in the design must be present with transmit
ports enabled and outputting proper optical power levels.
The network must have at least one pass-through wavelength at each express
or line amp node. This is a prerequisite since it is important to set the
Z(LAUNCH) pad correctly during the initial install. Having to add or change it
afterwards on an existing system will be traffic affecting.
• Verify the actual fiber span characteristics to ensure they match the fiber
type, length, and loss in the to-build network design.
• Unidirectional span losses may differ, but higher loss span should be
equivalent to the loss in the to-build network design.
• Measure back reflection (BR) at the input and outputs of the fiber spans
(and any associated patch panels) to ensure no single event has a BR of
greater than -40 dB.
• Fiber dispersion measurements are recommended if the fiber
characteristics are uncertain.
CAUTION
Do not attempt to optically turn up the network if the fiber span
data does not match the values in the network design. Contact
the Ciena account team to re-validate the design with the
updated fiber span data.
Step Action
Step Action
Figure 5-1
Example Network View diagram for a 5-node 6500 passive layer network
Figure 5-2
Example Node View diagram (CND) for an OTS of a 6500 passive layer node
Figure 5-3
Example NE OTS diagram (OnePlanner) for an OTS of a 6500 passive layer node
Figure 5-4
Excerpt from Fiber Run List Report (OnePlanner) for the network example in Figure 5-3 (columns
up to Source Conn)
Figure 5-5
Excerpt from Fiber Run List Report (OnePlanner) for the network example in Figure 5-3 (columns
from Source Slot on)
Figure 5-6
Example Power Level report (CND) for a 6500 passive layer node
Figure 5-7
Excerpt from Passive Provisioning grid report (OnePlanner) for the network example in Figure 5-3
(columns up to Equipment Group [OTS])
Figure 5-8
Excerpt from Passive Provisioning grid report (OnePlanner) for the network example in Figure 5-3
(columns from Equipment Group [OTS] on)
Figure 5-9
Excerpt from DWDM Adjacencies Report (OnePlanner) for the network example in Figure 5-3
(columns up to Provisioned PEC)
Figure 5-10
Excerpt from DWDM Adjacencies Report (OnePlanner) for the network example in Figure 5-3
(columns from Derived PEC to Tx Typ. Launch Power)
Figure 5-11
Excerpt from DWDM Adjacencies Report (OnePlanner) for the network example in Figure 5-3
(columns from Tx Max. Launch Power to PADDRFORM)
Figure 5-12
Excerpt from DWDM Adjacencies Report (OnePlanner) for the network example in Figure 5-3
(columns from Estimated Rx Pad on)
Figure 5-13
OTS TX and OTS RX terminology illustration
Z(FGA Tx)
Z(FGA Tx)
Z(FGA Tx)
Z(FGA Tx)
Z(FGA Tx)
Z(FGA Tx)
Z(FGA Tx)
Note: Equipment and placement within the OTS can be different from what is shown in this figure.
For example, at an express node, all the equipment in OTS2 can be in OTS1 or there can be only
one OTS provisioned. For the purposes of this equalization procedure, assume the equipment is
placed in the OTSs as shown.
Figure 5-14
Generic pad placement illustration
Z(FGA Tx)
Z(FGA Tx)
Z(FGA Tx)
4. Interconnection points between the receiving OTS and the transmitting OTS
Note: Unidirectional traffic only is shown for simplicity. Not all equipment may be present in a particular node.
Procedure 5-5
Equalizing the OTS TX at a ZPT node
This procedure provides detailed steps to equalize the OTS TX at a ZPT node.
This procedure must be executed in conjunction with Procedure 5-4,
“Equalizing a passive layer network”.
Step Action
4 Locate the per channel target power expected at the point the OSA is
connected in the Power Levels tab of the detailed design report. This value is
located in the “P/ch avg (dBm)” column of the Power Levels table in the Visio
schematics produced by the CND tool (attached to the EDPs). OnePlanner
provides this information in the Passive Provisioning grid.
For each wavelength corresponding to a transmitter connected to the OTS
you are working on, compute the required power adjustment at the filter input.
This is Z(add,n) in diagram 2 of Figure 5-13 on page 5-31.
Adjustment (dB) = Power of λn on the OSA (dBm) - per channel Target Power
(dBm)
Step Action
Procedure 5-6
Equalizing OTS RX and OTS TX at an express node
This procedure provides detailed steps to equalize the OTS RX and OTS TX
at an express node. This procedure must be executed in conjunction with
Procedure 5-4, “Equalizing a passive layer network”.
Step Action
Step Action
6 Select the appropriate pad to place at the input of each receiver. This is
Z(drop,n) in diagram 1 of Figure 5-13 on page 5-31. For each wavelength
being dropped, connect a power meter on the demux output port and
measure the dropped channel power. Determine the pad required to set the
power in the range indicated by the Power Levels table.
If you are using OnePlanner, the DWDM Adjacencies grid provides a
threshold value (Max Rx Power Required) and the Rx Nominal Level value.
If the measured power is above the threshold, you must install a pad to bring
the power level between the threshold and Rx Nominal Level. The power
level should be as close to the Rx Nominal Level as possible.
Make sure the adjusted power of the current wavelength is within the required
range. Repeat the adjustment if required (replace the pad if it does not
provide the expected loss). Add a column to the power levels table and record
the adjusted power of the Rx wavelength.
Connect the fiber from the demux output port to each receiver through the
pad.
7 Connect an OSA to the appropriate location as indicated below.
• If an OSC filter is present in the OTS TX, disconnect the input of that OSC
filter and connect it to the OSA.
• If no OSC filter is present in the OTS TX, connect the OSA to the Out port
of the last component in that OTS TX. The Out port of the last component
in the OTS TX should have the fiber that connects to the fiber plant so you
will need to disconnect this fiber before connecting the OSA.
8 Considering only the pass-through wavelengths (not the channels being
added at this OTS), compute the required pad adjustment needed at each
interconnection of the receiving OTS and the transmitting OTS. Locate the
per channel target power expected at the point the OSA is connected. This
value is located in the “P/ch avg (dBm)” column of the Power Levels table in
the Visio schematics produced by the CND tool (attached to the EDPs).
Compute the required power adjustment for the pad at each interconnection
of the receiving OTS and the transmitting OTS. This is Z(LAUNCH) in diagram
1 of Figure 5-13 on page 5-31.
Adjustment (dB) = (Pmax + Pmin)/2 - per channel Target Power (dBm)
where Pmax (dBm) and Pmin (dBm) are the highest and lowest channel power
measurements made on the OSA, respectively.
If an FGA is present on the OTS Tx path, you must use the FGA target power.
OnePlanner provides the FGA target output power in the Estimated Average
Power per Channel column of the Passive Provisioning grid.
Step Action
9 Make the adjustment. Round the adjustment to the nearest integer value and
apply it to the value of the current pad at each interconnection of the receiving
OTS and the transmitting OTS. Replace with the appropriate pad. Mark up the
schematics to record the pad adjustments.
• Make sure the adjusted power of all pass-through wavelengths falls within
the max per channel power and the min per channel power values as
indicated in the Power Levels table (under column “P/ch max” and column
“P/ch min”).
• Repeat the adjustment if required (replace the pad if it does not provide
the expected loss).
• Add a column to the Power Levels table and record the adjusted power of
the wavelength. Also mark up the Visio schematics accordingly.
Note: If you cannot get all the wavelengths within the minimum per
wavelength power and the maximum per wavelength power, it indicates that
the equalization may not have been correctly done upstream.
10 Considering only the add wavelengths (the channels being added at this
OTS), locate the per channel target power expected at the point the OSA is
connected in the Power Levels tab of the detailed design report. This value is
located in the “P/ch avg (dBm)” column of the Power Levels table in the Visio
schematics produced by the CND tool (attached to the EDPs). For each
wavelength corresponding to a transmitter connected to the OTS you are
working on, compute the required power adjustment at the filter input. This is
Z(add,n) in diagram 1 of Figure 5-13 on page 5-31.
Adjustment (dB) = Power of λn on the OSA (dBm) - per channel Target Power
(dBm)
If an FGA is present on the OTS Tx path, you must use the FGA target power.
OnePlanner provides the FGA target output power in the Estimated Average
Power per Channel column of the Passive Provisioning grid.
Step Action
15 Once the FGA Tx target power level is achieved, measure the FGA output
power and compare it against the Equipment Group Power/Channel target to
determine if an additional pad is required at the output of the FGA.
Step Action
16 Disconnect the OSA and reconnect the fiber you disconnected in step 7.
17 Return to the step in Procedure 5-4, “Equalizing a passive layer network” that
called this procedure.
—end—
Procedure 5-7
Equalizing the OTS RX at a ZPT node
This procedure provides detailed steps to equalize the OTS RX at a ZPT
node. This procedure must be executed in conjunction with Procedure 5-4,
“Equalizing a passive layer network”.
Step Action
Step Action
6 Select the appropriate pad to place at the input of each receiver. This is
Z(drop,n) in diagram 2 of Figure 5-13 on page 5-31. For each wavelength
being dropped, connect a power meter on the demux output port and
measure the dropped channel power. Determine the pad required to set the
power in the range indicated by the Power Levels table.
Make sure the adjusted power of the current wavelength is within the required
range. Repeat the adjustment if required (replace the pad if it does not
provide the expected loss). Add a column to the power levels table and record
the adjusted power of the Rx wavelength.
Connect the fiber from the demux output port to each receiver through the
pad.
If you are using OnePlanner, the DWDM Adjacencies grid provides a
threshold value (Max Rx Power Required) and the Rx Nominal Level value.
If the measured power is above the threshold, you must install a pad to bring
the power level between the threshold and Rx Nominal Level. The power
level should be as close to the Rx Nominal Level as possible.
7 Return to the step in Procedure 5-4, “Equalizing a passive layer network” that
called this procedure.
—end—
Procedure 5-8
Equalizing a line amplifier node with one FGA
This procedure provides detailed steps to equalize a line amplifier node with
one FGA. This procedure must be executed in conjunction with
Procedure 5-4, “Equalizing a passive layer network”.
Step Action
Step Action
3 Make the adjustment. Round the adjustment to the nearest integer value and
apply it to the value of the current pad. Replace with the appropriate pad.
Mark up the schematics to record the pad adjustments.
• Make sure the adjusted power of all wavelengths falls within the max per
channel power and the min per channel power values as indicated in the
Power Levels table (under column “P/ch max” and column “P/ch min”).
• Repeat the adjustment if required (replace the pad if it does not provide
the expected loss).
• Add a column to the Power Levels table and record the adjusted power of
the wavelength. Also mark up the Visio schematics accordingly.
• Store an OSA trace showing all channels power levels and archive it.
Archive and name the file so that the data can be easily associated to the
site and the precise location of the OSA test point (Bay/shelf/slot/port)
and the date.
Note: If you cannot get all the wavelengths within the minimum per
wavelength power and the maximum per wavelength power, it indicates that
the equalization may not have been correctly done upstream.
4 Select your next step.
If the FGA Tx target power is Then go to
equal to the Equipment Group Power/Channel target step 6
different than the Equipment Group Power/Channel target step 5
5 Once the FGA Tx target power is achieved, measure FGA output power and
compare against the Equipment Group Power/Channel target to determine if
an additional pad is required at the output of the FGA.
6 Disconnect the OSA and reconnect the fiber you disconnected in step 1.
7 Return to the step in Procedure 5-4, “Equalizing a passive layer network” that
called this procedure.
—end—
Procedure 5-9
Equalizing a line amplifier node with two FGA
This procedure provides detailed steps to equalize a line amplifier node with
two FGA. This procedure must be executed in conjunction with Procedure 5-4,
“Equalizing a passive layer network”.
Step Action
1 Disconnect the fiber connected to the FGA-RX output and then connect an
OSA to the FGA-RX output.
2 Locate the per channel target power expected at the point the OSA is
connected in the Power Levels tab of the detailed design report. This value is
located in the “P/ch avg (dBm)” column of the Power Levels table in the Visio
schematics produced by the CND tool (attached to the EDPs). OnePlanner
provides the FGA target output power in the Estimated Average Power per
Channel column of the Passive Provisioning grid.
Compute the required power adjustment for the pad. This is Z(FGA) in
diagram 4 of Figure 5-13 on page 5-31. The pad is at the FGA input if no
DSCM precedes the FGA or the pad is at the DSCM input if a DSCM
precedes the FGA.
Adjustment (dB) = (Pmax + Pmin)/2 - per channel Target Power (dBm)
where Pmax (dBm) and Pmin (dBm) are the highest and lowest channel power
measurements made on the OSA, respectively.
3 Make the adjustment. Round the adjustment to the nearest integer value and
apply it to the value of the current pad. Replace with the appropriate pad.
Mark up the schematics to record the pad adjustments.
• Make sure the adjusted power of all wavelengths falls within the max per
channel power and the min per channel power values as indicated in the
Power Levels table (under column “P/ch max” and column “P/ch min”).
• Repeat the adjustment if required (replace the pad if it does not provide
the expected loss).
• Add a column to the Power Levels table and record the adjusted power of
the wavelength. Also mark up the Visio schematics accordingly.
Note: If you cannot get all the wavelengths within the minimum per
wavelength power and the maximum per wavelength power, it indicates that
the equalization may not have been correctly done upstream.
4 Disconnect the OSA and reconnect the fiber you disconnected in step 1.
Step Action
Step Action
9 Once FGA Tx target is achieved, measure FGA output power and compare
against the Equipment Group Power/Channel target to determine if an
additional pad is required at the output of the FGA.
10 Disconnect the OSA and reconnect the fiber you disconnected in step 5.
11 Return to the step in Procedure 5-4, “Equalizing a passive layer network” that
called this procedure.
—end—
Procedure 5-10
Adding a new channel over a passive OTS network
Use this procedure to add a new channel over an existing passive OTS
network. This procedure is not traffic impacting.
Step Action
Step Action
6 In both locations where the new channel terminates, connect a power meter
on the demux output port and measure the power. Determine the pad
required to set the power in the range indicated by the Power Levels table in
the Visio schematics produced by the CND tool (attached to the EDPs). Make
sure the adjusted power at the new wavelength receiver input is within the
required range. Repeat the adjustment if required (replace the pad if it does
not provide the expected loss).
7 Take a screen capture of the OSA launch spectrum with all added channels
and archive it.
—end—
Procedure 5-11
Inserting a new add/drop filter
Use this procedure to insert a new add/drop filter to an existing passive OTS
network.
With correct planning, the expansion of the node's add/drop capacity can be
managed with minimal impacts to channel equalization. If the new add/drop
filters are inserted after the last drop filter and before the first add filter, the
only pad that needs to be changed is the pad located between the two OTSs.
Previously deployed FGA, DSCM, receiver overload and channel equalization
pads will remain unchanged if the expansion filters are added as described.
See Figure 5-15 on page 5-51 for an illustration of add/drop filter insertion
procedure. Labeled numbers in this figure identify the steps to follow.
Step Action
1 For wavelengths that are supporting protected channels, use the proper
manual switch and lockout to move the traffic away from the path that will be
interrupted.
2 Select the first direction you want to work on and connect an OSA on the
monitor port as close as possible to the connection to the transmit line fiber.
• If an FGA occupies a post amplifier position in the OTS, connect the OSA
to the output monitor port.
• If there is no FGA in a post amplifier position, connect the OSA to a
monitor port downstream from the point where all wavelengths are
multiplexed.
• Record the trace and the total spectrum power.
Step Action
3 Disconnect the fiber at the input of the PAD in the connection between the two
OTSs. Clean, inspect, label and connect a fiber between the EXPR output
port of the new DROP filter and the input of the PAD in the connection
between the two OTSs. In a similar manner, disconnect the fiber at the output
of the PAD in the connection between the two OTS. Clean, inspect, label and
connect a fiber between the EXPR input port of the new ADD filter and the
output of the PAD in the connection between the two OTSs.
4 Disconnect the fiber at the EXPR output port of the last existing drop filter.
Clean, inspect, label and connect a fiber between the EXPR output port of the
last existing DROP filter and the NTWK input port of the new DROP filter.
5 Disconnect the fiber at the EXPR input port of the first existing ADD filter.
Clean, inspect, label and connect a fiber between the EXPR input port of the
first existing ADD filter and the NTWK output port of the new DROP filter.
6 With the OSA still connected at the same location as in step 2, take another
trace of the spectrum and compute the adjustment needed on the PAD in the
connection between the two OTSs.
Adjustment (dB) = New total spectrum power (dBm) - Initial total spectrum
power (dBm)
7 Make the adjustment: Round the adjustment to the nearest integer value and
apply it to the value of the current pad. Replace with the appropriate pad.
Before proceeding to the next step, make sure the adjusted spectrum power
falls within ±1.0 dB of initial spectrum power.
Note: If the pad adjustment in the connection between the two OTSs is not
done properly, the power balancing between express wavelengths and added
wavelength at this node will be altered leading to possible performance and
system margin degradation.
8 Capture and label the adjusted OSA trace and archive as a proof of correct
installation. Mark up the Visio schematics to indicate the revised pad value.
9 If the new add/drop filter have not been inserted in the other direction, repeat
from step 2 in the other direction. Otherwise, go to the next step.
10 Release the manual or lockout switches that were done in step 1.
11 Perform Procedure 5-10, “Adding a new channel over a passive OTS
network” to bring up channels at the newly inserted add/drop filters.
—end—
Figure 5-15
Generic view of a passive OTS
Procedure 5-12
Turning up channels over a Passive Bridge to ROADM
configuration
This procedure provides steps for turning up channels over Passive Bridge to
ROADM configurations, using the example shown in Figure 5-16 on page
5-55. Labeled numbers in the figure identify the steps to follow. For the
procedure on turning up channels over Passive Bridge to ROADM—one
passive tail configurations, see Procedure 5-13, “Turning up channels over a
Passive Bridge to ROADM—one passive tail configuration”.
For details on Passive Bridge applications and engineering rules, see the
6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA.
Step Action
1 Turn up the ROADM network. Refer to the SLAT process description and
flowchart in Chapter 1, “SLAT process overview”.
2 Provision the inventory, OTS, and adjacencies for the passive equipment at
Sites A, 1, 2, and B (see Figure 5-16 on page 5-55).
Refer to the following procedures in this chapter:
• Procedure 5-1, “Adding passive components”
• Procedure 5-2, “Creating a passive OTS and defining its configuration”
• Procedure 5-3, “Provisioning line adjacencies”
Step Action
5 At Site 1, stitch channels from the passive OTS to the ROADM OTS.
Note: The network design output of either the Ciena Network Designer
(CND) or OnePlanner tool will show overload pads placed at Site 1/OTS4
CMD CH outputs (demux). Do not deploy these pads.
a. Connect the passive demux outputs directly to the ROADM mux inputs.
b. For each stitched channel at ROADM OTS CMD Channel In, set the Max/
typical launch power of the ADJ-TX facility to the power level measured
at ROADM OTS CMD Channel In.
The target powers for stitched channels at ROADM OTS mux are:
- approximately -6 dBm if ROADM OTS is equipped with MLA2
- approximately -1 dBm if ROADM OTS is equipped with MLA
6 Turn up the stitched channels over the ROADM network between Site 1 and
Site 2.
7 At Site 2, stitch the channels from the ROADM OTS to the passive OTS.
8 Equalize the channels transmitted from Site 2 to Site B. Refer to the
equalizing procedures in this chapter.
9 Equalize the channels received at Site B from Site 2. Refer to the equalizing
procedures in this chapter.
You have completed turning up the channels in the A to B direction.
Turning up channels in the Site B to Site A direction
10 Equalize the channels transmitted from Site B to Site 2. Refer to the
equalizing procedures in this chapter.
11 Equalize the channels received at Site 2 from Site B. Refer to the equalizing
procedures in chapter.
12 At Site 2, stitch channels from the passive OTS to the ROADM OTS.
Note: The network design output of the either the Ciena Network Designer
(CND) or OnePlanner tool will show overload pads placed at Site 2/OTS4
CMD CH outputs (demux). Do not deploy these pads.
a. Connect the passive demux outputs directly to the ROADM mux inputs.
Step Action
b. For each stitched channel at ROADM OTS CMD Channel In, set the Max/
typical launch power of the ADJ-TX facility to the power level measured
at ROADM OTS CMD Channel In.
The target powers for stitched channels at ROADM OTS mux are:
- approximately -6 dBm if ROADM OTS is equipped with MLA2
- approximately -1 dBm if ROADM OTS is equipped with MLA
13 Turn up the stitched channels over the ROADM network between Site 2 and
Site 1.
14 At Site 1, stitch the channels from the ROADM OTS to the passive OTS.
15 Equalize the channels transmitted from Site 1 to Site A. Refer to the
equalizing procedures in this chapter.
16 Equalize the channels received at Site A from Site 1. Refer to the equalizing
procedures in this chapter.
You have completed turning up the channels in the B to A direction.
—end—
Figure 5-16
Example of Passive Bridge to ROADM configuration
4 15 16 3
5 14
1
2
6 13
7 12
8 11 10 9
Procedure 5-13
Turning up channels over a Passive Bridge to
ROADM—one passive tail configuration
This procedure provides steps for turning up channels over Passive Bridge to
ROADM—one passive tail configurations, using the example shown in
Figure 5-17 on page 5-58. Labeled numbers in the figure identify the steps to
follow. For the procedure on turning up channels over Passive Bridge to
ROADM configurations, see Procedure 5-12, “Turning up channels over a
Passive Bridge to ROADM configuration”.
For details on Passive Bridge applications and engineering rules, see the
6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA.
Step Action
1 Turn up the ROADM network. Refer to the SLAT process description and
flowchart in Chapter 1, “SLAT process overview”.
2 Provision the inventory, OTS, and adjacencies for the passive equipment at
Sites A and 1 (see Figure 5-17 on page 5-58).
Refer to the following procedures in this chapter:
• Procedure 5-1, “Adding passive components”
• Procedure 5-2, “Creating a passive OTS and defining its configuration”
• Procedure 5-3, “Provisioning line adjacencies”
Step Action
5 At Site 1, stitch channels from the passive OTS to the ROADM OTS.
Note: The network design output of either the Ciena Network Designer
(CND) or OnePlanner tool will show overload pads placed at Site 1/OTS4
CMD CH outputs (demux). Do not deploy these pads.
a. Connect the passive demux outputs directly to the ROADM mux inputs.
b. For each stitched channel at ROADM OTS CMD Channel In, set the Max/
typical launch power of the ADJ-TX facility to the power level measured
at ROADM OTS CMD Channel In.
The target powers for stitched channels at ROADM OTS mux are:
- approximately -6 dBm if ROADM OTS is equipped with MLA2
- approximately -1 dBm if ROADM OTS is equipped with MLA
6 Turn up the stitched channels over the ROADM network between Site 1 and
Site 2.
You have completed turning up the channels from Site A to Site 2.
To turn up the channels from Site 2 to Site A, go to step 7.
Turning up channels in the Site 2 to Site A direction
7 Turn up the channels over the ROADM network between Site 2 and Site 1.
8 At Site 1, stitch channels from the ROADM OTS to the passive OTS. Connect
the ROADM demux outputs to the Passive mux inputs via equalization pads.
9 Equalize the channels transmitted from Site 1 to Site A. Refer to the
equalizing procedures in this chapter.
10 Equalize the channels received at Site A from Site 1. Refer to the equalizing
procedures in this chapter.
You have completed turning up the channels from Site 2 to Site A.
To turn up the channels from Site A to Site 2, go to step 3.
—end—
Figure 5-17
Example of Passive Bridge to ROADM—one passive tail configuration
4 3
9 10
5 8
6 7
The site testing procedures call up supporting procedures, which are included
in the list in the following table. After you perform the supporting procedure,
return to the step in the main procedure that sent you to the supporting
procedure and continue with the next step in the main procedure.
Table 6-1
Procedures in this chapter
Procedure
Procedure 6-1, “Testing the power at the optical interface Tx port”
Procedure 6-2, “Testing the power at the optical interface Rx port”
Procedure 6-3, “Testing optical signal continuity in the network element”
Procedure 6-4, “Testing DS1 service modules”
Procedure 6-5, “Testing E1 circuit packs”
Procedure 6-6, “Testing DS3/EC-1 circuit packs and DS3/E3 circuit packs”
Procedure 6-7, “Testing 16xSTM-1e circuit packs”
Procedure 6-8, “Testing Trans Mux (TMUX) circuit packs”
Procedure 6-9, “Testing 4xGE EPL circuit packs and testing GE protection”
Procedure 6-10, “Testing 24x10/100BT circuit packs”
Procedure 6-11, “Testing L2SS or 20G L2SS circuit packs”
Procedure 6-12, “Testing L2SS DS1/E1/DS3/E3 4XGE (PDH) circuit packs”
Procedure 6-13, “Testing L2SS, 20G L2SS, and PDH gateway equipment protection”
Procedure 6-14, “Testing RPR circuit packs”
Procedure 6-15, “Testing 1x10GE EPL circuit packs”
Procedure 6-16, “Testing SuperMux circuit packs”
Supporting procedures
Procedure 6-17, “Setting a hardware terminal loopback for a network element”
Procedure 6-18, “Restoring a network element to its initial state”
Procedure 6-1
Testing the power at the optical interface Tx port
Use this procedure to verify the transmit power of an optical interface circuit
pack.
Prerequisites
The following tools are mandatory to measure power on the optical interface
port:
• optical power meter
• antistatic wrist or ankle strap
• fiber-optic patch cords
• fiber microscope
Make sure that the equipment and the facilities you want to test are
provisioned. Refer to the “Retrieving equipment and facility details” procedure
in Part 1 of Configuration - Provisioning and Operating, 323-1851-310.
Make sure that ALS is disabled for the facilities you want to test. To
disable/enable ALS, refer to the “Editing facility parameters” procedure in
Part 1 of Configuration - Provisioning and Operating, 323-1851-310.
CAUTION
Risk of personal injury
When inserted in a shelf slot, the optical interface circuit pack
emits laser light that can blind. Keep all optical connectors on
the optical interface circuit packs capped when they are not
connected to optical fiber cables. Never look directly into the
end of an optical fiber.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Step Action
1 Make a paper copy of Table 6-2 on page 6-6 to record the test results.
2
CAUTION
Risk of personal injury
When inserted in a shelf slot, the optical interface
circuit pack emits laser light that can blind. Keep all
optical connectors on the optical interface circuit packs
capped when they are not connected to optical fiber
cables. Never look directly into the end of an optical
fiber.
Remove the protection cap from the Tx port of the optical interface circuit
pack. Clean the port connector.
3 Make sure that the system has been powered up and that the circuit pack is
in the working operational condition (indicated by a lit green LED on the top
of the circuit pack) before you test any of the optical ports.
4 Scope the optical patch cord, clean if necessary, and scope again.
Refer to the chapter on cleaning connectors in Installation - General
Information, 323-1851-201.0 for the following:
• the procedure on cleaning optical connectors and adapters on patch
cords
• the illustration of a dirty optical fiber
• the illustration of a clean optical fiber
5 Verify the optical patch cord integrity.
6 Connect one end of the optical patch cord to the optical power meter and the
other end to the Tx port on the optical interface circuit pack.
7 Switch the optical power meter power on and record the transmit power.
The power recorded must be equal to or higher than the minimum launch
power for the optical interface circuit pack. For the minimum launch power
applicable to a circuit pack, refer to the technical specifications chapter in
Part 3 of Planning, NTRN10EG.
8 Select your next step.
If the measured value Then go to
meets the requirements step 11
does not meet the requirements step 10
Step Action
Table 6-2
Data form: Measuring the power at the optical interface Tx port
OC-3/12/ OC-48/ OC-192/ 10GE GE SFP ports on SuperMux SFP ports
STM-1/4 STM-16 STM-64 24x10/100BT on MXC
EPL with
8xSFP
Slot Port Measured Measured Measured Measured Measured Measured Measured Measured
Table 6-2
Data form: Measuring the power at the optical interface Tx port (continued)
OC-3/12/ OC-48/ OC-192/ 10GE GE SFP ports on SuperMux SFP ports
STM-1/4 STM-16 STM-64 24x10/100BT on MXC
EPL with
8xSFP
Slot Port Measured Measured Measured Measured Measured Measured Measured Measured
Procedure 6-2
Testing the power at the optical interface Rx port
Use this procedure to verify the receive power at a non-DWDM optical
interface circuit pack.
Prerequisites
The following tools are mandatory to measure power on the optical interface
port.
• optical power meter
• antistatic wrist or ankle strap
• fiber-optic patch cords
• fiber microscope
Make sure that the equipment and the facilities you want to test are
provisioned. Refer to the “Retrieving equipment and facility details” procedure
in Part 1 of Configuration - Provisioning and Operating, 323-1851-310.
Make sure that ALS is disabled for the facilities you want to test. To
disable/enable ALS, refer to the “Editing facility parameters” procedure in
Part 1 of Configuration - Provisioning and Operating, 323-1851-310.
CAUTION
Risk of personal injury
When inserted in a shelf slot, the optical interface circuit pack
emits laser light that can blind. Keep all optical connectors on
the optical interface circuit packs capped when they are not
connected to optical fiber cables. Never look directly into the
end of an optical fiber.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Step Action
1 Test the transmit power. For more information, see Procedure 6-1, “Testing
the power at the optical interface Tx port”.
2 Disconnect the fiber-optic cable from the optical interface Rx port.
3 Scope the connector on the circuit pack, clean if necessary, and scope again.
Refer to the chapter on cleaning connectors in Installation - General
Information, 323-1851-201.0 for the following:
• the procedure on cleaning optical connectors and adapters on patch
cords
• the illustration of a dirty optical fiber
• the illustration of a clean optical fiber
4 Connect the end of the patch cord that you removed from the Rx port on the
circuit pack, to the optical power meter.
5 Switch the optical power meter power on and record the receive power.
The value of the power recorded must be within the range of power
specification for optical interface circuit pack. For the receiver overload and
minimum sensitivity applicable to circuit packs, refer to the technical
specifications chapter in Part 3 of Planning, NTRN10EG.
6 Repeat step 1 to step 5 for all optical interface circuit packs.
7 Switch the optical power meter power off and disconnect the optical power
meter from the fiber-optic cable.
8 Scope the connector on the circuit pack, clean if necessary, and scope again.
Refer to the chapter on cleaning connectors in Installation - General
Information, 323-1851-201.0 for the following:
• the procedure on cleaning optical connectors and adapters on patch
cords
• the illustration of a dirty optical fiber
• the illustration of a clean optical fiber
Procedure 6-3
Testing optical signal continuity in the network
element
Use this procedure to test signal continuity (optical) in the network element
(OCn/STMn interfaces only).
Prerequisites
Before you perform this test, make sure that you have:
• 155 Mbit/s, 622 Mbit/s, 2.5 Gbit/s, or 10 Gbit/s test equipment as required
• optical patch cords
• antistatic wrist strap or ankle strap
• fiber cleaning materials
Step Action
Step Action
10 After five minutes, read the error count on the test set. The working path
passes the signal continuity test if the signal is back, error free.
11 Repeat step 1 to step 10 for all circuit packs.
12 Review the test results. If any of the tests failed, see the alarm clearing
procedures in Fault Management - Alarm Clearing, 323-1851-543 to clear
any alarms raised.
—end—
Procedure 6-4
Testing DS1 service modules
Use this procedure to test the signal continuity and the protection switching on
a DS1 service module (DSM). The term DSM is used for LO-DSM and
HO-DSM in this procedure.
Prerequisites
Before you perform this test:
• Ensure that you have:
— a DS1 test set
— optical patch cords
— antistatic wrist strap or ankle strap
— fiber cleaning materials
— all the documentation referenced in this procedure
• The DS1 service module under test must be installed (see the procedures
on installing DS1 service module hardware in the Installation technical
publication specific to the respective 6500 shelf type) and provisioned (see
the procedures on provisioning a DSM 84xDS1 TM in Part 1 of
Configuration - Provisioning and Operating, 323-1851-310).
• If you are using protected equipment, you must ensure the protection
equipment is identical to the working equipment.
• Make sure your system has been powered up and stable for at least
Five minutes.
CAUTION
Risk of personal injury
When inserted in a shelf slot, the optical interface circuit pack
emits laser light that can blind. Keep all optical connectors on
the optical interface circuit packs capped when they are not
connected to optical fiber cables. Never look directly into the
end of an optical fiber.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Step Action
7 Connect the Tx port on the DS1 test set to the DS1 no.1 Rx port on the DS1
cross-connect panel.
8 Connect the Rx port on the DS1 test set to the DS1 no.1 Tx port on the DS1
cross-connect panel.
9 In the Protection menu of the Site Manager application, ensure the status of
the working DSM 84xDS1 termination module (TM) circuit pack is
Active;Working.
Step Action
10 In the Equipment & Facility menu of the Site Manager application, ensure the
status of the working OC3 facility connected to the 84xDS1 TM circuit pack is
Working receiver; Working transmitter.
Attention: Path Provisioning will be enabled for HO-DSM and the path trace
is done on the OC3 facility of HO-DSM. Path Provisioning application is used
to retrieve / change the path trace and signal label parameters.
17 On the DS1 service module, disconnect the IN or OUT fiber-optic cable from
the DSM 84XDS1 TM circuit pack in slot 1.
The DS1 service module passes the protection switching test if
• The LEDs on the DSM 84xDS1 TM circuit pack in DS1 service module
slot 1 indicate a loss of signal.
• The LEDs on the DSM 84xDS1 TM circuit pack in DS1 service module
slot 2 indicate traffic is on.
18 To test signal continuity for the 84xDS1 TM protection circuit pack, repeat step
7 to step 15 for the 84xDS1 TM protection circuit pack while it is active.
19 Review the test results. If any of the tests failed, solve the problem. See the
alarm clearing procedures in Fault Management - Alarm Clearing,
323-1851-543 to clear any raised alarms.
20 Return the system to its initial state. See Procedure 6-18, “Restoring a
network element to its initial state”.
—end—
Figure 6-1
Example of testing signal continuity and protection switching on a DS1 service module
Procedure 6-5
Testing E1 circuit packs
This procedure describes how to test E1 circuit packs. Perform this procedure
only if your shelf is equipped with VT1.5/VC12 cross-connect circuit packs. To
test all E1 circuit packs, repeat this procedure for each slot.
VC12 management and the E1 signal rate and facility type are supported only
if your shelf is equipped with VT1.5/VC12 cross-connect circuit packs.
Prerequisites
Before you perform this procedure, make sure that the following prerequisites
are met:
• You have all the documentation referenced in this procedure. This
procedure assumes that you have installed:
— the associated E1 I/O panel (optical/front electrical shelf) or E1 I/O
module (Metro front electrical shelf)
— the E1 working circuit pack in the slot under test
— the E1 cable connectors as required for the E1 circuit pack
CAUTION
Risk of personal injury
When inserted in a shelf slot, the optical interface circuit pack
emits laser light that can blind. Keep all optical connectors on
the optical interface circuit packs capped when they are not
connected to optical fiber cables. Never look directly into the
end of an optical fiber.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Step Action
Step Action
8 Make sure the test set is switched on and connected to the E1 I/O port (on
the E1 I/O panel [optical/front electrical shelf] or E1 I/O module [Metro front
electrical shelf]) that corresponds to the circuit pack you want to test.
9 Provision a 2WAY cross-connect from the E1 facility you are testing to the
optical interface you are using for the test. Refer to the “Adding a 2WAY,
1WAY, 2WAYPR, 1WAYPR, or 2WAYDPR path cross-connect” procedure in
Part 1 of Configuration - Bandwidth and Data Services, 323-1851-320.
10 Verify that the working optical interface circuit pack indicates working transmit
and receive activity. Refer to the “Retrieving equipment and facility details”
procedure in Part 1 of Configuration - Provisioning and Operating,
323-1851-310.
Testing traffic continuity and, if applicable, protection switching
11 Set the test set to introduce an error free signal.
12 Clear the error count on the test set.
13 Read the error count on the test set. The working path passes the signal
continuity test, if the signal is back, error free.
14 Select your next step.
If the E1 circuit pack Then go to
is protected step 15
is unprotected step 17
15 Pull out the E1 working circuit pack and check that the status of the
associated protection circuit pack in the Protection menu of the Site Manager
application is IS Working.
16 Repeat step 11 to step 13 to test traffic continuity on the protection circuit
pack, then go to step 17.
17 As required, delete the cross-connect you provisioned in step 9.
18 As required, repeat step 8 to step 17 for all ports of the E1 circuit pack.
19 Repeat step 8 to step 18 for all working E1 circuit packs in the shelf.
20 Review the test results. If any of the tests failed, see the alarm clearing
procedures in Fault Management - Alarm Clearing, 323-1851-543 to clear
any raised alarms.
21 Return the system to its initial state. See Procedure 6-18, “Restoring a
network element to its initial state”.
—end—
Figure 6-2
Example of testing E1 circuit packs
Network element
Tx
Rx
Protection module
Rx Tx
Test set
Note: The E1 protection circuit pack in slot 13 provides protection for the circuit packs in slots 1 to 4.
The E1 protection circuit pack in slot 14 provides protection for the circuit packs in slots 9 to 12.
Procedure 6-6
Testing DS3/EC-1 circuit packs and DS3/E3 circuit
packs
This procedure describes how to test DS3/EC-1 and DS3/E3 circuit packs.
Prerequisites
Before you perform this procedure, make sure that the following prerequisites
are met:
• You have all the documentation referenced in this procedure.
• This procedure assumes that you have installed:
— the associated DS3/E3/EC-1 I/O panel/module
— the working circuit pack (DS3/EC-1 or DS3/E3) in the slot under test
— the DS3/E3/EC-1 cable connectors as required for the circuit pack
(DS3/EC-1 or DS3/E3)
• If you are testing protection continuity, make sure you installed and
provisioned the protection circuit pack (DS3/EC-1 or DS3/E3) in its slot in
the shelf.
• You have:
— a DS3 test set for DS3 tests
— an STS1 test set for EC-1 tests
— an E3 test set for E3 tests
• Make sure the system has been powered up and stable for at least five
minutes before you start the test.
CAUTION
Risk of personal injury
When inserted in a shelf slot, the optical interface circuit pack
emits laser light that can blind. Keep all optical connectors on
the optical interface circuit packs capped when they are not
connected to optical fiber cables. Never look directly into the
end of an optical fiber.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Step Action
Step Action
14 Pull out the working circuit pack (DS3/EC-1 or DS3/E3) and check that the
status of the associated protection circuit pack in the Protection menu of the
Site Manager application is IS Working.
15 Repeat step 10 to step 12 to test traffic continuity on the protection circuit
pack, then go to step 16.
16 As required, delete the cross-connect you provisioned in step 8.
17 As required, repeat step 7 to step 16 for all ports of the circuit pack (DS3/EC-1
or DS3/E3).
18 Repeat step 7 to step 17 for all working circuit packs (DS3/EC-1 or DS3/E3)
in the shelf.
19 Review the test results. If any of the tests failed, see the alarm clearing
procedures in Fault Management - Alarm Clearing, 323-1851-543 to clear
any raised alarms.
20 Return the system to its initial state. See Procedure 6-18, “Restoring a
network element to its initial state”.
—end—
Figure 6-3
Example of testing DS3/EC-1 circuit packs (similar setup for DS3/E3 circuit packs)
Network element
Tx
Rx
Working Protection
DS3/EC-1 DS3/EC-1
circuit pack Tx Rx Tx Rx circuit pack
in slots 1 to 4 in slot 13
or slots 9 to 12 DS3/ DS3/ DS3/ DS3/ or slot 14
STS-1 STS-1 STS-1 STS-1
Rx Tx
Test set
Note: The DS3/EC-1 protection circuit pack in slot 13 provides protection for the circuit packs
in slots 1 to 4. The DS3/EC-1 protection circuit pack in slot 14 provides protection for the
circuit packs in slots 9 to 12.
Procedure 6-7
Testing 16xSTM-1e circuit packs
This procedure describes how to test 16xSTM-1e circuit packs.
Prerequisites
Before you perform this procedure, make sure that the following prerequisites
are met:
• You have all the documentation referenced in this procedure.
• This procedure assumes that you have installed:
— the associated I/O panel
— the working circuit pack in the slot under test
— the STM-1e cable connectors (single port or 16 ports) as required for
the circuit pack
• If you are testing protection continuity, make sure you installed and
provisioned the protection circuit pack in its slot in the shelf.
• You have a test set for STM-1e tests
• Make sure the system has been powered up and stable for at least five
minutes before you start the test.
CAUTION
Risk of personal injury
When inserted in a shelf slot, the optical interface circuit pack
emits laser light that can blind. Keep all optical connectors on
the optical interface circuit packs capped when they are not
connected to optical fiber cables. Never look directly into the
end of an optical fiber.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Step Action
Step Action
14 Ensure that the STM-1e circuit pack is provisioned for protection. For more
information, refer to the “Changing the protection scheme for electrical
equipment” procedure in Part 2 of Configuration - Provisioning and
Operating, 323-1851-310.
15 Pull out the working circuit pack and check that the status of the associated
protection circuit pack in the Protection menu of the Site Manager application
is IS Working.
16 Repeat step 10 to step 12 to test traffic continuity on the protection circuit
pack, then go to step 17.
17 Re-insert the working circuit pack. Wait until the circuit pack is powered up
(blue LED is lit) and the traffic is back on the circuit pack (after the WTR time).
18 As required, delete the cross-connect you provisioned in step 8.
19 As required, repeat step 7 to step 18 for all ports of the circuit pack.
20 As required, repeat step 7 to step 19 for all working circuit packs in the shelf.
21 Review the test results. If any of the tests failed, see the alarm clearing
procedures in Fault Management - Alarm Clearing, 323-1851-543 to clear
any raised alarms.
22 Return the system to its initial state. Refer to Procedure 6-18, “Restoring a
network element to its initial state”.
—end—
Figure 6-4
Example of testing STM-1e circuit packs
Network element
Tx
Rx
Rx Tx
Test set
Note: The STM-1e protection circuit pack in slot 13 provides protection for the circuit packs
in slots 1 to 4. The STM-1e protection circuit pack in slot 14 provides protection for the
circuit packs in slots 9 to 12.
Procedure 6-8
Testing Trans Mux (TMUX) circuit packs
This procedure describes how to test Trans Mux (TMUX) circuit packs.
Prerequisites
Before you perform this procedure, make sure that the following prerequisites
are met:
• You have all the documentation referenced in this procedure.
• Make sure that you have installed the working TMUX circuit pack in its slot
in the shelf. If you are testing protection continuity, make sure you have
installed the working TMUX circuit pack in an odd slot in the shelf and the
protection TMUX circuit pack in the adjacent (even) slot in the shelf.
• You have an optical test set capable of DS1 within a DS3, E1 within DS3,
or E1 within E3 signal which is mapped into a SONET/SDH OC-n /STM-n
signal.
• If an optical test set is not available, make sure that you have installed:
— a working DS3/EC-1, DS3/E3, or E1 circuit pack
— the associated DS3/E3/EC-1 I/O or E1 panel
— the DS3/E3/EC-1/E1 cable connectors as required for the circuit
pack(s) (DS3/EC-1, DS3/E3, or E1)
CAUTION
Risk of personal injury
When inserted in a shelf slot, the optical interface circuit pack
emits laser light that can blind. Keep all optical connectors on
the optical interface circuit packs capped when they are not
connected to optical fiber cables. Never look directly into the
end of an optical fiber.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Step Action
Step Action
19 Pull out the working TMUX circuit pack and check that the status of the
associated protection circuit pack in the Protection menu of the Site Manager
application is IS Working.
20 Repeat step 15 to step 17 to test traffic continuity on the protection circuit
pack, then go to step 21.
Step Action
21 Insert the TMUX working circuit pack back into its slot and check that its
status in the Protection menu of the Site Manager application is IS Working.
22 As required, delete the cross-connects you provisioned in step 8, step 10, or
step 12.
23 As required, repeat step 8 to step 22 for all 48 E3 or DS3 facilities of the
TMUX circuit pack.
24 As required, repeat step 4 to step 23 for all working TMUX circuit packs in the
shelf.
25 Review the test results. If any of the tests failed, see the alarm clearing
procedures in Fault Management - Alarm Clearing, 323-1851-543 to clear
any raised alarms.
26 Return the system to its initial state. See Procedure 6-18, “Restoring a
network element to its initial state”.
—end—
Figure 6-5
Example of testing an unprotected TMUX circuit packs with optical test set
Loopback
(fiber-optic
patch cords)
Network element
28 2WAY VT1.5
VT1.5/VC-12 cross-connects
cross-connect between the DS1
circuit pack
channels associated
2WAY
STS-1/VC-3 with the DS3 facility
...
cross-connect on the Trans Mux and
the optical port
DS3/DS1/E3/E1 where the loopback is
Mux/Demux or 21 2WAY VC-12
TMUX circuit pack between E1 channels
associated with
E3 facility or 21 2WAY
VC-12 between E1
channels associated
with DS3 facility
Procedure 6-9
Testing 4xGE EPL circuit packs and testing GE
protection
This procedure uses the term “4xGE EPL circuit pack” to refer to 4xGE EPL
circuit packs and 4xGE EPL EFM circuit packs.
Use this procedure to test 4xGE EPL circuit packs and GE protection. Perform
this procedure for each 4xGE EPL circuit pack in the network element. This
procedure requires personnel at the site of the network element.
Prerequisites
Before you perform this procedure, make sure that:
• You have all the documentation referenced in this procedure.
• The 4xGE EPL circuit pack is installed in the correct slot in the network
element. See the procedure on installing circuit packs in the Installation
technical publication specific to the respective 6500 shelf type.
• The equipment and the facilities you want to test are provisioned. For
detailed procedures, see the chapter on equipment and facility
provisioning in Part 1 of Configuration - Provisioning and Operating,
323-1851-310.
• You have available an Ethernet test set that can interface to the 4xGE EPL
circuit pack you are testing, including all SFP types you are using.
• You connect a personal computer (PC) to the shelf where the circuit pack
is located.
• You have available the appropriate fiber-optic cables that can interface to
the LAN ports of the 4xGE EPL circuit pack you are testing.
Step Action
1 Verify that the 4xGE EPL circuit pack is active by checking its LEDs. For more
information, see the section on alarm and trouble clearing strategy in Part 1
of Fault Management - Alarm Clearing, 323-1851-543.
2 Launch the Site Manager application and log in to the network element. For
more information, see the section on procedures and options for logging in
and logging out in Administration and Security, 323-1851-301.
3 Record the current configuration of the 4xGE EPL circuit pack.
4 Make sure that all LAN LOS LEDs on the faceplate of the 4xGE EPL circuit
pack are lit.
Step Action
For an illustration of the test setup on circuit packs with only one SFP type on
all ports, see Figure 6-6 on page 6-36.
You can also use the daisy-chain method to test circuit packs equipped with
multiple SFP types, if your configuration uses pairs of ports equipped with the
same SFP type, which you can daisy-chain. If there are ports that cannot be
included in a daisy-chain setup, they can be tested in pairs, as described in
this procedure, section on multiple SFP types.
When you connect the test set, check that the port on the test set matches
the type of the SFP on the circuit pack to which you are connecting.
For the first pass through step 10 and step 11, see section A in Figure 6-7 on
page 6-37. For the second pass (step 20), see section B.
7 Connect a test port of the test set to LAN port 4 of the 4xGE EPL circuit pack.
8 Provision STS24c/VC4-8c cross-connects on the 4xGE EPL circuit pack. For
more information, refer to the “Adding a 2WAY, 1WAY, 2WAYPR, 1WAYPR, or
2WAYDPR path cross-connect” procedure in Part 1 of Configuration -
Bandwidth and Data Services, 323-1851-320.
• Provision an STS24c/VC4-8c bidirectional cross-connect between the
WAN port associated with LAN port 1 and WAN port associated with
LAN port 2.
• Provision an STS24c/VC4-8c bidirectional cross-connect between the
WAN port associated with LAN port 3 and WAN port associated with
LAN port 4.
9 Daisy-chain LAN port 2 and LAN port 3 of the 4xGE EPL circuit pack. Make
sure autonegotiation values for ETH facilities on port 2 and port 3 match.
Then go to step 12.
10 Connect a test port of the test set to LAN port 2 of the 4xGE EPL circuit pack.
11 Provision an STS24c/VC4-8c bidirectional cross-connect between the WAN
port associated with LAN port 1 and LAN port 2 on the 4xGE EPL circuit
pack. For more information, refer to the “Adding a 2WAY, 1WAY, 2WAYPR,
1WAYPR, or 2WAYDPR path cross-connect” procedure in Part 1 of
Configuration - Bandwidth and Data Services, 323-1851-320.
Step Action
13 Clear the operational measurements counters for LAN and WAN facilities on
the circuit pack. See the procedure on clearing operational measurements in
Fault Management - Performance Monitoring, 323-1851-520.
14 Start the test set again. After about five minutes, stop the transmission on the
test set.
15 Verify that the receive byte count matches the transmit byte count in each
direction for each LAN port of the circuit pack (port 1 receive counts = port 4
transmit counts, port 4 receive counts = port 1 transmit counts). See the
procedure on retrieving operational measurements for 4xGE EPL circuit
packs in Fault Management - Performance Monitoring, 323-1851-520.
16 Verify that the receive byte count and frame count match the transmit byte
count and frame count on each test port of the test set (that is, test set port 1
transmit counts = test set port 4 receive counts, and test set port 4 transmit
counts = test set port 1 receive counts).
17 Select your next step.
If the circuit pack is equipped with Then go to
only one SFP type on all ports step 21
multiple SFP types step 18
18 Disconnect the test set from LAN port 1 and LAN port 2 of the 4xGE EPL
circuit pack.
Step Action
19 Delete the cross-connect that you provisioned between the WAN port
associated with LAN port 1 and WAN port associated with LAN port 2 in
step 11.
20 Repeat step 5 and step 10 to step 16 for LAN port 3 and LAN port 4 of the
4xGE EPL circuit pack. Then go to step 23.
21 Delete the cross-connects that you provisioned in step 8.
22 Remove the daisy-chain between LAN port 2 and LAN port 3 of the 4xGE
EPL circuit pack (added in step 9). Go to step 24.
23 Delete the cross-connect that you provisioned between WAN port associated
with LAN port 3 and WAN port associated with LAN port 4.
24 Remove the test set.
If you Then
want to test GE protection keep the settings on the test set
unchanged and go to step 25
do not want to test GE protection go to step 39
Step Action
Figure 6-7
Example of testing a 4xGE EPL circuit pack (multiple SFP types)
Figure 6-8
Example of GE protection testing
Procedure 6-10
Testing 24x10/100BT circuit packs
Use this procedure to test 24x10/100BT circuit packs. Perform this procedure
for each circuit pack in the network element. This procedure requires
personnel at the site of the network element.
Prerequisites
Before you perform this procedure, make sure that:
• You have all the documentation referenced in this procedure.
• You have installed:
— the associated 48x10/100BT I/O panel/module, if applicable to your
configuration
— the circuit pack in the correct slot in the network element. See the
procedure on installing circuit packs in the Installation technical
publication specific to the respective 6500 shelf type.
— the SFPs, if applicable to your configuration. See the procedure on
installing and removing pluggable modules in the Installation technical
publication specific to the respective 6500 shelf type.
• You have available the appropriate Ethernet or fiber-optic cables that can
interface to the LAN ports of the circuit pack you are testing.
• The equipment and the facilities you want to test are provisioned. For
detailed procedures, see the chapter on equipment and facility
provisioning in Part 1 of Configuration - Provisioning and Operating,
323-1851-310.
• You have available an Ethernet test set that can interface to the circuit
pack you are testing, including all SFP types you are using, if applicable.
• You connect a personal computer (PC) to the shelf where the circuit pack
is located.
CAUTION
Risk of personal injury
When inserted in a shelf slot, the optical interface circuit pack
emits laser light that can blind. Keep all optical connectors on
the optical interface circuit packs capped when they are not
connected to optical fiber cables. Never look directly into the
end of an optical fiber.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Step Action
Testing SFP LAN ports on the 24x10/100BT EPL with 8xSFP circuit pack (see Figure 6-9 on page
6-44)
8 Select an optical interface port to use for the test.
9 Add a terminal loopback on the optical interface port. For details, see
Procedure 6-17, “Setting a hardware terminal loopback for a network
element”.
10 Connect a test port of the test set to the SFP LAN port you want to test.
11 Add a 2WAY STS3c/VC4 cross-connect between the optical interface port
and the WAN port that corresponds to the SFP LAN port.
Step Action
13 Clear the operational measurements counters for LAN and WAN facilities on
the circuit pack. See the procedure on clearing operational measurements in
Fault Management - Performance Monitoring, 323-1851-520.
14 Start the test set again. After about five minutes, stop the transmission on the
test set.
15 On the circuit pack, check the operational measurements to verify that the
receive byte count matches the transmit byte count in each direction. See the
procedure on retrieving operational measurements for 24x10/100BT circuit
packs in Fault Management - Performance Monitoring, 323-1851-520.
16 On the test set, verify that the receive byte count and frame count match the
transmit byte count and frame count.
17 Select your next step.
If you are testing Then go to
the SFP LAN ports on the circuit pack step 18
LAN ports 9 to 24 on the I/O panel step 29
LAN ports 1 to 8 on the I/O panel step 37
18 Delete the cross-connect between the WAN port and the optical port.
19 If required, disconnect the SFP from the port and connect it to the next SFP
LAN port you want to test. Repeat step 10 to step 18 for all LAN ports.
20 Remove the terminal loopback from the optical interface.
Step Action
Testing the LAN ports on the I/O panel (see Figure 6-10 on page 6-45)
22 Provision ETH100 facilities for the LAN ports on the I/O panel. For details, see
the chapter on equipment and facility provisioning in Part 1 of Configuration -
Provisioning and Operating, 323-1851-310.
23 Select your next step.
If you want to test LAN ports Then go to
1 to 8 on the I/O panel step 32
9 to 24 on the I/O panel step 24
otherwise step 40
Step Action
Figure 6-9
Example of testing SFP LAN ports on the 24x10/100BT EPL with 8xSFP circuit pack
Figure 6-10
Example of testing LAN ports on 48x10/100BT I/O panels
Procedure 6-11
Testing L2SS or 20G L2SS circuit packs
Use this procedure to test the following Layer 2 Service Switch (L2SS) circuit
packs:
• L2SS VT1.5/LO 4xGE
• 20G L2SS 16 Port I/O 2xXFP / 8xSFP circuit pack
See the Data Application Guide, NTRN15BA, for more information on data
applications and functionality supported in this release. Refer to
Procedure 6-13, “Testing L2SS, 20G L2SS, and PDH gateway equipment
protection” for equipment protection testing.
Prerequisites
Before you start this procedure, make sure:
• You are wearing antistatic wrist straps or ankle straps.
• You have set up and provisioned the network element according to the
required configuration. See the chapter on equipment and facility
provisioning in Part 1 of Configuration - Provisioning and Operating,
323-1851-310 for details.
• You connect a personal computer (PC) to the shelf where the L2SS or 20G
L2SS circuit pack is installed.
• You have an Ethernet test set.
• You have fiber-optic patch cords.
• If you are testing 20G L2SS circuit pack, you have available the
appropriate fiber-optic cables that can interface to the LAN ports of the
1x10GE ports you are testing.
• You have all the documentation referenced in this procedure.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Step Action
1 Verify that the L2SS or 20G L2SS circuit pack is active by checking its LEDs.
For more information, see the section on alarm and trouble clearing strategy
in Part 1 of Fault Management - Alarm Clearing, 323-1851-543.
2 Launch the Site Manager application and log in to the network element. For
more information, see the section on procedures and options for logging in
and logging out in Administration and Security, 323-1851-301.
3 If Ethernet Facilities are provisioned, make sure that all LAN LOS LEDs on
the faceplate of the L2SS or 20G L2SS circuit pack are lit.
4 Provision the parameters involved in the test. For details, see the chapter on
provisioning roadmaps in the Data Application Guide, NTRN15BA.
5 Select and provision two ETH-UNI facilities for L2SS or 20G L2SS and two
WAN-UNI facilities (101 and 102) on the circuit pack you are testing.
Configure the “Untagged receive class of service” parameter to “Gold -
Green” if untagged traffic is used for test traffic. See the chapter on equipment
and facility provisioning in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310 (see Figure 6-11 on page 6-52).
6 Select your next step.
If you are testing Then go to
VT1.5/LO 4xGE L2SS circuit pack step 7
20G L2SS circuit pack step 20
Step Action
• Provision the associated virtual circuit endpoints for each of the two
virtual circuit segments. See Part 2 of Configuration - Bandwidth and
Data Services, 323-1851-320 for more information:
— For the first virtual circuit segment, provision one endpoint to be
associated with one of the ETH ports and the other endpoint to be
associated with one of the WAN ports. For the second virtual circuit
segment, provision the endpoints to be associated with the other
ETH and WAN ports. See the Data Application Guide, NTRN15BA,
for the different steps on how to create an end-to-end L2SS
connection.
• Provision endpoint mapping on the ETH-UNI ports. See Part 2 of
Configuration - Bandwidth and Data Services, 323-1851-320 for more
information.
Connecting the test set to the L2SS circuit pack
9 Connect the test set to the L2SS circuit pack (see Figure 6-11 on page 6-52).
10 Enable or disable VLAN tagging on the test port.
11 Configure the VLAN and PBIT if VLAN tagging is enabled. Set up the PBIT
so traffic is classified as GOLD CoS: this is determined by the Rx CoS profile
(Receive Class of Service profile) configured on the LAN/WAN port and VCE
(VCE Rx CoS profile overrides Rx CoS profile configured on the LAN/WAN
port).
12 Configure the test set:
Attention: The setting on the GE ports should have different source and
destination MAC addresses from a given port.
• packet size = <any value between 64 and 1600 bytes (or up to 9100 if the
maximum transfer unit [MTU] of the virtual circuit segment is also
changed)>
• utilization = <must be a lower value than the configured BW profile
without exceeding the WAN BW>
• autonegotiation = <same value as ETH facility autonegotiation value on
L2SS ports>. For example, if you are using the default value for the ETH
facility (default is ENABLE), you must set autonegotiation on the test set
to ENABLE also.
• Make sure that the VLAN Identifier (VLAN ID) and priority bits on the test
set match the respective values you provisioned for the endpoints
mappings on the L2SS circuit pack.
• Make sure you set up only one data stream to reduce test set errors.
Step Action
13 Clear the operational measurements counters for ETH and WAN facilities on
the L2SS circuit pack. See the procedure on clearing operational
measurements in Fault Management - Performance Monitoring,
323-1851-520.
14 Set up the test set BW not to exceed the configured BW profile on the VCE
Gold CoS.
15 Start the test set. After approximately five minutes, stop the transmission on
the test set.
16 On the test set, verify that the receive frame (byte) count matches the transmit
frame (byte) byte count.
17 Delete the virtual circuit (endpoint mapping, virtual circuit endpoints, virtual
circuit segments) you added. See Part 2 of Configuration - Bandwidth and
Data Services, 323-1851-320 for more information.
18 Delete the cross-connect you added between the WAN facilities. Refer to the
“Deleting path cross-connects” procedure in Part 1 of Configuration -
Bandwidth and Data Services, 323-1851-320.
19 Delete the ETH and WAN facilities you added for the test. Refer to the
“Deleting a facility from an equipment” procedure in Part 1 of Configuration -
Provisioning and Operating, 323-1851-310.
Go to step 36.
Connecting the test set to the 20G L2SS circuit pack
20 Set up a point to point virtual circuit segment using Gold CoS. See Part 2 of
Configuration - Bandwidth and Data Services, 323-1851-320 for more
information.
21 Provision the associated virtual circuit endpoints for the virtual circuit
segment. See Part 2 of Configuration - Bandwidth and Data Services,
323-1851-320 for more information.
22 Provision endpoint mapping on the ETH-UNI ports. See Part 2 of
Configuration - Bandwidth and Data Services, 323-1851-320 for more
information.
23 Connect a test port of the test set to Rx LAN port 1 of the 20G L2SS circuit
pack.
24 Connect a test port of the test set to a Tx LAN port of the 20G L2SS circuit
pack. For an illustration of the test setup on 20G L2SS circuit pack, see Figure
6-12 on page 6-53.
25 Provision STS192c/VC4-64c cross-connects on the 20G L2SS circuit pack.
For more information, refer to the “Adding a 2WAY, 1WAY, 2WAYPR,
1WAYPR, or 2WAYDPR path cross-connect” procedure in Part 1 of
Configuration - Bandwidth and Data Services, 323-1851-320.
Step Action
Attention: The throughput value for the 20G L2SS circuit pack when using
a STS-192c/VC4-64c connection rate is 100% for 256 bytes or smaller
packets (without FCS) or for 128 bytes or smaller packets (with FCS).
Step Action
35 Delete the ETH and WAN facilities you added for the test. Refer to the
“Deleting a facility from an equipment” procedure in Part 1 of Configuration -
Provisioning and Operating, 323-1851-310.
36 Remove the test set.
37 Repeat step 4 to step 36 for the other ETH facilities on the L2SS or 20G L2SS
circuit pack.
38 For 20G L2SS repeat for 10G ETH port but scale all values by multiple of 10.
39 Remove the test bandwidth profile you added.
—end—
Figure 6-11
Example of testing an L2SS circuit pack
Figure 6-12
Example of testing a 20G L2SS circuit pack
Procedure 6-12
Testing L2SS DS1/E1/DS3/E3 4XGE (PDH) circuit
packs
Use this procedure to test layer 2 function of L2SS DS1/E1/DS3/E3 4XGE
(referred as PDH gateway in this procedure) circuit packs. See the Data
Application Guide, NTRN15BA, for more information on data applications and
functionality supported in this release. Refer to Procedure 6-13, “Testing
L2SS, 20G L2SS, and PDH gateway equipment protection” for equipment
protection testing.
Prerequisites
Before you start this procedure, make sure:
• You are wearing antistatic wrist straps or ankle straps.
• You have set up and provisioned the network element according to the
required configuration. See Part 1 and 2 of Configuration - Provisioning
and Operating, 323-1851-310 for details.
• You connect a personal computer (PC) to the shelf where the PDH
gateway circuit pack is installed.
• You have an Ethernet test set.
• You have fiber-optic patch cords.
• Ensure that you have the required pluggables.
• You have all the documentation referenced in this procedure.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Step Action
1 Verify that the PDH gateway circuit pack is active by checking its LEDs. For
more information, see the section on alarm and trouble clearing strategy in
Part 1 of Fault Management - Alarm Clearing, 323-1851-543.
2 Launch the Site Manager application and log in to the network element. For
more information, see the section on procedures and options for logging in
and logging out in Administration and Security, 323-1851-301.
3 If Ethernet Facilities are provisioned, make sure that all LAN LOS LEDs on
the faceplate of the PDH gateway circuit pack are lit.
Step Action
4 Provision the parameters involved in the test. For details, see the chapter on
provisioning roadmaps in the Data Application Guide, NTRN15BA.
5 Select and provision two ETH-UNI and two WAN-UNI facilities on the circuit
pack you are testing. Configure the “Untagged receive class of service”
parameter to “Gold - Green” if untagged traffic is used for test traffic. See the
chapter on equipment and facility provisioning in Part 1 of Configuration -
Provisioning and Operating, 323-1851-310.
6 Provision WAN bandwidth (2WAY cross-connect between the two WAN
facilities). Refer to the “Adding a 2WAY, 1WAY, 2WAYPR, 1WAYPR, or
2WAYDPR path cross-connect” procedure in Part 1 of Configuration -
Bandwidth and Data Services, 323-1851-320 (see Figure 6-13 on page 6-57).
When provisioning the WAN, port can be set as non-PDH (same as regular
L2SS) or PDH (DS1, E1, DS3, E3): this will determine the max capacity that
the NNI link can provide.
7 Provision the test bandwidth profile. See Part 2 of Configuration - Bandwidth
and Data Services, 323-1851-320 for more information. If you have already
provisioned the test bandwidth profile, proceed to the next substep to set up
virtual circuit segments.
The bandwidth profile should match the NNI capacity to validate max NNI
throughput.
• Set up two point to point virtual circuit segments using Gold CoS.
Provision the virtual circuit segments identically. See Part 2 of
Configuration - Bandwidth and Data Services, 323-1851-320.
All the parameters for the two virtual circuit segments must be identical
(except the Virtual Circuit ID, which uniquely identifies each segment).
• Provision the associated virtual circuit endpoints for each of the two
virtual circuit segments. See Part 2 of Configuration - Bandwidth and
Data Services, 323-1851-320:
— For the first virtual circuit segment, provision one endpoint to be
associated with one of the ETH ports and the other endpoint to be
associated with one of the WAN ports.
— For the second virtual circuit segment, provision the endpoints to be
associated with the other ETH and WAN ports.
• Provision endpoint mapping on the two ETH UNI and two WAN UNI ports.
See Part 2 of Configuration - Bandwidth and Data Services,
323-1851-320.
8 Connect the test set to the PDH gateway circuit pack (see Figure 6-13 on
page 6-57). If your test set has only one port, then you can use a loop back
fiber on the second Ethernet port.
Step Action
Attention: The setting on the GE ports should have different source and
destination MAC addresses from a given port.
• packet size = <any value between 64 and 1600 bytes (or up to 9100 if the
maximum transfer unit [MTU] of the virtual circuit segment is also
changed)>
• utilization = depends on the provisioned connection rate on the circuit
pack and the configured BW profile. Refer to the Data Application Guide,
NTRN15BA for estimated throughput available per connection type
• autonegotiation = <same value as ETH facility autonegotiation value on
PDH gateway ports>. For example, if you are using the default value for
the ETH facility (default is ENABLE), you must set autonegotiation on the
test set to ENABLE also.
• Make sure that the VLAN Identifier (VLAN ID) and priority bits on the test
set match the respective values you provisioned for the endpoints
mappings on the PDH gateway circuit pack.
• Make sure you set up only one data stream to reduce test set errors.
12 Clear the operational measurements counters for ETH and WAN facilities on
the PDH gateway circuit pack. See the procedure on clearing operational
measurements in Fault Management - Performance Monitoring,
323-1851-520.
13 Start the test set. After approximately five minutes, stop the transmission on
the test set.
14 On the test set, verify that the receive frame count matches the transmit frame
count.
15 Delete the virtual circuit (endpoint mapping, virtual circuit endpoints, virtual
circuit segments) you added. See Part 2 of Configuration - Bandwidth and
Data Services, 323-1851-320.
16 Delete the cross-connect you added between the WAN facilities.
17 Delete the ETH and WAN facilities you added for the test. Refer to the
“Deleting a facility from an equipment” procedure in Part 1 of Configuration -
Provisioning and Operating, 323-1851-310.
Step Action
Procedure 6-13
Testing L2SS, 20G L2SS, and PDH gateway equipment
protection
Use this procedure to test L2SS VT1.5/LO 4xGE, 20G L2SS 16 Port I/O
2xXFP / 8xSFP circuit pack, and L2SS DS1/E1/DS3/E3 4xGE PDH gateway
equipment protection. Perform this procedure for each pair of L2SS or 20G
L2SS, and PDH gateway circuit packs in the network element. This procedure
requires personnel at the site of the network element.
Prerequisites
Before you perform this procedure, make sure that:
• You have all the documentation referenced in this procedure.
• The L2SS, 20G L2SS, or PDH gateway circuit pack is installed in the
correct slot in the network element (the working circuit pack should be in
an odd slot and protection circuit pack should be in the adjacent even slot).
See the procedure on installing circuit packs in the Installation technical
publication specific to the respective 6500 shelf type.
• The equipment and the facilities you want to test are provisioned. For
detailed procedures, see the chapter on equipment and facility
provisioning in Part 1 of Configuration - Provisioning and Operating,
323-1851-310.
• You have available an Ethernet test set that can interface to the L2SS, 20G
L2SS, and PDH gateway circuit pack you are testing, including all SFP or
XFP types you are using (a minimum of four GE interfaces are required).
• You connect a personal computer (PC) to the shelf where the circuit pack
is located.
• You have available the appropriate fiber-optic cables that can interface to
the LAN ports of the L2SS, 20G L2SS, and PDH gateway circuit pack you
are testing.
Step Action
1 Verify that both L2SS VT1.5/LO 4xGE, 20G L2SS or PDH gateway circuit
packs are active by checking their LEDs. For more information, see the
section on alarm and trouble clearing strategy in Part 1 of Fault Management
- Alarm Clearing, 323-1851-543.
2 Launch the Site Manager application and log in to the network element. For
more information, see the section on procedures and options for logging in
and logging out in Administration and Security, 323-1851-301.
Step Action
3 If Ethernet Facilities are provisioned, make sure that all LAN LOS LEDs on
the faceplate of the L2SS VT1.5/LO 4xGE, 20G L2SS or PDH gateway circuit
pack are lit.
4 Provision the protection scheme. Use the desired protection mode (Eqpt, L2,
L3, or LACP). If LACP mode is used, L2SS/20G L2SS ports must be
configured as LAG members. For details, see the protection switching
chapter in Part 2 of Configuration - Provisioning and Operating,
323-1851-310.
5 Select and provision two ETH-UNI facilities for L2SS, PDH, or 20G L2SS and
two WAN-UNI facilities on the circuit pack you are testing. Configure the
“Untagged receive class of service” parameter to “Gold - Green” if untagged
traffic is used for test traffic. If LACP protection mode is used, ETH-UNI
facilities must be configured as LAG members by configuring a LAG-UNI and
ETH-UNI ports with the same packet attributes and add the ETH-UNI ports to
the LAG. Two LAG ports should be configured. See the chapter on equipment
and facility provisioning in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310 on the circuit pack you are testing.
6 Provision WAN bandwidth (2WAY STS24c cross-connect between the two
WAN facilities). Refer to the “Adding a 2WAY, 1WAY, 2WAYPR, 1WAYPR, or
2WAYDPR path cross-connect” procedure in Part 1 of Configuration -
Bandwidth and Data Services, 323-1851-320 (see Figure 6-14 on page 6-62).
When provisioning the WAN, port can be set as non-PDH (same as regular
L2SS) or PDH (DS1, E1, DS3, E3): this will determine the max capacity that
the NNI link can provide.
7 Set up two virtual circuit segments with all CoS enabled. Provision the virtual
circuit segments identically.
All the parameters for the two virtual circuit segments must be identical
(except the Virtual Circuit ID, which uniquely identifies each segment).
Step Action
• Provision the associated virtual circuit endpoints for each of the two
virtual circuit segments:
— For the first virtual circuit segment, provision one endpoint to be
associated with one of the ETH ports or LAG ports if LACP mode is
used and the other endpoint to be associated with one of the WAN
ports.
— For the second virtual circuit segment, provision the endpoints to be
associated with the other ETH or LAG if LACP mode is used and the
second WAN port.
• For L2SS, 20G L2SS, or PDH provision endpoint mapping on the VCS of
the two ETH UNI ports and two WAN UNI ports on the circuit pack you
are testing with the appropriate VLAN. You can also add an endpoint
mapping for untagged traffic to allow untagged traffic in the VCS and “all
unprovisioned tags” to allow any VLAN in the VCS. See Part 2 of
Configuration - Bandwidth and Data Services, 323-1851-320.
8 Configure the test port’s VLAN and PBIT if VLAN tagging is used or untagged
traffic if an untagged VCE endpoint mapping was configured. Set up the PBIT
so traffic is classified in the desired CoS: this is determined by the Rx CoS
profile (Receive Class of Service profile) configured on the LAN/WAN port
and VCE (VCE Rx CoS profile overrides Rx CoS profile configured on the
LAN/WAN port).
Configure the test set as follows:
• packet size = <any value between 64 and 1600 bytes (or up to 9100 if the
maximum transfer unit [MTU] of the virtual circuit segment is also
changed)>
• utilization = depends on WAN BW and configured BW profile. Refer to the
Data Application Guide, NTRN15BA for estimated throughput available
per connection type.
• autonegotiation = <same value as ETH facility autonegotiation value on
L2SS, 20G L2SS, or PDH gateway ports>. For example, if you are using
the default value for the ETH facility (default is ENABLE), you must set
autonegotiation on the test set to ENABLE also.
• Make sure that the VLAN Identifier (VLAN ID) and priority bits on the test
set match the respective values you provisioned for the endpoints
mappings on the L2SS, 20G L2SS, or PDH gateway circuit pack.
9 Clear the operational measurements counters for ETH and WAN facilities on
the L2SS, 20G L2SS, or PDH gateway circuit pack. See the procedure on
clearing operational measurements in Fault Management - Performance
Monitoring, 323-1851-520.
Step Action
Testing L2SS, 20G L2SS, or PDH gateway protection (see Figure 6-14 on page 6-62)
10 Clear the operational measurements counters for LAN and WAN facilities on
the circuit pack. See the procedure on clearing operational measurements in
Fault Management - Performance Monitoring, 323-1851-520.
11 Connect the test set. See Figure 6-14 on page 6-62.
The test uses four GE ports, which can belong to either a single test set or
four separate test sets. If LACP mode is used, the test set ports must be
configured with LACP. Not all test sets support the LACP configuration.
12 Inject a test signal into the working circuit pack (13-1 and 13-2 in Figure 6-14
on page 6-62).
13 Verify that the test signal is running error-free.
Depending on the protection group provisioning, the test set ports connected
to the standby ports (14-2 and 14-3) will either receive no Ethernet frames or
no signal (laser off).
14 Re-seat the L2SS, 20G L2SS, or PDH gateway circuit pack.
15 Verify that the protection circuit pack is carrying traffic and the working circuit
pack either receives no signal (laser off) or receives no Ethernet frames.
16 Perform a forced switch on the protection circuit pack to move traffic back on
the working circuit pack. See the protection switching chapter in Part 2 of
Configuration - Provisioning and Operating, 323-1851-310.
When a failure occurs for L2 or LACP switch modes, a protection switch will
occur if the number of operational standby links is greater than the number of
active links. Otherwise, a protection switch will not be performed.
17 Stop and disconnect the test set.
18 Delete the virtual circuit (endpoint mapping, virtual circuit endpoints, virtual
circuit segments) you added. See Part 2 of Configuration - Bandwidth and
Data Services, 323-1851-320.
19 Delete the cross-connect you added between the WAN facilities.
20 Delete the ETH and WAN facilities you added for the test. Refer to the
“Deleting a facility from an equipment” procedure in Part 1 of Configuration -
Provisioning and Operating, 323-1851-310.
21 Repeat step 9 to step 20 for the other protection pairs.
22 Repeat for 20G L2SS 10GE ports but scale depending on the WAN port
capacity (total for all WAN ports cannot exceed 10G). For example, if 2 WAN
ports are used, each will not be able to exceed 5G so values should be scaled
by a multiple of 5.
—end—
Figure 6-14
Example of L2SS, 20G L2SS, or PDH gateway protection testing
Procedure 6-14
Testing RPR circuit packs
Use this procedure to test Resilient Packet Ring (RPR) circuit packs. See the
Data Application Guide, NTRN15BA, for more information on data
applications and functionality supported in this release.
Prerequisites
Before you start this procedure, make sure:
• You are wearing antistatic wrist straps or ankle straps.
• You have set up and provisioned the network element according to the
required configuration. See Part 1 of Configuration - Provisioning and
Operating, 323-1851-310 for details.
• You connect a personal computer (PC) to the shelf where the RPR circuit
pack is installed.
• You have an Ethernet test set with at least two GE ports.
• You have fiber-optic patch cords.
• You have all the documentation referenced in this procedure.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Step Action
1 Verify that the RPR circuit pack is active by checking its LEDs. For more
information, see the section on alarm and trouble clearing strategy in Part 1
of Fault Management - Alarm Clearing, 323-1851-543.
2 Launch the Site Manager application and log in to the network element. For
more information, see the section on procedures and options for logging in
and logging out in Administration and Security, 323-1851-301.
3 Make sure that all LAN LOS LEDs on the faceplate of the RPR circuit pack
are lit.
Step Action
Step Action
Attention: The setting on the GE ports should have different source and
destination MAC addresses from a given port.
7 Clear the operational measurements counters for ETH, WAN, and RPR
facilities on the RPR circuit pack. See the procedure on clearing operational
measurements in Fault Management - Performance Monitoring,
323-1851-520.
8 Start the test set. After approximately five minutes, stop the transmission on
the test set.
9 On the test set, verify that the receive frame (byte) count matches the transmit
frame (byte) byte count.
10 Delete the virtual circuit (endpoint mapping, virtual circuit endpoints, virtual
circuit segments) you added in step 4.
11 Delete the cross-connect you added in step 4 between the WAN facilities.
12 Delete the ETH, WAN, and RPR facilities you added in step 4 for the test.
13 Remove the test set.
14 Repeat step 4 to step 13 for the other ETH facilities on the RPR circuit pack.
15 Remove the test bandwidth profile you added in step 4.
—end—
Figure 6-15
Example of testing an RPR circuit pack
Procedure 6-15
Testing 1x10GE EPL circuit packs
Use this procedure to test 1x10GE EPL circuit packs. Perform this procedure
for each 1x10GE EPL circuit pack in the network element. This procedure
requires personnel at the site of the network element.
Prerequisites
Before you perform this procedure, make sure that:
• You have all the documentation referenced in this procedure.
• The 1x10GE EPL circuit pack is installed in the correct slot in the network
element. See the procedure on installing circuit packs in the Installation
technical publication specific to the respective 6500 shelf type
• The equipment and the facilities you want to test are provisioned. For
detailed procedures, see the chapter on equipment and facility
provisioning in Part 1 of Configuration - Provisioning and Operating,
323-1851-310.
• You have available an Ethernet test set that can interface to the 1x10GE
EPL circuit pack you are testing, including all XFP types you are using.
• You connect a personal computer (PC) to the shelf where the circuit pack
is located.
• You have available the appropriate fiber-optic cables that can interface to
the LAN ports of the 1x10GE EPL circuit pack you are testing.
Step Action
1 Verify that the 1x10GE EPL circuit pack is active by checking its LEDs. For
more information, see the section on alarm and trouble clearing strategy in
Part 1 of Fault Management - Alarm Clearing, 323-1851-543.
2 Launch the Site Manager application and log in to the network element. For
more information, see the section on procedures and options for logging in
and logging out in Administration and Security, 323-1851-301.
3 Record the current configuration of the 1x10GE EPL circuit pack.
4 Make sure that all LAN LOS LEDs on the faceplate of the 1x10GE EPL circuit
pack are lit.
Step Action
Attention: The throughput value for the 1x10GE EPL circuit pack when using
a STS-192c/VC4-64c connection rate is 100% for 256 bytes or smaller
packets (without FCS) or for 128 bytes or smaller packets (with FCS).
Step Action
Procedure 6-16
Testing SuperMux circuit packs
Use this procedure to test the SuperMux circuit packs. Perform this procedure
for each SuperMux circuit pack in the network element. This procedure
requires personnel at the site of the network element.
Prerequisites
Before you perform this procedure, make sure that:
• You have all the documentation referenced in this procedure.
• The SuperMux circuit pack is installed in the network element. Refer to the
procedure on installing circuit packs in the Installation technical
publication specific to the respective 6500 shelf type.
• The equipment and the facilities you want to test are provisioned. Refer to
the “Retrieving equipment and facility details” procedure in Part 1 of
Configuration - Provisioning and Operating, 323-1851-310.
• You have available an Ethernet, Fiber Channel or SONET/SDH test set
that can interface to the SuperMux circuit pack you are testing, including
all SFP types you are using.
• You connect a personal computer (PC) to the shelf where the circuit pack
is located.
• You have available the appropriate fiber-optic cables that can interface to
the LAN ports of the SuperMux circuit pack you are testing.
Step Action
1 Verify that the SuperMux circuit pack is active by checking its LEDs. For more
information, refer to the section on alarm and trouble clearing strategy in Part
1 of the Fault Management - Alarm Clearing, 323-1851-543.
2 Launch the Site Manager application and log in to the network element.
3 Record the current configuration of the SuperMux circuit pack.
4 Make sure that all LAN LOS LEDs on the faceplate of the SuperMux circuit
pack are lit.
Connecting the test set to the circuit pack
5 Perform Procedure 6-17, “Setting a hardware terminal loopback for a network
element” to add an optical fiber loopback at the optical interface you will be
using for the test.
Step Action
Step Action
Step Action
Testing protection
16 Make sure the protection circuit pack and its pluggables have their facilities
provisioned. You need two test sets to test the protection. See Figure 6-17 on
page 6-76 or Figure 6-18 on page 6-77 on how to connect the test set on the
circuit pack.
17 Perform “Setting a hardware terminal loopback for a network element” on
page 6-78 to add an optical fiber loopback at the protection optical interface
you will be using for the test.
18 Make sure both SuperMux circuit packs, to be configured in a protected
mode, are part of the same timing group. To do so, perform the following:
• Select Equipment & Facility Provisioning from the Configuration
menu.
• Ensure all facilities on the protection Supermux circuit pack are OOS.
Place the protection SuperMux’s equipment OOS.
• Edit the equipment of the protection SuperMux and set the Timing Group
ID to be the same as the working circuit pack. The Timing AID could be
the odd slot SuperMux equipment AID or the shelf equipment AID.
• Place the protection SuperMux’s equipment back IS. Ensure all facilities
are back IS.
19 Select your next step.
If the SFP is provisioned as Then go to
OC-n/STM-n step 20
FC100/FICON 1G, FC200/FICON 2G, step 29
FC400/FICON 4G, or GE
Step Action
21 Keep the setting on the test set unchanged. Select the protection pair to test
and provision the 1+1 or UPSR/SNCP protection scheme on the client ports.
Refer to the “Changing the protection scheme for a pair of facilities or
equipment” procedure in Part 2 of Configuration - Provisioning and
Operating, 323-1851-310.
22 Clear the performance monitoring and operational measurements counters
for client and line facilities on the protection circuit pack. Refer to the “Clearing
performance monitoring data” and “Clearing operational measurements”
procedures in Fault Management - Performance Monitoring, 323-1851-520.
23 Verify that traffic is carried error-free. Refer to the “Retrieving performance
monitoring data” and “Retrieving operational measurements” procedures in
Fault Management - Performance Monitoring, 323-1851-520.
24 Disconnect the Rx fiber from the working facility.
25 Inject a signal into the protection (standby) facility.
26 Clear the performance monitoring and operational measurements counters
for client and line facilities on the protection circuit pack. Refer to the “Clearing
performance monitoring data” and “Clearing operational measurements”
procedures in Fault Management - Performance Monitoring, 323-1851-520.
27 Verify that traffic is carried error-free. Refer to the “Retrieving performance
monitoring data” and “Retrieving operational measurements” procedures in
Fault Management - Performance Monitoring, 323-1851-520.
28 Select your next step.
If the circuit pack is equipped with Then go to
only one SFP type on all ports (testing method step 38
uses daisy-chaining)
multiple SFP types step 19
Step Action
33 Keep the setting on the test set unchanged. Verify that traffic is carried
error-free. Refer to the “Retrieving performance monitoring data” and
“Retrieving operational measurements” procedures in Fault Management -
Performance Monitoring, 323-1851-520.
34 Disconnect the Rx fiber from the working circuit pack.
35 Inject a signal into the protection (standby) circuit pack.
36 Clear the performance monitoring and operational measurements counters
for client (LAN and WAN) and line facilities on the protection circuit pack.
Refer to the “Clearing performance monitoring data” and “Clearing
operational measurements” procedures in Fault Management - Performance
Monitoring, 323-1851-520.
37 Verify that traffic is carried error-free. Refer to the “Retrieving performance
monitoring data” and “Retrieving operational measurements” procedures in
Fault Management - Performance Monitoring, 323-1851-520.
38 Delete all cross-connects. Make sure to reset the protection scheme on all
clients and line ports to Unprotected mode.
39 Restore the configuration data of the SuperMux circuit pack that you recorded
in step 3.
40 Repeat step 3 to step 39 for other SuperMux circuit packs in the shelf.
You have completed this procedure.
—end—
Figure 6-17
Example of testing a SuperMux circuit pack (single SFP type)
Figure 6-18
Example of testing a SuperMux circuit pack (multiple SFP types)
Procedure 6-17
Setting a hardware terminal loopback for a network
element
Use this procedure to set a hardware terminal loopback for a network element.
CAUTION
Risk of personal injury
When inserted in a shelf slot, the optical interface circuit pack
emits laser light that can blind. Keep all optical connectors on
the optical interface circuit packs capped when they are not
connected to optical fiber cables. Never look directly into the
end of an optical fiber.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Prerequisites
Before you perform this procedure, make sure that you have:
• optical power meter
• variable optical attenuators
• antistatic wrist or ankle strap
• fiber-optic patch cords
• fiber microscope
• all the documentation referenced in this procedure
Step Action
1 Disconnect the optical connectors from the optical interface you want to set
up the loopback.
2 Disable ALS on the optical facilities you are using for the test. Refer to the
“Editing facility parameters” procedure in Part 1 of Configuration -
Provisioning and Operating, 323-1851-310.
Step Action
Adding a VOA
3 Add a variable optical attenuator (VOA) to the Tx port on the working optical
interface circuit pack as follows:
a. Measure the output power at the optical interface Tx port. See Procedure
6-1, “Testing the power at the optical interface Tx port”.
Remove the protective cap from the connector of the VOA. Scope the optical
test cords, clean if necessary, and scope again. See the chapter on cleaning
connectors in Installation - General Information, 323-1851-201.0 for the
following:
• the procedure on cleaning optical connectors and adapters on patch
cords
• the illustration of a dirty optical fiber
• the illustration of a clean optical fiber
b. Connect one end of the VOA to the Tx port of the optical interface circuit
pack.
c. Connect the other end of the VOA to the optical power meter connector.
See Figure 6-19 on page 6-80.
d. Switch the optical power meter power on.
e. Adjust the set screw of the VOA until the display of the optical power
meter reads between the receiver sensitivity and overload level for the
respective optical interface. For more information on the normal operating
range and technical specifications, refer to the section on interface circuit
packs specifications in Part 3 of Planning, NTRN10EG.
f. Switch the optical power meter power off and disconnect the optical
power meter from the VOA.
g. Connect the VOA to the Rx port on the working optical interface circuit
pack.
4 Repeat step 1 and step 3 for the protection optical interface circuit pack.
5 If the DCC for the ports under test have been enabled, the optical loopback
sets an SDCC/RS DCC link failure alarm (the shelf processor is expecting
data from another shelf). By default, the DCCs are not enabled.
Step Action
VOA OPM
6500 shelf
Procedure 6-18
Restoring a network element to its initial state
Use this procedure to restore a network element to its initial state.
CAUTION
Risk of personal injury
When inserted in a shelf slot, the optical interface circuit pack
emits laser light that can blind. Keep all optical connectors on
the optical interface circuit packs capped when they are not
connected to optical fiber cables. Never look directly into the
end of an optical fiber.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Step Action
Table 7-1
Procedures in this chapter
Procedure
Procedure 7-1, “Adding bidirectional optical channels”
Procedure 7-2, “Adding unidirectional optical channels”
Procedure 7-3, “Deleting bidirectional optical channels”
Procedure 7-4, “Deleting unidirectional optical channels”
Procedure 7-5, “Force deleting optical channels”
Procedure 7-6, “Express deleting optical channels”
Procedure 7-7, “Adding the first optical channel to a Stretched Span”
Procedure 7-1
Adding bidirectional optical channels
Use this procedure to add bidirectional channels that originate or terminate at:
• a SCMD4 at a Thin OADM (TOADM)
• a CMD44 at a ROADM
• a CMD44 at a DIA OADM
• a CCMD12 at a Colorless OADM
• a CCMD12 at a low channel count DIA ROADM
• a CMD44, OMD4, OMDF4, or OMDF8 at a Metro ROADM
• a CCMD8x16 at a CDC ROADM
For instructions on how to add channels using the Control Plane for 6500
photonic systems that have the L0 Control Plane application enabled (that is,
OTS parameters Autoroute set to Disabled and CPS set to Enabled), refer to
the Layer 0 Control Plane Activation and Service Provisioning Overview in
Part 2 of the Control Plane Application Guide - Layer 0 (Photonic),
NTRN71AA.
You can begin adding channels for optimization once the network topology is
created and is visible.
When Autoroute is disabled, if the cross connections are provisioned with the
Active parameter set to True, the channels will be automatically added in all
domains. If the Active parameter is set to False, you must add the channels in
every domain even if DOC Auto Add is enabled.
Prerequisites
If new 6500 hardware is required to support a new channel at add/drop point,
you must first perform the new hardware installation before performing this
procedure (see Procedure 4-2, “Adding a new CMD44, CMD64, or BMD2”,
Procedure 4-3, “Adding a new OMD4 or OMX”, Procedure 4-4, “Adding a new
SCMD4”, Procedure 4-5, “Adding a new CCMD12”, or Procedure 5-1, “Adding
passive components”).
• review the “Guidelines for provisioning the Expected far end address
(EFEA) between a CMD and a transponder” on page 7-2
• for 40G or 100G services, ensure the transponder connection between the
40G or 100G mate circuit packs has been provisioned. Refer to the
procedure on adding a transponder connection in Part 1 of Configuration
- Bandwidth and Data Services, 323-1851-320.
• ensure that the differential provisioning is already provisioned. Refer to the
“Differential Provisioning” chapter in Part 1 of Configuration - Provisioning
and Operating, 323-1851-310.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
CAUTION
Backup and restore after a channel reconfiguration
When any channel reconfiguration (adding or deleting of
channels) is performed, it is recommended that you back up
the provisioning data for all network elements that the channels
traverse. This includes a backup on all shelves in any
consolidated TID site where the channel reconfiguration was
performed. If a restore is performed using an old database
backup (pre-channel reconfiguration), problems may occur on
any channel that was added, dropped, or passed through that
network element. When restoring data on a consolidated TID
site, you must restore the provisioning data for all the shelves
in the consolidated TID site.
Step Action
4 Provision a 2WAY photonic connection at each branch site (site where the
channel changes domains) for the selected channel. Refer to the procedure
on adding a photonic connection in Part 1 of Configuration - Bandwidth and
Data Services, 323-1851-320.
Note that if the OTS parameter Autoroute is disabled, the photonic
connections at domain boundaries can alternatively be provisioned after
provisioning CMD ADJ-TX adjacencies (after step 55).
(Note that for CDC configurations with existing WSS 50 GHz w/OPM C-Band
9x1 [NTK553FA/FC] and WSS Flex C-Band w/OPM 9x1 [NTK553LA] circuit
packs. when the cross connect is created, regardless of the ACTIVE flag
status, the Tx will tune to the wavelength and the channel will be added and
controlled by the Twin 1x20 WSSOPM controller, but will not be added onto
the line until either a DOC add or ACTIVE flag is set to TRUE. Contact Ciena
for information on deploying CDC configurations with NTK553FA/FC/LA
circuit packs.)
5 If the configuration uses an OPS, for the same selected channel provision the
associated 2WAY photonic connection on the second OPS path.
Step Action
Step Action
Provisioning for a service interface that supports SPLI Tx/Rx Type autodiscovery
13 In the Edit ADJ-TX dialog box, ensure that Paired Rx is set to Yes and Auto
Discovered is set to Auto.
14 If using SPLI to autoprovision the Tx power and Tx wavelength, ensure that
Sync Provisioned is set to True. Ensure SPLI Management is set to True on
transponder facility.
15 Edit the “Expected far end address format” to “TID-SH-SL-PRT”.
16 Enter the “Expected far end address” to be the OTMn facility of the service
layer circuit pack that was connected to the CMD in step 2.
The format must be <TID>-<shelf>-<slot>-<port> of the OTMn facility.
17 If required, provision additional ADJ-TX parameters:
• Customer defined facility identifier
• Circuit Identifier
• Active—This is an ADJ-TX parameter if Autoroute is enabled only. (When
Autoroute is disabled, Active is a cross connection parameter and can be
edited when provisioning the cross connection.)
• Expected Far End PEC
18 Click OK in the Edit ADJ-TX dialog box.
19 Ensure the CMD ADJ-TX facility primary state becomes “IS”.
20 If the OnePlanner Report specifies values for the Launch Power Overwrite
parameters that are different from the default values corresponding to the
transmitter type, you must edit the following CMD ADJ-TX fields:
• Min. Launch Power (dBm)
• Max. Launch Power (dBm)
• Actual Tx Power (dBm)
Step Action
21 If the OnePlanner Report specifies values for the Receive Power Overwrite
parameters that are different from the default values corresponding to the
receiver type, you must edit the following CMD ADJ-RX fields:
• Sensitivity level (dBm)
• Overload level (dBm)
• Nominal level (dBm)
Go to step 28.
Provisioning for a service interface that does not support SPLI Tx/Rx Type autodiscovery
22 In the Edit ADJ-TX dialog box, ensure that Paired Rx is set to Yes and Auto
Discovered is set to Manual.
23 Select the Transmitter Type as indicated in the EDP/IDP.
The Transmitter Type should match the service layer equipment (as Colored)
or be set to “Foreign” or “Foreign Coherent” for other types of transmitters.
a. If the OnePlanner Report specifies values for the Launch Power
Overwrite parameters that are different from the default values
corresponding to the transmitter type, you must edit the following CMD
ADJ-TX fields:
— Minimum launch power (dBm)
— Maximum launch power (dBm)
— Actual Tx Power (dBm)
b. If you selected the “Foreign” transmitter type, you can use the default
values or edit the following CMD ADJ-TX fields:
— Modulation Class (Custom1 to Custom6)
— Tx Minimum Spectral Width (GHz)
— Tx Signal Bandwidth 3dB (GHz)—cannot be less than 12.5 GHz
— Tx Signal Bandwidth 10dB (GHz)
— Min. Launch Power (dBm)
— Max. Launch Power (dBm)
— Actual Tx Power (dBm)
Step Action
c. If you selected the “Foreign Coherent” transmitter type, you can use the
default values or edit the following CMD ADJ-TX fields:
— Modulation Class (Custom1 to Custom6)
— Tx Minimum Spectral Width (GHz)
— Min. Launch Power (dBm)
— Max. Launch Power (dBm)
— Actual Tx Power (dBm)
You must edit the ‘Tx Signal Bandwidth 3dB (GHz)’ and ‘Tx Signal
Bandwidth 10dB (GHz)’ values to match the spectral characteristics of
the actual signal. Refer to the Photonic Layer Guide, NTRN15DA, for
information on setting these values.
24 If required, provision other ADJ-TX parameters:
• Expected far end address format
• Expected far end address
• Customer defined facility identifier
• Circuit Identifier
• Active—This is an ADJ-TX parameter if Autoroute is enabled only. (When
Autoroute is disabled, Active is a cross connection parameter and can be
edited when provisioning the cross connection.)
25 Click OK in the Edit ADJ-TX dialog box.
26 Ensure the CMD ADJ-TX primary state becomes “IS”.
27 If the “Foreign” or “Foreign Coherent” transmitter type is selected or if the
OnePlanner Report specifies values for the Receive Power Overwrite
parameters that are different from the default values corresponding to the
receiver type, you must edit the following CMD ADJ-RX fields:
• Sensitivity level (dBm)
• Overload level (dBm)
• Nominal level (dBm)
28 Select your next step.
If Then go to
the channel originates through a DIA step 29
otherwise step 30
autoroute is disabled For local add/drop, provision a
2WAY photonic connection from
the CMD Tx port to LIM port 5,
and from LIM port 8 to the CMD
Rx port.
Step Action
Provisioning for a service interface that supports SPLI Tx/Rx Type autodiscovery
36 In the Edit ADJ-TX dialog box, ensure that Paired Rx is set to Yes and Auto
Discovered is set to Auto.
37 Ensure that Sync Provisioned is set to True.
38 Edit the “Expected far end address format” to “TID-SH-SL-PRT”.
39 Enter the “Expected far end address” to be the OTMn facility of the service
layer circuit pack.
The format must be <TID>-<shelf>-<slot>-<port> of the OTMn facility.
Step Action
Step Action
Provisioning for a service interface that does not support SPLI Tx/Rx Type autodiscovery
43 In the Edit ADJ-TX dialog box, ensure that Paired Rx is set to Yes and Auto
Discovered is set to Manual.
44 Select the transmitter type as indicated in the EDP/IDP. It should match the
service layer equipment (as Colorless) or be set to “Foreign” or “Foreign
Coherent” for other types of transmitters.
a. If the OnePlanner Report specifies values for the Launch Power
Overwrite parameters that are different from the default values
corresponding to the transmitter type, you must edit the following CMD
ADJ-TX fields:
— Min. launch power (dBm)
— Max. launch power (dBm)
— Actual Tx Power (dBm)
b. If you selected the “Foreign” transmitter type, you can use the default
values or edit the following CMD ADJ-TX fields:
— Modulation Class (Custom1 to Custom6)
— Tx Minimum Spectral Width (GHz)
— Tx Signal Bandwidth 3dB (GHz)—cannot be less than 12.5 GHz
— Tx Signal Bandwidth 10dB (GHz)
— Min. Launch Power (dBm)
— Max. Launch Power (dBm)
— Actual Tx Power (dBm)
c. If you selected the “Foreign Coherent” transmitter type, you can use the
default values or edit the following CMD ADJ-TX fields:
— Modulation Class (Custom1 to Custom6)
— Tx Minimum Spectral Width (GHz)
— Min. Launch Power (dBm)
— Max. Launch Power (dBm)
— Actual Tx Power (dBm)
You must edit the ‘Tx Signal Bandwidth 3dB (GHz)’ and ‘Tx Signal
Bandwidth 10dB (GHz)’ values to match the spectral characteristics of
the actual signal. Refer to the Photonic Layer Guide, NTRN15DA, for
information on setting these values.
Step Action
Step Action
Step Action
60 In the DOC settings tab, make sure the Auto add channels is Enabled. If not,
then do the following:
• In the Settings tab, click on Edit button.
• In the Edit dialog box, set ''Auto add channels'' to Enabled.
• Click on the OK button to confirm your selection.
61 Repeat step 60 for all Photonic domains crossed by channel(s) being added.
62 Make sure all Photonic domains crossed by channel(s) being added are set
to the same automation mode. Refer to the “Editing the DOC Settings”
procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310 for details on how to edit DOC settings.
63 Repeat step 58 to step 62 in the opposite direction.
Setting OTDR baselines and calibrating SRA circuit packs
64 Before adding the first channels on the domain, identify whether SRA or
ESAM circuit packs are present in the domain. If there are SRA or ESAM
circuit packs in the domain:
• Run a Long (40000ns/120000m) OTDR trace and a Short
(1000ns/20000m) OTDR trace manually.
• Set the traces as baselines.
Step Action
Step Action
69 Repeat step 67 and step 68 in the opposite direction once the new channels
have been added and optimized in the first direction. (After the first channel
add, you can perform step 67 and step 68 on both directions simultaneously.)
When Autoroute is enabled, if the channels being added span multiple
domains, because Auto Add Channels is enabled in the DOC settings
throughout the network, addition of the channel to the upstream domain will
trigger the addition of the channel in all domains, starting from the upstream
domain and ending with the domain where the channel is received.
When Autoroute is disabled, if the cross connections are provisioned with the
Active parameter set to True, the channels will be added automatically in all
domains. If the Active parameter is set to False, you must add the channels
in every domain even if DOC Auto Add is enabled. To add the channels, you
can either use the DOC application or edit the cross connection Active
parameter value to True.
If “Partially Added” or “Partially Deleted” DOC status appears when
performing the Add/Delete channels procedures, refer to the “DOC Action
Failed: Add” and “DOC Action Failed: Delete” alarm clearing procedures in
Part 1 of Fault Management - Alarm Clearing, 323-1851-543.
For Raman spans over 35 dB, if the “Target Unachievable” alarm is raised on
Raman facilities, refer to the alarm clearing procedure in Part 2 of Fault
Management - Alarm Clearing, 323-1851-543.
If “Inactive:waiting for power” channel status appears when performing the
Add procedures, check the transmitter input power, and follow the alarm
clearing procedures to clear any Circuit Pack Missing, LOS, High Fiber Loss,
Adjacency Far End Not Discovered, Adjacency Discovery Unreliable, and
Adjacency Mismatch alarms at the site.
Once the channels are added, the Overall Status field displays a value of
Optimal. The Channel Condition and End-to-End Condition for the added
channels displays a value of Optimized.
—end—
Procedure 7-2
Adding unidirectional optical channels
Use this procedure to add unidirectional channels that originate or terminate
at:
• a SCMD4 at a Thin OADM (TOADM)
• a CMD44 at a ROADM
• a CMD44 at a DIA OADM
• a CMD44, OMD4, OMDF4, or OMDF8 at a Metro ROADM
For instructions on how to add channels using the Control Plane for 6500
photonic systems that have the L0 Control Plane application enabled (that is,
OTS parameters Autoroute set to Disabled and CPS set to Enabled), refer to
the Layer 0 Control Plane Activation and Service Provisioning Overview in
Part 2 of the Control Plane Application Guide - Layer 0 (Photonic),
NTRN71AA.
You can begin adding channels for optimization once the network topology is
created and is visible.
When Autoroute is disabled, if the cross connections are provisioned with the
Active parameter set to True, the channels will be automatically added in all
domains. If the Active parameter is set to False, you must add the channels in
every domain even if DOC Auto Add is enabled.
Optical Drop and Continue (OD&C) channels are uni-directional and can be
dropped at any intermediate site between far-end Rx target and Tx source.
ATTENTION
If the channel is unidirectional, the TX and RX adjacencies at both end points
must be un-paired.
Prerequisites
If new 6500 hardware is required to support a new channel at add/drop point,
you must first perform the new hardware installation before performing this
procedure (see Procedure 4-2, “Adding a new CMD44, CMD64, or BMD2”,
Procedure 4-3, “Adding a new OMD4 or OMX”, Procedure 4-4, “Adding a new
SCMD4”, Procedure 4-5, “Adding a new CCMD12”, or Procedure 5-1, “Adding
passive components”).
Make sure the transmitter wavelength is provisioned and set to the correct
Tx power required.
• review the “Guidelines for provisioning the Expected far end address
(EFEA) between a CMD and a transponder” on page 7-2
• for 40G or 100G services, ensure the transponder connection between the
40G or 100G mate circuit packs has been provisioned. Refer to the
procedure on adding a transponder connection in Part 1 of Configuration
- Bandwidth and Data Services, 323-1851-320.
• ensure that the differential provisioning is already provisioned. Refer to the
“Differential Provisioning” chapter in Part 1 of Configuration - Provisioning
and Operating, 323-1851-310.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
CAUTION
Backup and restore after a channel reconfiguration
When any channel reconfiguration (adding or deleting of
channels) is performed, it is recommended that you back up
the provisioning data for all network elements that the channels
traverse. This includes a backup on all shelves in any
consolidated TID site where the channel reconfiguration was
performed. If a restore is performed using an old database
backup (pre-channel reconfiguration), problems may occur on
any channel that was added, dropped, or passed through that
network element. When restoring data on a consolidated TID
site, you must restore the provisioning data for all the shelves
in the consolidated TID site.
Step Action
4 Provision a 1WAY photonic connection at each branch site (site where the
channel changes domains) for the selected channel. Refer to the procedure
on adding a photonic connection in Part 1 of Configuration - Bandwidth and
Data Services, 323-1851-320.
Note that if the OTS parameter Autoroute is disabled, the photonic
connections at domain boundaries can alternatively be provisioned after
provisioning CMD ADJ-TX adjacencies (after step 43).
5 If the configuration uses an OPS, for the same selected channel provision the
associated 1WAY photonic connection on the second OPS path.
Step Action
Step Action
Provisioning for a service interface that supports SPLI Tx/Rx Type autodiscovery
12 In the Edit ADJ-TX dialog box, set Paired Rx to No, Auto Discovered to Auto,
and Sync Provisioned to True for the ADJ-TX facility.
13 If using SPLI to autoprovision the Tx power and Tx wavelength, ensure that
Sync Provisioned is set to True. Ensure SPLI Management is set to True on
transponder facility.
14 Edit the “Expected far end address format” to “TID-SH-SL-PRT”.
15 Enter the “Expected far end address” to be the OTMn facility of the service
layer circuit pack that was connected to the CMD in step 2.
The format must be <TID>-<shelf>-<slot>-<port> of the OTMn facility.
16 If required, provision additional ADJ-TX parameters:
• Customer defined facility identifier
• Circuit Identifier
• Active—This is an ADJ-TX parameter if Autoroute is enabled only. (When
Autoroute is disabled, Active is a cross connection parameter and can be
edited when provisioning the cross connection.)
• Expected Far End PEC
17 Click OK in the Edit ADJ-TX dialog box.
18 Ensure the CMD ADJ-TX facility primary state becomes “IS”.
19 If the OnePlanner Report specifies values for the Launch Power Overwrite
parameters that are different from the default values corresponding to the
transmitter type, you must edit the following CMD ADJ-TX fields:
• Min. Launch Power (dBm)
• Max. Launch Power (dBm)
• Actual Tx Power (dBm)
20 If the channel is an optical drop and continue (OD&C) channel, set the
ADJ-TX routing rule to the Longest path using the TL-1 command:
ED-ADJ-TX::ADJ-<CMD shelf#>-<CMD slot#>-<CMD
port#>:CTAG:::ROUTINGRULE=LONGESTPATH;
Go to step 26.
Step Action
Provisioning for a service interface that does not support SPLI Tx/Rx Type autodiscovery
21 In the Edit ADJ-TX dialog box, ensure that Paired Rx is set to Yes and Auto
Discovered is set to Manual.
22 Select the Transmitter Type as indicated in the EDP/IDP.
The Transmitter Type should match the service layer equipment (as Colored)
or be set to “Foreign” or “Foreign Coherent” for other types of transmitters.
a. If the OnePlanner Report specifies values for the Launch Power
Overwrite parameters that are different from the default values
corresponding to the transmitter type, you must edit the following CMD
ADJ-TX fields:
— Min. launch power (dBm)
— Max. launch power (dBm)
— Actual Tx Power (dBm)
b. If you selected the “Foreign” transmitter type, you can use the default
values or edit the following CMD ADJ-TX fields:
— Modulation Class (Custom1 to Custom6)
— Tx Minimum Spectral Width (GHz)
— Tx Signal Bandwidth 3dB (GHz)—cannot be less than 12.5 GHz
— Tx Signal Bandwidth 10dB (GHz)
— Min. Launch Power (dBm)
— Max. Launch Power (dBm)
— Actual Tx Power (dBm)
c. If you selected the “Foreign Coherent” transmitter type, you can use the
default values or edit the following CMD ADJ-TX fields:
— Modulation Class (Custom1 to Custom6)
— Tx Minimum Spectral Width (GHz)
— Min. Launch Power (dBm)
— Max. Launch Power (dBm)
— Actual Tx Power (dBm)
You must edit the ‘Tx Signal Bandwidth 3dB (GHz)’ and ‘Tx Signal
Bandwidth 10dB (GHz)’ values to match the spectral characteristics of
the actual signal. Refer to the Photonic Layer Guide, NTRN15DA, for
information on setting these values.
Step Action
Step Action
33 Select the type of receiver as indicated in the EDP/IDP: it should match the
service layer equipment or be set to “Foreign” for other types of receivers.
If you select a foreign receiver, you must enter the following parameters
manually:
• Sensitivity level (dBm)
• Overload level (dBm)
• Nominal level (dBm)
34 You can also provision other ADJ-RX parameters:
• Expected far end address format
• Expected far end address
• Customer defined facility identifier
35 Click OK in the Edit ADJ-RX dialog box.
36 Ensure the CMD ADJ RX facility primary state becomes “IS”.
37 If the OnePlanner Report specifies values for the Receive Power Overwrite
parameters that are different from the default values corresponding to the
receiver type, you must edit the following CMD ADJ-RX fields:
• Sensitivity level (dBm)
• Overload level (dBm)
• Nominal level (dBm)
38 If the configuration includes an OPS, make sure that the Tx and Rx
adjacencies are provisioned at the OPS on both OPS paths. See
Procedure 3-2, “Provisioning adjacencies”.
39 Select your next step.
If Then go to
the channel terminates through a DIA step 40
otherwise step 41
autoroute is disabled (drop) For local add/drop,
provision a 2WAY
photonic
connection from
the CMD Tx port to
LIM port 5, and
from LIM port 8 to
the CMD Rx port.
Step Action
Step Action
48 In the DOC settings tab, make sure the Auto add channels is Enabled. If not,
then do the following:
• In the Settings tab, click on Edit button.
• In the Edit dialog box, set ''Auto add channels'' to Enabled
• Click on the OK button to confirm your selection.
49 Repeat step 48 for all Photonic domains crossed by channel(s) being added.
50 Make sure all Photonic domains crossed by channel(s) being added are set
to the same automation mode. Refer to the “Editing the DOC Settings”
procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310 for details on how to edit DOC settings.
Setting OTDR baselines and calibrating SRA circuit packs
51 Before adding the first channels on the domain, identify whether SRA or
ESAM circuit packs are present in the domain. If there are SRA or ESAM
circuit packs in the domain:
• Run a Long (40000ns/120000m) OTDR trace and a Short
(1000ns/20000m) OTDR trace manually.
• Set the traces as baselines.
Step Action
Step Action
55 Select all the new channels and click on the Add button.
Note: If the added channel is declared to be Optimized and a receiver alarm
is raised, verify the connectivity, padding and receiver adjacency provisioning
against the network design.
When Autoroute is enabled, if the channels being added span multiple
domains, because Auto Add Channels is enabled in the DOC settings
throughout the network, addition of the channel to the upstream domain will
trigger the addition of the channel in all domains, starting from the upstream
domain and ending with the domain where the channel is received.
When Autoroute is disabled, if the cross connections are provisioned with the
Active parameter set to True, the channels will be added automatically in all
domains. If the Active parameter is set to False, you must add the channels
in every domain even if DOC Auto Add is enabled. To add the channels, you
can either use the DOC application or edit the cross connection Active
parameter value to True.
To guarantee that the addition of OD&C channels is non-service affecting
(NSA), OD&C channels must be added to DOC one at a time.
If “Partially Added” or “Partially Deleted” DOC status appears when
performing the Add/Delete channels procedures, refer to the “DOC Action
Failed: Add” and “DOC Action Failed: Delete” alarm clearing procedures in
Part 1 of Fault Management - Alarm Clearing, 323-1851-543.
For Raman spans over 35 dB, if the “Target Unachievable” alarm is raised on
Raman facilities, refer to the alarm clearing procedure in Part 2 of Fault
Management - Alarm Clearing, 323-1851-543.
Once the channels are added, the Overall Status field displays a value of
Optimal. The Channel Condition and End-to-End Condition for the added
channels displays a value of Optimized.
—end—
Procedure 7-3
Deleting bidirectional optical channels
Use this procedure to delete bidirectional channels that originate or terminate
at:
• a SCMD4 at a Thin OADM (TOADM)
• a CMD44 at a ROADM
• a CMD44 at a DIA OADM
• a CCMD12 at a Colorless OADM
• a CCMD12 at a low channel count DIA ROADM
• a CMD44, OMD4, OMDF4, or OMDF8 at a Metro ROADM
• a CCMD8x16 at a CDC ROADM
You can delete any number of channels in the same operation; however, DOC
will sequence the deletion such that channels will be deleted in limited-size
bundles during the same operation to guarantee non-service affecting (NSA)
operation.
When Autoroute is disabled, if the cross connections are provisioned with the
Auto Delete parameter set to True, the cross connections will be automatically
deleted from all optical domains when the channel is deleted from DOC. If the
connection Auto Delete parameter is set to False, you must delete the cross
connections from each node, even if DOC Auto Delete is enabled.
Prerequisites
To perform this procedure you must:
• use an account with a UPC level of 4 or higher
• have the Site Manager interface open
• be logged into each network element to be traversed by channels to be
deleted
• do not disconnect any service layer transmitters from the system
• review the “Guidelines for provisioning the Expected far end address
(EFEA) between a CMD and a transponder” on page 7-2
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Step Action
Deleting channels
1 Select your next step.
If the OTS parameter Autoroute Then
is
enabled go to step 2
disabled and the channel(s) you go to step 7
want to delete are not managed
by Layer 0 Control Plane
disabled and the channel(s) you This procedure does not apply to
want to delete are managed by channels managed by Layer 0 Control
Layer 0 Control Plane Plane. To delete channels managed by
Layer 0 Control Plane, you must delete
the respective Control Plane
sub-network connection. Refer to
Configuration - Control Plane,
323-1851-330. (For detailed
information on Control Plane concepts,
applications, and engineering rules,
refer to 6500 Packet-Optical Platform
Control Plane Application Guide,
NTRN71AA.)
3 Log in to the site where the DOC entity resides for each optical domain being
crossed by the channel(s) being deleted and open the Domain Optical
Controller (DOC) application.
4 In the DOC settings tab, make sure “Auto delete channels” is Enabled. If not,
then do the following:
• In the Settings tab, click on Edit button.
• In the Edit dialog box, set ''Auto delete channels'' to Enabled.
• Click on the OK button to confirm your selection.
5 Repeat step 4 for all Photonic domains crossed by channel(s) being deleted.
Step Action
6 Make sure all Photonic domains crossed by channel(s) being deleted are set
to the same automation mode. Refer to the “Editing the DOC Settings”
procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310 for details on how to edit DOC settings.
Then go to step 8.
7 If Autoroute is disabled, log into each network element along the channel path
and use the Photonic Connections application to set the Active parameter of
the cross connection to False and the Auto Delete parameter to True.
8 Log in to the site where the DOC entity resides, in the domain where the
channels ingress the optical network (that is, where the service layer DWDM
transmitter is connected to the CMD). Perform the following:
• In the Configuration -> Photonic Services -> Domain Optical
Controller (DOC), click on either the Start Monitoring or the Refresh
button.
• Select the DOC entity that is controlling the channel to be deleted.
• Select the channels to be deleted.
• Click on the Delete button.
• Click on the Yes button in the confirmation dialog that appears.
If the delete command fails or if the “Partially Deleted” DOC status appears
when performing the Delete channels procedure, refer to the “DOC
Command Failed: Delete” alarm clearing procedure in Part 1 of Fault
Management - Alarm Clearing, 323-1851-543.
Once the channels are deleted, the Overall Status field displays a value of
Optimal, and the value displayed in the Channel Condition and in the
End-to-End Condition columns for each remaining channel entity is
Optimized. The Channel Condition and the End-to-End Condition of the
deleted channels is Inactive.
When Autoroute is enabled, if the DOC Auto delete channels parameter is
enabled in all optical domains (different Optical System Identifiers) that the
selected channel is crossing, then deleting this channel from an upstream
domain will automatically delete it from all downstream domains, starting with
the receiving domain and going back towards the source domain.
When Autoroute is disabled, if the cross connections are provisioned with the
Auto Delete parameter set to True (step 7), the cross connections will be
automatically deleted from all optical domains when the channel is deleted
from DOC. (If the connection Auto Delete parameter is set to False, you must
delete the cross connections from each node, even if DOC Auto Delete is
enabled.)
9 Repeat step 8 for the other direction. You can perform step 8 on both
directions simultaneously.
Step Action
10 For the selected channel, delete the 2WAY photonic connection at each
branch site (site where the channel changes domain) if the deleted channel
crosses optical domains. Refer to the “Deleting Photonic connections”
procedure in Part 1 of Bandwidth and Data Services Management,
323-1851-320.
At ROADM sites where the channel stays within the same Photonic domain
(that is, both directions are in the same Photonic domain), if Autoroute is
enabled, the photonic connections are system-derived and will be
auto-deleted when the CMD ADJ-TX is deprovisioned.
11 If the configuration uses an OPS, for the same deleted channel delete the
associated photonic connection on the second OPS path.
Deprovisioning the CMD ADJ-TX/ADJ-RX
12 Log in to the site where the selected channel originates.
13 Select your next step.
If the channel you are deleting Then go to
originates through a DIA step 14
otherwise step 15
14 Delete the 2WAY photonic connection between the DIA CMD44 Ch In port
and the Backbone amplifier Line B Out port for the selected channel. Refer to
the “Deleting Photonic connections” procedure in Part 1 of Bandwidth and
Data Services Management, 323-1851-320. If autoroute is disabled, delete
the photonic connection for the CMD to LIM manually.
15 Select your next step.
If the channel you are deleting Then go to
originates through a Colorless OADM step 16
otherwise step 17
16 Delete the 2WAY photonic connection between the CCMD12 Ch In port and
the Backbone amplifier Line B Out port for the selected channel. Refer to the
“Deleting Photonic connections” procedure in Part 1 of Bandwidth and Data
Services Management, 323-1851-320.
17 Open the Equipment and Facility Provisioning application. Select the CMD
equipment corresponding to the channel to be deleted.
18 Select “ADJ-TX” from the Facility Type drop down list.
19 Select the ADJ-TX that corresponds to the wavelength to be deleted and click
on the Edit button.
The Edit ADJ-TX dialog box opens.
Step Action
21 In the Edit ADJ-TX dialog box, change the Expected far end address to Null.
Go to step 23.
22 In the Edit ADJ-TX dialog box, change the Transmitter type to Unknown.
23 Click OK in the Edit ADJ-TX dialog box.
24 Click OK in the confirmation message if it appears.
25 Repeat from step 12 for the site where the selected channel is terminating.
26 Repeat from step 10 for each deleted channel.
After you delete a channel, some ports on photonic circuit packs that
originally had light may no longer have light, and will raise a Loss of signal
alarm. This is an expected behavior. To clear the alarm, change the
secondary state of the affected facility to AINS.
27 If the transponder must be disassociated from the CMD port, remove the
EFEA provisioning on the transponder ADJ pointing to the CMD, if present:
• In the Equipment and Facility Provisioning application, select the
transponder equipment.
• Select “ADJ” from the Facility Type drop down list.
• In the Edit ADJ dialog box, remove the EFEA provisioning.
• Click OK in the Edit ADJ dialog box.
• Click OK in the confirmation message if it appears.
Note: For TOADM configurations, line amplifiers connected to sCMD4s may
not go into shutoff mode when all channels are deleted due to the limited
range of the internal VOAs coupled with the fact that the transponders stay
tuned and outputting power in this colored configuration. To avoid this,
disconnect all transponders connected to the affected SMD4s after the last
channel is deleted.
—end—
Procedure 7-4
Deleting unidirectional optical channels
Use this procedure to delete unidirectional channels that originate or
terminate at:
• a SCMD4 at a Thin OADM (TOADM)
• a CMD44 at a ROADM
• a CMD44 at a DIA OADM
• a CMD44, OMD4, OMDF4, or OMDF8 at a Metro ROADM
You can delete any number of channels in the same operation; however, DOC
will sequence the deletion such that channels will be deleted in limited-size
bundles during the same operation to guarantee non-service affecting (NSA)
operation.
When Autoroute is disabled, if the cross connections are provisioned with the
Auto Delete parameter set to True, the cross connections will be automatically
deleted from all optical domains when the channel is deleted from DOC. If the
connection Auto Delete parameter is set to False, you must delete the cross
connections from each node, even if DOC Auto Delete is enabled.
Note: For TOADM configurations, line amplifiers connected to sCMD4s
may not go into shutoff mode when all channels are deleted due to the
limited range of the internal VOAs coupled with the fact that the
transponders stay tuned and outputting power in this colored
configuration. To avoid this, disconnect all transponders connected to the
affected SMD4s after the last channel is deleted.
Prerequisites
To perform this procedure you must:
• use an account with a UPC level of 4 or higher
• have the Site Manager interface open
• be logged into each network element to be traversed by channels to be
deleted
• do not disconnect any service layer transmitters from the system
• review the “Guidelines for provisioning the Expected far end address
(EFEA) between a CMD and a transponder” on page 7-2
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Step Action
Deleting channels
2 Log in to the site where the DOC entity resides for each optical domain being
crossed by the channel(s) being deleted and open the Domain Optical
Controller (DOC) application.
Step Action
4 In the DOC settings tab, make sure the Auto delete channels is Enabled. If
not, then do the following:
• In the Settings tab, click on Edit button.
• In the Edit dialog box, set ''Auto delete channels'' to Enabled
• Click on the OK button to confirm your selection.
5 Repeat step 4 for all Photonic domains crossed by channel(s) being deleted.
6 Make sure all Photonic domains crossed by channel(s) being deleted are set
to the same automation mode. Refer to the “Editing the DOC Settings”
procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310 for details on how to edit DOC settings.
Then go to step 8.
7 If Autoroute is disabled, log into each network element along the channel path
and use the Photonic Connections application to set the Active parameter of
the cross connection to False and the Auto Delete parameter to True.
8 Log in to the site where the DOC entity resides, in the domain where the
channels ingress the optical network (that is, where the service layer DWDM
transmitter is connected to the CMD). Perform the following:
• In the Configuration -> Photonic Services -> Domain Optical
Controller (DOC), click on either the Start Monitoring or the Refresh
button
• Select the DOC entity that is controlling the channel to be deleted.
• Select the channels to be deleted.
• Click on the Delete button.
• Click on the Yes button in the confirmation dialog that appears.
If the delete command fails or if the “Partially Deleted” DOC status appears
when performing the Delete channels procedure, refer to “DOC Command
Failed: Delete” alarm clearing procedure in Part 1 of Fault Management -
Alarm Clearing, 323-1851-543.
After the channels are deleted, the Overall Status field displays a value of
Optimal, and the value displayed in the Channel Condition and in the
End-to-End Condition columns for each remaining channel entity is
Optimized. The Channel Condition and the End-to-End Condition of the
deleted channels is Inactive.
Step Action
13 Delete the 1WAY photonic connection between the DIA CMD44 Ch In port
and the Backbone amplifier Line B Out port for the selected channel. Refer to
the “Deleting Photonic connections” procedure in Part 1 of Bandwidth and
Data Services Management, 323-1851-320. If autoroute is disabled, delete
the photonic connection for the CMD to LIM manually.
Step Action
14 Open the Equipment and Facility Provisioning application. Select the CMD
equipment corresponding to the channel to be deleted.
15 Select “ADJ-TX” from the Facility Type drop down list
16 Select the ADJ-TX that corresponds to the wavelength to be deleted and click
on the Edit button.
The Edit ADJ-TX dialog box opens.
17 In the Edit ADJ-TX dialog box, change the Transmitter type to Unknown.
18 It is recommended to set the Paired Rx parameter to Yes.
19 Click OK in the Edit ADJ-TX dialog box.
20 For an OD&C channel, set the ADJ-TX routing rule to the Shortest path using
the TL-1 command:
ED-ADJ-TX::ADJ-<CMD shelf#>-<CMD slot#>-<CMD
port#>:CTAG:::ROUTINGRULE=SHORTESTPATH;
21 Log in to the site where the selected channel terminates and open the
Equipment and Facility Provisioning application. Select the CMD equipment
corresponding to the channel to be deleted.
22 Select your next step.
If the channel you are deleting Then go to
terminates through a DIA step 23
otherwise step 24
23 Delete the 1WAY photonic connection between the Backbone amplifier Line
A In port to the DIA CMD44 Ch Out port for the selected channel. Refer to the
“Deleting Photonic connections” procedure in Part 1 of Configuration -
Bandwidth and Data Services, 323-1851-320. If autoroute is disabled, delete
the photonic connection for the CMD to LIM manually.
24 Select “ADJ-RX” from the Facility Type drop down list.
25 Select the ADJ-RX that corresponds to the wavelength to be deleted and click
on the Edit button.
The Edit ADJ-RX dialog box opens.
26 In the Edit ADJ-RX dialog box, change the Receiver type to Unknown.
27 Click OK in the Edit ADJ-RX dialog box.
28 Click OK in the confirmation message.
Step Action
29 If applicable, repeat step 21 to step 27 for all OD&C intermediate drop Rx Adj,
including branch domain drops for the channel that was deleted.
30 Repeat from step 9 for each deleted channel.
After you delete a channel, some ports on photonic circuit packs that
originally had light may no longer have light, and will raise a Loss of signal
alarm. This is expected. To clear the alarm, change the secondary state of the
affected facility to AINS.
31 If the transponder must be disassociated from the CMD port, remove the
EFEA provisioning on the transponder ADJ pointing to the CMD, if present:
• In the Equipment and Facility Provisioning application, select the
transponder equipment.
• Select “ADJ” from the Facility Type drop down list.
• In the Edit ADJ dialog box, remove the EFEA provisioning.
• Click OK in the Edit ADJ dialog box.
• Click OK in the confirmation message if it appears.
Note: For TOADM configurations, line amplifiers connected to sCMD4s may
not go into shutoff mode when all channels are deleted due to the limited
range of the internal VOAs coupled with the fact that the transponders stay
tuned and outputting power in this colored configuration. To avoid this,
disconnect all transponders connected to the affected SMD4s after the last
channel is deleted.
—end—
Procedure 7-5
Force deleting optical channels
Note: Perform this procedure when channel deleting using
Procedure 7-3, “Deleting bidirectional optical channels” or Procedure 7-4,
“Deleting unidirectional optical channels” has failed. This procedure must
be performed in conjunction with Procedure 7-3, “Deleting bidirectional
optical channels” or Procedure 7-4, “Deleting unidirectional optical
channels”, and not as a stand-alone procedure.
CAUTION
Risk of traffic interruption
Channel deletion using the Force Delete button can impact
existing channels that are not force deleted.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Step Action
Step Action
Procedure 7-6
Express deleting optical channels
Use this procedure to express delete optical channels from a 6500
Packet-Optical Platform system when a major outage has occurred on the
optical line fibers that prevents delete (Procedure 7-3, “Deleting bidirectional
optical channels” or Procedure 7-4, “Deleting unidirectional optical channels”)
and force delete (Procedure 7-5, “Force deleting optical channels”) operations
from being successful. This procedure applies only to DOC Enhanced
Automation mode.
Prerequisites
• For every section of the optical line, check the line adjacencies (ADJ-LINE)
of the line-facing amplifier and make sure that the following information is
provisioned:
— Actual Far End Address
— Expected Far End Address
and that the Status is Reliable.
• Before you disconnect any service layer transmitters from the system, you
must delete the optical channel from the DOC.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
Step Action
1 From the navigation tree, select Configuration -> Photonic Services ->
Domain Optical Controller (DOC).
2 Identify and select the channel you want to express delete.
3 From the DOC Trail, identify the upstream DOC.
4 From the NE Trail, identify the network element and the shelf where the
channel originates.
5 If you have not already done so, open a Site Manager session to the selected
network element and log into the Site Manager interface as an admin level
user.
6 Select Configuration -> Equipment & Facility Provisioning.
7 Select the shelf you identified in step 4.
8 Select the CMD and ADJ-TX for the channel you want to delete.
9 Click the Edit button and in the Edit facility ADJ-TX dialog window, set the
Active parameter to False. Then set the Express delete parameter to True.
10 Repeat step 1 to step 9 for all channels you want to delete.
11 Log into the upstream DOC network elements that control the channels.
12 Select Configuration -> Photonic Services -> Domain Optical Controller
(DOC) and click the Start Monitoring button. Monitor the status of all the
channels you are deleting.
Step Action
13 After all the channels report an End-to-End Condition of Inactive, select your
next step.
If you performed the express Then
delete to
move the channels to another Re-add the channels to the new path.
path See Procedure 7-1, “Adding
bidirectional optical channels”.
completely remove the channels Go to Procedure 7-3, “Deleting
(that is, remove all the information bidirectional optical channels” or
associated with the channels, Procedure 7-4, “Deleting unidirectional
remove/disconnect TX/RX optical channels” to delete the Tx/Rx
equipment) adjacency.
—end—
Procedure 7-7
Adding the first optical channel to a Stretched Span
Use this procedure to manage traffic on a Stretched Span configuration,
specifically to manually add a wavelength used to carry OSC traffic over a
span exceeding the OSC link budget. Figure 7-1 on page 7-55 illustrates a
configuration example. The ROADM in the Stretched Span does not support
the DIA or Colorless OADM configuration.
This procedure applies to systems with the OTS parameter Autoroute set to
Enabled. For instructions on how to add channels using the Control Plane for
6500 photonic systems that have the L0 Control Plane application enabled
(that is, OTS parameters Autoroute set to Disabled and CPS set to Enabled),
refer to the Layer 0 Control Plane Activation and Service Provisioning
Overview in Part 2 of the Control Plane Application Guide - Layer 0 (Photonic),
NTRN71AA.
This procedure does not apply for Raman spans, but can be used for spans
equipped with line facing equipment such as MLA2, MLA2 w/ VOA, MLA3.
After you complete this procedure, you can add other traffic wavelengths using
DOC (see Procedure 7-1, “Adding bidirectional optical channels”).
CAUTION
Risk of laser radiation exposure
During this procedure the fiber plant does not have to be
disrupted and the system remains a Class 1(IEC)/Class I
(FDA) product.
If the fiber downstream of the MLA2/MLA3 Line A output
connector becomes disconnected accidentally while the Amp
Auto Shutoff Disabled feature is active, the radiation at the
exposed fiber can be at hazard level 1M (IEC 60825-2). In this
situation, you must take all safety precautions appropriate to
hazard level 1M (IEC 60825-2).
Prerequisites
• The installation of terminal (6500/5000) equipment is completed and
terminal equipment is fibered.
If 5000 equipment is used as a data communications route, an MOTR
circuit pack is required for communications. One of the optical mux ports
is connected to a switch (which acts as a media converter) to which an
Ethernet cable can be connected, thus extending the ILAN connection
between sites.
• Network element and nodal commissioning is complete.
• Amplifier peak power provisioning is complete.
• Communications are available to the 6500 network elements on either
side of the Stretched Span.
• Resources are deployed on both sides of each Stretched Span that exists
in the network, at the sites where the 6500 data communications are
bridged to a terminal shelf. Resources can communicate to coordinate
their actions.
• The site EDPs (engineering design packages)/IDPs (international
documentation packages) and the terminal (6500/5000 Technical
Publications) are available.
• Have an optical power meter available.
• The transmitters and the receivers of the terminal cards carrying the OSC
traffic are fibered but not connected to the CMD44.
• There are no wavelengths present on the system.
Figure 7-1
Example of adding the first optical channel to a Stretched Span (using 6500 terminal equipment)
Stretched Span
6500 6500
Step Action
2 Set an OSPF router on the 6500 shelves over which the data communications
will be bridged.
3 Provision an OSPF circuit on the ILAN IN or ILAN OUT facility of the 6500
shelves over which the data communications will be bridged.
4 On the 6500 photonic shelf, provision an OSPF circuit on the ILAN (IN or
OUT) facilities that are handing off the data communication traffic to the 6500
shelf with the GCC0 carrying cards.
This procedure assumes that the necessary ILAN port has been correctly
provisioned when the shelf was commissioned.
5 Where the data communications are bridged over to a 6500 shelf, connect a
straight-through Ethernet cable between the ILAN IN or ILAN OUT port of the
6500 shelf with the GCC0 carrying cards and the ILAN (IN or OUT) of the
6500 photonic shelf.
6 On each 6500 shelf over which the data communications are bridged,
provision an OSPF circuit on the GCC0 facility that will carry the traffic.
Go to step 12.
Step Action
Step Action
17 At the channel Ingress NE, set the channel access loss to minimum by setting
the parameters of the corresponding channel control (CHC) facility on the
WSS as follows:
• Opaque state set to No
• Switch Selector as per EDP/IDP (ROADM channel access)
• Target Loss set to 0 dB
18 Select the Line B (transmit) facility (port 6 of MLA/MLA2/MLA3) that comes
after the multiplexing in the wavelength path. Using an optical power meter,
verify that the loss between the terminal transmitter and the Line B input is
within specifications (use the values in Table 4-3 on page 4-107 and calculate
the maximum loss that applies to your configuration, then enter in Table 7-2).
If the loss is higher than expected, locate the source of the excessive loss and
take the appropriate corrective actions.
Table 7-2
Maximum multiplexing loss
Site configuration Maximum loss (dB)
Step Action
21 The LINE B amplifier facing the Stretched Span will be in automatic shutoff.
You must disable ALSO to add the wavelength. This is done by putting the
Line A AMP facility (port 8) into shutoff disabled mode as follows:
Edit the amplifier facility to set the ALSO Disabled value to True.
22 A few seconds after completing step 21, the following alarms should clear:
• the Automatic Shutoff alarm against the LINE B AMP facility (port 6)
amplifier facing into the Stretched Span
• the Optical Line Fail alarm against the downstream Line A AMP facility
(port 8)
23 Set the gain of the LINE B amplifier facing the Stretched Span so that the total
output power is equal to the provisioned target peak power.
This procedure assumes that at this stage, the peak power targets of all the
amplifiers in the Stretched Span network have been provisioned as indicated
in the EDP/IDP. Take the appropriate actions if this is not the case.
24 Communicate with the team on the other side of the Stretched Span to
indicate that the wavelength is now present over the Stretched Span.
25 From this point on, the resource on the other side of the Stretched Span takes
the relay to complete the amplifier gain adjustments until they reach the
demux. Vice-versa, the team on the other side will ask you to take the relay
in the other direction.
26 Set the amplifier gain of the downstream Line A amplifier as follows:
a. Use the Site Manager Performance Monitoring application to measure
the input power of the LINE A IN port and compare it with the output
power from the previous amplifier (Line B OUT [port 5]). If the span loss
is not as expected, take the appropriate actions.
b. Select the type of site.
If the site is Then
a ROADM site Use the CHMON PMs to measure the output power of
the channel being added at the LINE A OUT port of the
amplifier (CHMON-<shelf>-<slot>-7).
a Line Amp site Use the AMP PMs to measure the output power of the
LINE A OUT port of the amplifier.
Set the gain of the LINE A amplifier so that the total
output power is equal to the provisioned target peak
power.
Step Action
c. Ensure that there are no Input or Output LOS alarms against the Line A
amplifier (AMP-<shelf>-<slot>-8). If this amplifier is connected to the
stretched span, the input LOS threshold should be set to -40 and the
output LOS threshold should be set to at least 3 dB lower than the current
output power.
This procedure assumes that at this stage the peak power targets of all the
amplifiers in the network have been provisioned as indicated in the EDP/IDP.
Take the appropriate actions if this is not the case.
The output power may be higher than expected due to minimum gain.
27 Select your next step.
If Then
you are at the terminal site go to step 28
otherwise return to step 19 and repeat until you
reach the terminal site
29 If the site uses an interior SLA that is managed by DOC, set the gain of the
interior SLA as follows:
a. Use the Site Manager Performance Monitoring application to measure
the input power of the LINE A IN port and compare it with the output
power from the previous amplifier. If the span loss is not as expected, take
the appropriate actions. (The loss between the MLA and the interior SLA
could be due to a DSCM or other form of pad.)
b. Use the Site Manager Performance Monitoring application to measure
the output power of the LINE A OUT port of the amplifier.
c. Set the gain of the amplifier so that the total power at the Line A Out is
equal to the provisioned target peak power.
30 If the site uses a 9x1 50GHz WSS, you must take the demux amplifier out of
forced shutoff. In the Site Manager interface, select the WSS AMP facility and
edit FORCEDSHUTOFF=DISABLED.
Step Action
31 At the demux, adjust the Receiver power as close as possible to the nominal
power of the receiver adjacency. Use an optical power meter to measure the
receiver power. Make adjustments by changing the gain of the WSS demux
EDFA if applicable.
32 When step 31 is completed in both directions, allow a few minutes for the
terminal cards to settle. Retrieve the OTU layer performance monitoring
parameters for the terminal cards in both directions. Confirm that the OTU
layer defects are not incrementing (CV, ES, SES, SEFS).
33 Select your next step.
If OTU layer PMs Then go to
are incrementing for a given direction step 34
are not incrementing in either direction step 36
34 Starting from the receiving end, increase the pre-amplifier (Line A [port 8]
AMP facility of the MLA) gain by 1 dB, wait for one minute, then refresh the
PM data to see if OTU layer defects are still incrementing.
35 Repeat step 34 as necessary until the OTU layer defects are no longer
detected. If the amplifier is already at its maximum gain (see gain ranges
below), leave it as is and move to the next amplifier.
Amplifier Gain range (dB)
MLA Line A 7 - 20
36 When communication is established through the routed link, allow the system
a few minutes to provide complete visibility of the domain from both sides of
the Stretched Span. To verify data communication continuity, log into the
network element on the other side of the Stretched Span.
37 If the network contains another Stretched Span that requires a manual
channel addition, go to step 14. After a channel has been manually added to
all Stretched Spans to provide communications to the entire network, go to
step 38.
38 Clear all the alarms as indicated in Fault Management - Alarm Clearing,
323-1851-543. Make sure all amplifier facilities are in-service (set input LOS
threshold 3 dB below current power and secondary state to AINS, if need be).
Step Action
d. If a channel that has not yet been manually added to the system is
unintentionally set to “Not Optimal” using this procedure, repeat step 41
substep a, substep b, and substep c to set the channel that has been
manually added to the system to “Not Optimal”.
e. Log out of the TL-1 interface using the following command:
CANC-USER::<ADMIN Level User>:<CTAG>;
42 Repeat step 41 for all channels manually added to the system.
Step Action
43 Take the Line A AMP facilities out of Auto Shutoff Disabled mode to re-enable
normal response to ALSO Automatic Shutoff requests to Line A Amps on the
Stretched Span(s):
Edit the Line A AMP facilities to set the ALSO Disabled value to False.
44 For normal operation of Stretched Span applications with valid optical safety
feature operation, the Shutoff Thresholds for the Line A AMP facilities must
be provisioned to -40 dBm, which is below their defaults. (MLA Line A default
is -35 dBm; MLA2 Line A default is -39 dBm; MLA3 Line A default is -39 dBm.)
Do not provision this threshold below -40 dBm during normal operation. All
optical safety testing and accreditation is suspect if this threshold is
provisioned below -40 dBm.
Check that the Shutoff Thresholds for the Line A AMP facilities are
provisioned correctly.
45 If the OTS parameter Autoroute is enabled, open the Facilities -> Adjacency
screen and select the TX Adjacency for the channel added to the system. Edit
the Ingress Active Flag in the TX Adjacency to be TRUE.
If Autoroute is disabled, go to step 46.
46 Repeat step 45 for all channels manually added to the system.
47 Change the DOC settings in both directions to put the DOC facilities
in-service.
48 If a channel that has not yet been manually added to the system was
unintentionally set to “Not Optimal” in step 41, set the channel to “Inactive” by
selecting the channel in the DOC facility screen and clicking the Force Delete
button.
49 Click on the Reset TCA Baselines button in the DOC facility screen.
50 When the DOC facilities in both directions are in-service and the Ingress
Active Flag is updated, click on the Re-optimize button and wait until the
Channel Condition is “Optimal” before proceeding.
51 When the Channel Condition is “Optimal”, click on the Reset TCA Baselines
button in the DOC facility screen.
52 Change the DOC settings in each direction as indicated in the EDP/IDP.
53 Use DOC to add the remaining channels (see Procedure 7-1, “Adding
bidirectional optical channels”).
Step Action
54 Put the following facilities OOS based on link budget and/or to mask alarms:
• OSC-<shelf>-<slot>-<port> for the OSC facility facing the stretched span
If the span loss of the stretched span is greater than 37 dB, the OSC
facility must be put OOS in order for the Automatic Laser Shut Off feature
to function properly. All optical safety testing and accreditation is suspect
if the OSC is kept IS on stretched spans with span loss greater than 37
dB. Putting the OSC facility OOS means that the manual workaround will
have to be performed for recovery from fiber cut, and that Optical Line Fail
alarms will be raised against both sides of the stretched span, regardless
of whether a fiber is cut in one or both directions along the stretched
span.
If the span loss of the stretched span is 37 dB or less, the OSC facility can
be kept IS. The signal degrade threshold must be set to 1E-4 for the OSC
facility. Depending on the span loss of the stretched span, the signal
degrade alarm may still be present after increasing the signal degrade
threshold. In order to avoid a standing alarm on the system, the facility
can be put OOS. Putting the OSC facility OOS means that the manual
workaround will have to be performed for recovery from fiber cut, and that
Optical Line Fail alarms will be raised against both sides of the stretched
span, regardless of whether a fiber is cut in one or both directions along
the stretched span.
—end—
Table 8-1
Procedures in this chapter
Procedure
Supporting procedures
Procedure 8-1
Testing signal continuity and protection switching in
a basic network configuration
Use this procedure to test the signal continuity and protection switching in a
basic network configuration.
Prerequisites
Before you perform this procedure, you must ensure that:
• the system is set up according to the required configuration
• you have:
— all the documentation referenced in this procedure
— fiber-optic patch cords
— antistatic wrist strap or ankle strap
— fiber cleaning materials
— calibrated optical test equipment as required
— if you plan to use hardware loopbacks, you have personnel at both the
near-end and the far-end network elements
CAUTION
Risk of personal injury
When inserted in a shelf slot, the optical interface circuit pack
emits laser light that can blind. Keep all optical connectors on
the optical interface circuit packs capped when they are not
connected to optical fiber cables. Never look directly into the
end of an optical fiber.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Step Action
Step Action
5 Provision the protection scheme for the selected optical facilities for all
network elements in the configuration. For more information, see the
procedure on changing the protection scheme for a pair of optical facilities in
Part 2 of Configuration - Provisioning and Operating, 323-1851-310.
If your configuration is Then make sure the protection scheme is
1+1/MSP linear, SDH-J linear 1+1/MSP linear
1+1, or 1+1 OTN line-side
1+1 TPT 1+1 TPT
BLSR/MS-SPRing/HERS 2F or 4F BLSR/MS-SPRing
UPSR/SNCP unprotected or UPSR/SNCP
unprotected unprotected
7 Provision 2WAY nodal connections. For more information, see the chapter on
nodal cross-connect management in Part 1 of Configuration - Bandwidth and
Data Services, 323-1851-320. Go to step 12.
8 Provision 2WAYPR nodal connections for the end network elements. For
more information, see the chapter on nodal cross-connect management in
Part 1 of Configuration - Bandwidth and Data Services, 323-1851-320. Go to
step 11.
9 Provision a 2-Fiber or 4-Fiber BLSR/MS-SPRing/HERS configuration. For
more information, see the procedure on adding a BLSR/MS-SPRing/HERS
ring map in Part 1 of Configuration - Bandwidth and Data Services,
323-1851-320.
10 Provision 2WAY nodal connections for the end network elements.
Testing the signal continuity in the system
11 Provision 2WAY connections for all pass-through network elements.
Step Action
12 Complete the test setup for all configurations except for 1+1 TPT:
• At the near-end network element, connect the test set to the optical
interface circuit pack you selected for the test (the near-end connection
endpoint).
• At the far-end network element, add a terminal loopback at the optical
interface you selected for the test (the far-end connection endpoint). If
you are using a software terminal loopback, see the procedure on
operating/releasing a loopback on a port in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310.
See examples of applicable configurations:
• 1+1/MSP linear, SDH-J linear 1+1, or 1+1 OTN line-side in Figure 8-1 on
page 8-9
• 2-Fiber BLSR/MS-SPRing in Figure 8-2 on page 8-10
• 4-Fiber BLSR/MS-SPRing/HERS in Figure 8-3 on page 8-11
• UPSR/SNCP in Figure 8-4 on page 8-12
13 Complete the test setup for 1+1 TPT:
• At the near-end network element, connect the test set to the TPT tray (the
near-end connection endpoint).
• At the far-end network element, connect another test set to the TPT tray
(the far-end connection endpoint).
14 Ensure the test set is switched on.
15 Operate the single-bit inject error three times. The receiver display of the test
set must show three bit errors.
16 Reset the transmission test set. The receiver display must indicate zero
errors.
17 Verify that the working optical interface circuit pack indicates working transmit
and receive activity. For more information, see the procedure on retrieving
equipment and facility details in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
18 Set the test set to introduce an error free signal.
19 Read the error count on the test set. The working path passes the signal
continuity test if the signal is back, error free.
Step Action
If there is indication that continuity is not established, make sure that the
facilities you are using are in-service. If there are active alarms that affect the
continuity of the provisioned test connections, identify and apply alarm
clearing procedures according to the following in Part 1 and Part 2 of Fault
Management - Alarm Clearing, 323-1851-543:
• the procedure on retrieving active alarms for a network element
• the chapters on detailed alarm clearing procedures and generic alarm
clearing procedures
20 Select your next step.
If your configuration is Then go to
1+1/MSP linear, 1+1 TPT, SDH-J linear 1+1, 1+1 step 21
OTN line-side, BLSR/MS-SPRing/HERS, or
UPSR/SNCP
unprotected step 28
22 On the Site Manager Protection Status window, verify that the x optical
interface or the protection facility indicates working transmit and receive
activity.
23 Clear the error count on the test set.
24 Set the test set to introduce an error free signal.
Step Action
25 Read the error count on the test set. The configuration passes the protection
switching test if the signal is back, error free.
26 Perform step 12 to step 19 to test the signal continuity on the protection path.
27 Release the terminal loopback at the far-end network element, if applicable.
28 Return the near-end, far-end, and pass-through network elements to their
initial states. See Procedure 6-18, “Restoring a network element to its initial
state”.
29 Review the test results. If any of the tests failed, solve the problem.
If there is indication that the protection switching is not working (where
applicable), apply trouble clearing procedures. For more information, see the
chapters on detailed alarm clearing procedures and generic alarm clearing
procedures in Part 1 of Fault Management - Alarm Clearing, 323-1851-543.
—end—
Figure 8-1
Example of testing the signal continuity and line protection in a bidirectional 1+1/MSP linear,
SDH-J linear 1+1, or 1+1 OTN line-side protection configuration
Figure 8-2
Example of testing the signal continuity and line protection in a 2-fiber BLSR/MS-SPRing
configuration
x w
Pass-through
network element 2
w x
Hardware
Pass-through Far-end terminal
network element 1 network element loopback
x w
Near-end
network element
w x
Tx Rx
Test set
Legend
= Optical interface circuit pack
= Signal
Figure 8-3
Example of testing the signal continuity and line protection in a 4-fiber BLSR/MS-SPRing/HERS
configuration
Figure 8-4
Example of testing the signal continuity and line protection in a UPSR/SNCP configuration
x w
w x
Pass-through Pass-through
network element 1 network element 2
x w
Near-end
network element Switch mate
w x
Tx Rx Tributary facility
Test set
Legend
= Signal
= Path selector
Procedure 8-2
Testing a Resilient Packet Ring
This procedure tests the Resilient Packet Ring (RPR) functionality and layer 2
protection switching. This procedure requires personnel at the site of each
circuit pack in the RPR.
If you have two or more RPRs inside the same SONET/SDH ring, you must
test each RPR separately. If you are setting up stacked rings, also test the
second RPR on the circuit pack.
Prerequisites
• Ensure that the SONET/SDH ring or unprotected ports configuration is
commissioned and operational. See Procedure 8-1, “Testing signal
continuity and protection switching in a basic network configuration”.
• Have available Gigabit Ethernet (GE) test sets that can interface to the
circuit packs in the RPR.
• Have available the appropriate cables that can interface to the LAN ports
of the circuit packs in the RPR.
Step Action
1 Verify that the RPR circuit packs are active by checking their LEDs. For more
information, see the section on alarm and trouble clearing strategy in Part 1
of Fault Management - Alarm Clearing, 323-1851-543.
2 Make sure that all LAN LOS LEDs on the faceplate of the RPR circuit packs
are lit.
The SFPs of the RPR circuit packs have to be inserted for the LAN LOS LEDs
on the faceplate to be lit.
3 Launch the Site Manager application and log in to the network elements in
the RPR. For more information, see the section on procedures and options
for logging in and logging out in Administration and Security, 323-1851-301.
4 Select your next step.
If the RPR to be tested Then go to
does not exist step 5
exist but the configuration information is not available step 6
exist and the configuration information is available step 15
Step Action
Attention: For the BLSR OCn ports you have to select the ENUT option.
Step Action
Attention: The ring name must be exactly the same (case sensitive) for all
the stations on the ring. If there is any difference in the ring name, the ring will
not operate properly. The station name must be different for all the stations on
the ring.
Step Action
Step Action
32 Set up source and destination MAC addresses on the GE test sets to create
unicast flows for all GE ports.
Confirming that RPR is up
33 Start the test set at the transmit end. After about 15 minutes, stop the
transmission on the test set.
34 On the test set at the receive end, verify that the receive frame (byte) count
matches the transmit frame (byte) byte count.
Testing layer 2 switching
35 Clear the operational measurements counters for ETH and WAN facilities on
the RPR circuit packs. For details, see the procedure on clearing operational
measurements in Fault Management - Performance Monitoring,
323-1851-520.
36 From Site Manager, operate a layer 2 manual protection switch on one of the
RPR spans (Use the Protection Status application and select the required
WAN facility. For details, see the procedure on operating a protection switch
in Part 2 of Configuration - Provisioning and Operating, 323-1851-310). For
example, in Figure 8-5 on page 8-18, the span with OC-n/STM-n circuit
pack x.
Alarms associated with the manual switch are raised.
37 Check that traffic is carried error-free.
38 Release the manual protection switch you operated in step 36. For details,
see the procedure on releasing a protection switch in Part 2 of Configuration
- Provisioning and Operating, 323-1851-310
39 Check that traffic is carried error-free and that the alarms raised by the
manual switch have cleared (for example, protection switch active alarms. For
details, see the alarm clearing procedures in Fault Management - Alarm
Clearing, 323-1851-543).
40 If required, repeat step 36 to step 39 for any other span in the RPR ring.
41 Verify the operational measurements for ETH and WAN facilities on the RPR
circuit packs. See the procedure on retrieving operational measurements in
Fault Management - Performance Monitoring, 323-1851-520.
Ending the test
42 Remove the test sets.
43 If you created the RPR configuration and layer 2 services for testing purposes
only, delete the associated provisioning.
—end—
Figure 8-5
Example of RPR testing
Procedure 8-3
Testing L2SS or PDH Gateway
This procedure tests the L2SS, or PDH Gateway functionality and layer 2
protection switching. This procedure requires personnel at the site of each
L2SS VT1.5/LO 4xGE, 20G L2SS, or PDH Gateway circuit pack in the 6500
point-to-point configuration.
Prerequisites
• Ensure that the SONET/SDH ring or unprotected ports configuration is
commissioned and operational. See Procedure 8-1, “Testing signal
continuity and protection switching in a basic network configuration”.
• Have available Gigabit Ethernet (GE) test sets that can interface to the
L2SS, 20G L2SS, or PDH Gateway circuit packs.
• Have available the appropriate cables that can interface to the LAN ports
of the L2SS, 20G L2SS, or PDH Gateway circuit packs.
Step Action
1 Verify that the L2SS VT1.5/LO 4xGE or 20G L2SS, or PDH Gateway circuit
packs are active by checking their LEDs. For more information, see the
section on alarm and trouble clearing strategy in Part 1 of Fault Management
- Alarm Clearing, 323-1851-543.
2 Make sure that all LAN LOS LEDs on the faceplate of the L2SS, 20G L2SS
or PDH Gateway circuit packs are lit.
The LAN LOS LEDs on the faceplate will be lit only when the SFPs/XFPs of
the L2SS, 20G L2SS, or PDH Gateway circuit packs are inserted and the ETH
facility is provisioned.
3 Launch the Site Manager application and log in to the network element. For
more information, see the section on procedures and options for logging in
and logging out in Administration and Security, 323-1851-301.
4 Select your next step.
If the L2SS, 20G L2SS, or PDH Gateway to be tested Then go to
does not exist step 5
exist but the configuration information is not available step 6
exist and the configuration information is available step 14
Step Action
Step Action
13 You need to create one cross connection from the OCN port in the odd slot to
WAN 101.
L2SS, 20G L2SS, or PDH Gateway Virtual Circuit Provisioning
14 From the Configuration menu, select Data Services then Segment
Management. In the VC Segment ID click on the Add button.
15 Select desired Classes of Service and click OK.
16 Highlight the virtual circuit segments in the VC Segment ID part of the window
and in the Virtual Circuit Endpoint part of the window click on Add button.
17 Provision virtual circuit endpoints.
18 From the Configuration menu, select Data Services then Endpoint
Management. In the Virtual Circuits list, select the LAN L2SS endpoint
added in the previous step. In the Virtual Circuit Endpoint Mappings part of
the window, click on the Add button.
The “Add Virtual Circuit Endpoint Map” window will appear.
19 Create the desired endpoint mapping.
20 Provision the endpoint maps “All untagged frames” and “All unprovisioned
tagged frames” if you want all VLAN IDs to go through the virtual circuit.
Configuring and connecting the test sets
21 Connect Gigabit Ethernet (GE) test sets to each LAN port where the virtual
circuit is provisioned.
22 Check that LOS LEDs on the L2SS circuit packs are off.
23 Configure the test sets:
• speed = 1000 Mbit/s
• duplex mode = full
• packet size = <any value between 64 and 1522 bytes for ETH-UNI or
1600 for ETH-NNI (or up to 9100 for ETH-UNI or 9216 for ETH-NNI, if the
maximum transfer unit [MTU] of the LAN port on the L2SS circuit pack is
also changed)>
• utilization = <value that matches the selected bandwidth>. Set up the test
signal so that it does not exceed the bandwidth profile values (ETH-UNI
facilities) or class of service scheduler values (ETH-NNI and WAN-NNI
facilities).
• autonegotiation = <same value as ETH facility autonegotiation value on
L2SS ports>. For example, if you are using the default value for the ETH
facility (default is ENABLE), you must set autonegotiation on the test set
to ENABLE also.
Step Action
• Make sure that the VLAN ID on the test set matches the value you
provisioned on the L2SS circuit packs for the endpoint map VLAN ID
(ETH-UNI facilities), or for the interface label at NNI (ETH-NNI facilities).
• If you are using ETH-NNI facilities, make sure that the priority of traffic set
on the test set matches the value you provisioned on the L2SS circuit
packs in step 5 for the Receive Class of Service Profiles.
24 Set up source and destination MAC addresses on the GE test sets to create
unicast flows for all GE ports.
Confirming that L2SS, 20G L2SS, or PDH Gateway is up
25 Start the test set at the transmit end. After about 15 minutes, stop the
transmission on the test set.
26 On the test set at the receive end, verify that the receive frame (byte) count
matches the transmit frame (byte) byte count.
Ending the test
27 Remove the test sets.
28 If you created the L2SS and layer 2 services for testing purposes only, delete
the associated provisioning.
—end—
Figure 8-6
Example of L2SS to L2SS WAN interconnection testing
Tx Rx
Figure 8-7
Example of L2SS to EPL WAN interconnection testing
Tx Rx
GE Test Set LAN L2SS WAN WAN EPL LAN GE Test Set
Table 9-1
Procedures in this chapter
Procedure
Procedure 9-1
Validating connections with TTI or TR control
Use this procedure to perform trail trace identifier (TTI) validation and TR
control validation of the connections. See Figure 9-1 on page 9-6, Figure 9-2
on page 9-7, and Figure 9-3 on page 9-8 for examples of TTI validation with
different regen configurations. TR control is only applicable to NGM OTM2
ports (port 1 on WT circuit packs).
Prerequisites
Before you perform this procedure, you must:
• make sure the system is set up according to the required configuration
• use an account with a UPC level of 3 or higher
• be logged in to all the network elements using Site Manager
• make sure that circuit packs are already provisioned, ODU3 connection is
provisioned between 40G OCI/40G MUX and 40G OCLD, and ODU4
connection is provisioned between
10x10GE MUX/10x10G MUX/100GE OCI and 100G OCLD
Step Action
Step Action
Step Action
Figure 9-1
Example of TTI validation for transparent regen configurations
NE 1 NE 4
Client NE 2 (regen) NE 3 (regen) Client
Tx Tx
40G Rx Tx Rx Tx Rx Tx 40G
Rx Rx
or or
Tx Tx
BP
BP
BP
BP
4x10G OCLD OCLD OCLD OCLD OCLD OCLD 4x10G
Rx Rx
MUX MUX
• Tx Rx Tx Rx Tx Rx •
OCI OCI
• •
AMP AMP AMP
line line OCLD line line client client line line
NE 1 NE 2 (regen) NE 3 (regen) NE 4
Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx
10GOTSC 10G 10G 10G 10G 10GOTSC
OTNWT OTNWT OTNWT OTNWT
Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx
AMP AMP AMP
line line client client line line client client line line
Figure 9-2
Example of TTI validation for MOTR configurations
NE 1 NE 2 (regen) NE 3 (regen) NE 4
Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx
10GWT
10GWT
MOTR
MOTR
10G 10G 10G 10G
OTNWT OTNWT OTNWT OTNWT
RxTx RxTx Rx Tx Rx Tx Rx Tx Rx Tx RxTx RxTx
client line AMP line client client line AMP line client client line line client
AMP
Figure 9-3
Example of TTI validation for non-transparent regen configurations
NE 1 NE 2 (regen) NE 3 (regen) NE 4
Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx
10G 10G 10G 10G 10G 10G
ELWT ELWT ELWT ELWT ELWT ELWT
Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx
AMP AMP line client client line AMP line client
client line line client client line
Procedure 9-2
Performing system acceptance testing
Use this procedure to perform the system acceptance testing. The purpose of
system acceptance testing is to validate that the line bit error rate (BER)
before forward error correction (FEC) is within the specified performance
margin for the system.
The performance margin is defined using the high correction count second
reference (HCCSREF). HCCSREF is user provisionable in units of dBQ.
The value used for the HCCS count for a 15-minute bin TCA corresponds to
dBQ value equivalent to the pre-FEC (raw) BER at which the customer desires
an early warning indication to highlight degradation in the individual channel.
Refer to Fault Management - Performance Monitoring, 323-1851-520, for
HCCS values for a given dBQ reference for RS8, SCFEC or PFEC.
Note: RS8 FEC algorithm is also known as ITU-T G.709 RS-8. SCFEC
FEC algorithm is also known as ITU-T G.975 I.4. UFEC FEC algorithm is
also known as ITU-T G.975 I.7.
This procedure applies only to 10G eDCO, 10G OTR, 2x10G OTR, 10GOTSC,
SuperMUX, AM1/AM2, 40G OCLD and 100G OCLD circuit packs.
Figure 9-4 on page 9-15 and Figure 9-5 on page 9-16 show examples of the
system acceptance testing boundary and testing points for different
configurations. Validation of client to line side continuity on the circuit packs is
performed in the factory. Therefore, the client side test equipment is optional.
LOFEF description
The Laser Off Far End Fail parameter is used to indicate if the client Tx should
turn off the laser versus conditioning the appropriate signal when a critical
traffic fault is detected on the line port (LOS, LOF, ODU-AIS, etc.). This fault is
usually caused by the equipment downstream thus the term far end failure is
used in the descriptive text. When LOFEF is triggered, the “Laser Off Far End
Failure Triggered” alarm is raised, which indicates that the laser is shutoff.
LOFEF Usage
LOFEF should be set to enabled under the following circumstances:
• For 10G rates, when using the Enhanced Trunk Switch (ETS)
configuration, LOFEF is used to turn off the client Tx laser so that the ETS
can switch traffic away from the fault.
• Interfacing with legacy routing equipment that cannot decode the 802.3 LF
signal.
• Interfacing with equipment where the customer prefers to have the laser
shutoff versus signal conditioning.
• At regen sites (with back to back 10G LAN PHY WT circuit packs) when
LOFEF is required to be enabled at the terminal sites. If the regen site is
not set to enabled, the terminal sites will see LF for faults at the regen and
the client Tx will not turn the laser off.
• At regen sites (with back to back 10G OTR cards used for OTU2e line rate)
when OTSC is used in a 1+1 configuration at the terminal sites. If the
regen site is not set to enabled in this case, the terminal sites will see LF
and a protection switch will not take place.
When you validate the back-to-back patch cord connections for regen
configurations, if test sets are not connected to the client optics (test sets are
optional), you must make sure that the laser off far end failure (LOFEF) feature
on the client facility is disabled. When LOFEF is disabled, link failure (LF) or
alarm indication signal (AIS) can be inserted at the client to provide a valid
frame for checking the client facility PM counts.
If test sets are connected to the client optics, you can check the back-to-back
connections (with PM tools) regardless of the LOFEF setting.
Prerequisites
Before you perform this procedure, you must:
• have completed Procedure 9-1, “Validating connections with TTI or TR
control”
• use an account with a UPC level of 3 or higher
• be logged in to all the network elements using Site Manager
Step Action
Step Action
16 Click OK.
17 Click Refresh. Make sure that there are no HCCS-OTU/OTU-HCCS counts.
FEC-OTU/OTU-FEC counts are expected.
18 Repeat step 11 to step 17 for all 6500 nodes.
19 Select your next step.
If Then go to
regen sites exist which are formed by client ports step 20
connected back-to-back and no test sets are connected to
the client optics at the terminal sites
otherwise step 37
Disabling LOFEF for all circuit packs in regen configurations (no test sets present)
20 Select Equipment & Facility Provisioning from the Configuration menu.
21 Select the required client port from the equipment list.
22 Click Edit in the Facility area to open the Edit facility dialog.
23 Select Disabled from the Laser off far end fail drop-down list.
24 Repeat step 20 to step 23 for all 6500 nodes in regen configurations.
Clearing client facility PM counts for regen configurations
Note: step 25 to step 33 only apply to circuit packs that have client ports
connected back-to-back to form regen configurations.
25 Select Performance Monitoring -> New from the Performance menu.
26 Select the facility type from the Type drop-down list:
• ETH10G for LAN PHY WT circuit packs
• OC192/STM64 for SONET/SDH WT circuit packs
30 Click OK.
31 Click Refresh.
32 Make sure that the untimed column is 0 for all monitor types (ignore the
OPR-OCH/OCH-OPR, OPRN-OCH/OCH-OPRN, and
INFRAMES-E/E-INFRAMES monitor types).
33 Repeat step 25 to step 32 for all connected client facilities at all regen sites.
Step Action
Step Action
Checking client facility PM counts for all back-to-back circuit packs at regen sites
39 Click the PM tab.
40 Select the facility type from the Type drop-down list:
• ETH10G for LAN PHY WT circuit packs
• OC192/STM64 for SONET/SDH WT circuit packs
41 Select the facility type from the Facility drop-down list:
• ETH10G-<shelf>-<slot>-<port>
• OC192/STM64-<shelf>-<slot>-<port>
42 Click Refresh.
43 Make sure that the untimed column is 0 for all monitor types (ignore the
OPR-OCH/OCH-OPR, OPRN-OCH/OCH-OPRN, and
INFRAMES-E/E-INFRAMES monitor types).
44 Repeat step 39 to step 43 for all connected client facilities on all circuit packs
at all regen sites.
Cleaning up and final system provisioning
45 If you want to use LOFEF for all regen circuit packs at regen sites, enable
LOFEF you disabled in step 20 (only applicable to circuit packs that have
client ports connected back-to-back to form the regen configuration).
46 Provision HCCSREF back to default value for all 6500 nodes, using the
Facility PM Attributes application.
47 Verify that there are no unexpected alarms on the system.
48 Perform final customer specific provisioning required for the system. For
provisioning procedures, refer to Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
49 Perform a system data backup using the Backup and Restore application. For
detailed backup procedures, refer to Administration and Security,
323-1851-301.
—end—
Figure 9-4
Example of system acceptance testing boundary and testing points for transparent regen
configurations
check
OTU-HCCS
NE 1 NE 4
Client NE 2 (regen) NE 3 (regen) Client
Tx 40G Tx 40G
Rx or Rx Tx Rx Tx Rx Tx Rx or
Tx 100G Tx 100G
BP
BP
BP
BP
OCLD OCLD OCLD OCLD OCLD OCLD
Rx MUX Rx MUX
• or Tx Rx Tx Rx Tx Rx • or
• OCI • OCI
AMP AMP AMP
line line line line line line
ODU3/ODU4
NE 1 NE 2 (regen) NE 3 (regen) NE 4
Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx
10GOTSC
10GOTSC
ODU2
System acceptance testing boundary
Figure 9-5
Example of system acceptance testing boundary and testing points for non-transparent regen
configurations
NE 1 NE 2 (regen) NE 3 (regen) NE 4
Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx
10G 10G 10G 10G 10G 10G
ELWT ELWT ELWT ELWT ELWT ELWT
Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx
AMP AMP AMP
client line line client client line line client client line line client
ODU2
This section contains safety guidelines that you must follow for personal safety
and to operate the equipment correctly.
Audience
Personnel working directly on equipment must be
• trained, authorized, and qualified to carry out the tasks required
• able to follow safety guidelines specific to the product and all local
customer-specific safety procedures
Precautionary messages
To prevent personal injury, equipment damage, and service interruptions,
follow all precautionary messages in Ciena documentation and all local safety
standards required by your company.
DANGER
Risk of personal injury
A precautionary message with this symbol indicates a risk of
personal injury.
DANGER
Risk of electrical shock
A precautionary message with this symbol indicates a risk of
personal injury caused by an electrical hazard.
CAUTION
Risk of laser radiation exposure
A precautionary message with this symbol indicates a risk of
personal injury caused by exposure to a laser beam.
WARNING
Risk of burn
A precautionary message with this symbol indicates a risk of
personal injury caused by a hot surface.
CAUTION
Risk of interruption to service
A precautionary message with this symbol indicates a risk of
service interruption or equipment damage.
CAUTION
Risk of damage to circuit packs
A precautionary message with this symbol indicates a risk of
static damage to circuit packs. Use antistatic protection.
WARNING
Hazardous moving parts
Keep fingers and other body parts away.
WARNING
Parties mobiles dangereuses
Tenir les doigts et les autres parties du corps éloignés.
CAUTION
Risk of electric shock
Disconnect all power sources before servicing to avoid shock
hazard.
CAUTION
Risque de choc électrique
Débranchez toutes les sources d'alimentation avant l'entretien
afin d'éviter tout risque de choc.
Safety standards
Ciena network elements conform to all relevant safety standards. The 6500
complies with the following safety standards:
• IEC 60950-1:2005+A1:2009+A2:2013—Information technology
equipment - Safety, Part 1: General requirements
• IEC 60825-1:2014 and IEC 60825-2:2004+A1:2006+A2:2010—Safety of
Laser Products
• FDA 21 CFR 1040—Performance Standards for Light-Emitting Products.
This product complies with FDA performance standards for laser products
except for deviations pursuant to laser notice No.50, date June 24, 2007.
Grounding standards
Ciena network elements support grounding connections to the following
electrical standards:
• ITU-T K.27, Bonding Configurations and Earthing Inside a
Telecommunication Building
• GR-295-CORE, Telcordia Technologies System Documentation, Mesh
and Isolated Bonding Networks: Definition and Application to Telephone
Central Offices
• Telcordia Technologies GR-1089-CORE Issue 6, Electromagnetic
Compatibility (EMC) and Electrical Safety
• ETSI ETS 300 253, Environmental Engineering (EE); Earthing and
bonding configuration inside telecommunications centres
• RUS Telecom Engineering and Construction Manual, section 810
• NFPA70, (US National Electrical Code)
• CSA 22.1, (Canadian Electrical Code)
International standards
The IEC 60825 series of international standards cover the safety of laser and
LED products. The following list provides examples from the International
Electrotechnical Commission (IEC), Code of Federal Register (CFR), and
European Norm (EN) series of standards:
• IEC 60825-1 Safety of Laser Products—Part 1: Equipment Classification,
Requirements and User’s Guide (Part 1 of a series of publications under
the general title of: Safety of Laser Products). This standard provides
information about equipment classification and on limit values for the
safety of laser products. In Europe, the EN 60825 series of standards for
CE marking purposes evaluate the safety of laser and LED products. The
EN 60825 series is technically equivalent to IEC 60825.
• IEC 60825-2, Safety of Laser Products—Part 2: Safety of Optical Fibre
Communication Systems. This standard provides information about the
safety of optical fiber communication systems.
• Regional standards such as the EN 60825 series: for example, British
Standard BS EN 60825-1, Safety of Laser Products, Equipment
Classification, Requirements and User’s Guide. These standards are
Although the FDA classifications (I, IIIb, IV) are similar to IEC classification
(1, 3B, 4), the classifications are not equivalent. Ciena ensures that all its
products are compliant with either or both FDA and IEC requirements, as
required.
When used and operated as per the procedures described herein, the
maximum radiation level encountered does not exceed the accessible
emission limit (AEL) for Class 1 (IEC) or Class I (FDA). The worst case hazard
level that may be encountered (as defined by IEC 60825-2) is Hazard Level
1M, and defined by ANSI Z136.2 as a Service Group 1. Because the system
is intended to be installed in a restricted access location, no additional
engineering design features are required to prevent exposure to the laser
radiation.
CAUTION
Risk of injury
For a FIM Type 4 module and to respect the 1M laser safety
limit on the aggregate MPO output, the individual input powers
to the LC ports must be <=13 dBm.
The following statement (English and French versions shown) refers to all
6500 cards and components bearing an IEC 60825-2 Hazard Level 1M label.
For further details on optical power and wavelength for each instance, refer to
Table 10-1 on page 10-14 and Table 10-2 on page 10-20.
Labeling
The 6500 system and circuit packs have been labeled in accordance with
IEC 60825-1, IEC 60825-2, and FDA Laser Notice 50 (Dated June 24, 2007).
For laser hazard labels found on the 6500 system, refer to the following
illustrations.
• “(1) Laser hazard level 1 label” on page 10-8—applies to equipment as
specified in:
— “Additional information for optical pluggable modules (see Note 1 and
Note 2)” on page 10-14
— “Additional information for circuit packs and lasers on fixed ports of
circuit packs” on page 10-20
• “(2) Laser hazard level 1M label” on page 10-8—applies to equipment as
specified in “Additional information for circuit packs and lasers on fixed
ports of circuit packs” on page 10-20
• “(3) Laser hazard level 1M label” on page 10-9—applies to equipment as
specified in “Additional information for circuit packs and lasers on fixed
ports of circuit packs” on page 10-20
• “(4) Laser hazard level 1M label” on page 10-9—applies to equipment as
specified in “Additional information for circuit packs and lasers on fixed
ports of circuit packs” on page 10-20
• “(5) Laser hazard level 1M label” on page 10-9—applies to equipment as
specified in “Additional information for circuit packs and lasers on fixed
ports of circuit packs” on page 10-20
• “(6) Laser hazard level 1M label” on page 10-9—applies to equipment as
specified in “Additional information for circuit packs and lasers on fixed
ports of circuit packs” on page 10-20
• “(7) Laser hazard level 1M label” on page 10-10—applies to equipment as
specified in “Additional information for circuit packs and lasers on fixed
ports of circuit packs” on page 10-20
• “(8) Laser hazard level 1M label” on page 10-10—applies to equipment as
specified in “Additional information for circuit packs and lasers on fixed
ports of circuit packs” on page 10-20
• “(9) Laser hazard level 1M label” on page 10-10—applies to equipment as
specified in “Additional information for circuit packs and lasers on fixed
ports of circuit packs” on page 10-20
• “(10) Laser hazard level 1M label” on page 10-10—applies to equipment
as specified in “Additional information for circuit packs and lasers on fixed
ports of circuit packs” on page 10-20
• “(11) Laser hazard level 1M label” on page 10-11—applies to equipment
as specified in “Additional information for circuit packs and lasers on fixed
ports of circuit packs” on page 10-20
Figure 10-1
(1) Laser hazard level 1 label
Figure 10-2
(2) Laser hazard level 1M label
Figure 10-3
(3) Laser hazard level 1M label
Figure 10-4
(4) Laser hazard level 1M label
Figure 10-5
(5) Laser hazard level 1M label
Figure 10-6
(6) Laser hazard level 1M label
Figure 10-7
(7) Laser hazard level 1M label
Figure 10-8
(8) Laser hazard level 1M label
Figure 10-9
(9) Laser hazard level 1M label
Figure 10-10
(10) Laser hazard level 1M label
Figure 10-11
(11) Laser hazard level 1M label
Figure 10-12
(12) Laser hazard level 1M label
Figure 10-13
(13) Laser hazard level 1M label
Figure 10-14
(14) Laser hazard level 1M label
Figure 10-15
(15) Laser hazard level 1M label
Figure 10-16
(16) Laser hazard level 1M label
Figure 10-17
(17) Laser hazard level 1M label
Figure 10-18
(18) Laser hazard level 1M label
The 6500 circuit packs use lasers that may exceed the AEL for Class 1, and
therefore require wavelength and optical power information at the aperture.
Additionally, the information in the following list is provided in this section for
every optical circuit pack and optical pluggable transceiver—refer to specific
information in Table 10-1 on page 10-14 and Table 10-2 on page 10-20:
• wavelength, shown as a nominal value or dense wavelength division
multiplexing (DWDM) range of values, such as in the following examples:
— 1310 nm nominal indicates a single wavelength in the range of
1260 nm to 1380 nm
— 1550 nm nominal indicates a single wavelength in the range 1525 nm
to 1625 nm
— 1510 nm to1625 nm indicates a range of multiple discrete DWDM
wavelengths
— 1471- 1611 nm indicates a range of multiple discrete CWDM
wavelengths
ATTENTION
The Transmit Output Power (max and min), Receiver Sensitivity, and
Receiver Overload data in the Optical Specifications table for each pluggable
(SFP, SFP+, QSFP+, XFP, or CFP) are performance specifications for the
device. Alarm and warning thresholds may differ based on monitor accuracy
of the specific pluggable device.
The standards for the equipment listed in Table 10-1 on page 10-14 and Table
10-2 on page 10-20 are as follows:
• IEC 60825-1:2014
• FDA 21CFR 1040.10
• IEC 60825-2:2004/A1:2006/A2:2010
Table 10-1
Additional information for optical pluggable modules (see Note 1 and Note 2)
160-9013-900 850 nm < 0.75 mW (-1.25 dBm) 1/Figure 10-1 on page 10-8 (see Note 3)
160-9111-900 850 nm < 0.5 mW (-3 dBm) 1/Figure 10-1 on page 10-8
160-9112-900 850 nm < 0.5 mW (-3 dBm) 1/Figure 10-1 on page 10-8
160-9116-900 850 nm < 0.5 mW (-3 dBm) 1/Figure 10-1 on page 10-8
Table 10-1
Additional information for optical pluggable modules (see Note 1 and Note 2) (continued)
160-9400-900 850 nm < 2.31mW (3.6 dBm) 1/Figure 10-1 on page 10-8
160-9403-900 1310 nm < 14 dBm (25 mW) 1/Figure 10-1 on page 10-8
160-9503-900 850 nm < 2.31 mW (3.6 dBm) 1/Figure 10-1 on page 10-8
160-9506-900 1290 nm to < 100 mW (20 dBm) 1/Figure 10-1 on page 10-8
1330 nm
NTK580<xy> 1528.77 nm - <= 2.63 mW (4.2 dBm) 1/Figure 10-1 on page 10-8
1564.68 nm
Table 10-1
Additional information for optical pluggable modules (see Note 1 and Note 2) (continued)
NTK586xxE5 1528.77 - <= 2.6 mW (4.2 dBm) 1/Figure 10-1 on page 10-8
1605.74 nm
NTK587AAE5- 1528.77 - <= 7.1 mW (8.5 dBm) 1/Figure 10-1 on page 10-8
NTK587DUE5 1564.68 nm
NTK588xxE5 1530.33 nm - <= 5.4 mW (7.3 dBm) 1/Figure 10-1 on page 10-8
1564.68 nm
NTK590NH
NTK590PH
NTK590QH
NTK590RH
NTK590SH
NTK590TH
Table 10-1
Additional information for optical pluggable modules (see Note 1 and Note 2) (continued)
NTK592NGE5 1511 nm <= 0.399 mW (-4 dBm) 1/Figure 10-1 on page 10-8
NTK596xH 1471 nm - <= 6.9 mW (8.4 dBm) 1/Figure 10-1 on page 10-8
1611 nm
NTTA01BJE6 1310 nm <= 2.8 mW (4.5 dBm) 1/Figure 10-1 on page 10-8 (see Note 3)
NTTA01FJE6 1310 nm <= 2.8 mW (4.5 dBm) 1/Figure 10-1 on page 10-8 (see Note 3)
NTTA03AA 850 nm < 6.72 mW (8.27 dBm) 1/Figure 10-1 on page 10-8 (see Note 3)
NTTA03BJE6 1310 nm <= 10 mW (10 dBm) 1/Figure 10-1 on page 10-8 (see Note 3)
(see Note 5)
NTTA11AA 850 nm <= 2.35 mW (3.7 dBm) 1/Figure 10-1 on page 10-8 (see Note 3)
NTTA11BAE6 1310 nm <= 10 mW (10 dBm) 1/Figure 10-1 on page 10-8 (see Note 3)
NTTA12BAE6 1310 nm <= 10 mW (10 dBm) 1/Figure 10-1 on page 10-8 (see Note 3)
NTTA13EEE6 1550 nm 7.19 mW (8.6 dBm) 1/Figure 10-1 on page 10-8 (see Note 3)
NTTP01AF 850 nm <= 0.5 mW (-3 dBm) 1/Figure 10-1 on page 10-8
NTTP01CF 1310 nm <= 0.5 mW (-3 dBm) 1/Figure 10-1 on page 10-8
NTTP02AD 1310 nm <= 0.5 mW (-3 dBm) 1/Figure 10-1 on page 10-8
Table 10-1
Additional information for optical pluggable modules (see Note 1 and Note 2) (continued)
NTTP04CDE6 1310 nm <= 5.9 mW (7.7 dBm) 1/Figure 10-1 on page 10-8
NTTP04CF 1310 nm <= 0.16 mW (-8 dBm) 1/Figure 10-1 on page 10-8
NTTP06CF 1310 nm <= 0.5 mW (-3 dBm) 1/Figure 10-1 on page 10-8
NTTP06CD 1310 nm <= 0.5 mW (-3 dBm) 1/Figure 10-1 on page 10-8
NTTP11AF 850 nm <= 0.56 mW (-2.5 dBm) 1/Figure 10-1 on page 10-8
Table 10-1
Additional information for optical pluggable modules (see Note 1 and Note 2) (continued)
NTTP80BA 1310 nm <= 2.3 mW (3.6 dBm) 1/Figure 10-1 on page 10-8
NTTP81AA 850 nm < 0.5 mW (-3 dBm) 1/Figure 10-1 on page 10-8
NTTP81BA 1310 nm <= 3.8 mW (5.8 dBm) 1/Figure 10-1 on page 10-8
NTTP83BA 1310 nm <= 2.3 mW (3.6 dBm) 1/Figure 10-1 on page 10-8
Table 10-1
Additional information for optical pluggable modules (see Note 1 and Note 2) (continued)
Note 1: The Transmit Output Power (max and min), Receiver Sensitivity, and Receiver Overload data
in the Optical Specifications table for each pluggable (SFP, SFP+,SFP28, QSFP+, XFP, or CFP) are
performance specifications for the device. Alarm and warning thresholds may differ based on monitor
accuracy of the specific pluggable device.
Note 2: For a complete list of circuit packs that support each pluggable module, refer to the section on
supported pluggable modules in each circuit pack, in Part 3 of Planning, NTRN10EG.
Note 3: The hazard level label may or may not appear on the related circuit pack. For these optical
pluggables, the reference to Figure 10-1 on page 10-8 is provided for information only.
Note 4: The LR-2 spec for Telcordia GR-253-CORE indicates a C-Band wavelength range of 1530 nm
to 1565 nm. The LR2 XFP ordered will have a wavelength operating anywhere within this range.
Note 5: For a 4x25G, 100G, CFP, 1310 nm nominal indicates 4 discrete wavelengths at nominal
wavelengths of 1295.56 nm (1294.53 to 1296.59 nm), 1300.05 nm (1299.02 to 1301.09 nm), 1304.58
nm (1303.54 to 1305.63 nm) and 1309.14 nm (1308.09 to 1310.19 nm).
Note 6: For a 10x10G, 100G, CFP, 1550 nm nominal indicates 10 discrete wavelengths at nominal
wavelengths of 1523 nm (1521 to 1525 nm), 1531 nm (1529 to 1533 nm), 1539 nm (1537 to 1541 nm),
1547 nm (1545 to 1549 nm), 1555 nm (1553 to 1557 nm), 1563 nm (1561 to 1565 nm), 1571 nm (1569
to 1573 nm), 1579 nm (1577 to 1581 nm), 1587 nm (1585 to 1589 nm), 1595 nm (1593 to 1597 nm).
Table 10-2
Additional information for circuit packs and lasers on fixed ports of circuit packs
NTK504BA 1516.9 nm <= 10 mW 1M/ Figure 10-2 on page 10-8 (see Note 2)
(10 dBm)
Table 10-2
Additional information for circuit packs and lasers on fixed ports of circuit packs (continued)
NTK508ACE5
NTK508ADE5
NTK508AEE5
NTK508AFE5
NTK508AGE5
NTK508AHE5
NTK508AJE5
NTK526JAE5 1527 nm - <= 64.5 mW 1M/Figure 10-4 on page 10-9 (see Note 3)
(see Note 3) 1566 nm (18.1 dBm)
Table 10-2
Additional information for circuit packs and lasers on fixed ports of circuit packs (continued)
NTK527JAE5 1527 nm - <= 64.5 mW 1M/Figure 10-4 on page 10-9 (See Note 3)
(see Note 3) 1566 nm (18.1 dBm)
NTK530BA
NTK530BB
NTK530AC
NTK530BC
NTK530MA
NTK530NA
NTK530NCE5
Table 10-2
Additional information for circuit packs and lasers on fixed ports of circuit packs (continued)
Table 10-2
Additional information for circuit packs and lasers on fixed ports of circuit packs (continued)
Table 10-2
Additional information for circuit packs and lasers on fixed ports of circuit packs (continued)
Table 10-2
Additional information for circuit packs and lasers on fixed ports of circuit packs (continued)
Table 10-2
Additional information for circuit packs and lasers on fixed ports of circuit packs (continued)
Note 1: The laser hazard threat, as indicated by the aperture label on the faceplate of the SuperMux
circuit pack, is inappropriately rated too high. The actual laser hazard threat is (IEC) Hazard Level 1.
Use the information provided in this table to take appropriate action for laser safety in your application/
location as for any circuit pack that is labeled Hazard Level 1.
Note 2: The current IEC 60825-2 label artwork for the NTK504BA overstates the threat actually posed
by a disconnection or break at the output. The optical power emitted at the output of the NTK504BA,
when used in conjunction with the NTK592NR DWDM OSC Transceiver, will not exceed the level
indicated in this table.
Note 3: OC-192/STM-64 1 Port G.709 DWDM circuit packs NTK526JA/NTK526JAE5 Release 04 and
earlier, NTK527JA/NTK527JAE5 Release 06 and earlier incorrectly indicate the laser hazard level on
the faceplate as (IEC 60825-2) Hazard Level 1. Subsequently released circuit packs are correctly
labeled to reflect the actual hazard level as (IEC 60825-2) Hazard Level 1M (indicating the power and
wavelength ranges as appropriate). For any questions related to product safety for the 6500, contact
your Ciena representative.
Note 4: The maximum output power level on these amplifier cards is the power level after engagement
of laser safety mechanisms (see the section on optical power safety mechanisms in 6500 Photonic
Layer Guide, NTRN15DA). These levels are not the maximum operational levels achievable for each
amplifier. For this information, see the technical specifications in Part 3 of Planning, NTRN10EG.
Note: Only the shelf processor software can disable APR at Mux sites.
Users cannot disable APR. When APR is disabled, clamping is added
automatically to ensure safety.
The amplifiers used in this application are required to have a Hazard Level 1M
warning label as illustrated in Figure 10-17 on page 10-12. Consequently, the
latest circuit pack release will be labeled for use in Class 1M applications.
The circuit packs and hardware releases in Table 10-3 were originally
manufactured with a Hazard Level 1 warning label as illustrated in Figure 10-1
on page 10-8 and can be re-labeled with the Level 1M label kit (Figure 10-19
on page 10-29) as described in Procedure 10-1, “Applying a 1M Hazard Level
Caution label on NTK552AAE5, NTK552BAE5, NTK552FAE5, NTK552FB,
and NTK552GAE5 circuit packs”.
Table 10-3
List of circuit packs within the scope of “Applying a 1M Hazard Level Caution
label on NTK552AAE5, NTK552BAE5, NTK552FAE5, NTK552FB, and
NTK552GAE5 circuit packs”
The new (higher) hazard level is consistent with certain existing amplifier
circuit packs and OCLD circuit packs (for example, WL3 circuit packs), so
there is no effective change to the overall system-level laser safety risk for the
6500.
Figure 10-19
Laser Hazard Level 1M Caution label with self adhesive backing
(415-2818-001 rev B)
You are responsible for ensuring the following requirements are met:
• be aware of the optical powers at the inputs and outputs of the
subassemblies
• place the appropriate labels on subassemblies
• only qualified personnel, trained in optical safety, and who understand the
optical safety issues associated with the subassemblies, work on the
equipment
• Do not look into the opening of an optical fiber, or the opening of an optical
fiber connector, if the optical fiber is active or the unit has the power turned
on.
• Avoid direct exposure to optical fiber ends or optical connector ends where
you can access the laser signal directly.
• Clean your hands after you handle optical fibers. Small pieces of glass are
not always visible and can damage your eyes.
DANGER
Risk of eye injury
If you have a piece of a glass in your eye, get medical
assistance immediately.
• Do not handle pieces of optical fiber with your fingers. Use tweezers or
adhesive tape to lift and discard any loose optical fiber ends.
• Wear rubber gloves when you clean optical connectors. The gloves
prevent direct contact with the isopropyl alcohol and prevent
contamination of the ferrules with skin oils.
• Place all optical fiber clippings in a plastic container provided for that
purpose.
• Handle optical fibers with caution. Place the optical fibers in a safe location
during installation.
• Protect all optical fiber connectors with clean dust caps at all times.
Use optical terminators on unused input faceplate connectors of installed
WSS circuit packs. If dust caps are used instead of optical terminators,
PMs can be reported against the port and the port may appear in-service.
• Follow the manufacturer instructions when you use an optical test set.
Incorrect calibration or control settings can create hazardous levels of
radiation.
• Power down all laser sources to the optical fiber or disconnect the remote
optical fiber end from the laser sources. The laser sources can be in a
central office, on subscriber premises, or in a remote location.
• If you remove a cooling fan module from a 6500 shelf to inspect or replace
it, you must replace it within 30 to 60 seconds depending on the shelf type.
Make sure that you have a replacement cooling fan module ready before
removing the cooling fan module.
CAUTION
Risk of personal injury
The fan blades on cooling fan modules rotate at high speed
while operating. If you are removing an active fan module from
a shelf, partially remove it then wait a few seconds for the fan
blades to stop rotating before handling it. Do not hold or carry
a fan module in a manner that could cause detrimental contact
to the fan blades or any backflow louvers.
All 6500 shelves are cooled by forced air pulled through the system by one or
more cooling fan modules. The circuit packs and modules in the system
depend on a constant flow of air in order to operate efficiently and reliably. The
following guidelines apply:
• Do not allow a shelf equipped with active circuit packs to operate without
any working cooling fan modules for more than 30 seconds as some circuit
packs or modules may overheat and malfunction or fail.
• Do not block the air exhaust or operate the system in a fully enclosed
cabinet or room that will re-circulate exhaust air back into the system.
• Do not operate a shelf indefinitely with empty slots as it affects shelf
cooling. You must equip unused slots with appropriate filler cards or
panels.
Grounding requirements
Follow this precaution.
CAUTION
Risk of electrical shock and equipment damage
Grounding is mandatory to satisfy local electrical codes/
regulations for the safe use of the equipment.
Marked locations on the rack and/or shelf bearing the Protective Earthing
Conductor are appropriate locations for attaching grounding hardware (for
example, approved cables, lugs)—see Figure 10-20 on page 10-34.
Figure 10-20
Protective Earthing Conductor (IEC 60417-5019)
Bonding topologies
Bonding is a complementary feature to, but should not be confused with,
Protective Grounding and is intended to create equipotential nodes
throughout the office installation. Marked locations bearing the symbol
illustrated in Figure 10-20 identify sites that can be used to bond equipment
but are not intended for safety grounding. The Protective Earthing Conductor
can be connected using either of these topologies to satisfy the mandatory
(safety) grounding dependencies for the 6500.
Figure 10-21 on page 10-35 illustrates the key differences and relationships
among the bonding topologies.
Figure 10-21
Bonding topologies—CBN, IBN, MESH
Additionally, grounding the 6500 will ensure that all external surfaces
(including the ESD jack locations) are of sufficiently low impedance to
non-intrusively reduce static charge build-up that may occur when operating,
repairing or installing new equipment in the 6500. When correctly grounded,
the ESD jack locations work effectively in coordination with good ESD
A continuously lit green "Power OK" LED at the faceplate of an AC power input
card Type 2 (NTK505RA and NTK505SB) or a “Power OK–A”, “Power OK–B”
LED on the faceplate of a shelf with integrated AC power inputs (such as the
NTK505NAE5 variant of the 2-slot shelf) indicates that the AC power input
circuit is functioning correctly. If the green “Power OK” LED is lit, there is
voltage detected on the associated AC feeder.
If the green “Power OK” LED on a power input card or on the shelf faceplate
(for a shelf with integrated AC power inputs) is not lit, the possible causes can
include, but are not limited to:
• the AC power cord may be unplugged or damaged.
• the AC source breaker tripped or turned off or the fuse in the source panel
may be blown or missing.
• AC feeder low voltage or power failure
• damaged or non-functional power input card (or power input circuit in the
case of a shelf with an integrated AC power input)
WARNING
Risk of personal injury, energy hazard
The battery feeds are capable of supplying very high current
which, during an unintentional short, can cause burns. Read
and understand the power procedures you are performing.
Take necessary precautions and use the appropriate insulated
tools when working with power.
ATTENTION
NTK505CAE5 60A Power Input Card (breakered) and NTK505DAE5 60A
Power Input Card (breakerless) can only be equipped in specific 6500
shelves rated for 60A or greater. These power cards do not have agency
(CSA/UL) approval for use in the NTK503xA (except NTK503SA),
NTK503xB and NTK503xC 14-slot shelf assemblies. Therefore, these
combinations are not supported.
ATTENTION
The 60A Power Input Cards (NTK505CAE5/NTK505DAE5/NTK505EAE5),
2x50A Power Input Card (NTK505DS) and 3x60A Power Input Cards
(NTK605CAE5/NTK605EAE5/NTK605FA/NTK605FE), and 4x60A Power
Input Cards (NTK605GA/NTK605GE) use protective covers to prevent
access to powered terminals and are required when the equipment is
powered. Ensure the covers are securely in place before applying power and
remain in place at all times when powered.
When you install power feeds to the product input terminals or if you perform
routine power maintenance, make sure that you do the following:
• Read and understand the power procedures you are performing.
• Take the necessary precautions and use the appropriate insulated tools to
perform any tasks.
present and working and one yellow “Low Voltage” LED that is lit when one or
more feeds are not working (and at least one of three feeds has sufficient
voltage to illuminate the yellow LED).
If the green “Power OK” LED on a power input card or on the shelf faceplate
(for a shelf with integrated DC power inputs) is not lit, the possible causes can
include, but are not limited to:
• the power cable assembly or a feed/return wire is not correctly connected
to the power card or the power source
• the breaker is in the “off” or “tripped” position (applies to breakered power
input card types)
• the main fuse is blown or not equipped in the fuse cartridge (applies to
fused power input card types)
• a bus bar required to bridge power from a shared feed/return to multiple L-
/L+ input terminals is missing (applies to 3x60A/4x60A power input cards
being configured for power sharing)
• feeder low voltage or source power failure
• an over-current fail (power input card circuit breaker trip or fuse blown)
• the fuse in the source panel may be blown, defective or missing, the
source breaker tripped or turned off, or the main fuse (and optional alarm
indicator fuse if equipped) of a fused power input card is blown, defective
or missing
• a reverse polarity condition at the input terminals has caused a circuit
breaker trip or a fuse to blow
• damaged or non-functional power input card (or power input circuit in the
case of a shelf with an integrated DC power input)
Fused power input card NTK505EEE5 (for the 7-slot optical shelf
[NTK503PAE5] and 14-slot shelf variants) is rated and certified for a maximum
fuse of 40A. Fused power input card NTK505QE (for the 7-slot optical Type 2
shelf [NTK503KA]) is rated and certified for a maximum fuse of 50A. Fused
power input card NTK505EC (for the 6500-7 packet-optical shelf
[NTK503RA]) is rated and certified for a maximum of 50A. Fused power input
cards NTK505EAE5 (for the 14-slot converged and packet-optical shelves)
and NTK605DAE5 and NTK605FE (for the 32-slot packet-optical shelf) are
rated and certified for a maximum fuse of 60A.
20A, 40A, 50A, and 60A fuses are available (see Planning - Ordering
Information, 323-1851-151). Other fuse ratings may be supported in specific
applications. Contact your Ciena representative for Cooper Bussman type
TPS or Littelfuse type TLS part numbers. Use of a fuse rated for more than
the power card or shelf rating or use of a different brand of fuses can result in
equipment damage and voids all warranties.
The 2-slot optical Type 2 shelf (NTK503LA) when equipped with 24 Vdc
breakered power input cards (NTK505TR) is rated for a maximum of 17 A at
20 Vdc to 30 Vdc. The 24 Vdc power input card has a breaker rated for 25 A
so it may be connected directly to a 24 Vdc power source as long as the
supplied current rating does not exceed the lesser of the power cable rating or
the power input card breaker rating of 25 A.
The 2-slot shelf (NTK503MAE5 variant with integrated DC power and the
NTK503LA variant when equipped with NTK505TA breakerless input cards) is
rated for 10 A per feed and must be protected by an external fuse or breaker
panel such as a 4x10A BIP (NTK599BH) or 1U BIP/FIP (NTK599DA/
NTK599EA) equipped with 10 A breakers.
For the 7-slot optical Type 2 shelf (NTK503KA), DC power input cards are only
available in breakered and fused variants so use of the 4x10A, 4x20A, 4x40A
or 4x50A BIP (NTK599BH, NTK599BGE5, NTK599BA or NTK599BK) or the
1U BIP/FIP (NTK599DA/NTK599EA) equipped with 10 A, 20 A or 40 A circuit
breakers is optional.
CAUTION
Risk of equipment damage
Heel grounders or similar worn footwear attachments work
when the floor is designed to dissipate static electricity. If the
properties of the floor are unknown or in doubt, use a
wrist-strap and make sure it is connected to a piece of
electrostatic discharge (ESD) grounding equipment before
proceeding with any maintenance or installation activity.
When you wear an antistatic wrist-strap or a heel grounder, you must make
sure the grounding straps are in contact with a moist part of your skin.
Connect the grounding cord to the grounding plug on a grounded fixture of the
product you are working on, such as the shelf ESD jack or rack mounted ESD
jack. Grounded fixtures are accessible on most Ciena products. See the ESD
ground jacks shown in:
• “Example of ESD jack location—6500 2-slot shelf (NTK503NAE5)” on
page 10-42
• “Example of ESD jack location—6500 7-slot optical shelf (NTK503PAE5)”
on page 10-42
• “Example of ESD jack location—6500-7 packet-optical shelf (NTK503RA)”
on page 10-43
• “Example of ESD jack locations—6500 14-slot optical shelf” on page
10-43
• “Example of ESD jack locations—6500 14-slot packet-optical shelf
(NTK503SA)” on page 10-44
• “Example of ESD jack locations—6500 32-slot packet optical shelf
(NTK603AAE5)” on page 10-45
Figure 10-22
Example of ESD jack location—6500 2-slot shelf (NTK503NAE5)
Figure 10-23
Example of ESD jack location—6500 7-slot optical shelf (NTK503PAE5)
ESD
Ground
Figure 10-24
Example of ESD jack location—6500-7 packet-optical shelf (NTK503RA)
Figure 10-25
Example of ESD jack locations—6500 14-slot optical shelf
Figure 10-26
Example of ESD jack locations—6500 14-slot packet-optical shelf (NTK503SA)
Figure 10-27
Example of ESD jack locations—6500 32-slot packet optical shelf (NTK603AAE5)
If Ciena ships modules separately from the network element shelf, then these
circuit packs can come in shielded containers marked with the following
symbol:
ATTENTION ATTENTION
OBSERVER LES FOLLOW PRECAUTIONS
PRÉCAUTIONS. MANIPULER FOR HANDLING
LE MATERIEL SENSIBLE A ELECTROSTATIC SENSITIVE
L’ELECTROSTATIQUE EN DEVICES
SUIVANT LES MESURES DE
SECURITE
CAUTION
Risk of equipment damage
Do not touch any solder points, pins, connectors or
components including any integrated electrical cables or
optical fibers when handling a circuit pack or module. Contact
with surfaces other than handles, faceplates, latches/ejectors,
thumbscrews, card guides or module outer shells may result in
contamination that will increase the risk of early failure.
Touching pins, connectors, integrated cables or fibers may
degrade performance or cause permanent damage. When
handling a circuit pack or module, hold it only by the faceplate,
pull handle, card guide or outer shell as directed. During
unpacking or packing of a circuit pack, handle by the card
guide or outer edges only if absolutely necessary. Manipulate
latches, ejectors and thumbscrews only as described in the
applicable procedure.
• Inspect all pin connectors on each module for damage before use.
• Inspect each module for damage before you insert the component into the
shelf.
• Store un-installed modules separately in a shielded box.
• Do not stack modules on or against each other.
• Do not force modules into their packaging material.
• Do not store several modules in the same container.
• Allow each module to reach room temperature before you insert the
module into the shelf.
• Protect all optical connectors of the transmit (Tx) and receive (Rx) optical
modules with clean dust caps at all times.
Use optical terminators on unused input faceplate connectors of installed
WSS circuit packs. If dust caps are used instead of optical terminators,
PMs can be reported against the port and the port may appear in-service
• Store pluggable modules in their protective static-dissipative containers
(when not in use) to prevent damage to the exposed connector terminals.
Leave spare modules in the original shielded containers until you need the
modules. To prevent damage to modules in storage, follow procedures that
prevent:
• accumulation of dirt or dust on the pin connectors
• damage to the printed-circuit board or its components
• warpage (of printed-circuit boards stored in areas where the humidity can
exceed 95% and the temperature can exceed 70°C)
Table 10-4
Supported 6500 shelves, common equipment, and circuit packs that operate in an extended
temperature environment
Bracket kit Bracket and air baffle kit, 6500 2-slot Type 2, front or NTK509NEE6
rear exhaust 567 mm center-to-center mounting holes,
100/127 mm setback, EIA hole pitch
Shelf Shelf processor w/access panel (SPAP-2) w/2xOSC NTZF14xx (kit includes the
processor 2xSFP circuit pack NTK555NA circuit pack)
NTZF15xx (kit includes the
NTK555NB circuit pack)
Power input Power Input Card (breakerless) - 2-Wire D-Sub Input, NTK505TA
cards Max 10A
Table 10-5
Supported pluggable optics that operate in an extended temperature environment
Note: For support in an extended temperature environment, the pluggable must be used in a circuit
pack and shelf configuration that also supports operation in an extended temperature environment
(Table 10-4 on page 10-49). Dust caps that ship with the pluggables must be left in place until an optical
patch cord is connected.
Table 10-6
Supported power and electrical interface cables and optical fiber patch cords that operate in an
extended temperature environment
DC power Cable Assembly, Power, 8AWG, HiFlex, Right Routed 2W2, 2.5 m, NTTC01CHE6
cables Connectorized at one end only
Cable Assembly, Power, 8AWG, HiFlex Blue/Gray, Right Routed 2W2, NTTC01CKE6
2.5 m, Connectorized at one end only
Cable Assembly, Power, 12AWG, Black/Black, Right Routed, 2W2, 4.0 NTTC01EF
m, Connectorized at one end only
AC power AC Power Cord - North America, right-angle IEC 60320 C13 (F) to NT0H49ADE6
cables standard plug (NEMA 5-15); 10A/125VAC; 3 m (10 ft)
AC Power Cord - North America, right-angle IEC 60320 C13 (F) to twist- NT0H49ACE6
lock plug (NEMA L5-15P); 10A/125VAC; 3 m (10 ft)
AC Power Cord - European, right-angle IEC 60320 C13 (F) to 2-pin plug NT0H49AEE6
(CEE 7/7); 16A/250VAC; 3 m (10 ft)
AC Power Cord, right-angle IEC 60320 C13 to C14; 10A 125/250VAC; 441-0096-001
2.5 m (8.2 ft)
DCN and Cable Assembly, Cat 5E, RJ45, TIA568B, Crossover, Single (different NTTC09AxE6
craft access lengths) (Note)
cables
Cable Assembly, Cat 5E, RJ45, TIA568B, Straight, Single (different NTTC09BxE6
lengths) (Note)
Cable Assembly, STP Cat 5E, RJ45, TIA568B, Crossover, Single NTTC09CxE6
(different lengths) (Note)
Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single NTTC09Dx,
(different lengths) (Note) NTTC09DxE6
Table 10-6
Supported power and electrical interface cables and optical fiber patch cords that operate in an
extended temperature environment (continued)
Alarm and Alarm cable, DB9M angled to open, solid wire (30 m) NTTC08ATE6
telemetry
cables Environmental alarm cable kit (3 m) NT6Q59ABE6
(kit contains
two
NT6Q71ABE6
cables)
Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 3 m NTTC09DM
used for Alarm/Telemetry (Note)
Optical fiber Optical patchcord, FPC, LC-LC, 1.6D, 1F, SM, riser, bend insensitive, NTTC52xx
patch cords 42.5 MM LC boot end to ferrule tip, field removable trigger, anti-snag
(bend device (different lengths)
insensitive)
Console Cyclades RJ45 Female to EIA/TIA-561 Standard RJ45 Male Serial NTTC09EA
adapter Console Port Adapter Cable, 6 in
cables
EIA/TIA-561 Standard RJ45 Male to Cisco RJ45 Female Serial Console 170-0062-900
Port Adapter, 6 in
DB9 Female to EIA/TIA-561 Standard RJ45 Male Serial Console Port 170-0063-900
Adapter Cable, 6 ft
DB9 Male to EIA/TIA-561 Standard RJ45 Male Serial Console Port 170-0064-900
Adapter Cable, 6 in
Note: The NTTC09AxE6, NTTC09BxE6, NTTC09CxE6, andNTTC09Dx[E6] cables are not rated for
the entire extended temperature range defined by GR- 3108 OSP Class 2. These cables must only be
used in an extended temperature environment that is -20oC to +65oC.
Procedure 10-1
Applying a 1M Hazard Level Caution label on
NTK552AAE5, NTK552BAE5, NTK552FAE5,
NTK552FB, and NTK552GAE5 circuit packs
Use this procedure to apply a 1M Hazard Level Caution label on
NTK552AAE5, NTK552BAE5, NTK552FAE5, NTK552FB, and NTK552GAE5
circuit packs. To determine whether the 1M Hazard Level Caution label
applies to your equipment and application, see “Hazard level labeling on
NTK552AAE5, NTK552BAE5, NTK552FAE5, NTK552FB, and NTK552GAE5
circuit packs” on page 10-27.
Prerequisites
Before you start, ensure you have the following materials:
• the amplifier circuit pack(s) with Hazard Level 1 label. See “Hazard level
labeling on NTK552AAE5, NTK552BAE5, NTK552FAE5, NTK552FB, and
NTK552GAE5 circuit packs” on page 10-27 and Figure 10-1 on page 10-8
for an illustration of the Hazard Level 1 label.
• Laser Hazard Level 1M Caution label with self adhesive backing
(415-2818-001 rev B) for each Hazard Level 1 labeled circuit pack. New
labels must contain the following wording: “Hazard level 1M” and
“λ=1528-1567 nm; <100 mW”. See Figure 10-19 on page 10-29.
• an appropriate antistatic surface to work on. It is advisable to perform this
procedure outside of the shelf. The fibering/functioning of the in-service
circuit packs present in the shelf may be disturbed when performing this
procedure.
• an appropriate antistatic or grounding strap
• general purpose rubbing alcohol
• lint free tissue
• a pair of tweezers
The ideal application temperature range for the label adhesive is from 21°C to
38°C. Application is not recommended if the surface temperature is below
10°C.
Precautions
CAUTION
Risk of equipment damage
Electrostatic discharge (ESD) can damage electrostatic
sensitive devices. Use antistatic protection to avoid damaging
circuit packs.
CAUTION
Risk of damaging equipment
Extreme caution is required when manipulating the circuit
packs to avoid damaging the components on the circuit pack.
Make sure that you do not drop the circuit pack.
Step Action
Step Action
3 Confirm you have the correct circuit pack by looking at the name on the top
latch label (Figure 10-28). See Table 10-3 on page 10-28 for target circuit
pack names.
Figure 10-28
Confirming the circuit pack name
Step Action
4 Confirm the target circuit pack by the PEC printed on the barcode label on the
lower latch label (Figure 10-29). See Table 10-3 on page 10-28 for target
circuit pack PECs.
Figure 10-29
Confirming the circuit pack PEC
Step Action
5 Confirm you have the correct circuit pack by looking at the Hazard Level 1
label (Figure 10-30).
Figure 10-30
Confirming the existing label
Step Action
6 Gently clean any dirt or oil from the target surface (that is, the yellow portion)
with rubbing alcohol and a lint free tissue. See Figure 10-31. Avoid damaging
existing label material and its adhesive from over use of rubbing alcohol.
Figure 10-31
Cleaning the target surface
Step Action
7 Carefully remove the patch label from its backing liner. It is recommended to
use a pair of tweezers for ease of handling and to avoid touching the adhesive
surface. See Figure 10-32.
Figure 10-32
Removing the label from the backing liner
Step Action
8 Position the new label so that it covers the current laser label area. See Figure
10-33.
CAUTION
Risk of label misalignment
Do not apply pressure at this point.
Figure 10-33
Positioning the new label
Step Action
9 Apply pressure evenly to finalize the bonding process, taking care to avoid
any sliding motion (which could cause some misalignment). See Figure
10-34. Allow two to three days for the adhesive to cure completely.
Figure 10-34
Finalizing the label bonding
10 If the circuit pack was in-service and you performed this procedure outside of
the shelf, follow the instructions in the procedure on replacing an amplifier
module in Fault Management - Module Replacement, 323-1851-545, to install
the circuit pack back in the shelf.
If the circuit pack was not in-service and you performed this procedure
outside of the shelf, follow the instructions in the procedure on inserting or
removing circuit packs, in the Installation technical publication specific to your
shelf type to insert the circuit pack back in the shelf.
—end—
—end—
Attention: The configuration data examples are guidelines and are not to
be copied in a field system. Each company has a different class IP address
range assigned. It is a requirement to cross-check with the appropriate Ciena
customer engineering documentation package (EDP/IDP) and customer
IT/IS department before performing datacomms and NE provisioning.
Note: For other configuration types, use the Advanced SLAT Assistant Tool.
See “Node setup solutions” on page 2-3 and “Selecting the turning-up solution
for a newly installed system” on page 2-6.
For Node Setup procedure steps, see Procedure 2-4, “Quick-start turning-up
using the Node Setup application”.
Figure 11-1
Direct Connect configuration example (Standalone shelf)
DCN 1.x.x.x
Single
Sing
g shelf TIDs
Dedicated
Dedd DCN LAN drop per TID
DCN routable IP address per shelf
COLAN-X
1.2.2.2 NE1 RJ-45-Ethernet
Table 11-1
Direct Connect with basic Node Setup parameters—Standalone data example (NE1 in Figure
11-1)
The Date and Time are provisioned automatically to the date and time of
the user’s PC, converted to GMT.
Optional step for the Date and Time parameters: To change after Node Setup is
complete, use Site Manager->Node Information->Node Information tab.
(continued)
Table 11-1
Direct Connect with basic Node Setup parameters—Standalone data example (NE1 in Figure 11-1)
(continued)
(continued)
Table 11-1
Direct Connect with basic Node Setup parameters—Standalone data example (NE1 in Figure 11-1)
(continued)
Flowcharts of the quick-start turning-up of the shelves using the Node Setup
application are illustrated in:
• Figure 2-3 on page 2-8 — Primary with Members shelf
• Figure 2-4 on page 2-9 — Member shelf
For Node Setup procedure steps, see Procedure 2-4, “Quick-start turning-up
using the Node Setup application”.
Figure 11-2
Gateway Connect configuration example (Primary with Members shelf and Member shelves)
DCN 1.x.x.x
COLAN-X
GNE
Shelf 1 1.3.3.2
(Primary)
TID A GNE Proxy ARP GNE
1.3.3.4 Shelf 3
1.3.3.3 Shelf 2 (Member)
(Member) TID A
TID A
Table 11-2
Gateway Connect with basic Node Setup parameters—Member data example (Shelf 2 in Figure
11-2 on page 11-6)
The Date and Time are provisioned automatically to the date and time of the
user’s PC, converted to GMT.
Optional step for the Date and Time parameters: To change after Node Setup is
complete, use Site Manager->Node Information->Node Information tab.
(continued)
Table 11-2
Gateway Connect with basic Node Setup parameters—Member data example (Shelf 2 in Figure
11-2 on page 11-6) (continued)
(continued)
Table 11-2
Gateway Connect with basic Node Setup parameters—Member data example (Shelf 2 in Figure
11-2 on page 11-6) (continued)
Table 11-3
Gateway Connect with basic Node Setup parameters—Primary with Members data example
(Shelf 1 in Figure 11-2 on page 11-6)
The Date and Time are provisioned automatically to the date and time of the
user’s PC, converted to GMT.
Optional step for the Date and Time parameters: To change after Node Setup is
complete, use Site Manager->Node Information->Node Information tab.
(continued)
Table 11-3
Gateway Connect with basic Node Setup parameters—Primary with Members data example
(Shelf 1 in Figure 11-2 on page 11-6) (continued)
(continued)
Table 11-3
Gateway Connect with basic Node Setup parameters—Primary with Members data example
(Shelf 1 in Figure 11-2 on page 11-6) (continued)
Release 13.0
Publication: 323-1851-221
Document status: Standard
Issue 3
Document release date: June 2019
CONTACT CIENA
For additional information, office locations, and phone numbers, please visit the Ciena
web site at www.ciena.com